v2.4.4

Viction v2.4.4 is a hotfix release that resolve some issues on RPC:

• Remove contention on worker.currentMu for pending RPC requests. (#477)
• Disable verify header completely when calling debug APIs. (#479)
• Add BlockHash support for RPC method eth_getBlockReceipts. (#478)
• Add BlockHash support for RPC method eth_getLogs. (#480)

This update is intended for full node and archive node. Master node is not recommended to update at this time to verify that transition to go1.18 wouldn't cause problem with the consensus.

v2.4.3

Viction v2.4.3 is a hotfix release that resolve some issues on RPC:

• Fix mismatch BlockHash between block header and transaction logs. (#472)
• Fix invalid penalty list on checkpoint block error when tracing blocks under 3,000,000. (#476)
• Add new RPC method eth_getBlockReceipts. (#467)

This update is intended for full node and archive node. Master node is not recommended to update at this time to verify that transition to go1.18 wouldn't cause problem with the consensus.

v2.4.2

This update is intended for full node and archive node. Master node is not recommended to update at this time to verify that transition to go1.18 wouldn't cause problem with the consensus.

Viction v2.4.2 fixes some issues related to RPC and upgrade supported go lang version to go1.18.

• Fix nonce too low error when on some blocks when calling debug_traceBlockByNumber and debug_traceTransaction (#469)
• Fix required historical state unavailable and Get tomox state fail when calling debug api against block number less than 20,581,700 (#470)
• Fix compatibility issue when calling eth_estimateGas with modern tools and libraries: MetaMask, Remix IDE, ethers.js v6.x, web3.js, and others. (#471)

v2.4.1

Viction v2.4.1 enables the #VIP1 for Viction Mainnet at block #86158494, estimated for 29th of October 2024.

About #VIP1:

• Increase reward for master nodes at 250 VIC/epoch. This reward is halved every 4 years and lasts for 16 years.
• Initiate more funds for Viction Foundation to support Outlining Future Ecosystem Initiatives.
• Details on VIP#1 can be found at https://gov.viction.xyz/

v2.4.0

[Deprecated] Viction v2.4.0 enables the Sai Gon hard fork for Viction Mainnet at block #85619448, estimated for 15th of October 2024.
Please use Viction v2.4.1 instead.

About Sai Gon hard fork:

• Increase reward for master nodes at 250 VIC/epoch. This reward is halved every 4 years and lasts for 16 years.
• Initiate more funds for Viction Foundation to support Outlining Future Ecosystem Initiatives.
• Details on VIP#1 can be found at https://gov.viction.xyz

Other changes:

• Some minor tweaks to make the new Testnet run as close as Mainnet as possible.

v2.3.1

This is a OPTIONAL update.

News:

• Update the creation smart contract fee

v2.3.0

New:

• Flat cancellation fee
• Upgrade EVM
• TomoP Precompiler

This is a mandatory update. Masternodes & Fullnodes have to update this version before block 30915660 (est: 22 Jan 2021).

If you are running the node with the mode --tomox.dbengine "mongodb", you need to follow the issue #302 to remove the duplicated records

ChangeLogs:

• Upgrade TomoChain's EVM to support Solidity Compiler version <= v0.6.6 #295
• Flat TomoX's Cancellation Fee #310
• Add TomoP Precompiler functions #101

v2.2.5

Add eth_ChainID

v2.2.4

This version is an OPTIONAL update.

If the node forgot to update to v2.2.2+ before block number 21430200, it will meet the issue #282.

This version is a fix for the issue (#282)
And update default bootnodes params (8d903fc)

v2.2.3

This version is an OPTIONAL update.

Includes:

• Update default TomoX Datadir (#280)

NOTES: This update will help who are running the node in Docker container. (includes using tmn CTM tools)

Issue:
With a node in Docker container, when they update the version for the node, the node get back to block number 20,580 million. It will take a long time to re-sync the tomox and chain data to the latest block.

Explanation:
TomoChain v2.2.1, v2.2.2 uses $HOME/.tomo (e.g /root/.tomo) as the default TomoX datadir.
It means that if you do not mount $HOME/.tomo as a Docker volume, $HOME/.tomo will be removed when you remove the container to update TomoChain to the new version.

From TomoChain v2.2.3, TomoChain will use $DATADIR/tomox as the default TomoX datadir as the top priority and $HOME/.tomo as the second priority.

So If you are NOT running the node in Docker Container, there is no issue with your node.

Solutions:
As the explanation above, If you are running the node in Docker container, you should follow the steps below to solve the issue.

• Backup $HOME/.tomo (directory in the container)
• Copy current TomoX data from $HOME/.tomo to $DATADIR/tomox
• Update your node to v2.2.3

Guide:
You need to follow the guide before updating the node:

• The guide for tmn tool
• The guide for CMT tool

If you lost the TomoX data by removing the container, you can download the data here