Protocol
A public layer for digital proof.
Claims, evidence, verification, and disputes, structured for independent review.
Noesea is designed for proof, not presentation.
When a claim matters, the supporting record should survive outside the original sender, tool, or interface. Noesea turns that record into something another party can check.
Structured claims
One stable identity for the statement, evidence, and challenge path.
Evidence integrity
Hashes, bundles, and custody events anchored for later review.
Independent checks
Outputs designed for counterparties, auditors, and developers.
Core System
Four layers
01
Claim registry
Stable claim identity and type rules.
02
Evidence graph
Linked evidence, provenance, custody events, and anchors.
03
Dispute engine
Challenge flow, juror selection, verdicts, and dissent records.
04
Verification layer
Browser checks, reports, bundles, and developer validation.
Claim Lifecycle
From claim to verified record
Register the claim with a content hash and type.
Attach locally hashed evidence and bundle roots.
Preserve custody events in the case history.
Generate verification output for review.
Anchor verdicts and dissent if challenged.
Let a third party recheck the artifact later.
Verification
Three levels of assurance
Browser check
Claim status, evidence count, and latest update. No wallet required.
Report review
Portable outputs for legal, compliance, and audit workflows.
Independent validation
Event logs, Merkle proofs, and contract interfaces for developers.
Operating Principles
The receiving side matters.
Every design decision comes back to one question: can the receiver verify this without trusting us?
Principles
Durable proof records, not temporary platform trust.
Public claims stay inside what the product can defend.
Verification works for non-Noesea users.
Protocol Objects
Read the adjacent materials
Noesea is founded by Jan Formánek, Founder & Protocol Architect of Noesea.