Runtime 140 (transaction version 134) and framenode 4.8.14.
- Guardian bridge halt. Governance-appointed guardians halt the bridge workers with one fee-free transaction. The HASHI offchain worker on every bridge node stops and stays stopped until devops restart that node with
--bridge-resume-after-halt <number>; no Root call is needed. The upgrade installs the first guardian,cnSECvLF9MwFojPXk94PVKS4N34WsgZDPNDYMjxcbJWWTPWkY. Halt page: https://emergency.sora.org - Operational calls that their signer can never make are rejected before inclusion.
- Each HASHI peer waits 120 seconds before signing an outgoing request.
- A batch of validator payouts pays the direct payout fee for each claim.
Runtime Wasm framenode-runtime-4.8.14.compact.compressed.wasm: 2,143,899 bytes, SHA-256 0d9c61bc3142318f595404cc7809128a11beaf80369660688d9b740d08517b7e. system.setCode proposal hash 0x43db4b428b9b3e9295e35ee9dd2a8eb494bfd84e694772e581b6777cfec4c4c0.
Tested on a fork of live mainnet at finalized block 28,296,247: the upgrade, its migrations and a guardian halt all passed. The package, unsigned governance calls and test record are in runtime-upgrade-4.8.14/.
Bridge (HASHI peer) nodes need this framenode build to restart their workers after a halt. Validators need no node change for the runtime upgrade.