Releases: BuildOnViction/victionchain
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:
v2.2.5
Add eth_ChainID
v2.2.4
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:
If you lost the TomoX data by removing the container, you can download the data here
v2.2.2
This version is a mandatory update.
All the nodes (Masternodes, Fullnodes) have to update to this version before the hard-fork block number: 21430200 (Est. 2020-06-02 00:02 UTC).
The update includes:
v2.2.1
This version is a mandatory update.
Hot-fix transfer relayer function #262
This release contains all changes from the Excalibur release v2.2.0.
All the nodes (Masternodes, Fullnodes) have to update to this version before the hard-fork block number: 20581700 (Est. 2020-05-12 00:02 UTC).
v2.2.0 - Excalibur
Updated: we release a mandatory hot-fix v2.2.1
This version is a mandatory release.
From this version, TomoChain will support TomoX Protocol.
It means that the node that runs TomoChain V2.2+ can store orderbook (spot trading, p2p lending) and process order-matching.
TomoChain v2.2+ also added tomox and posv JSON-RPC APIs to allow the clients to interact with nodes using TomoX protocol.
All the nodes (Masternodes, Fullnodes) have to update to this version before the hard-fork. The hard-fork will happen at block number: 20581700 (Est. 2020-05-12 00:02 UTC).