the honest faq.

Your dollars are USDC — a payment stablecoin issued by Circle and backed 1:1 by reserves under the GENIUS Act. The key that moves them is made inside your phone’s secure chip, the same one behind Apple Pay; we never hold it and cannot move your money. Every transfer settles on the Solana public ledger, so you can check it yourself.

A digital dollar: one USDC is always redeemable for one US dollar. It is issued by Circle, a regulated company, and every USDC is backed by cash and short-term US treasuries held in reserve. It moves on public ledgers in about a second, for less than a cent.

Your account is a passkey, and passkeys sync with your iCloud or Google account. Sign in on a new phone and it is back. If you want a second safety net, add a backup owner in settings — another device with its own key that can sign for the account.

Add money with a card or bank account through Coinbase; it arrives as USDC in your balance. To cash out, send USDC to any exchange or Solana address you control and withdraw from there. Nothing is locked.

Opening an account is free and there is no monthly fee. A transfer costs less than a cent in network fees. Trades include a small routing fee inside the quoted price. That is the whole list.

Your moji is the face on your account — the avatar a friend sees when you send them money, and the one that tells you when something lands. Its type is read from what the account actually does, not chosen. Six kinds: diplomat, trader, sentinel, oracle, sage, shadow.

A payment account for stablecoins — regulated digital dollars. Keys live in your device’s secure chip and can never be extracted; every transfer is signed by the same chip that guards Apple Pay. One account works for you (face id, no seed phrase), for your agent (the CLI), and for the shops that take it (the SDK), on Solana and seven EVM chains.

The Secure Enclave is a dedicated security chip inside Apple devices. Private keys are generated inside the chip and never leave it — there is no API to export them. All signing happens within the chip itself. Even if the OS is fully compromised, the keys stay safe.

Parts of it. The browser SDK — @soulpass/passkey-sdk v0.3.0 — is MIT and fully open source at github.com/SoulPass-AI/soulpass-passkey-sdk, as is the Agent Skill that teaches coding agents how to drive the CLI: github.com/SoulPass-AI/soulpass-cli-skill. The CLI itself ships as a free, publicly distributed binary — v0.2.0 at github.com/SoulPass-AI/soulpass, installable via Homebrew or the install script, every download SHA-256 verified. Its Swift source is not published yet.

A natural-language guide that teaches any coding agent how to use every soulpass CLI command. Instead of remembering syntax, you say "sell 100 USDC for SOL" — or swap, buy, trade, however you’d phrase it — and the skill translates that into the correct command for your account to sign.

Yours. The CLI on your Mac holds its own key in that Mac’s secure chip, and a one-time human-approved step registers it as an owner of the same on-chain account your phone uses. Money the agent earns lands in your balance; money it spends comes from it.

Yes — that is the device-link architecture. Run `soulpass link` on a new Mac to join a web-created account, or run `soulpass owner add --chain SOLANA --passkey` on your CLI Mac to add a web passkey to a CLI-created account — the web app walks you through it at /wallet/link. Either way a human-approved ceremony begins: the new device proves possession of its own key, an existing owner approves, and the new key is registered on-chain. Every device signs with its own key; nothing is ever copied.

The CLI needs an Apple Silicon Mac (M1 or later) — it signs with the Mac’s Secure Enclave. The web app runs in any browser with passkeys, and the iOS app (on the way) uses the iPhone’s Secure Enclave. All of them can control the same account via device link. There is no software-key fallback anywhere — hardware or passkey, never a .env.

Solana (mainnet-beta and devnet) plus seven EVM chains: Ethereum, Base, BSC, Polygon, Arbitrum, HyperEVM, Robinhood. Trades route via Jupiter on Solana and 0x on EVM; yield via Jupiter Lend and Aave V3; perps on Hyperliquid; prediction markets on Polymarket; native USDC bridging via Circle CCTP V2. One secure-chip root derives an Ed25519 Solana key and a secp256k1 EVM address — one chip, every chain.

Yes. Encrypted soulpass↔soulpass messaging is built in. Agents send text DMs, run structured trade flows (rfq, offer, accept, invoice, deliver, confirm), and stream messages over SSE. All encrypted with X25519 keys derived in the secure chip.

Yes — that is what @soulpass/passkey-sdk (v0.3.0, MIT) is for. `npm install @soulpass/passkey-sdk`, pass an amount and your Solana + EVM receiving addresses to one call, and the payer approves USDC with a single passkey tap. No account, API key, client secret, or custody: funds settle straight to your addresses. Full walkthrough at soulpass.ai/developers.

Yes, with the same integration. A person approves with face id in the popup; their agent pays from the CLI with the same account. Either way you get one chain-verified settlement to your address, and the SDK resolves only after both transfers are confirmed on-chain.