Pillar
Proof Infrastructure Protocol
Noesea is a proof infrastructure protocol for digital claims, provenance, verification and evidence records.
On this page
What is proof infrastructure?
Proof infrastructure is a shared layer that lets a claim, and the evidence behind it, be checked by someone who does not trust the sender. Instead of asking parties to believe a screenshot or a platform, it turns the supporting record into something a counterparty can verify independently.
Digital claims
A claim is a statement that something is true. Noesea gives each claim a stable identity with a content hash and type rules, so the same statement resolves to the same record and can carry evidence, challenges and outcomes over time.
Provenance
Provenance records where an artifact came from and how it has changed. Noesea prioritizes cryptographic provenance over after-the-fact detection: a verifiable origin and custody history is more durable than a probabilistic guess about authenticity.
Verification
Verification produces outputs designed for the receiving side — browser checks, portable reports and developer-level validation — so a third party can confirm a record without reconstructing the entire case or relying on Noesea-operated infrastructure.
Evidence records
Evidence is hashed locally, bundled under Merkle roots and preserved with custody events. The record survives outside the original tool or interface, which is what makes it useful in legal, compliance, media and enterprise review.
Protocol governance
Governance governs the protocol, not the truth of claims. Token governance can adjust bounded fees, emissions and treasury withdrawals. Dispute resolution and slashing rules are fixed per deployment and pinned into each dispute, so no vote, team key or operator can change an individual outcome. Protocol neutrality means the layer serves every participant on the same terms.
How it works, end to end
A claim is first canonicalized: its text is normalized, its fields are ordered, and a deterministic claim ID is derived, so two independent clients produce the same identifier for the same claim. Supporting files are hashed on the device that holds them and grouped under a Merkle root. The root and custody events are anchored on-chain while the files stay with their holder. A receiver who gets the files and the exported proof recomputes the hashes and checks inclusion against the anchor. If someone disagrees with the claim, they open a stake-backed challenge, and a randomly drawn jury settles it through commit-reveal voting, with appeals going to fresh jurors.
What goes on-chain, and what stays off-chain
On-chain: claim identifiers, evidence hashes and Merkle roots, custody anchors, stakes, dispute outcomes and reputation. Off-chain: the claim text and every evidence file, held by their owner or in content-addressed storage and referenced by hash. Confidential evidence is referenced by an encrypted pointer. This split keeps personal and regulated data off a public ledger while keeping every commitment publicly checkable.
What proof infrastructure does not do
It does not decide whether a statement is true. A matching hash shows that a file is the one that was recorded; it does not show that the file's contents are accurate, who created it, or that it is still stored somewhere. A dispute outcome records how the protocol's process resolved a contested claim — its direction, whether it was decisive, and the dissent — not a universal verdict. Governance can tune bounded parameters but cannot decree outcomes.
Current status
Noesea is pre-launch. The contracts, canonicalizer, SDK and browser verifier are implemented and tested, and claim and evidence flows run in the browser and on test deployments. The dispute lifecycle has not yet been operated on a public network, so no live verdict exists yet. No token sale or exchange listing has taken place.
Noesea’s architecture
Noesea anchors hashes, stakes, outcomes and reputation on-chain, never raw content. A claim registry, evidence graph, dispute engine and verification layer combine into one auditable proof system for an AI-native internet.
Verifiability tiers
Six levels of what can be independently checked
Noesea grades a record by what a third party can verify, not by how confident anyone feels about it. Each tier adds a checkable property; none of them is a verdict on its own.
| Tier | Name | What can be checked |
|---|---|---|
| 0 | Unverified | Submitted data with no hash, signature or custody anchor. |
| 1 | Hash-verifiable | A content hash exists, so anyone holding the file can confirm its integrity. |
| 2 | Anchored | The hash or Merkle root is anchored on-chain with a timestamp and custody event. |
| 3 | Evidence-graph verifiable | Claim, evidence, custody and provenance relationships can be reconstructed from artifacts. |
| 4 | Dispute-settled | A dispute produced a decisive outcome with recorded dissent and stake effects. Ties and below-quorum rounds do not qualify. |
| 5 | Fully protocol-verifiable | The full output is checkable from chain state, content-addressed data, signed computation receipts and public schemas. |
Comparison
Proof infrastructure vs. detection vs. platform trust
| Approach | Basis | Durability as AI improves | Verifiable by the receiver |
|---|---|---|---|
| Proof infrastructure (Noesea) | Cryptographic provenance + anchored evidence records | Stable — does not degrade as AI improves | Yes — the receiver can check without trusting the sender |
| Forensic detection | Probabilistic model analysis of the artifact | Degrades as generators improve | No — you trust the model's guess |
| Platform trust / screenshots | Sender assertion, exports, platform logs | Fragile — content is editable and can disappear | No — you trust the sender or platform |
FAQ
Common questions about proof infrastructure
What is a proof infrastructure protocol?
A proof infrastructure protocol is a shared layer that lets a digital claim, and the evidence behind it, be verified by someone who does not trust the sender. Instead of relying on screenshots or platform trust, it gives each claim a stable identity, anchors its evidence, and preserves its dispute history so the record can be independently rechecked.
What is Noesea?
Noesea is a proof infrastructure protocol for digital claims, provenance, verification and evidence records. It anchors hashes, stakes, outcomes and reputation on a public ledger — never raw content — so claims and evidence can be reviewed independently.
Who founded Noesea?
Noesea was founded by Jan Formánek, Founder & Protocol Architect of Noesea.
How is provenance different from detection?
Detection asks a model to guess whether content is authentic and degrades as generators improve. Provenance records where an artifact came from and how it changed, and stays verifiable regardless of how good generation becomes. Noesea prioritizes provenance over detection.
Is Noesea live?
Noesea is pre-launch. Claim and evidence flows run in the browser and on test deployments, and exported proofs can be verified in the browser today. The dispute lifecycle has not yet been operated on a public network.
Does proof infrastructure decide what is true?
No. It makes claims and their evidence independently checkable and records how contested claims were resolved. A matching hash shows a file is unchanged, not that its contents are accurate.
What does Noesea store on-chain?
Noesea anchors only hashes, stakes, outcomes and reputation on-chain. Raw content is never stored on-chain.
Continue