Using Attestation & Hypercerts Data
Verify on-chain records and prepare for future impact tokenization.
Verifying Attestations
Get Attestation UID from GraphQL query, then verify on EAS explorer.
Example:
Work attestation:
0xb4318a3d228cb57828e9c56d96f88756beb71be540140226b8fc31ca97099f26View on: https://arbitrum.easscan.org/attestation/view/{UID}
What to Verify:
Attester (garden account)
Schema UID matches expected
Timestamp
Data (decoded)
Referenced attestations (work → approval chain)
Attestation Chains
Trace work through approval:
Find work attestation
Look for approval attestations referencing it
Verify operator who approved
Check timestamps
Confirm data consistency
Karma GAP Integration
Query GAP Attestations:
Green Goods automatically creates GAP attestations
Gardens = GAP Projects
Approved work = GAP Impacts
View on Karma GAP: https://gap.karmahq.xyz/
Future: Hypercerts
Coming Soon:
Gardens mint Hypercerts
Aggregated verified work
Fractionalized ownership
Impact markets
Example Evaluation Workflow
Grant Allocation Decision:
Query gardens by location/focus
Calculate approval rates
Verify top candidates' attestations on-chain
Export data for board presentation
Make funding decision
Learn More
Last updated