Toccata Mainnet pre-activation pre-release
This pre-release is intended for community-wide mainnet sanity testing before the final Toccata rollout.
The main goal is to verify that pre-activation mainnet behavior remains fully compatible with the current master release across a wider range of real-world node histories, upgrade paths, pruning states, and operator setups.
This pre-release does not activate Toccata on mainnet. Operators who test it should expect one more upgrade when the final Toccata release is published.
Key notes
-
Node operators are encouraged to test this pre-release on mainnet, especially on nodes with different upgrade histories and pruning states.
-
Operators, pools, and miners are encouraged to test with a limited subset of infrastructure rather than fully migrating operations.
-
Miners may use this pre-release to sanity-test mining flows, but this does not replace testing on an activated testnet. Before activation, mainnet block templates only contain current transaction versions, so some Toccata-specific paths are only meaningfully exercised after activation.
-
RPC transaction submission now applies the upcoming higher minimum standard fee rule:
100 sompi * max(compute grams, 2 * transaction bytes). -
The
2 * transaction bytesterm reflects the post-Toccata normalized transient-mass component. -
This fee rule is a node policy / mempool rule, not a consensus rule. Consensus does not have a fee policy; zero-fee transactions are and remain consensus-valid.
-
In this pre-release, the higher minimum standard fee rule is applied at the RPC transaction-submission level. P2P relay remains under the current pre-activation behavior.
-
Wallets and other transaction-submitting software should verify that they do not rely on outdated fixed minimum-fee assumptions. Software should derive the required minimum fee from the node API where possible, or otherwise be updated to match the new minimum standard fee rule.
-
gRPC/protobuf integrators can update and test their integrations ahead of the final release to make sure existing APIs continue to behave as expected and to prepare for Toccata compatibility.
-
The node database upgrade is one-way. After upgrading a node database to this pre-release, it cannot be downgraded back to an earlier version. Operators who need to return to an earlier version can resync, but larger operators and pools should account for that operational cost.