SCANNING
SUPRAOS
EDITORIAL · NO. 001
PAGE 001 / CXLVIII
I. THE MYTH
EDITORIAL · NO. 001 · JUNE 2026
True or False?
Scroll Down
CHAPTER II · THE INTERROGATION

Enterprise struggles with AI liability concerns.

EXHIBIT A · FEBRUARY 2024

Air Canada's AI chatbot gave a customer wrong information…

The airline was found liable.

A tribunal ruled the company was bound by what its chatbot said — and rejected Air Canada's claim that the bot was a separate legal entity. Your AI's wrong answer is now your contract.
EXHIBIT B · JUNE 2023

A lawyer's AI invented six court cases that never existed…

The court sanctioned him.

Six court cases, confidently cited in a federal filing. Every one was invented by ChatGPT. A federal judge sanctioned the lawyers and their firm.
EXHIBIT C · PROJECTED 2029

A billion AI agents arrive by 2029…

Almost none can be audited.

IDC projects over a billion AI agents in the wild by 2029 — 40× today — acting at machine speed. Billions of autonomous decisions, almost none independently verifiable.
EXHIBIT D · STANFORD · 2024

Stanford tested the AI on real legal questions…

It hallucinated up to 88%.

Stanford tested leading models on specific legal questions. They hallucinated 69–88% of the time — and stated every answer with total confidence.
EXHIBIT E · THE ROOT CAUSE

AI has no live source to verify against…

It never had an oracle.

DATA · SIGNAL · VERIFICATION
No live feed. No tamper-proof source. No way to ask "is this still true?" It's the exact problem blockchains once had with the real world — the one oracles were built to solve. AI never got its oracle.
THE PROBLEM · TWO CRITICAL FAILURES

Agents are flying blind — and forgetting everything.

No real-time data

Most models are frozen at training time, with no live feed to the world. They reason from stale memory, with nothing to verify against.

No trustworthy memory

Every task starts from scratch, with nothing to build on. They can't prove what they saw or did, so recall is guesswork, not record.

The result: hallucinations, broken trust, and agents that can't operate autonomously at scale.

CHAPTER III · THE PROBLEM WE SOLVE

The problem we
seek to solve.

One fact appears after the AI training cutoff. Ten thousand people ask for it — and users have to re-discover it, from scratch, ten thousand times.

01 · the same question
?“Did it happen — the thing announced last week?”
asked jun 14, 2026 — 4:56:03 pm · after the model’s training cutoff
0:00waiting

No memory of it. So the model crawls the live web — a dozen sources, parsed fresh. You wait thirty seconds.

01 · now multiply it
1
people · same question
12
page-crawls · repeated
0 min
of human life · spent waiting

Ten thousand people. One answer. Re‑derived from scratch ten thousand times.

Nobody kept the result. So everybody pays for it again.

02 · the cost of one answer — paid again and again
one answer
0tokens
read twelve pages · synthesize · bill it
× 10,000
the same answer, ten thousand times
0tokens
re-reading the identical paragraph · re-billed every time

One answer, metered to the token — then re-derived and re-billed, ten thousand times over.

1
value created
one fact, learned
10,000×
work billed
the same fact, re-derived

Brilliant for the meter. A quiet tax on everyone who pays it.

03 · what if the world learned it once?
verified record · written once

Reach consensus on the fact. Verify it. Keep it. Now no one has to find it again.

03 · verified once · served to everyone
consensus
participants agree the fact is true
ledger
indexed, enriched, sealed on-chain
proof
0:30
cryptographically verified
cache
already verified · served instantly
30 sec → 100 ms
time to a verified fact
10,000 → 1
lookups become one verification
a tax → a dividend
providers earn per lookup
◉ 1/100¢ flows to whoever secured the knowledge — every time AI taps it

Learn it once. Verify it forever.
Serve it to everyone — in one hundred milliseconds.

PRE-EVENT · SYSTEMIC INSTABILITY
true false [unverified] hallucinated $100B LIABLE sanctioned 69–88% 40× STANFORD truth trust source verify audit cited binding deferred implicated IDC unaudited no oracle 1B agents

Welcome to the other side.

Where every claim has a hash. And every hash has a consensus witness.

THE SOLUTION · THE VERIFIABLE MEMORY LAYER

A verifiable memory layer for AI agents.

Real-time, blockchain-verified data meets advanced, persistent memory — so agents pull trusted facts, recall everything, and prove exactly what they know.

Real-time, verified

Instant access to live, blockchain-verified data — a source of truth that's always current, never frozen.

Persistent recall

Perfect memory across every session — recall that compounds and hash-chains instead of resetting to zero.

Provable

Every claim hashed and witnessed on-chain — agents can prove exactly what they knew, and when they knew it.

Not an improvement — the foundational infrastructure that makes truly reliable agentic systems possible.

CHAPTER · CRYSTALLIZATION

Now every claim leaves a trail.

This is the oracle AI never had — every claim hashed, timestamped, and witnessed on-chain. A live source of truth an agent can finally check against.

Air Canada lost the chatbot case.

0x4a7f...8e92
UNVERIFIED

A lawyer cited six fake cases.

0x8c2a...4f13
UNVERIFIED

1 billion AI agents by 2029.

0x3b6c...d029
UNVERIFIED
CHAPTER · PROOF

Tested head-to-head on the hardest memory benchmarks.

On every public benchmark we ran, SupraOS memory beats the best-known system — by 13 to 17 points.

LongMemEval-S
0.00
ZEP
0.00
SUPRAOS
LONG-TERM MEMORY RECALL
LoCoMo cat 1–4
0.00
FULL-CONTEXT
0.00
SUPRAOS
CONVERSATIONAL MEMORY
MemoryAgentBench
0.00
SONNET 3.7
0.00
SUPRAOS
+16 PTS vs CLAUDE 3.7 SONNET
CHAPTER · HOW IT WORKS

How the memory layer works.

One pipeline — from edge data to verified, on-chain recall.

  1. 01

    Edge indexing

    Data is indexed daily across a group of edge SupraOS users.

  2. 02

    Consensus promotion

    That data is promoted to Global Memory once the network reaches consensus.

  3. 03

    Oracle synthesis

    It is synthesized through the Threshold AI Oracle — multi-model consensus, not a single source.

  4. 04

    Rich embeddings

    Memories are indexed with rich embeddings for fast, efficient retrieval.

  5. 05

    Cognitive recall

    AI agents tap Supra's Cognitive Modes recall system to pull facts instantly — with full provenance of the sourcing material.

  6. 06

    Micro-fees & shielding

    Agents pay micro-fees to the network. Enterprises and frontier providers are shielded from liability.

  7. 07

    Faster, cheaper truth

    End consumers get accurate answers faster and cheaper — no waiting on agents to re-crawl dozens of sites, no ballooning latency or token spend.

CHAPTER · FOUNDATIONS

Built on real infrastructure.

An oracle for AI takes two layers working together — a public chain that can't be tampered with, and a memory that writes every claim to it.

SUPRA · L1
The substrate
The blockchain underneath. Every entry is permanent, timestamped, and public — nothing can be altered or quietly deleted after the fact.
SUPRAOS · MEMORY
The witness
The agent's memory layer. Every fact it stores is hashed and anchored to the chain below — so any claim can be traced back and proven.

Together: a claim the memory makes, and a chain that proves it was never faked. That's the oracle.

CHAPTER · THE NETWORK

With an oracle, AI can finally be trusted.

Every memory hashed. Every hash witnessed. Every witness on-chain. This is the verification layer that makes AI agents reliable enough to act.

ten thousand agents · one fact
without a verifiable source
10,000×
full synthesis · re-derived from scratch
~30 sec · ~8,000 tokens — paid again, every time
vs
with supraos
verified record · hash · timestamp · reputation
1 × verify
proven once · reused by everyone
~100 ms · checked, never re-derived

Same answer, ten thousand times over. One path makes every agent pay to re-derive it. The other proves it once — and serves it to all of them, instantly.

a cache gives you
speed
+
a proof gives you
trust

The efficiency win and the trust win are the same win.

The proof is what lets an agent verify instead of re-derive — one query replaces ten thousand syntheses. Cheaper for everyone. Instant for everyone.

Google indexed the web for people.

We're building the“Google search”
for AI Agents.

AI search isn't blue links to skim — it's verified facts retrieval. Every answer comes back proven authentic, current, and true: one query, instant, trusted.

Our edge is the stack that makes it real: our own Layer-1 · a deployed oracle securing data in production · benchmark-leading memory.

what one lookup costs you — re-derived vs. verified
$0.025  ·  the old way: re-crawl ~12 sources, burn ~8,000 tokens per lookup AI can't answer from training
$0.005
$0.020 saved — back to the user
our fee · 20%the user keeps 80% of the spend
and on speed ~30 sec ~100 ms ≈ 300× faster — same verified answer

cheaper. 300× faster.

Every fact the model never learned used to cost a full re-derivation. We turn it into one verified lookup: the user pays a fifth, saves the rest, and gets the answer in 100 milliseconds. We keep 20% of what we save them.

1 billion agents by 2029  ·  10 verified lookups / day  ·  $0.005 fee
10%
$0.00B
20%
$0.00B
30%
$0.00B
50%
$0.00B

OUR FEE PER 10 POINTS  +$1.83B / yr   |   USERS SAVE  +$7.3B / yr

Base case — one in ten agents — is a $1.83B line for us, and it sits on top of ~$7.3B we just saved those users in token spend. The fee never moves; the volume does — and every point of growth saves the market four dollars for every one we keep.

at 50% adoption  ·  cheaper and faster, every lookup
value created for users · cost + time saved$0.0B
our fee · 20%$0.00B
users keep the other $36.5B in token spend — and get every answer in milliseconds, not minutes.

The user keeps 80% and all the speed. We keep 20%.

We only ever charge a fifth of the value we create — so the cheaper and faster we make every lookup, the more we earn. That fifth, at a billion agents, is a multi-billion-dollar business aligned with the customer on every single query.

CITATIONS · FACT-CHECKED 2026

Every claim, sourced.

  1. [01] LIABLE · AIR CANADA CHATBOT Moffatt v. Air Canada, 2024 BCCRT 149 (British Columbia Civil Resolution Tribunal, February 2024). The tribunal found Air Canada liable for negligent misrepresentation after its chatbot misstated bereavement-fare policy, and rejected the argument that the chatbot was a separate legal entity. Award $812.02 total ($650.88 damages, $36.14 interest, $125 fees). CanLII (full decision).
  2. [02] SANCTIONED · SIX FABRICATED CASES Mata v. Avianca, Inc., 22-cv-1461 (PKC), 678 F. Supp. 3d 443 (S.D.N.Y. June 22 2023). Judge P. Kevin Castel imposed a $5,000 Rule 11 sanction, jointly and severally, on attorneys Steven Schwartz and Peter LoDuca and their firm Levidow, Levidow & Oberman, P.C., after they filed a brief containing six ChatGPT-fabricated case citations. Wikipedia.
  3. [03] 1B AGENTS · 40× BY 2029 IDC forecasts more than 1 billion actively deployed AI agents worldwide by 2029 — roughly 40× the 2025 level — executing on the order of 217 billion actions per day. IDC FutureScape, 2025.
  4. [04] 69–88% · LEGAL HALLUCINATION RATE Dahl, Magesh, Suzgun & Ho, Large Legal Fictions: Profiling Legal Hallucinations in Large Language Models, Journal of Legal Analysis (2024), Stanford RegLab. General-purpose LLMs hallucinated on 69–88% of specific legal queries. Stanford.
  5. [05] MAB v3 · 65.84 · +16PP vs CLAUDE 3.7 SONNET Tobkin, J. et al. Supra Cognitive Modes: A Memory-Augmented Benchmark and Architecture. arXiv:2507.05257v3. Final hardened N=3 build; identical harness and Sonnet backbone across comparators. Paper.

— cryptographic hash digests shown in fact cards are illustrative · the verification architecture they represent is real · live hashes appear on-chain at the supra explorer —

Bonus · for operators & investors

The business, today.

Everything above describes a global, public substrate. But the same architecture pays for itself long before any of that exists — inside a single company.

The redundancy isn't unique to the open web; behind the firewall it's often worse. A company running hundreds of agents across fifty people has the same problem at smaller scale. One rep's agent researches a customer on Monday; another rep's agent researches the same customer on Thursday; a third does it again next week. Legal re-derives the same clause. Security re-investigates the same CVE. Every redo is tokens spent re-buying an answer the company already paid for.

Inside one company, the same fact gets re-derived, and re-billed, team after team.

Supra Cognitive Modes runs locally, over a company's own processed data, with nothing leaving its walls. When an agent does real work, the result is stored, scored, and provenance-tagged — so the next agent retrieves it instead of recomputing it. The classifier routes internal questions exactly as it routes everything else:

  • single-fact lookup“What's this customer's renewal date?”
  • time-anchored lookup“What changed in their contract since last quarter?”
  • long-form synthesis“Summarize everything we've learned about this account in two years.”
  • latest-version resolution“Which pricing policy is currently in force?”
  • pattern from examples“How do we usually handle an exception like this?”

The win here is a line item, not a someday: lower token spend, faster agents, less duplicated work, and more consistent answers across teams. That's a number an operator can point at this quarter — not a network they have to wait for the world to join.

The ledger has a private form too. An enterprise can run its own audit chain — its own hashes and timestamps, with no public network involved. The point there isn't decentralization; it's governance: an immutable record of which sources produced an answer, which model generated it, what was known at the time, and whether anything changed since. For finance, healthcare, insurance, and government, that provenance trail is fast becoming a compliance requirement rather than a nicety.

The offering is concentric · not a single far-off bet
Enterprise Memory · the floorSupra Cognitive Modes deployed locally; agents retrieve instead of recompute. An ROI sale, measured directly in token spend.
Knowledge LedgerA private audit chain for provenance, source lineage, and explainability. A risk-reduction sale for regulated industries.
Knowledge FederationOptional, privacy-preserving sharing of anonymized, derived findings across trusted organizations — each keeping its own data and chain. A network-effect sale.
Global Knowledge Layer · the upsideThe public, provenance-backed substrate this deck describes. The platform.

The public network is the upside.
The enterprise business is the floor.

That ordering is the point. The first layer pays for itself inside one company. The second adds governance the regulated industries already want. The third lets organizations that don't trust each other reuse knowledge anyway. And the global layer becomes a natural expansion of the first three — not a prerequisite for any of them.

We don't need the whole world to adopt a protocol for this to be worth building. We need one company tired of paying twice for the same answer — and there are a great many of those.

CHAPTER · THE ASK

The trust layer for AI is being built. Build it with us.

For investors

Frequently asked.
Straight answers.

01 · The problem
AI has no trustworthy, attributable source of truth to check itself against — so it hallucinates and can't prove what it knows. And as the models commoditize, durable value is migrating to the memory and verification layer around them. We build that layer: any AI can retrieve a fact and cryptographically verify it's authentic, current, and reputation-scored — in one lookup instead of re-deriving it from scratch.
Search solves access, not trust. A model can fetch a page; it can't prove the page is authentic, unaltered, current, or attributable — and every model re-reads and re-synthesizes the same sources independently, with no shared verifiable memory. We close the provenance gap search structurally can't.
02 · Why this team
Solving AI trust requires three capabilities that rarely coexist, and we have all three already built: a production Layer-1, deployed oracle expertise, and a benchmark-leading memory engine. The AI trust problem is, at its core, an oracle problem — and we're among the strongest oracle teams in the world, with peer-reviewed research and a protocol securing real financial data in production for years. We don't theorize about a truth mechanism; we run one.
SupraOS is built on our own Layer-1. The substrate is ours, not rented — which is exactly why we can put verification on-chain cheaply and keep it credibly neutral. Entity and cap-table structure shared in diligence.
03 · How it works
Only the proof, not the payload. On-chain: the hash and metadata (timestamp, confidence, reputation) needed to verify a factoid — small, cheap, neutral, tamper-evident. Off-chain: the actual content, served fast from caches, with the chain's proof attached. An AI fetches at cache speed, then verifies against the on-chain commitment. Speed of a cache, trust of a chain — cryptographically bound.
It's the retrieval-time proof check — confirming provenance, integrity, timestamp, and reputation via an inclusion proof and signature. Truth is established once, up front, by our oracle protocol; the lookup simply proves you're getting that established result, untampered.
Objectively checkable, consensus-stable claims: did event X happen on date Y, document and version hashes, rulings, API schemas, a price or rate at a timestamp. We deliberately don't adjudicate contested, subjective, or political claims — we provide verifiable, attributable provenance, not a referee for opinion.
This is what our oracle protocol is built for. Rather than claiming "objective truth," we attach a verifiable, timestamped confidence and reputation score to every factoid — a calibrated, cryptographically provable trust signal an AI can threshold on. Full consensus/validation mechanism detailed in diligence.
04 · Why blockchain
We do use centralized caches — for delivery. What a centralized service can't be is the neutral, tamper-proof source of the proof itself: censorship-resistant, permissionless, with a trustless payment rail no operator can take rents on or use to deplatform. Those properties together are what a permissionless ledger is. We put only the lightweight proof on-chain, so we get neutrality cheaply while the heavy data stays in fast caches.
They could build a fast verified cache tomorrow. They structurally cannot credibly offer a neutral, user-owned, permissionless knowledge commons where contributors are paid and no one can be deplatformed — because their neutrality and data practices are precisely what's in question. Our edge is the position they're constrained from taking, on infrastructure (a live L1 + a deployed oracle) they'd have to build from scratch.
No — the crypto is plumbing. Keys and payments are abstracted behind the product; it should feel like setting up a profile, not configuring a trading account.
05 · Business & incentives
Contributors earn a micro-payment when a factoid they generated and verified is later retrieved by an AI — monetizing the byproduct of work they'd already done and no longer need. Consumers pay because they get verified data (provable authenticity + reputation, far fewer confident hallucinations), instant speed, and token savings — one proven lookup instead of re-scanning a dozen sites and re-synthesizing.
A protocol fee on verified lookups plus enterprise licensing. Pricing, take rate, and unit economics shared in diligence.
06 · Data ownership & privacy
Both — and your data never goes on-chain, only its hash and verification metadata. Your private data stays yours (on-prem for enterprise, user-owned for individuals). What's optionally contributed is the result you already computed and no longer need — and you're paid if the network reuses it. Keep your data; donate the answer you already paid to compute; earn when it's reused.
Enterprise data stays on-prem / in-tenant by design — only proofs and opt-in factoids ever touch the shared layer, never wholesale data egress.
07 · Moat & competition
Memory alone isn't the moat — they're all building it. The moat is the combination they can't easily assemble or credibly offer: benchmark-leading memory + an operating oracle for verification + our own neutral L1 + user-owned, portable, private data, under a credibly-neutral commons. Each piece is hard; together, incumbents are structurally constrained from offering it.
Memory-layer startups (e.g., Zep, Mem0), frontier-lab native memory, and the verified-data / oracle ecosystem. Our differentiator is verifiable retrieval backed by a deployed oracle and our own chain — not memory alone.
08 · Proof, team & raise
On the hardest public memory suites (LongMemEval, LoCoMo, MemoryAgentBench), with comparators run through our own harness at a consistent backbone so the deltas are honest and like-for-like. Final hardened head-to-head numbers in the paper and diligence.
A deployment. Our oracle protocol has secured real financial data in production for years, with peer-reviewed research behind it. The AI knowledge layer applies infrastructure we already run — not infrastructure we hope to build.
Pilots, usage, revenue, and current round details shared in diligence.
We name them because we have answers: adoption / behavior change (proving enough users and enterprises will choose ownership and verifiability), benchmark durability under honest comparison, and incumbent encroachment on the memory layer. Our hedge against all three is an asset stack — a live L1, a deployed oracle, a neutral commons — that incumbents can't replicate overnight.
STILL CURIOUS?  —  j.tobkin@supra.com