Trust should never
be optional.
TENUP lets any prediction, document, AI output, report, certificate or digital claim be cryptographically sealed on-chain before it is revealed — so it can be checked by anyone, later, without trusting whoever published it.
Digital evidence stopped meaning anything.
Anything on a screen can be produced, edited or deleted after the fact — and generative models made that cheap enough to do at scale. Every claim now arrives with an implicit question: was this really said, then?
Seal it now. Open it later. Anyone can check.
Five steps, no crypto knowledge required of the person checking. The only thing published up front is a fingerprint — useless to a competitor, decisive to an auditor.
One primitive, twelve industries.
Anywhere a claim needs to be provably older than its outcome, the same commit–reveal cycle applies. The protocol does not care what the content is.
The first application built on TENUP.
AI trading signals are the hardest possible test of the protocol: a claim with money attached, an outcome minutes away, and every incentive to revise history. If verification holds here, it holds anywhere.
What actually happens on-chain.
Scroll through the four states. The diagram on the left is the same lifecycle every claim on the protocol passes through, whatever the industry.
The content is canonicalised with JCS — sorted keys, no whitespace, deterministic numbers — then hashed with keccak256 against a 32-byte random nonce. Only the hash is submitted, so anyone watching the mempool learns nothing.
Claims inside a window become leaves of a Merkle tree, and one root goes on-chain. Cost stays flat as volume grows — a university anchoring 40,000 diplomas pays roughly what a single claim costs — and each item is still provable individually.
Content, nonce and Merkle proof are submitted inside the window fixed at anchor time. The contract recomputes the leaf and walks it to the stored root. Too early leaks a live claim; too late and the anchor is permanently marked Expired.
Anyone re-hashes the revealed content and compares it to the anchor using the open-source verifier. The Explorer shows block height, wall-clock time and finality. No step depends on trusting TENUP or the publisher.
Because a database can be edited by whoever owns it.
Only the fingerprint goes on-chain — never the document, the patient record or the model weights. Privacy is preserved by construction, because a hash is not the content.
Two calls to make anything verifiable.
Anchor a claim, reveal it later. The protocol handles canonicalisation, nonce generation, Merkle batching and window enforcement. You never touch a wallet or pay gas directly.
// seal a claim before its outcome is known const anchor = await tenup.anchor({ app: "research", content: { hypothesis, dataset, method }, revealAfter: "7d", revealBefore: "30d" }); // → { // → id: "anc_8Kd2m…", // → fingerprint: "0x9f1a4c…", // → block: 248310774, // → state: "anchored" // → }
// open it inside the window const result = await tenup.reveal({ id: "anc_8Kd2m…" }); // → { // → state: "verified", // → matches: true, // → anchoredAt: "2026-08-09T11:04:22Z", // → revealedAt: "2026-08-16T11:04:22Z", // → proof: ["0x4c1e…", "0xd90a…"] // → }
// signed event, delivered at every state change { "event": "claim.expired", "id": "anc_71ea08…", "app": "signals", "fingerprint": "0x71ea08…", "anchoredAt": "2026-08-16T09:12:40Z", "windowClosedAt": "2026-08-16T17:12:40Z", "penalty": "scored_against_publisher" }
The token is not the product. It meters the protocol.
Fixed supply of 100,000,000 on Arbitrum. It pays for verification capacity, secures the marketplace through staking, and governs the parameters that make anchors credible. No equity, no debt, no revenue rights.
Everything settles against the same anchor.
Protocol first, network last.
The contracts and the verifier are being built now. Testnet follows, then mainnet — each phase shipping only once the one beneath it holds.
Foundations
In progressThe verification contracts, the open-source verifier and the CLI — the parts everything else depends on.
- Verification contracts
- Verifier SDK and CLI
- Public Explorer
Public testnet
November 2026Anchor and reveal real artifacts on testnet with sandbox keys, and verify them from a second machine.
- Testnet anchoring
- Sandbox API keys
- Explorer on testnet
Mainnet
January 2027The registry goes live, with batching for volume and webhooks for state changes. External audit before launch.
- Registry on mainnet
- Batch anchoring
- Webhooks and dashboards
Applications & institutions
2027Signals as the proving ground, then credentials at institutional scale and per-inference anchoring for enterprise models.
- Signal verification
- Credentials and certificates
- Enterprise and university deployments
Global verification network
BeyondIndependent verifiers, multi-chain anchoring and governance over the parameters that make anchors credible.
- Multi-chain anchoring
- Token governance
- Independent verifiers
Dates are targets, not commitments. Phases, parameters and figures may change as the protocol is built and audited.
The protocol, specified in full.
33 pages on how arbitrary digital content is serialized, fingerprinted, committed to a public chain, revealed and independently verified — written for engineers integrating the SDK, reviewers auditing the contracts, and institutions assessing the network.
Tell us what you need to prove.
Whether you are integrating the SDK, evaluating the protocol for an institution, or reviewing the contracts — start here and we will route it to the right person.
Make your claims
checkable by anyone.
Anchor your first claim in a sandbox in under five minutes. No wallet, no gas, no blockchain knowledge required.