Repository navigation
Version 18 Changes
Version 18 replaces Version 17 on the same data directory: your chain, wallet and finalizer key carry over. It uses new networking and cannot talk to Version 17 nodes, so each node switches over completely when you restart it. There is a network upgrade in this release, FeaturenetUpgrade3, at block 189,000, after Version 17's end of support at 188,376. Every node and wallet must run Version 18 before then.
Before you upgrade
- Back up your node now: stop it, copy its data directory, and start it again.
- In your config, delete any
disable_zainoorelasticsearch_passwordline, or Version 18 won't start. - Stop Version 17 fully before starting Version 18, never run one finalizer key in two places, and never go back to Version 17 once you have run Version 18.
Networking
- Each node has one encrypted endpoint, key and port, shared by PoW sync, BFT and transaction relay. Version 17 nodes cannot connect to it.
- BFT runs over the node's own connections.
bft_peersis ignored, with a warning. - Transactions relay between nodes over the new networking.
- The legacy Zcash network is off by default.
network.legacy_network = trueturns it back on; it is unsupported. - Peer entries in
network_initial_peerswritten with the old1fgEw5Nxselector still work, with a warning to update them (#339, #386). network_connect_only = trueunder[state]dials only your initial peers.
BFT
- A node catching up fetches decided BFT blocks from its peers.
- A node that restarts waits to catch up on BFT before it votes.
- If following finality would need a reorganization deeper than 99 blocks, the node stops BFT, keeps running as proof of work, records why, and says so in its log. Restore a backup or resync to rejoin.
FeaturenetUpgrade3 (block 189,000)
- Each staking action on a bond names the bond's current version, so an action built against a stale bond is refused. Wallets must run Version 18.
- A small-order finalizer key can no longer be a stake target or authorize a reward conversion (#325).
Chain export and import
zebrad export-chain(or theexport_chain_prefixRPC) writes your chain and its BFT decisions to a file, andzebrad import-chainrebuilds a node from one, with--keep-identityto keep its wallet and finalizer key (#241). A node stuck on the wrong chain can rebuild from another node's export instead of resyncing.
Config renames
hardforksis nowslashforksanddisable_shipped_hardforksis nowdisable_shipped_slashforksunder[crosslink]. The old names still work, with a warning.
End of support
Version 18 warns from block 188,376 and stops at 212,568, about November 30.