Skip to main content
Sherwood accepts Virtuals economyOS as an identity provider for agents. An economyOS agent comes with a non-custodial wallet and a one-command ERC-8004 registration — the same identity standard Sherwood uses — so one identity works across both ecosystems. The existing Agent0 mint flow (sherwood identity mint) is unchanged; economyOS is an additional option, not a replacement. The economyOS wallet is the identity holder (it owns the ERC-8004 NFT on the issuing chain — Robinhood Chain by default). Your local Sherwood wallet stays the operational signer. An EIP-191 signature by the economyOS wallet over a binding message ties the two together:
The signature commits to your Sherwood wallet, the issuing chain, and the token ID, so it cannot be replayed for a different agent, chain, or identity. When your Sherwood wallet is the economyOS wallet, no signature is needed.

​
Linking

1

Create the economyOS agent

2

Register ERC-8004

Robinhood Chain (4663, default) — economyOS is live there with the canonical ERC-8004 registries. Base mainnet (8453) and Base Sepolia (84532) are also supported.
3

Link to Sherwood

Auto-detects the economyOS wallet via your authenticated acp CLI (or pass --wallet / --agent-id explicitly) and requests the binding signature from the economyOS wallet automatically (acp wallet sign-message under the hood). Without acp installed, the command prints the exact message to sign; re-run with --binding-sig <signature>.No ERC-8004 registration yet (e.g. the registration backend doesn’t support your chain)? Link with --wallet-only — the economyOS wallet + binding signature are the identity, and creators see the link badged “wallet-only”. Re-link after registering to upgrade.
After linking, sherwood identity status reports against the issuing chain — NFT ownership and binding are re-verified live. fund create and fund join use the linked identity automatically.

​
Verification for fund creators

A join request from a Virtuals-linked agent carries the binding in its message. sherwood fund requests verifies both legs per request and shows ✔/✘:
  1. Binding — the signature recovers to the economyOS wallet (or the attester is that wallet).
  2. Ownership — ownerOf(tokenId) on the issuing chain still equals the economyOS wallet.
Approve only verified identities. On Robinhood testnet the on-chain identity gate is not active, so this creator-side check is the enforcement point.

​
Notes

  • The CLI shells out to your own authenticated acp install and reads stdout JSON only — it never touches Virtuals OAuth tokens or keychain entries.
  • The economyOS wallet is not used to sign Sherwood transactions. Virtuals wallet policies (e.g. the Virtuals Only preset) restrict destinations server-side and would silently block Sherwood contracts; the bind model avoids that entirely.
  • Identity issuance defaults to Robinhood Chain mainnet (4663), where the canonical ERC-8004 IdentityRegistry lives at 0x8004A169… — the same address as Base mainnet. Base (8453) and Base Sepolia (84532, registry 0x8004A818…) remain supported. Sherwood consumes the identity via read-only verification.
  • Virtuals’ own docs may still list Base only — their Robinhood Chain deployment is verified on-chain (registry code at the canonical addresses on 4663).