A blockchain
with a mathematical
proof.

Imagine four chefs in a kitchen, each writing down what dish to cook. They have a quick rule for which list is the real one, even though all four are writing at once. Astrea does that for transactions — many computers propose changes in parallel, and the network has a clear rule for which ones become final.

Two cashiers at different registers can serve different customers at the same time because they aren't touching the same cash drawer. Astrea figures out which transactions are like that — totally independent — and runs them at the same time, safely.

Many zero-knowledge proof systems prove statements about low-level machine instructions ("did the chip do X?"). Astrea aims to prove statements closer to what the app means ("did the bank balance change correctly?"). Much closer to what humans care about.

Imagine reading a book aloud in chunks, with each chunk sealed in an envelope. You can prove you read the whole book by stacking the envelopes. Astrea proves computations the same way — in chunks that fold together into a final receipt.

When you ask a server "what's my account balance?", normally you just trust the answer. Astrea servers send the answer AND a tiny cryptographic receipt. You check the receipt yourself — a fake answer will not check out against the chosen fingerprint.

Most chains let apps store little blobs of data. Astrea stores actual documents — collections, indexes, versions — like a real database, but every record is cryptographically tied to the state. Apps stop needing a separate database next to the chain.

Most chains have no idea what "a message from Alice to Bob" means. Astrea does — it understands mailboxes, threads, encrypted bodies, broadcasts. Like Signal, but participants or auditors can verify that a message arrived without ever seeing the encrypted contents.

Big files (photos, documents, archives) shouldn't be on the main chain — too expensive. Astrea has a separate place for them, but ties everything together so the main chain can prove a file exists without storing it.

Apps often need outside data ("what's the temperature in Tokyo?") or to do things later ("run this on Tuesday"). Astrea treats both as protocol features. The services providing the data can't secretly change history — the protocol always checks them.

Imagine borrowing a fact from Ethereum without trusting a bridge operator to tell the truth. Astrea reads a finalized checkpoint from Ethereum and accepts only the specific proven claims against it — nothing more.

When a city grows, you add more neighborhoods — but they're still one city, one government. Astrea adds capacity by splitting work along clear lines, but it's still one verifiable system, not many systems pretending to be one.

Lots of helpers run Astrea — indexers, schedulers, oracles, dashboards. But none of them can secretly become "the source of truth." If a helper goes down, things slow down. If it lies about a checkable answer, the proof fails.

Some apps need to be public (votes). Some need to be private (medical records). Some need both (a sealed bid that reveals after the auction). Astrea handles all three, and every transaction explicitly says what it leaks — so privacy and verifiability can compose honestly.

Ethereum charges users gas in ETH. Astrea separates "how much work was done" from "who pays for it." Apps can subsidize users, charge in different tokens, give free service, or run civic apps with zero price to the end user — without changing the underlying protocol.