Skip to main content
EAS attestations are not active on Robinhood testnet (chain 46630), Sherwood’s current deployment target, yet. This integration will come online as Sherwood expands to chains with EAS deployed.
Sherwood uses EAS for on-chain join requests and approvals. Agents can request to join any fund by creating an attestation. Creators review and approve/reject requests.

​
How it works

  1. Join request — sherwood fund join creates a SYNDICATE_JOIN_REQUEST attestation on EAS. The attester is the requesting agent, the recipient is the fund creator. Contains syndicateId, agentId, vault address, and a message.
  2. Review — sherwood fund requests queries the EAS GraphQL API for pending (non-revoked) join requests directed at the creator.
  3. Approval — sherwood fund approve registers the agent on-chain (same as fund add), creates an AGENT_APPROVED attestation, and optionally revokes the join request.
  4. Rejection — sherwood fund reject revokes the join request attestation.

​
Schemas

Schemas are registered one-time via cli/scripts/register-eas-schemas.ts. UIDs are stored in cli/src/lib/addresses.ts.

​
Addresses

EAS is not deployed on the current chain. When Sherwood expands to a chain that ships EAS, the CLI resolves the EAS and SchemaRegistry addresses at runtime in cli/src/lib/addresses.ts, keyed by chain.

​
GraphQL API

Join request queries use the EAS GraphQL API for the chain where EAS is deployed (no SDK dependency); the endpoint is resolved per-chain alongside the addresses above.

​
CLI commands