Chain Compatibility
Robinhood Chain / Ethereum compatibility and Spawn verification standards.
Working target
The v2 direction is Robinhood Chain, with Ethereum-environment testing used as an independent EVM compatibility baseline.
Spawn targets Robinhood Chain, an EVM-compatible network using $ETH as its native gas asset. Network identifiers, RPC endpoints, explorer links, and deployment requirements must be verified against current official network documentation immediately before production deployment.
Evidence standard
Standard EVM compatibility means the primitives are plausible; it does not prove the Spawn combination is correct.
Every security-critical module should be deployed/tested with the same scenario suite on:
- an Ethereum test environment; and
- Robinhood Chain testnet.
Historical contract warning
The legacy source documents identify $SPAWN on Robinhood Chain as:
0x41080c9d7908CE567eFe239042c49D8159a2A3bb
Before any production vault or launch gate is bound to a contract, confirm the canonical contract identity, verified source or bytecode behavior, pair, fee behavior, and venue integration directly.
Historical documentation conflict
The active documentation, verified contract registry, and canonical whitepaper are the only sources for current chain, token, and deployment claims.