// your identity. your money. your wallet.
Self-custodial, one binary, nothing to sync. Your keys are generated and stay on your machine — the chain data comes from a node somebody else already runs.
The difference
A full node is the right tool if you want to validate the chain yourself. It is a poor tool if you want to check a balance on a laptop. Pecu is a light client: it asks a node the same questions your wallet would have asked its own, and it does not keep one.
If you do run verusd, not everything is wasted: for shielded transactions Pecu looks for the Sapling proving parameters your node already downloaded before it considers fetching its own. It will not read balances from it, though. The endpoints are the ones this build ships, one per chain, and they are not configurable — a node is where a wallet reads balances and hands over signed transactions, and a URL typed into a box is not the shape that decision should take.
Screens
Not mockups. Every image here is a reference screenshot the test suite renders and compares on each run — 150 of them, in both themes. A layout change nobody looked at fails the build.
Built in
Most of what matters in a wallet is where it declines to be clever on your behalf.
Generated locally, encrypted on disk with Argon2id at roughly three and a half times the OWASP interactive minimum. The interface crate cannot even name the type that carries a private key — that is a compile error, not a rule.
The review screen is decoded from the signed bytes: the outputs, the fee and the change as they actually are, not re-rendered from what you typed into the form.
A key can hold transparent and shielded funds. Choosing for you would decide whether a payment is traceable, silently. It asks.
Anything that could move value sits behind a typed confirmation — not only the main chain. Only the one chain positively known to be worthless is exempt.
An unknown price is a dash. A pool nobody has scanned says so. A zero is a number somebody measured. The wallet would rather admit a gap than fill it.
A test walks the log files on every run and fails the build if a key, a passphrase or a recovery phrase appears in one.
The trade
Not running a node means asking somebody else's. That is a real trade and it deserves a plain answer rather than a footnote.
Status
Built in public, with the reasoning written down as it goes. Here is what runs today and what is being worked on next.
Every decision, including the ones deliberately postponed, is written down in the repository. Releases will land here when they are ready to install.