Creating Impact Certificates
Overview
Hypercerts are semi-fungible tokens representing claims of verified impact work. Minting a hypercert bundles your garden's approved work and assessments into a tradeable on-chain certificate. Once minted, you can list hypercerts on the marketplace for retroactive funding.
UI and hooks
Implemented (activation pending deployment)Admin routes and shared hooks for mint/list/approvals are implemented.
Marketplace activation
Implemented (activation pending deployment)marketplaceAdapter remains zero-address in latest deployment artifacts, so public listing is not fully active.
How It Works
- 1
Prepare claim
Aggregate verified work and assessment scope for the hypercert claim. Select which approved work to include and define the impact scope.
- 2
Mint hypercert
Use the create/mint flow in your garden's Hypercerts tab. Configure metadata, allowlist of contributor addresses, and transfer restrictions. Confirm and sign the minting transaction.
- 3
Approve marketplace
Grant the marketplace adapter permissions to manage your hypercert for listing.
- 4
Create listing
Set pricing, number of units, and expiration strategy. Publish the listing.
Best Practices
- Verify all included work is approved and attestation chains are intact before minting
- Set clear contributor allowlists so that fractions go to the gardeners who did the work
- Review transfer restriction settings carefully — they cannot be changed after minting
- Confirm non-zero module/adapter addresses in
deployments/*-latest.jsonbefore attempting marketplace operations - Run an end-to-end mint/list test on a testnet before going live on production chains
Activation checklist:
- Non-zero module/adapter addresses in
deployments/*-latest.json - Indexer config updated with those addresses
- End-to-end mint/list test passes on target chain
What's Next
Next best action
With impact certificates minted, manage your garden's financial infrastructure.
Managing Endowments