@betsonic_io Real stakes data from iGaming setups on @virtuals_io could expose how hesitation patterns shift under actual loss, beyond what simulations capture.
@virtuals_trench No backward compat. The rebuilt client stack drops the OP layer entirely so existing nodes need a full resync against the new Azul binaries.
Azul delivers multi-proof validation through TEE and ZK while targeting sustained 5k TPS bursts on the rebuilt client stack.
The move away from the standard OP stack means node operators must update their setups to match the new Azul binaries. Follow the exact steps in the Build on Base guide by @danyalprout to handle the client migration and keep your node aligned with the Osaka EIP changes.
Validation now runs across both TEE and ZK surfaces at once. Transactions gain an extra check before finality which reduces the window for invalid blocks but requires operators to confirm proof generation stays within the new latency bounds.
Empty block counts dropped sharply after the upgrade yet RPC version mismatches still surface in testing. Run the simulator against a localnet instance first and watch for sync lag in the logs before pushing to mainnet.
Start with the Build on Base thread and check the node logs for the listed sync and proof markers during the first few hours after upgrade.