↓ Download
Security

Your keys are created
and stored locally.

Magnum generates and encrypts wallet keys on your computer. Transactions are signed locally before they are sent to the network.

Wallet keys are not stored on Magnum servers.

Private keys are generated on your computer and encrypted before storage. Public addresses and transaction data may be sent to network services when the app loads balances or broadcasts transactions.

AES-256 Encryption

AES-256-CBC with 100,000 PBKDF2 rounds. Decryption happens locally. The password never moves.

PBKDF2 Derivation

100,000 iterations. PBKDF2 increases the cost of password guessing attacks.

Mnemonic Phrase

A 12 or 24-word recovery phrase can restore supported accounts in a compatible wallet.

Watch-Only Mode

Monitor your portfolio without ever exposing private keys.

Zero Personal Data

No accounts, no KYC, no email, no phone. 100% anonymous operation.

Open Source

Fully auditable codebase on GitHub. Transparency is our security policy.

Threat Model

What we defend against. And what we can't.

No wallet stops every attack. Magnum is honest about which threats its architecture neutralises and which still depend on you.

✓

Magnum protects you from

  • · Exchange insolvency & frozen withdrawals
  • · Server-side breaches of customer keys
  • · Subpoenas demanding your transaction data
  • · Phishing through fake login emails (there is no login)
  • · Brute-force attacks against weak password hashing
✕

Magnum can't protect you from

  • · Losing a mnemonic stored in a screenshot
  • · Malware running on the same OS as the wallet
  • · Sending funds to the wrong network or address
  • · Approving a malicious smart-contract signature
  • · Sharing your seed phrase with "support"
Key Lifecycle

From password to signed transaction. Step by step.

Every key in Magnum follows the same path, generated, encrypted and used entirely on your device. Here's exactly what happens between your password and the blockchain.

Step 01

Entropy on device

256 bits of randomness are generated by your OS's CSPRNG, never on a server, never over the network.

Step 02

Mnemonic + seed

BIP-39 turns entropy into 12/24 readable words. BIP-32 derives every coin's private key from a single seed.

Step 03

Encrypted at rest

Your password runs through 100,000 PBKDF2 rounds, then AES-256-CBC seals the seed before it touches disk.

Step 04

Sign & broadcast

Transactions are signed in memory and broadcast to public RPC nodes. The key never leaves the encrypted vault.

Lives only on your device

Encrypted vault file in your local app folder. No cloud sync, no backup-to-server option, no escape hatch.

Recoverable from 12 words

Lose the device, keep the mnemonic, restore the entire wallet on any OS in under a minute. No accounts to recover.

Audits & Transparency

Read every line. Or hire someone who will.

Open Source

Code on GitHub

Crypto library, key derivation and signing routines all sit in public repositories. Forks and audits are encouraged.

Bug Bounty

Up to $5,000 USDT

Critical reports get paid in crypto, no NDAs, no corporate onboarding. Submit on GitHub and get a response within 48h.

Reproducible Builds

Verify what you install

Build from source and compare hashes against our signed releases, full instructions in the docs.