How we got here

The project used to be called ZkVanguard. People kept asking if we were a bond fund. It sounded like your dad's retirement plan. So we renamed it to ZKward. Same idea, slightly awkward to say out loud. You'll get used to it.

What it is, in one sentence

A savings pool that trades for you and shows its math, so you don't have to take our word for it.

How it works, plainly

You put in USDC. A small crew of computer programs reads what people are betting on in prediction markets and measures every signal against what actually happens. Money only follows a signal once it has proven itself. The rules can be checked with a zero-knowledge proof: a cryptographic receipt that shows a trade stays within its limits, without revealing it. You can make one yourself on the proof page today; attaching one to every trade is the next step.

Think of it as an autopilot with a black box flight recorder. Except the recorder is public, and the autopilot won't take off in bad weather.

Where it started

A hackathon weekend. Too much coffee. One question: if computers move real money, why does anyone trust their reasoning? We thought we'd answer in two days. It took eighteen months.

Along the way we won five hackathons and shipped on a handful of blockchains. Most of the test deployments lasted about an afternoon. SUI stuck. It's fast, cheap, and doesn't break when you look at it wrong. That's where the money lives now.

What we ship today

• A real pool on SUI mainnet. Small on purpose. The contract itself caps deposits at $10,000. We wanted to prove it works before scaling. Slow is the point.
• Eight safety switches that can pause the whole thing if something looks off. One tripped yesterday, after a rough day of testing (more on that below).
• A grading loop: every signal is scored against what the market did next, and only what holds up after costs is allowed to trade. So far nothing has held up. We publish that too.
• An on-chain record of every deposit, withdrawal and transfer. Not a screenshot.

Why we tell you when it loses

Most projects only talk about their wins. Right now, our test traders are losing slightly on paper, and the signals have not yet shown an edge after costs. We're telling you because that's the whole point. If you can't see the losses, the wins don't mean much.

Also, hiding a loss is how a small loss turns into a much larger one three months later. We tried that once. Do not recommend.

Who's making it

Mostly one person, working from nine time zones away from most of you. Computer science degree, some years at big companies, an unreasonable number of side quests. Funded by savings and small grants that pay out roughly around the time the founder starts skipping lunch.

The paper trader has occasionally cost more per month than the founder eats. We consider this on-brand.

Where this goes next

Two things need to happen. First, prove the trader stops losing money in the test pool. Then raise the deposit cap, one careful step at a time, with a real drawdown test at each step. If we skip a step, please yell at us on Telegram.