For builders
Noesea Protocol SDK
The Noesea SDK surface for builders — register claims, anchor evidence, read signed responses, and verify records with deterministic, cross-platform canonicalization.
On this page
What the SDK does
The SDK lets a product register claims, hash and bundle evidence, anchor Merkle roots, and read machine-consumable signed responses — without each integrator re-implementing the proof model. It targets parity across web, server and extension environments.
Deterministic canonicalization
Claim canonicalization is consensus-relevant: the same meaning must produce the same identifier on every platform. The SDK ships golden test vectors so canonicalization stays deterministic across languages and runtimes, which is what keeps claim identity stable.
Independent verification
Verification helpers let a downstream consumer recompute a hash and check a Merkle proof against the public anchor, so a record can be confirmed without trusting the sender or relying on Noesea-operated infrastructure.
Same claim, same ID, on every platform
Claim IDs are keccak256 over the ABI encoding of the canonicalization version, topic ID, content hash and nonce. The SDK, the Rust canonicalizer, the web verifier and the contracts are tested against one shared corpus of golden vectors, and unknown canonicalization versions fail closed instead of silently falling back to other rules.
Availability
The SDK is developed in the Noesea repository and is not yet published to a public package registry. Teams integrating before publication work with the Noesea team through the pilot program. The browser verifier uses the same verification code and needs no installation.
FAQ
Common questions about protocol SDK integration
Who is the SDK for?
Builders integrating proof infrastructure into products, agents and services — anyone who needs to register claims, anchor evidence, or verify records programmatically.
Why do golden test vectors matter?
Claim identity depends on deterministic canonicalization. Golden vectors guarantee that the same claim canonicalizes identically across platforms, so the same statement always resolves to the same record.
Where do I start?
Begin with the integration guide for the end-to-end flow — claim registration, evidence anchoring, and verification — then use the builder program for support.
Is the SDK on npm?
Not yet. The SDK is not published to a public package registry during the pre-launch phase; integration currently runs through the pilot program, and the browser verifier needs no installation.
Continue