app · /bonsai/app
the whole flow, in the browser
setup, requests, funding, paying, claiming, withdrawing, on Sepolia with test funds. proofs are made in the page; the wallet signs twice. a published client for your own code is coming.
share a link, get paid from any wallet. the amount and the two parties stay inside a proof; the ledger only learns that it checked out.
step through the flow, or watch it run once
no payment network is available until a Peal Links node is running. nothing here moves real money.
the problem
the same invoice, paid the ordinary way. three facts, and your income is public.
send a client one address for the invoice and they can look it up on the chain. every transfer carries both addresses and the amount, so the address is a window onto everything it has ever received.
the client paying you can read what everyone else paid you, what you paid out, and what you keep. nothing about it expires: the record stays there for anyone who looks later.
the usual answer is a new address per invoice. the moment funds move together, the addresses are one person again, and the record was public the whole time.
what Peal Links does
value moves between private accounts on a small ledger built for it. three steps from link to balance.
an exact amount in one asset, a title, an optional expiry. your account signs it, so a payer can check nothing changed on the way.
the payer funds a private balance from their wallet if they have none, then their browser makes the proof. the ledger checks it and records one commitment; the amount and the receiver stay inside it.
the receipt opening is encrypted to you and left in your inbox. you can be offline the whole time. your client verifies it against the ledger and claims it.
funds come in and go out through ordinary token transfers on the backing chain, which are as public as any other. everything between them is not.
create a payment linkexactly who sees what
the checkout at the top of this page is an illustration with fictional data. the real one at #/pay/… is signed by the payee's account, verified in the payer's browser, and proves the payment with the pinned ZK-Pari circuits from the Bonsai construction; a proof takes a few seconds on a laptop.
one wallet
nothing new to install or remember: one signature sets it up.
there is no second address to manage. your wallet is the thing you connect, the thing people pay, and the thing that recovers you.
on first use your wallet signs one authorization for a private account. the ledger holds one commitment for it; the balance itself stays sealed on your device.
the account’s state is also kept in an encrypted backup. wallets that sign deterministically open it with a signature; the rest get a recovery code, shown once. lose the device, keep the wallet, and the account comes back.
what is visible
every account on the ledger is one commitment. a payment changes two commitments and appends one receipt, and the proof that it was done correctly is 128 bytes. this is the honest list, not the brochure version.
| who | sees | does not see |
|---|---|---|
| the public ledger | which account acted, and when | the amount, the other party, whether it was a send or a receive |
| the backing chain | deposits and withdrawals: address, amount, token | which private account a deposit went to, or which payments happened in between |
| the payer | the amount, your display name and your wallet address | your balance, your other payments |
| you, the receiver | the amount and, for a payment to your address, who paid | the payer's balance or their other payments |
| Peal's directory | which wallet address owns which private account: the signed receiving profile you publish so others can pay your address | your payments, amounts or balance |
| Peal's services | request titles and amounts you publish, when a request is viewed, encrypted receipt envelopes, submission times and IP addresses | the contents of receipts, your spending key, your balance |
for developers
the core is a Rust crate over the pinned ZK-Pari circuits, compiled to WebAssembly and driven by a typed TypeScript client that runs in the hosted app; it is not published yet. a wallet holds the account opening and its private list of claimed receipts; the ledger holds one commitment per account and verifies every operation; an HTTP API sits between them for anything that is not a proof. amounts are integer base units everywhere.
app · /bonsai/app
setup, requests, funding, paying, claiming, withdrawing, on Sepolia with test funds. proofs are made in the page; the wallet signs twice. a published client for your own code is coming.
HTTP API · /links/v1
public reads need nothing and work from any language today. writes carry a proof or an account signature, so they wait for the published client. errors are problem+json with a stable code.
BASE=https://peal.network/links/v1 # the node: namespaces, circuit, signers curl $BASE/status # the public ledger: a proof per record, # no amounts, no counterparties curl $BASE/ledger/{ns}/history # what a payer reads when a link opens curl $BASE/requests/{id}
the node is not reachable from this page right now, so nothing is shown in its place.
agents
one skill carries the procedure, a shop recipe, the verification script and the words not to use.
curl -fsSL https://peal.network/skill/install.sh | sh
read the developer guidethe API
the ledger is replicated by Commonware simplex consensus; the circuits are pinned by revision.
what it is for
the receipts are yours. export them for your accountant, show one to a client, or show nobody. the chain does not get a copy.
questions
Each asset lives on one backing chain and is not interchangeable with the same symbol elsewhere. Right now: Ethereum Sepolia · USDC and tUSD · testnet funds (the node lists the live set at /links/v1/status).
A payment moves value between private accounts on the ledger, so the payer needs a balance there first. Funding is a normal token transfer into the gateway contract; it is credited once the chain has confirmed it. The checkout adds exactly what is missing as part of paying. From then on payments do not touch the chain.
When someone pays you, the ledger records a receipt commitment and your inbox gets the encrypted opening. Claiming is your client proving to the ledger that the receipt is yours and unclaimed, which adds the amount to your spendable balance. The app claims automatically while it is open; until then the payment shows as incoming.
Your account state lives encrypted on your device and in a backup the node stores for your wallet. Connect the same wallet on a new device: if it signs deterministically, one signature opens the backup; otherwise you enter the recovery code you were shown at setup. Peal cannot open the backup, and without the wallet or the code nobody can.
Yes. Each wallet gets its own private account, on the same device or on different ones, and switching wallets switches accounts. Peal never links two of your wallets to each other.
This build charges no fee on the private ledger. Deposits and withdrawals pay the gas of the backing chain in the usual way, and the checkout shows the estimate before you confirm. If a ledger fee is introduced it will be shown as a separate line first.
No. They are ordinary token transfers on the backing chain and are as public as any other. What stays private is everything between them.
Peal Links is built on the Bonsai private payment construction and its ZK-Pari proof system, published by Commonware. Peal is not affiliated with or endorsed by Commonware. The upstream implementation is pinned by revision; the trusted setup used here is a local development setup, and what the construction's security argument still leaves unproven is listed under what you are trusting in the developer guide.
one wallet signature to set up, and the link is ready to share.
no payment network is available until a Peal Links node is running. nothing here moves real money.