The repository browser source pins the Robinhood Chain mainnet identity below. Source records leave readiness, independent review, and production privacy unapproved, and state that authenticated deployment evidence is unavailable; repository files do not establish current chain state or relayer availability.
Repository records bind a Robinhood Chain mainnet deployment identity and browser-use decision. They do not authenticate current chain state or service availability. Mainnet readiness, independent audit, external review, and production privacy claims remain unapproved.

​
Contracts

​
Proving artifacts

​
Evidence boundary

  • The deployment record contains RPC-observed receipts and state at its stated observation block; repository evidence provides no finality claim, no authenticated state proof, and no historical state pin.
  • Phase 2 used one local operator trust domain with zero independent contributors. Three agent contribution processes on one host/operator are not independent trust domains.
  • The pool fee is mutable. 33 bps is the deployment initial value, not authenticated current chain state; read feeBps() at a fresh, block-consistent state before proving or submitting.
  • Relayer approval in the source records is limited to the configured browser endpoint above; availability and current request policy require a live check.
  • Source records mark mainnet readiness and production privacy claims false.

​
Read it as one object

Chain ID, pool, verifiers, adapters, fee policy, selectors, and proving files belong to the same deployment. Copying one address into another runtime can make a proof or transaction target the wrong system. The generated record is source-bound to deployment evidence, the browser prover manifest, the setup record, and the frontend runtime. See Security status for current audit, formal verification, and privacy coverage.