Post-Helicon state sync is not supported immediately around activation; disabling state sync mid-partial-sync can FATAL (Firewood nodes must set state-sync-enabled=false or FATAL). Recovery is delete-DB + restart.
avalanchego v1.15.0 bumps plugin version to 46 — matched by this image already.
eth-apis → apis (unknown names are now fatal post-Helicon; dropped the removed/renamed namespaces admin, debug, internal-personal, internal-debug, debug-tracer, debug-file-tracer, debug-handler).
commit-interval: 4096 set (required on Mainnet post-Helicon).
warp-api-enabled/log-level removed (ignored post-Helicon; logging now via AVAGO_LOG_LEVEL).
PLUGIN_ID left untouched (official mainnet value, not the repo example).
Verification
./update.sh regenerated cleanly with this asset present (compose discarded, per procedure — only context.yml/this asset ship).
Rollout plan
kite.mainnet is not currently deployed on any fleet host (confirmed via fleet client-census + DRPC node status — no kite entries in either). This is a dormant-client bump: no canary/deploy step applies today. The bump lands in context.yml/this asset so that whenever kite.mainnet is next deployed, it comes up already on the Helicon-compatible v1.15.0 + migrated config — avoiding deploying the now-broken v1.0.0 pin from scratch.
Merge this PR first (or together with StakeSquid/vibe-node#5360 — the gitlink pin there depends on this branch existing on main).
Companion asset PR for StakeSquid/vibe-node#5360 (context.yml bump `kite`/`go` `v1.0.0`→`v1.15.0`).
### Why
Avalanche mainnet **Helicon** activated **2026-09-22T15:00:00Z** — already past-due (7 days as of today). Kite mainnet (`AVAGO_NETWORK_ID=mainnet`, `AVAGO_PARTIAL_SYNC_PRIMARY_NETWORK=true`) cannot follow post-Helicon mainnet on the `v1.0.0` pin. Release: https://github.com/gokite-ai/gokite-chain/releases/tag/v1.15.0 ("Helicon: Continuous Execution & Auto-Renewed Staking", published 2026-09-09).
### Breaking changes (Helicon / C-Chain)
- `admin`, `warp`, `personal` API namespaces removed; several `debug_*`/`eth_accounts`/`eth_coinbase`/`eth_etherbase` RPCs removed.
- `avax.getAtomicTxStatus` deprecated → `avax.getAtomicTx`.
- Named-block semantics change (`latest`/`pending`/`safe`/`finalized`).
- Post-Helicon state sync is not supported immediately around activation; disabling state sync mid-partial-sync can FATAL (Firewood nodes must set `state-sync-enabled=false` or FATAL). Recovery is delete-DB + restart.
- avalanchego v1.15.0 bumps plugin version to 46 — matched by this image already.
### Config migration — `rpc/kite/mainnet/pruned/config.json`
```diff
- {"database-type":"leveldb","state-sync-enabled":true,"pruning-enabled":true,"eth-apis":["eth","eth-filter","net","admin","web3","internal-account","internal-blockchain","internal-debug","internal-eth","internal-personal","internal-transaction","internal-tx-pool","debug","debug-tracer","debug-file-tracer","debug-handler"]}
+ {"database-type":"leveldb","state-sync-enabled":true,"pruning-enabled":true,"commit-interval":4096,"apis":["eth","eth-filter","net","web3","internal-account","internal-blockchain","internal-eth","internal-transaction","internal-tx-pool"]}
```
- `eth-apis` → `apis` (unknown names are now fatal post-Helicon; dropped the removed/renamed namespaces `admin`, `debug`, `internal-personal`, `internal-debug`, `debug-tracer`, `debug-file-tracer`, `debug-handler`).
- `commit-interval: 4096` set (required on Mainnet post-Helicon).
- `warp-api-enabled`/`log-level` removed (ignored post-Helicon; logging now via `AVAGO_LOG_LEVEL`).
- `PLUGIN_ID` left untouched (official mainnet value, not the repo example).
### Verification
`./update.sh` regenerated cleanly with this asset present (compose discarded, per procedure — only `context.yml`/this asset ship).
### Rollout plan
**`kite.mainnet` is not currently deployed on any fleet host** (confirmed via fleet client-census + DRPC node status — no `kite` entries in either). This is a **dormant-client bump**: no canary/deploy step applies today. The bump lands in `context.yml`/this asset so that whenever `kite.mainnet` is next deployed, it comes up already on the Helicon-compatible `v1.15.0` + migrated config — avoiding deploying the now-broken `v1.0.0` pin from scratch.
Merge this PR first (or together with StakeSquid/vibe-node#5360 — the gitlink pin there depends on this branch existing on `main`).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Companion asset PR for StakeSquid/vibe-node#5360 (context.yml bump
kite/gov1.0.0→v1.15.0).Why
Avalanche mainnet Helicon activated 2026-09-22T15:00:00Z — already past-due (7 days as of today). Kite mainnet (
AVAGO_NETWORK_ID=mainnet,AVAGO_PARTIAL_SYNC_PRIMARY_NETWORK=true) cannot follow post-Helicon mainnet on thev1.0.0pin. Release: https://github.com/gokite-ai/gokite-chain/releases/tag/v1.15.0 ("Helicon: Continuous Execution & Auto-Renewed Staking", published 2026-09-09).Breaking changes (Helicon / C-Chain)
admin,warp,personalAPI namespaces removed; severaldebug_*/eth_accounts/eth_coinbase/eth_etherbaseRPCs removed.avax.getAtomicTxStatusdeprecated →avax.getAtomicTx.latest/pending/safe/finalized).state-sync-enabled=falseor FATAL). Recovery is delete-DB + restart.Config migration —
rpc/kite/mainnet/pruned/config.jsoneth-apis→apis(unknown names are now fatal post-Helicon; dropped the removed/renamed namespacesadmin,debug,internal-personal,internal-debug,debug-tracer,debug-file-tracer,debug-handler).commit-interval: 4096set (required on Mainnet post-Helicon).warp-api-enabled/log-levelremoved (ignored post-Helicon; logging now viaAVAGO_LOG_LEVEL).PLUGIN_IDleft untouched (official mainnet value, not the repo example).Verification
./update.shregenerated cleanly with this asset present (compose discarded, per procedure — onlycontext.yml/this asset ship).Rollout plan
kite.mainnetis not currently deployed on any fleet host (confirmed via fleet client-census + DRPC node status — nokiteentries in either). This is a dormant-client bump: no canary/deploy step applies today. The bump lands incontext.yml/this asset so that wheneverkite.mainnetis next deployed, it comes up already on the Helicon-compatiblev1.15.0+ migrated config — avoiding deploying the now-brokenv1.0.0pin from scratch.Merge this PR first (or together with StakeSquid/vibe-node#5360 — the gitlink pin there depends on this branch existing on
main).🤖 Generated with Claude Code
merge-bot (del-018): classified B (hand-maintained rpc file(s), single scope). Auto-merge after a 72h objection window - comment 'hold' to block.