# Blip

> Blip is a self-custody Quai Network wallet for iOS and Android. It ships an in-app dApp browser that injects an EIP-1193-style provider at window.quai (aliased to window.pelagus and window.ethereum), and gives every dApp origin its own deterministic "app wallet" that can be auto-funded from the user's main vault. dApps that run on Quai run inside Blip with no SDK to install.

## Key facts

- Network: Quai Network. Default chain Cyprus1, chain id 0x9.
- Assets: native QUAI, private Qi, wrapped Qi (WQI), USDT.
- Custody: fully self-custody. Keys stay on device; there is no Blip account or remote wallet API. All signing happens on device with explicit user approval.
- App wallets: per-origin EOAs derived from the user's mnemonic. Derivation index 0 = main vault, 1 = referral wallet, 2+ = app wallets. The origin->index map is published as an encrypted on-chain snapshot (BlipEncryptedLookupRegistry).
- Provider id flags: isBlip, isPelagus, isQuai true; isMetaMask false; marker _isSwiftBlip. Also announced via EIP-6963 (eip6963:announceProvider).
- iOS app id: UAUQLZY5XP.me.blippay.blip. Android package: me.blippay.blippay. Universal links: blippay.me. Custom scheme: blip://.

## Provider methods (provider.request({ method, params }))

- quai_requestAccounts / eth_requestAccounts: connect, returns the app-wallet address for the origin.
- quai_accounts / eth_accounts: connected accounts, no prompt.
- quai_chainId / eth_chainId / net_version: current chain (0x9), no network round-trip.
- wallet_switchEthereumChain / wallet_addEthereumChain: change chain, fires chainChanged.
- personal_sign / eth_sign / quai_sign: message signing.
- quai_sendTransaction / eth_sendTransaction: build, sign, broadcast. eth_sendRawTransaction is NOT supported.
- wallet_requestPermissions / wallet_revokePermissions: EIP-2255 permissions.
- wallet_getProviderState: discover app-wallet address and funding features.
- blip_requestAppWalletFunding: top up the app wallet from the main vault (native auto-topup within nativeAutoTopUpLimitWei, default 1000 QUAI; token funding always needs approval).
- Events: accountsChanged, chainChanged, connect, disconnect.

## Deep links

- Open a dApp in the in-app browser: https://blippay.me/browser?url=<https-encoded-url> or blip://browser?url=<https-encoded-url> (HTTPS only).
- Referral: short links use https://blippay.me/r/<code> and blip://referral?shortCode=<code>. Legacy links still use https://blippay.me/referral/<code>?name=&q=&qi=&uqi= or blip://referral?code=&name=&q=&qi=&uqi=
- Contact/profile: https://blippay.me/contact?name=&q=&qi=&referralCode=

## Docs

- [Developer docs](https://blippay.me/docs): full guide — app wallet spec, referral design, deep links, in-app browser, provider reference, app-wallet funding, and a dApp quickstart.
- [AI agents section](https://blippay.me/docs#agents): what is and isn't automatable for autonomous clients.
- [Quai Network docs](https://docs.qu.ai/): chain details, RPC, and the quais.js library for building transactions.

## Notes for autonomous clients

- Blip exposes no headless/remote API to control the wallet. The provider exists only inside the in-app browser, and every signature or send requires on-device user approval.
- To prepare transactions programmatically off-app, use quais.js against a Quai RPC, then have the user submit/sign in Blip.
- Contact: hey@blippay.me