Addresses

Verified addresses per network with the source release each contract was built from (testnet-12 is the review-repository tag of the deployment 12 sources). The token launch is the only mainnet deployment; the protocol contracts are on testnet.

Robinhood Chain (Mainnet)

Proxies are ERC-1967; the implementation address is readable from storage slot 0x360894a13ba1a3210667c828492db98dca3e2076cc3735a920a3ca505d382bbc or from the latest Upgraded event. Governance contracts are immutable except for parameters changed through proposals; see Governance.

Robinhood Chain (Testnet)

Chain id 46630, deployment 12 (weekly issuance calendar since 14 Oct 2026, daily before that: RollPolicy opens one new series per underlying a week from a per-underlying template, five trading days of subscription, strike one trading day after the close, the next series opening on the closing day of the current one (maxOpenSeries 1); NoteAutomation roll and fill jobs), deploy block 120437317, all contracts verified.

Legs on other chains (LayerZero, see Legs on other chains):

Credit (COUPON collateral on Morpho, see Credit):

The first market of deployment 12 (a LegWrap and a LegOracle per series, created through the factory) opens once a series of this deployment has struck; the Credit page lists markets from the factory’s events. On mainnet the live Morpho deployment on Robinhood Chain is used in place of the fixture; nothing from this layer is deployed there yet.

Vault layer (ERC-4626 over USDG, see Embed a vault):

All six are verified on the testnet explorer. Vault creation code hash pinned by the factory: 0x9841e48fbb9e441cbbf47568d347d4a5975f458cf297f3199d6a654b9f7c1151.

Protocol contracts (NoteCore, Treasury, sNOTE, governance) are on testnet only until the audit completes; the token launch is the only mainnet deployment.

Pyth Pro backup feeds (PythProFeed, verifier 0xACeA761c27A909d4D3895128EBe6370FDE2dF481, maxAge 60 s, maxConfidenceBps 100), registered as OracleAdapter backups and wired to the MarketCalendar through the governance, active 24 h after registration (MODULE_GRACE):

Testnet-only parameters: OracleAdapter close window 5 min / maxPreCloseLag 24 h / maxRoundWalk 500 / freshLag 6 h; Desk.minHold 24 h; NoteGovernor.QUORUM_FLOOR 50,000 veNOTE (a testnet fixture so governance can be exercised with test balances; the mainnet estimate remains 800,000); governance is 0 on testnet so parameter changes and fixes can be exercised without waiting, while the intended mainnet value is 172800 seconds (48 h). upgrade governance is 604800 (7 days) on testnet as it will be on mainnet, because UpgradeGovernor enforces that floor at construction.

External Dependencies

Verification

Before interacting, compare the deployed bytecode with forge build output at the listed source release, and check that NoteCore.oracle(), NoteCore.calendar(), NoteCore.feeSink() and NoteCore.legs() return the listed addresses, that SeriesRegistry.activeCore() returns the listed NoteCore, that Desk.gaugeController() returns the listed GaugeController, and that each proxy’s version() and governance return the published version string and the listed upgrade governance. upgrade governance should report getMinDelay() of 604800 seconds and governance the delay published for the deployment you are checking (0 on testnet, 172800 intended for mainnet), governance and upgrade governance should return them respectively, and neither governance should have any DEFAULT_ADMIN_ROLE holder.

Do not trust addresses from any source other than this page and the governance’s on-chain records.