On this page

Build on Fuyu

Add private payments, asset operations and recovery to your application.

What you can build#

Fuyu stores funds in a shared Pool. Your client proves spends and encrypts recipient notes; the chain settles them. Applications can also use approved adapters for public venue calls while keeping the result in private notes.

The protocol checks note ownership and value conservation. Your application handles its service logic and interface, chooses a deployment and stores the data needed to resume interrupted operations.

How the wallet, Pool and disclosure tools fit together
How the wallet, Pool and disclosure tools fit together
Private Payments

Pay a private receiving address and return any remaining value as change.

Payment Links

Get paid from an external wallet or send a claim link to an unregistered recipient.

Batch Payments

Pay several recipients or combine small notes in one router transaction.

Asset Operations

Swap assets or enter vaults through approved routes, then recover the output in private notes.

Swaps

Use an approved Uniswap route and receive the returned tokens as a private note.

Earn & Vault Positions

Supply assets to a vault, track your private shares and use its redemption path.

Withdrawals & Exits

Withdraw to a public wallet and recover any private change after confirmation.

Migrate to Fuyu

Withdraw from another privacy protocol into a new Fuyu note on the same chain.

Multi-step Action Plans

Combine approved swap and vault steps into one action with a final output minimum.

Selective Disclosure

Prove a supported fact about your account without sharing its private history.

Account & Payment Recovery

Reopen your account or finish an interrupted payment using its saved authorization.

Safe Treasuries

Use private notes that also require approval from your Safe.

Fuyu features

Find the guides for account setup, payments, DeFi, approvals and recovery.

Receiving names and addresses

Choose a private address, name, registered wallet address or deposit portal for your payer.

Pay wallets with claim links

Send to someone without a Fuyu account, set a claim deadline and recover a claim that was interrupted.

History and reconciliation

Read account activity, check pending operations and understand what a history export contains.

Token balances and USD values

Keep token amounts precise, separate checking funds and show USD estimates without hiding missing prices.

Disclosure consent and policies

Review an audit request, share a supported proof and understand what policy grants can do.

Spending wallets and Safe approvals

Set up wallet B or Safe approvals and resume an operation without changing what was signed.

Encrypted recovery files

Save history and pending operations, restore them on another device and handle backup conflicts.

Gas sponsorship and fee reviews

See who pays gas, which operations are sponsored and how fees affect a public payout.

Choose a starting point#

FeatureUse it forResult
Private paymentsPay a private receiving accountA recipient note and any private change
Payment linksGet paid from external or unregistered walletsPortal credit or a controlled claim
Batch paymentsPayroll, multi-recipient sends and consolidationSpends that each authorize their own inputs and outputs
Asset operationsUse approved swap and vault routesA measured output note or private ticket
DisclosureLet a holder choose to prove an account factA verified answer to a supported question
RecoveryChange devices or finish an interrupted operationRecovered state and the original authorization
Swaps and EarnHold tokens or shares through approved venuesThe tokens or shares actually returned
MigrationWithdraw from a source into FuyuA new note on the same chain, with public linkage

Show the next action#

Track drafts, prepared proofs and pending approvals through submission, confirmation and note recovery. If a submission times out, show that its outcome is unknown. Two-stage actions also need a reserved-output state and a way to finalize it.

A payment status view can use public transaction records. Keep private witnesses on the holder's device; the backend does not need a plaintext account history to report transaction status.

Start with one payment#

Choose one supported asset and deployment. Send a payment, confirm its transaction and recover the recipient's note in another browser. Once that works, add controllers, more routes or service billing.

Use the guides below to check what each flow needs. An adapter's presence in the repository is not a supported route on every network; availability comes from the deployment you are integrating.