For builders
Integration Guide: Add Proof Infrastructure to Your Product
A step-by-step path to integrate Noesea proof infrastructure — register a claim, anchor evidence under a Merkle root, emit a signed response, and verify on the receiving side.
On this page
1. Register a claim
Give the statement a canonical form and register it. The protocol derives a stable identifier from the content hash and type rules, so the same claim resolves to the same record and can accumulate evidence, challenges and outcomes over time.
2. Anchor evidence
Hash the supporting artifacts locally, bundle them under a Merkle root, attach custody events, and anchor the root. Raw content stays in content-addressed storage; only the hash and root are anchored.
3. Emit a signed response
Expose a machine-consumable signed response that carries the claim status, proofs and evidence references, so another system — or an AI agent — can consume the result programmatically.
4. Verify on the receiving side
On the consuming side, recompute the hash, check the Merkle proof against the public anchor, and review custody. Verification succeeds without trusting the sender and without Noesea-operated infrastructure in the path.
FAQ
Common questions about protocol integration
Do my users need a wallet?
Verification is hash- and proof-based and does not require a wallet. Wallet interaction is only relevant for on-chain actions such as anchoring or staking, which can be handled by your integration rather than the end user.
What stays off-chain?
All raw content. The integration anchors hashes, Merkle roots, custody and outcomes; the artifacts themselves stay in content-addressed storage referenced by hash.
How do downstream consumers trust the result?
They do not have to trust you — they recompute the hash and check the Merkle proof against the public anchor, which is the entire point of receiver-side verification.
Continue