Receiving names and addresses
Choose a private address, name, registered wallet address or deposit portal for your payer.
Choose how you want to receive#
Open Receive to copy your full Fuyu address or an available receiving name. The address contains the public descriptor a sender needs to encrypt a payment to you. It gives no spending access. Show its address check so the payer can compare it with you through another trusted channel.
A private address belongs to one Pool domain and key generation. Sharing it reveals a receiving identity, but not your balance or owned-note list. Wait until the account and recovery record are ready before sharing. After a key change, share the new address and keep access to earlier keys for payments already on their way.
| Method | Use it for | What becomes public |
|---|---|---|
| Full fuyu1 address | Another Fuyu sender | The descriptor and any identity you connect to it |
| Configured @name | A name people can read and share | Name ownership, descriptor and address updates |
| Registered 0x wallet address | A payer who knows your wallet | The wallet's permanent association with its receiving descriptor |
| Reusable deposit address | An exchange or ordinary wallet transfer | Source, token, value and portal terms |
Choose a receiving name#
This client reads names from an immutable onchain registry configured in the frontend. It checks the chain, Pool, domain, registry runtime, deployment block and settlement-token code. If the registry is missing from the manifest, names are unavailable. There is no HTTP-directory fallback; you can still use your full address.
Choose an available two-word name or a handle made of letters and digits. Two everyday words are free. One rare word costs $2 and two cost $10. Handles cost $10 for 7–20 characters, $50 for 5–6 and $300 for 4. Shorter or reserved names are unavailable. These prices exclude transaction gas. Check the deployment's quote before buying.
Register a name and finish its checkout#
The app commits your name claim, waits until it can be revealed and checks the registration result. Your connected wallet confirms the registry transactions and pays gas. Paid checkout uses the configured USDC settlement asset and any eligible onchain name credit. Check the name, address descriptor, fee and escrow before paying.
The app saves checkout before releasing an authorization. When you reopen it, it reads the purchase from the registry and checks the original payment. It will not send a replacement automatically. If the purchase becomes credit, or a delayed payment reaches its closed escrow, continue recovery and check your credit balance before choosing another name.
Receive through your 0x wallet address#
Wallet-address receiving lets a Fuyu sender look up your 0x address and get a private receiving descriptor. Check its registration first. Registering, changing or revoking it needs the owner's typed signature and an onchain transaction. The app provides the ordinary EOA-owner path. The contract can verify other signatures, but the app has no Safe registration interface for this step.
Registration permanently connects your public wallet to the descriptor and its controller. Revocation stops new lookups; earlier records stay public, and someone who saved an old address can still pay it. Keep recovery for those earlier keys and check for late payments. RPC providers can see lookups. Use a full Fuyu address if you do not want to publish a wallet association.
Receive from an exchange or ordinary wallet#
Create a reusable deposit portal with a token, invoice amount limits, a finite invoice sequence and a fixed public fallback address. Check that you can access it before sharing its Ethereum address. Money transferred to the portal becomes a private note only after an eligible invoice is credited into the Pool.
Publish later invoice material if you want someone else to credit payments while you are offline. A wrong token, out-of-range amount, exhausted invoice sequence or disabled token needs the portal recovery flow. Public recovery reveals the fallback address and permanently closes private crediting for that portal. Stop sharing it once it is closed.
Check the recipient again before sending#
A name payment page looks up the receiving record when it opens. A pinned link also fixes the management identity, chain, Pool, address check and revision. Before preparing a proof and again before sending it, the controller checks that the record has not changed. If it changed or the lookup failed, review a fresh record.
A name identifies where to send money. It does not verify a person's identity, provide account recovery or prove a balance. If the name is unavailable, ask for the full private address through a trusted channel. If registration or payment is uncertain, check the original operation before repeating checkout.