Skip to main content

Tokenbound Accounts (ERC-6551)

Overview​

Tokenbound accounts are part of the live garden account model. Each garden token can map to a smart account that owns assets, stores metadata, and acts as the garden's protocol identity.

Current surfaces​

  • Garden account contracts under packages/contracts/src/accounts.
  • Garden token contracts under packages/contracts/src/tokens.
  • TBA helper library in packages/contracts/src/lib/TBA.sol.
  • Shared contract utilities and deployment artifacts for consumers.

Builder notes​

  • Keep garden-account assumptions chain-scoped; each frontend build targets one chain.
  • Use shared contract utilities and deployment artifacts rather than hardcoding addresses.
  • Separate gardener auth/smart accounts from garden tokenbound accounts in docs and UI copy.

Next page

Next best action

Contracts documentation explains how garden accounts fit into the broader protocol deployment.

Contracts package