Every official release is built in an air‑gapped container on macOS, Windows and Ubuntu. The three artefacts are hashed with SHA‑256, and the build only ships if every byte matches across all OSes. Any attempt to tamper with the compiler, dependencies or CI pipeline results in a hash mismatch and an immediate build failure.

Download both the .sha256sum and .asc files that come with every installer. Run sha256sum -c to confirm the checksum, then run gpg --verify. Official builds are signed with maintainer key 0xA3126F54D23B18EF; the same key is pinned in Git and on the website.

No. Keys are encrypted with AES‑256‑GCM and stretched with scrypt 16k/8/1. Signing happens in an isolated WebAssembly sandbox and the raw private key material never touches the network or the Electron renderer.

Yes. Scatter accepts WIF, raw hexadecimal keys, BIP‑39 12/24‑word seeds and SLIP‑10 hardened derivation paths. For MetaMask users simply paste the seed phrase: Scatter will derive the same addresses (m/44'/60'/0'/0/x) so your balances appear instantly.

Vaulta Swap is an on‑chain AMM for EOS pairs. Scatter embeds the Vaulta SDK so you can add liquidity, claim LP rewards and execute swaps from the “Vaulta” tab — no browser required.

A session key is an ephemeral child key derived from your master seed. You decide which contract actions it can sign and for how long. Once the TTL expires Scatter invalidates the key automatically, reducing the blast radius of a compromised dApp.

Scatter is MIT‑licensed and completely free. You only pay network costs such as EOS RAM/CPU/NET, EVM gas or Tron energy. No hidden mark‑ups, no subscription, ever.

If the dApp uses Scatter‑JS v3 or Anchor‑Inject, the desktop signer is auto‑detected. For legacy integrations enable the WebSocket bridge (Settings → Connectivity) and paste the URI into the dApp when prompted.

Yes. Open the “Resources” panel, enter the desired CPU and NET stake amounts and click “Preview”. Scatter simulates the transaction locally and shows you the exact delta before broadcast.

Not at the moment. A read‑only portfolio and push‑signing companion app is planned for Q2 2026, but the desktop signer remains the security reference implementation.

Plug in your Ledger Nano X/S, Trezor T or Keystone. Scatter detects the device via WebHID/WebUSB/QR, shows the exact derivation path and requires an on‑device confirmation to prevent blind signing.

Without both the encrypted vault file and your master password an attacker cannot decrypt the seed. Restore your most recent backup on a trusted machine, then rotate permissions on any active session keys and smart‑contract permissions.

Please email security@scatter-wallet.com with a PGP‑encrypted report. We follow coordinated disclosure and pay bounties for critical issues that result in patches.

Ask on GitHub Discussions or join the #scatter channel on the EOSIO Slack. Core maintainers are usually online 09:00–23:00 UTC.