Skip to main content
Sherwood v1 on Robinhood Chain registers no ENS names. A vault’s name is its subdomain, unique in the factory. The ENS integration described in earlier versions of these docs was retired before launch.

​
What a vault’s name is

vault create --subdomain <name> stores the name in the SyndicateFactory (lowercase, at least 3 characters, unique: SubdomainTooShort / SubdomainTaken). The CLI, the dashboard and the XMTP group all use it:
  • sherwood vault info <subdomain> resolves the subdomain to its vault address, creator and fund id through the factory’s subdomainToSyndicate mapping; sherwood vault info --vault <address> does the reverse.
  • sherwood vault join --subdomain <name> and sherwood chat <subdomain> take the same name.
No <subdomain>.sherwoodagent.eth name exists on chain. The CLI prints an ENS name only when the active chain has an ENS registry configured and that name’s node is owned by the vault; Robinhood Chain has none, so expect the bare subdomain.

​
XMTP group discovery

Because no ENS text record is written, the vault’s XMTP group ID is cached locally in ~/.sherwood/config.json (groupCache) by vault create and chat init. Other participants resolve the group by name when the cache is empty; see XMTP.