# Pelagus

> Pelagus is the community-owned, open-source browser wallet for Quai Network. It is fully self-custodial: keys are generated and stored on the user's device and every transaction is signed locally with explicit approval. Pelagus supports Quai's dual-token model (QUAI and Qi), moving value across Quai's sharded multi-chain architecture, and connecting to Quai dApps through an injected EIP-1193 provider at window.pelagus. Website: https://pelaguswallet.io

## Key facts

- Type: Web3 wallet delivered as a browser extension (Chrome, Brave, Edge, Opera; Firefox from source).
- Network: Quai Network. Sharded into regions (Cyprus, Paxos, Hydra) and zones; default zone Cyprus-1, chain id 0x9.
- Assets: native QUAI (primary asset) and Qi (energy-based currency that tracks the cost of mining). Convert between them natively — no bridge.
- Custody: fully self-custody. There is no Pelagus account and no server that holds funds. Keys never leave the device; losing the recovery phrase means losing access.
- Open source: community owned and operated. Source: https://github.com/PelagusWallet/pelagus-extension
- Provider: injects an EIP-1193 provider at window.pelagus (announced via EIP-6963). Use quais.js to build and send transactions.
- Core features: create/import wallet, multi-account across zones, send/receive, built-in Swap, convert QUAI <-> Qi, connect to Quai dApps.

## Provider (window.pelagus.request({ method, params }))

- quai_requestAccounts / eth_requestAccounts: connect; prompts the user, returns authorized accounts.
- quai_accounts: connected accounts, no prompt.
- quai_chainId: current zone/chain id (e.g. 0x9).
- personal_sign: sign a human-readable message.
- quai_sendTransaction: build, sign, and broadcast a transaction (always requires on-screen approval).
- wallet_switchEthereumChain / wallet_addEthereumChain: change the active zone; fires chainChanged.
- wallet_requestPermissions / wallet_getPermissions: EIP-2255 permissions.
- Events (window.pelagus.on): accountsChanged, chainChanged, connect, disconnect.
- Build transactions with quais.js (not ethers) so addresses are sharded correctly: new quais.BrowserProvider(window.pelagus).

## Docs

- [Pelagus documentation](https://pelaguswallet.io/docs): user guide (install, accounts & zones, send/receive, swap, convert Quai/Qi, security) and developer guide (connect your dApp, provider reference, build on Quai).
- [Convert Quai to Qi](https://pelaguswallet.io/docs#convert): the dual-token model and how conversion works.
- [Connect your dApp](https://pelaguswallet.io/docs#connect): detect the provider and connect.
- [Provider reference](https://pelaguswallet.io/docs#provider): methods and events.

## Quai Network resources

- [Quai Network](https://qu.ai/): the network Pelagus is built for.
- [Quai docs](https://docs.qu.ai/): chain details, RPC, and protocol reference.
- [quais.js](https://www.npmjs.com/package/quais): JavaScript library for reading Quai state and building transactions.
- [QuaiScan](https://quaiscan.io/): block explorer.
- [go-quai](https://github.com/dominant-strategies/go-quai): official Go node implementation.

## Notes for autonomous clients

- Pelagus exposes no headless or remote API. The provider exists only inside a browser with the extension installed, and every signature or send requires explicit on-device user approval.
- To prepare transactions programmatically, use quais.js against a Quai RPC, then have the user sign/submit in Pelagus.
- Install: https://chromewebstore.google.com/detail/pelagus/nhccebmfjcbhghphpclcfdkkekheegop
- Support: https://support.qu.ai/