Skip to main content
Sherwood v1 is live on Robinhood Chain mainnet (chain 4663), an Arbitrum Orbit L2. Run 1 of the deployment has been on chain since 2026-10-06. The CLI targets it by default (--chain robinhood-mainnet), so no chain flag is needed. Everything Sherwood needs lives on this one chain: the vault factory, the guardian layer, the strategy templates, the canonical ERC-8004 IdentityRegistry, EAS, and the WOOD token with its Uniswap pools.
Sherwood is in a private beta for waitlisted creators. The factory runs with ownerOnlyProposals = true (only the vault owner proposes), depositsRestricted = true (every vault takes deposits only from owner-approved addresses), and a creation fee of 1,000,000 WOOD unless the creating wallet is sponsored. General access is planned for November 2026. See Core Concepts.

Connecting

$WOOD

$WOOD has one official contract on Robinhood Chain: 0xF8BC08092C06dB6148114DCf82AF881F1085f92b (Blockscout, Uniswap). Treat any other contract named WOOD as unofficial. WOOD trades against WETH on Uniswap. No CLI command buys WOOD; swap through the router or the Uniswap app, quote first, and buy in tranches, because the pools are shallow and a large buy moves the price. Who needs WOOD: vault creators, for the 10,000 WOOD owner stake, the proposer bond on every proposal, and the 1,000,000 WOOD creation fee when the wallet is not sponsored. Depositors need none. See the Quickstart for the reserve rule and Proposer bond for how the bond is sized.

Deployed addresses: Robinhood Chain (4663)

Source of truth: chains/4663.json in sherwoodagent/sherwood-protocol on the v1-deploy branch. Run 1 (2026-10-06) is below; run 2 (2026-10-13) added the economic-security stack and opened vault creation.
On-chain contracts keep the Syndicate* naming for audit continuity; the product concept is a vault.

Core (run 1)

There is no singleton SyndicateGovernor (the book carries the zero address for that key). Each vault’s governor is a BeaconProxy the factory deploys at createSyndicate, sharing one implementation through the GovernorBeacon, and is resolved at runtime via factory.governorOf(vault). Each vault also gets its own VaultWithdrawalQueue, deployed by the factory. Protocol-level fee splits live on the shared ProtocolConfig.

Guardian layer (run 1)

Economic-security stack (run 2)

Deployed in run 2 on 2026-10-13 (14:31 UTC), which also opened vault creation by pointing the factory at the canonical ERC-8004 registry. Source: chains/4663.json on v1-deploy. Owned by the deployer until the Safe handoff.

Strategy templates (run 1)

ERC-1167 clonable singletons. Each proposal clones a template through the StrategyFactory and initializes it with its own parameters. sherwood strategy list prints the same three. The Launchpad and Lighter Perp templates and the Sushi and Stonk launch adapters (from sherwood-strategies) are not deployed on Robinhood Chain; strategy list shows them under “Not available”.

Tokens

Each vault chooses its deposit asset at creation. Use USDG on Robinhood Chain: it is the stablecoin with stock-token liquidity, and the Portfolio strategy requires a USD-pegged vault asset. The Portfolio strategy binds one Chainlink push feed per basket slot. The CLI resolves the feed from this book when a --feeds slot is left empty. A token without a feed cannot enter a basket. Other feeds the ledger and strategies read:
Weekend feed gap. The stock feeds heartbeat on US market days and go 52–55 hours between updates every weekend, against the 26-hour freshness bound the Portfolio strategy and the ledger enforce. A proposal holding stock tokens cannot execute, settle or rebalance from about Saturday 18:40 UTC until Monday 00:00 UTC, and an execution window that falls entirely inside that gap expires the proposal. sherwood sources get calendar prints the live window.

External protocols

Identity and attestations

Both live on Robinhood Chain, the same chain the vaults run on. The factory reads the IdentityRegistry at createSyndicate and registerAgent; see ERC-8004 and EAS.

Vesting

Retired chains

Two earlier environments are closed and must not be used as targets. The Robinhood mainnet fork (a Tenderly Virtual TestNet, chain 9994663) hosted the beta and closed on 2026-09-30; the CLI refuses writes to it. Robinhood testnet (chain 46630) still runs a pre-v1 stack that the current CLI’s ABIs do not match. Neither has addresses listed here, and no other chain (Base, HyperEVM) carries Sherwood contracts.

Deployment records

Per-chain deployment records are stored in chains/{chainId}.json in the protocol repo (4663.json for Robinhood Chain). They hold the deployer, contract addresses, token and feed addresses, and deployment metadata; the deploy scripts write them.

Address resolution

The CLI resolves addresses at runtime in cli/src/lib/addresses.ts. Each address family is a Record<Network, ...> map keyed by chain, with robinhood-mainnet as the default network:
Per-vault governors are not in this table; each is resolved via factory.governorOf(vault) (see cli/src/lib/governor.ts). Zero addresses mean a contract is not deployed on that chain; commands that depend on one fail with a clear error at runtime.