Solana
Robinhood ChainNetwork identity
Treat public RPCs as shared infrastructure. They may be rate limited. Confirm
the reported chain ID before asking the wallet to sign.
Available KEK.PRO evidence
Robinhood Chain testnet · chain ID 46630 · historical development manifest
The checked-in testnet manifest records deployment block 93747023, contract
addresses, runtime code hashes, ABI hashes, and source revision
1a41aa8d096a4dd6ac298835483850ece8dce02b.
That manifest proves only that a development deployment was recorded. It
predates later source hardening and does not prove that the current source or
current abi/v2 files are deployed.
Robinhood Chain mainnet · chain ID 4663 · network profile only
There is no checked-in KEK.PRO deployment manifest for mainnet. The repository
does contain pinned fork checks for Robinhood Chain’s V3 dependencies. Those
checks do not prove that KEK.PRO contracts are deployed.
Release identity
Treat these fields as one versioned unit:protocolVersion strings are not enough when ABI hashes differ.
Preflight every session
1
Resolve the chain
Require the wallet and every RPC to report the intended chain ID.
2
Select one release
Load an approved deployment manifest and its exact ABI manifest. Do not
combine addresses and ABIs from different revisions.
3
Verify code and links
Compare runtime hashes. Confirm the factory, locker, deployer, V3
dependencies, Permit2, and block provider.
4
Read live policy
Fetch launch and DEX configs, launch enablement, fee allocation,
recipients, compounding policy, and optional feature readiness.
5
Apply finality
Treat sequencer-confirmed activity as provisional until the selected
staged-finality policy promotes it.