# one link. a private payment.

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.

[create a payment link](https://peal.network/bonsai/app) [how it works](#pl-how)

the public ledger**nothing yet**_a link is not a ledger entry_

illustration · fictional data

Mara Okaforwallet 0x8a3f…c21e

Brand illustration, final files

1,250.00USDC

referenceINV-0417

fee on the private ledgernone

awaiting payment

the receiver**link shared**_can close the laptop now_

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

## on a public chain, getting paid is publishing your income.

the same invoice, paid the ordinary way. three facts, and your income is public.

1

0x8a3f…c21eyour invoice address

### your invoice is a public address

exposed

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.

you shareone address

anyone holding it seesevery payment in and out

2

+1,250.00 USDC · a client

−80.00 USDC · a supplier

+2,400.00 USDC · a client

readable by anyone, forever

### every payment stays readable

on the record

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.

amountspublic

both partiespublic

for how longforever

3

fresh address A fresh address B ↓ funds move together one person again

### a fresh address does not hold up

linked

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.

a new address per invoicelinked when funds move

the historypublic the whole time

what Peal Links does

## the payment happens inside a proof. the chain only learns it checked out.

value moves between private accounts on a small ledger built for it. three steps from link to balance.

1

#/pay/**…** · signed

### one signed link

request

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.

amountexact, in one asset

signed byyour private account

paidonce; a second payer waits

2

G1G1Fr

48 + 48 + 32 = **128 bytes**

### proved in the browser

private

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 proof128 bytes

made onthe payer’s device, in seconds

the ledger learnsthat it checked out

3

**encrypted receipt**_waiting in your inbox_

### claimed when you are back

offline is fine

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.

the receiptencrypted to you

you need to beonline later, not now

claimed byyour client, checked against the ledger

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 link](https://peal.network/bonsai/app)[exactly who sees what](#pl-visible)

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

## your wallet is the only identity. the private account stands behind it.

nothing new to install or remember: one signature sets it up.

1

0xf5e0…f41cyour wallet

### your wallet is the identity

one address

there is no second address to manage. your wallet is the thing you connect, the thing people pay, and the thing that recovers you.

you connectyour wallet

people payyour wallet address

a second addressnone

2

**1 commitment** · no balance

### a private account behind it

private

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.

set up withone wallet signature

on the ledgerone commitment

your balancesealed on your device

3

**encrypted backup**_opens with your wallet_

### a backup only your wallet opens

recoverable

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.

opens withyour wallet, or the recovery code

lose the devicethe account comes back

Peal can open itno

what is visible

## exactly who sees what, and who does not.

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

## a wallet, a ledger, and a proof between them.

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`

### 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.

[open the app](https://peal.network/bonsai/app)[how a payment moves](https://peal.network/developers/links)

HTTP API · `/links/v1`

### JSON in, JSON out, any language

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.

[API reference](https://peal.network/developers/links-api)[run it in the playground](https://peal.network/developers/api)

agents

### hand it to an agent

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

[use it from an agent](https://peal.network/developers/agents)[the reference file](https://peal.network/skill/reference/links.md)

[read the developer guide](https://peal.network/developers/links)[the API](https://peal.network/developers/links-api)

the ledger is replicated by Commonware `simplex` consensus; the circuits are pinned by revision.

what it is for

## payments that are yours to disclose.

the receipts are yours. export them for your accountant, show one to a client, or show nobody. the chain does not get a copy.

-   **independent work**one link per invoice. the client pays it from a wallet; you receive it in a balance that does not publish your income to the chain.
-   **business invoices**a reference on the request, an exact amount, and a receipt you can export when your books need it. nothing exported unless you choose to.
-   **contributions**a fixed-amount link for a workshop seat, a membership or a collection. everyone pays the same; nobody learns who else paid.
-   **paying an address**no link at all: send to a wallet address that has activated private receiving, and the amount stays between the two of you.

questions

## the short answers.

Which networks and assets are supported?

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).

Why do I need a private balance?

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.

What does claiming a receipt mean?

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.

What if I lose my device?

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.

Can I use more than one wallet?

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.

Are there fees?

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.

Are deposits and withdrawals private?

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](https://peal.network/developers/links) in the developer guide.

## create a link and get paid privately.

one wallet signature to set up, and the link is ready to share.

[create a payment link](https://peal.network/bonsai/app) [see who sees what](#pl-visible)

no payment network is available until a Peal Links node is running. nothing here moves real money.

---
Source: https://peal.network/bonsai
