Chain Configuration

#Chain IDs

Contributor safety rules prohibit broadcasting Robinhood Chain mainnet transactions from this repository. Read-only chain validation does not grant permission to deploy.

#Canonical token configuration

These addresses are configured external token identities. Deployment validation must still check runtime code and token metadata. They are not WeedToken, vault, or farm addresses.

#Uniswap v3 configuration

#Validation rules

• Connected RPC chain ID must equal the configured ID.
• Configured external addresses must contain bytecode and expose expected interfaces.
• The position manager, router, and quoter must report the configured factory where applicable.
• Final token ordering, fee tier, tick spacing, ticks, price, and pool identity must agree.
• Missing or inconsistent data blocks the operation instead of selecting defaults.

These are release requirements, not a claim that one script proves all of them. The current TypeScript gate directly checks only the connected chain and governance-contract code described in Deployment Preparation; other address and relationship checks require separate read-only evidence.

#Testnet caution

Only the Robinhood Chain Testnet identity and public endpoints are configured. Token and Uniswap v3 addresses for chain 46630 remain unresolved. Testnet preparation must supply explicit addresses and verify their bytecode, metadata, and relationships before use.