πŸ”’Node Release Notes

Dev release nodes for mainnet node post-conversion

v1.8.0 - Aspen Hardfork PART TWO on Mainnet

Hardfork at block 8,572,000 on Mainnet

This completes the Aspen hardfork!

Docker image:

docker pull taraxa/taraxa-node:v1.8.0

Github:

https://github.com/Taraxa-project/taraxa-node/pull/2668

Release Highlights:

Token Economic Improvements

  • Aspen Hardfork, implements the community approved TIP-2 which caps the max Taraxa token supply to 12 billion going forward. The first part of the hardfork (v1.7.2 at block 8,118,000) created the necessary data retention to ensure light-nodes will be able to smoothly upgrade in the final hardfork.

v1.7.2 - Aspen Hardfork PART ONE on Mainnet

Hardfork at block 8,118,000 on Mainnet

Docker image:

docker pull taraxa/taraxa-node:v1.7.2

Github:

https://github.com/Taraxa-project/taraxa-node/pull/2713 (v1.7.2)

https://github.com/Taraxa-project/taraxa-node/pull/2675 (v.1.7.0)

NOTE: v.1.7.0 contains the Aspen Hardfork, but v1.7.2 contains a critical bug-fix for node inter-communication during the upgrade process.

Release Highlights:

Token Economic Improvements

  • Aspen Hardfork, when complete will implement the community approved TIP-2 which will cap the max Taraxa token supply to 12 billion going forward. Hardfork PART ONE creates the necessary data retention to ensure light-nodes will be able to smoothly upgrade in Aspen Hardfork PART TWO which will follow shortly after Aspen Hardfork part one.

  • Another significant improvement in Aspen Hardfork PART ONE is that block rewards for DAG block production will be tied more directly to stake by rewarding DAG blocks on their possessing low VDF difficulty level, which is solely determined by VRF sortition tied to stake. It will no longer be based also on unique transaction inclusion. Under the previous system nodes could game unique transaction inclusion, or were rewarded based on proximity to transaction creators, or by using significant CPU hardware to somewhat outpace the VDF calculations of others.

v1.5.1 - Magnolia Hardfork on Mainnet

Hardfork at block 5,730,000 on Mainnet

This hardfork will take effect at PBFT block height: 5,730,000.

Features:

  • Parallel Execution of State Pruning: Enhanced efficiency by enabling parallel execution during state pruning.

  • Improved Tracing API: Upgraded tracing API for better performance and usability.

  • State Root Verification on Syncing: Ensured data integrity through state root verification during syncing processes.

  • Transaction Pool Overflow Improvements: Addressed transaction pool overflow issues for improved stability.

  • Sync-Gossip Transition Improvement: Optimized the transition between syncing and gossip protocols.

  • LOG.old Files Cleanup on Database Start*: Initiated cleanup of old log files on database startup for a cleaner DB environment.

  • Syncing Optimizations: Implemented optimizations for a smoother syncing process.

  • Removal of Existing Transactions Check: Streamlined operations by removing checks for existing transactions.

  • Reduced Prune Memory Usage: Optimized memory usage during pruning processes.

  • Added RPC Methods for Faster Indexing: Introduced new RPC methods to expedite the indexing process.

  • Optimized Peer Cache Memory Usage: Improved memory utilization within the peer cache.

  • Improved Performance of Vote Weight Calculation: Enhanced efficiency in vote weight calculation.

  • Improved Ping Timeout Handling on Discovery: Optimized handling of ping timeouts during the discovery process.

  • Handled Batch Requests via WebSocket Interface: Enabled handling of batch requests through the WebSocket interface.

  • Improved Light Node History Deletion: Enhanced the process of history deletion in light nodes.

Fixes:

  • Corrected Reward Votes Initialization: Fixed the initialization process of reward votes for accurate tallying.

  • Usage of All Passed Gas on Reverts: Resolved an issue with unused gas on reverts.

  • Period Data Transactions Order: Corrected the ordering of period data transactions.

  • Resolved Ignorance of PBFT Size Check on Syncing: Fixed an issue where PBFT size check was being ignored during syncing.

  • Fixed Syncing of DAG Blocks: Addressed syncing issues of DAG blocks for improved data consistency.

Hard Fork (HF) Features:

  • Process Rewards in Batches Every N Blocks: Implemented batch processing of rewards every N blocks for efficiency.

  • Jailing of Validator on Double Voting: Introduced a penalty mechanism for validators engaged in double voting by jailing them.

Github:

v1.4.0

Hardfork at block 3091000 on Mainnet

Docker image:

docker pull taraxa/taraxa-node:v1.4.0

Github:

https://github.com/Taraxa-project/taraxa-node/pull/2548

Release Highlights:

DPOS Contract

  • Fixes a critical security vulnerability where a call to DPOS contract could cause a persisting error in the state readout for a validator.

  • Removes the depth limit on contract call enabling other contracts to interact with the DPOS contract

v1.3.2

Docker image:

docker pull taraxa/taraxa-node:v1.3.2

Github:

https://github.com/Taraxa-project/taraxa-node/pull/2539

Release Highlights:

RPC

  • Added batch RPC request support via websockets

v1.3.1

Docker image:

docker pull taraxa/taraxa-node:v1.3.1

Github:

https://github.com/Taraxa-project/taraxa-node/commit/24e6c310b3168dc93b5d4095556eb41544f13e8b

Release Highlights:

RPC

  • RPC changes to increase indexer performance

  • Update EVM submodule with added getTotalDelegation method to DPOS contract

Consensus

  • Disconnect nodes that send multiple PBFT votes (ie. equivocate) in same step in network layer

  • Properly rebroadcast blocks that local node has voted for

v1.3.0

Docker image:

docker pull taraxa/taraxa-node:v1.3.0-rc.10253

Github:

https://github.com/Taraxa-project/taraxa-node/compare/master...release/v1.3.0

Release Highlights:

Storage

Syncing

Consensus

EVM

RPC

Improved Tracing

Light Node

Last updated