ZooBC Signer

ZooBC Signer keeps your keys on your device and signs transactions where you are. ZooBC Signer is a key manager and transaction signer for the ZooBC blockchain. Your account keys are stored locally in an encrypted vault, and transactions are signed only after you approve them, whether you start them yourself in the extension or a website asks you for a signature. HOW IT WORKS When a ZooBC-compatible site wants to work with your accounts, it asks the extension for a connection. Nothing is shared until you approve that specific site, and you choose which accounts it can see. Approvals are per-site and you can revoke any of them at any time from the Sites tab. When a connected site requests a signature, the extension decodes the transaction itself and shows you what you are actually signing: the recipient, the amount, the network fee and the total leaving your account. You either approve it or reject it. Nothing is signed silently. WHAT YOU CAN DO Create new ZooBC accounts or import existing ones, with support for several address formats, including Ethereum-style and Bitcoin-style addresses, all of them ZooBC accounts on the ZooBC network. See your balances and a history of your activity across accounts. Review and approve each transaction with a decoded summary and an estimated network fee before you sign. Configure multisig accounts. Switch between MainNet and TestNet, or point the extension at your own RPC node. Grant time-limited session keys for in-game moves, so you are not prompted for every move. You are notified each time a session key signs something, and you can revoke it. SECURITY Your vault is encrypted with AES-GCM using a key derived from your password with PBKDF2-SHA256 at 600,000 iterations. The decrypted key exists only in memory while the extension is unlocked. Optional passkey unlock using WebAuthn PRF, so you can unlock with your device biometrics instead of typing a password. Auto-lock after a period of inactivity that you choose, from 1 to 240 minutes, defaulting to 15. When it locks, the decrypted key is wiped from memory and connected sites are told the signer is locked. Per-site connections that you grant explicitly and can revoke individually. No analytics, no telemetry, no crash reporting, no tracking of any kind. All transaction decoding and signing happens locally on your device. WHAT LEAVES YOUR DEVICE Your seed phrases and private keys never leave your device. They are never transmitted anywhere, by anyone, for any reason. The extension does talk to ZooBC network nodes, because that is how a blockchain works. It reads account balances, fee estimates and transaction status, and when you approve a transaction it broadcasts the signed result to the network. By default these requests go to the official ZooBC MainNet and TestNet nodes; you can replace them with your own node URL in Settings if you prefer. PERMISSIONS Storage is used to keep your encrypted vault and settings on your device. Alarms is used for the inactivity auto-lock. Notifications is used to tell you when a session key signs a transaction. Access to all sites is needed because ZooBC applications are built by independent developers on their own domains, so the extension cannot know in advance where you will need to sign. The page script reads nothing from the sites you visit; it only listens for ZooBC signing requests, and it does nothing at all until you connect a site. IMPORTANT ZooBC Signer is non-custodial. You hold your keys, which means you are responsible for backing up your seed phrase. If you lose it and you lose access to your device, nobody — including us — can recover your accounts. Write it down and store it offline. SUPPORT Support: https://zoobc.pro GitHub: https://github.com/zoobc/Signer Privacy: https://zoobc.foundation/privacy-signer/