The real hero, running here. It cycles through a wallet, proof of reserves and a payment, and each one checks its own numbers as you watch. Click the tabs underneath to switch.
The problem
Provably makes databases where every answer comes with a proof. That is hard to picture. A proof is invisible, and words like zero knowledge mean little unless you already know them.
So the site had one job: show what goes wrong without a proof, and what changes with one, without asking anyone to understand the maths.
Show the product working
Every illustration on the page is the product doing something real. A wallet checks its balance, an exchange proves its reserves, a payment prints a receipt. Each one plays on its own, and every number that matters is shown being checked.
The illustrations are built in code, not exported as images, so they stay sharp, move properly and rearrange for phones.
The problem as a scroll story. Someone swaps your balance on the way in, your app can't tell, and a payout goes out on a forged number. Then the proof catches it.
Telling it as a story
The problem section moves one beat at a time. The painting stays pinned while the text moves on, and the scene changes with each beat: a balance arrives, a bad actor throws forged numbers at your app, a payout goes out on the wrong one, and then the proof rejects it.
By the time the word verified turns into a badge, you have seen exactly why it matters.
Provenance as a passport. Each step in the data's life is stamped as it happens. Pick a feature to change the scene.
Objects people already trust
Proofs are abstract, so I borrowed objects people already trust to vouch for things: a passport with stamps, a printed receipt, a floppy disk for size, a departure board for speed.
They turn an invisible idea into something you can look at, and they make a technical page fun to scroll.
Under the hood, live. Pick a table size and the departure board flips to the measured time to verify, and the stack of paper grows with it. Run a query to print its receipt.
Eleven use cases, each with its own small scene. Open a category and pick one.
Paintings instead of neon
Every scene sits on a public domain landscape painting from The Met or the Art Institute of Chicago. It makes a crypto product feel calm and trustworthy, and very different from the usual dark neon.
Each painting carries a small provenance stamp that links to where it came from. A site about proving where data comes from proves where its own pictures come from.
Hover the footer and it prints a receipt for your visit: sections read, proofs checked, trust required 0.00.
The 404 runs a query for the missing page and prints a receipt, with a small game on each one.
Idea to code
I took this from the first idea through to the design and the build. It is built in Next.js with Tailwind and Motion, so the animation was tuned in the browser at real speed rather than described in a prototype.