AvalancheGo 1.15.1 flags stalled executors and fixes gas estimates
Victoria Shinder1 min readAva Labs published AvalancheGo v1.15.1 on 1 October. The release notes describe it as backwards compatible with v1.15.0 and optional but encouraged; the plugin version is unchanged at 46.
The headline change concerns SAE, the execution component the notes refer to throughout: VM.HealthCheck() now reports a stalled executor, which previously surfaced only through ERROR or FATAL log lines. For operators this means a node whose execution has stopped can now fail its health check, so monitoring catches it instead of somebody reading logs.
Several fixes target API nodes. SAE re-execution of C-Chain blocks from before the ApricotPhase5 upgrade that contain cross-chain transactions was failing, which broke historical state queries on some nodes; that is fixed. eth_estimateGas and eth_createAccessList now include the minimum gas limit the mempool requires for a transaction's size, after large transactions signed with the old estimate were rejected with insufficient gas limit for tx size. Snapshot generation is now cancelled promptly, where previously SAE block execution lagged on large hashdb archives, and new Firewood archival nodes now commit genesis state on all chains.
The release also adds two fields, restakedValidationRewards and restakedDelegateeRewards, to platform.getCurrentValidators results for auto-renewed validators, and a gauge for the amount of AVAX delegated to a node on the Primary Network. The minimum Go version rises from 1.25.10 to 1.26.8. One incompatibility is called out: Helicon is now active from genesis on local networks, so a local network started on an earlier version will not work with this one.
Why it matters
None of this changes consensus, which is why it is optional. The gas-estimate fix is the one users notice, since wallets relying on eth_estimateGas could sign large transactions the network then refused.