Integrations
Green Goods composes existing protocols instead of reinventing them: attestations from EAS, accounts from ERC-6551, roles from Hats, funding rails from Octant, Gardens, Hypercerts, and 1Hive's Cookie Jar, and badges from Unlock. Each integration page explains why Green Goods uses the protocol, where it lives in the code, and what the checked-in artifacts say is deployed where.
The integrations
- EAS: the attestation layer for Green Goods' attested records, like work, approvals, and assessments.
- Hats Protocol: on-chain role trees that decide who may do what.
- Tokenbound Accounts: the ERC-6551 accounts that make each garden an owner.
- Passkeys: wallet-free sign-in for gardeners.
- Octant: garden vaults and yield-donation mechanics.
- Gardens: conviction-voting communities and signal pools.
- Hypercerts: certified impact claims and their fractions.
- Karma GAP: project reporting and milestone records.
- ENS: names for gardens.
- Cookie Jar: small, capped allowances from 1Hive's Cookie Jar, one jar per garden asset.
- Unlock Protocol: the locks behind GreenWill badges, the credentials a gardener or funder proves and claims.
Status by network
The table below is generated from the checked-in deployment artifacts and the indexer configuration: for each cataloged integration, where its components are recorded and which of its contracts the indexer follows. Passkeys are not in it because they have no on-chain deployment. A recorded address proves a deployment was written down, never that a feature is live and healthy; the Deployments & Addresses page lists every address.
| Integration | Networks with recorded components | Indexed contracts |
|---|---|---|
| Cookie Jar | Sepolia Testnet (Deployed), Arbitrum One (Deployed) | CookieJarFactory |
| EAS | Sepolia Testnet (Partial), Arbitrum One (Deployed), Celo (Partial) | WorkApprovalResolver |
| ENS | Sepolia Testnet (Deployed), Arbitrum One (Deployed) | none |
| Gardens | Sepolia Testnet (Deployed), Arbitrum One (Deployed) | none |
| Hats Protocol | Sepolia Testnet (Deployed), Arbitrum One (Deployed) | HatsModule |
| Hypercerts | Sepolia Testnet (Partial), Arbitrum One (Deployed) | HypercertMinter |
| Karma GAP | Sepolia Testnet (Deployed), Arbitrum One (Deployed) | KarmaGAPModule |
| Octant | Sepolia Testnet (Deployed), Arbitrum One (Deployed) | OctantModule, OctantVault |
| Tokenbound Accounts | Sepolia Testnet (Deployed), Arbitrum One (Deployed), Celo (Deployed) | GardenAccount, GardenToken |
| Unlock Protocol | Arbitrum One (Deployed) | GreenWill |
Who owns which fact
An integration crosses several layers, and each fact about it has exactly one home. Contract
behavior lives in the contract source and its tests. Where something is deployed lives in the
chain's deployment artifact, and a schema's identity in the schema configuration that artifact
records. Which events are indexed lives in packages/indexer/config.yaml and its handlers. How an
app reaches the integration lives in shared's modules, hooks, and package exports. What a
partner's concepts mean in Green Goods terms lives in the ontology and the
entity matrix. When you change an integration, change the
layer that owns the fact; each integration page links its layers.
| Concern | Authority |
|---|---|
| Contract behavior | Contract source and tests |
| Recorded deployment | Chain deployment artifact |
| Schema identity | Schema configuration and deployment artifact |
| Indexed events | packages/indexer/config.yaml and handlers |
| Application access | Shared modules, hooks, and package exports |
| Semantic mapping | The ontology and the entity matrix |
Next steps
- EAS is the best place to start: work, approvals, and assessments all live there.
- Anatomy of a Work Submission shows several integrations working together in one flow.
- Deployments & Addresses lists every recorded address per chain.