The wallets you need

Some wallets only receive; others have to sign. Every one of them is connected through your wallet app and proven with a signature — an address is never typed in.

📷 Screenshot placeholder — Settings, the Receiving wallets and Connected wallets cards.

Your business unit uses wallets for two different jobs. Receiving wallets are where revenue lands when you withdraw it. Connected wallets sign and pay: the charges the platform bills you, prize funding, and — on your own account — anything personal. Both kinds are set the same way: connect the wallet, approve a signature, done. The platform never holds a key, and it never accepts an address you paste in, because a signature is the only proof that the wallet is yours.

Receiving wallets

A receiving wallet is a plain destination. Revenue you withdraw is paid to it; nothing is ever signed from it.

There are three layers, and a withdrawal uses the first one it finds:

1. Project wallet — set on the project's page, in the Payout wallets card.
2. Organisation wallet — set on the organisation's page, in the same card.
3. Business-unit default — set in Settings → Receiving wallets → Default payout. Used when neither the project nor its organisation has a wallet of its own.

Your business's share of claiming, project and bonus fees is paid out the same way.

A project withdrawal checks project → organisation → default; an organisation withdrawal checks organisation → default. The recipient is resolved on the server and shown read-only on the withdraw form together with its source — Project wallet, Organisation wallet or Default payout wallet. If no layer has a wallet the form shows No wallet set, and a request is refused until you add one.

Each scope holds one wallet per chain. Connecting a new wallet to a scope replaces the old one, and a wallet can be removed outright. Only Solana wallets can be set today.

Connected wallets

Settings → Connected wallets holds the wallets that sign. Spending needs a signature, so these cannot be typed in either: you connect the wallet here, and later approve each transaction in your wallet app.

• Fee payer — the wallet your business unit pays platform charges from, such as storage and minting when a project launches, and the wallet a community project's prize vault is funded from. It is the only wallet a prize can be funded from, and the one refunds return to. A charge that needs it stops with Connect and verify a Fee payer wallet in Settings → Connected wallets first until it is set.
• Ads spending — the wallet promotions are paid from, and the only one: the Promote wizard names it on the Review step, the Pay step refuses a wallet app that is on another account, and a payment sent from any other address is not accepted. Until one is saved, Continue to payment stops with Save an ads-spend wallet first.
• Personal — your own account's linked wallet, the same one shown under My Profile → Security → Linked wallet. It belongs to you, not to the business unit.

One wallet per purpose per chain; connecting another replaces it. Disconnect removes it.

Treasury wallet

A treasury wallet pays for treasury buybacks and receives the SOL from treasury sales. Set an organisation's on its page in Organisations, in the Treasury wallet card, and give a project its own on the project page. A project uses its own first, then its organisation's; with neither, treasury trades are unavailable for it. It is connected and signed for like every other wallet. Nothing is ever spent from it without your say: each treasury trade asks the wallet to sign one approval for exactly that order. See Treasury trades: buybacks and sales.

How connecting works

📷 Screenshot placeholder — Connect wallet, then the Use button with the wallet's signature prompt open.

1. Click Connect wallet. Your wallet app opens a picker the first time; afterwards the button names the wallet already connected.
2. Click Use on that address. The console asks the server for a one-time message that names this site, this purpose and the address.
3. Approve the signature in your wallet. The server checks that the message was signed by the address it names, then saves the wallet with a verified stamp.

The message is specific to its job: a signature given to set a receiving wallet cannot be replayed to set a spending wallet, or to sign in. If the request expires before you approve it, reconnect and try again.

Nothing here moves money. Connecting proves control; the only wallets that later spend are the ones you approve each transaction from.

Which wallet does what