Fuyu features

Start with your private account#

Open a Fuyu account to scan its notes and prepare proofs in the browser. The account holds encrypted access material and receiving keys for one Pool. Your funding wallet, recovery wallet and spending controller each have a separate job. When someone connects a wallet, keep the private account they already opened.

The same notes can fund a payment, a swap or an Earn deposit. What happens next depends on the asset: receiving vault shares gives you shares, and you redeem them separately to get the underlying token. Recovering account keys restores access to notes. You still need to pass source checks, meet venue conditions and collect any controller approvals.

Choose a guide#

Start with the task you want to build. Then check that your network enables the required assets, routes and contracts, and that your app build allows transactions.

All feature guides#

The feature IDs below come from the product specifications. They cover account setup, receiving, payments, DeFi, approvals and recovery. Each link opens the guide for that task, including the network requirements and what to do when a step cannot continue.

Set up access and receiving#

The app can create a Passkey plus paper-recovery account, a paper-only account, or an account with optional wallet recovery when the deployment supports it. Several passkeys can open the same account and earlier keys. Removing one requires a key change and moves to protect earlier funds. Include new receiving instructions and late payments to old keys in your recovery flow.

The full private address works without a name. Names need a configured registry, while receiving through a 0x wallet address requires a public registration. Reusable deposit addresses accept ordinary wallet or exchange transfers under fixed invoice terms. Choose the method that fits the payer, and explain what it publishes and how uncredited money is recovered.

Build payments, streaming and DeFi#

Private send creates encrypted outputs for the recipient. Claim links let a named wallet claim before a deadline, even if its owner has no Fuyu account. Batch payments put several proved steps into the configured router flow. Payment-session streaming uses signed cumulative vouchers and the session-payment core. If your app schedules private sends instead, it must handle timing, balances and approval for each send.

For DeFi, choose an enabled adapter and the input/output asset pair it supports. The proof includes the input, minimum output, execution context and controller. A two-stage action needs a later append of its reserved outputs; a one-transaction action settles them together. Check route admission, liquidity and withdrawal windows before offering a venue. An adapter in the repository may still be disabled on your network.

Recover interrupted work and review disclosure#

Save pending authorizations in encrypted storage before they leave the browser. If a wallet, relay or page stops responding, look up the original operation in authenticated history. Keep checking an unknown result. A second proof can leave two authorizations able to spend the same inputs.

Audit answers need a separate review. The holder reads the questionnaire, checks what it reveals and generates supported proofs locally. A payment, receiving name or balance does not grant access to private history. Anyone receiving an exported answer should verify it against the request and finalized snapshot.

Check your network before funding#

Open the contracts and testnet guide. Match the chain ID, Pool address, domain, deployment block, runtime code and proof artifacts. Check token support, action routes, name registry, relay fees and Safe support for that Pool.

These guides cover the client and protocol implementation. Feature availability is set by the deployment: a read-only preview cannot transact, a disposable fork is a test environment, and a feature may need additional configuration on the public app. Mainnet deployment, physical-authenticator certification and independent audit status need their own release records. Check those records before choosing a production environment.