Send USDC to your Folio address on Base or Arc. A few minutes later it’s in Funding, on Solana. You didn’t approve anything, and your phone could have been off.
Folio’s server signed that move. It never had your private key, and it couldn’t have sent your money anywhere else.
Folio’s deposit signer is an extra signer on your Base and Arc wallet that can sign exactly two transactions, and both of them send your USDC to your own Solana account.
Two calls. Privy refuses the rest.
Your wallets come from Privy. Their private keys live in Privy’s secure enclave, and your Privy sign-in owns them. Folio’s app and server never see a key.
Folio joins your EVM wallet, the one with the same address on Base and Arc, as an additional signer. That signer carries a policy written for you alone, and Privy checks every request against it before it signs. The policy allows two calls:
- Approve. Let Circle’s CCTP messenger move your USDC.
- Burn. Call
depositForBurnon that messenger, with the recipient fixed to your own Solana USDC account, a maximum fee of zero and standard finality.
Privy refuses everything else. That covers a USDC transfer to any address, Folio’s included, a burn to someone else’s Solana account, a burn that pays a relayer fee, and a call to any other contract, token or chain.
The most Folio’s signer can do with your Base or Arc wallet is deliver your USDC to you.
The approval’s amount isn’t capped, and it doesn’t need to be. The messenger only pulls USDC when your wallet calls depositForBurn, and the only burn Folio’s signer can sign pays you.
Who can do what
Folio’s server does hold a key, the authorization key for its signer. Your money isn’t safe because that key is hard to reach. It’s safe because the rule lives at Privy, not in Folio’s code. A bug in Folio’s server can build a wrong transaction, and Privy still won’t sign it. A stolen signing key can only send your USDC to you.
The policy itself is administered with Folio’s Privy app credentials, and the signing key on its own can’t change it. When your signer is set up, Folio also reads the policy back from Privy and compares it rule by rule. A mismatch keeps Base and Arc from being marked ready and alerts Folio’s team.
Your phone adds the signer, not Folio
Folio’s server can’t add itself to your wallet. Your phone does that when you choose to set up Base or Arc deposits, under your own Privy session.

- Identity check. Your phone sends Folio only your identity token. Folio checks Privy’s signature on it, that it was issued for Folio, and that it hasn’t expired.
- Grant. Folio answers with a grant that names the signer to add and its policy. The grant is tied to this sign-in and expires after ten minutes.
- Confirm. Your phone adds the signer, usually with nothing to tap. Folio then reads your wallet back and marks Base and Arc ready only if its signer appears exactly once, with exactly your policy.
Folio never asks for your private key, never gets a token that can act as you, and you never sign a blanket approval.
One deposit, end to end
Say you add 50 USDC from Base.
- Open Deposit, choose Base and tap Prepare deposit. Folio watches your address for 24 hours, and Check again starts a new window.
- Send USDC from any wallet. Folio’s server sees your balance rise.
- If your wallet can’t cover the network fee for the next two calls, Folio tops it up from its own fee wallet, within a cap.
- Privy signs the approval, then the burn. Folio sends both from your wallet.
- Circle attests the burn. Folio submits the mint on Solana and pays its fee, plus the cost of opening your Solana USDC account if you don’t have one yet.
- 50 USDC lands in Funding, and the Deposit screen says Cash added to Funding.

This is CCTP, Circle’s Cross-Chain Transfer Protocol. Nothing is wrapped and no pool sits in between. Your wallet burns the USDC on Base, Circle attests the burn, and the same amount is minted to your Solana account.
What you see when it waits
Folio checks a few conditions before every sweep. If one isn’t met, the deposit waits and the app tells you why in one sentence:
| When | The app says |
|---|---|
| Base and Arc aren’t open for your account | “Deposits from Base and Arc aren’t open for this account yet.” |
| Folio’s signer is missing | “Briefly unavailable. Check back soon.” |
| A signing request didn’t finish | “We couldn’t finish preparing your deposit. Try again in a moment.” |
| A Folio spending limit is reached | “Received. Arriving later than usual.” |
| Deposits on that chain are paused | “Base deposits are paused right now.” |
A waiting deposit isn’t lost. Folio keeps track of it, reuses the transaction it already prepared, and carries on once the condition clears.
If Folio’s signer ever disappears from your wallet, Folio notices at the next setup check or when Privy refuses to sign. It holds Base and Arc deposits, alerts its team, and your phone adds the signer again under your sign-in.
Solana doesn’t need one
Your Solana wallet has no Folio signer. The trades and transfers you start in Folio are signed on your phone, and Folio’s server signs only as the fee payer, so the network fee is on Folio. The deposit signer exists because money can arrive on Base or Arc while you aren’t there to sign.
The short version
- Your keys stay in Privy’s enclave, and your Privy sign-in owns your wallets.
- Your phone adds Folio as a signer on your Base and Arc wallet.
- Privy lets that signer sign two calls, both ending in your own Solana account, and refuses everything else.
Send it on Base or Arc. Find it in Funding.
Investing involves risk, including loss of the money you invest.
Updated 14 October 2026: Folio’s signer is added when you choose to set up Base or Arc deposits, not at sign-in.
