Your Security. Our Obsession.
Most wallets protect your private key. Lumina protects everything else.
Losing crypto doesn't always mean someone stole your seed phrase. The vast majority of crypto losses happen during everyday actions: sending funds to the wrong address, clicking "Approve" on a malicious contract, or connecting your wallet to a fake website. These are the attacks that target real users, every single day.
Lumina Wallet was built with one core belief: you should never have to be a security expert to stay safe. That's why we engineered three dedicated protection layers that analyze every action before you confirm it. No technical knowledge required. Just clear, instant, visual feedback — every time.
The Contextual QR Reader
Two specialized scanners. Zero ambiguity.
Lumina doesn't use a single "universal" QR scanner. We made a deliberate choice to build two separate, specialized scanners — each one dedicated to a single purpose.
The Send section scanner
Reads crypto addresses only. It automatically recognizes the format of the scanned code — whether it's a bitcoin: URI, an ethereum: URI, a solana: address, a ripple: address, or a raw address string — and pre-fills the destination field for you. If the QR code scanned is not a valid crypto address, the transaction is immediately blocked with a clear error message. There is no ambiguity, no misrouting, no room for error.
The WalletConnect section scanner
Reads dApp connection URIs only. These are the QR codes generated by DeFi platforms, NFT marketplaces, and Web3 applications when they ask you to connect your wallet. If the scanner detects a valid wc: URI, it initiates a secure pairing session via the WalletConnect v2 protocol — the open-source standard used by Uniswap, OpenSea, Rainbow, and virtually every major Web3 application. Any other type of QR code is rejected with an explicit error message.
Why this separation is a security decision
A "universal" scanner would increase the attack surface. A malicious QR code presented in the wrong context could trigger unintended actions. By restricting each scanner to its precise role, Lumina ensures that a QR phishing attempt is always caught — even if the user opens the wrong section. The scanner cannot be tricked into doing something it wasn't designed for.
Supported address formats (Send section)
Lumina's QR scanner recognizes and validates addresses across all supported blockchains:
- Ethereum and all EVM-compatible chains: Polygon, BNB Smart Chain, Arbitrum, Optimism, Base, Avalanche, Fantom, Cronos, Gnosis
- Bitcoin: Legacy (1...), P2SH (3...), SegWit and Native SegWit (bc1...)
- Solana
- XRP (Ripple)
- Tron
The Address Security Audit
Every address is a suspect until proven safe.
Before you can send a single satoshi, Lumina runs a comprehensive security audit on the destination address. This happens automatically, every time, without you having to do anything. The entire process completes in under 3 seconds.
The Address Security Audit operates in two stages that run the moment you enter or scan a recipient address.
Stage 1 — Instant Local Checks
Under 1 millisecond. Entirely on your device. No internet connection required.
The first stage happens locally, with no data leaving your phone. Lumina immediately checks:
- Address format validity — Lumina performs strict format validation for every supported blockchain. For Ethereum and EVM-compatible chains, this means full EIP-55 checksum verification using the official keccak256 algorithm — a single incorrectly capitalized character is detected and rejected. For Solana, base58 encoding validation. For Bitcoin, correct prefix rules: bc1 for Native SegWit, 1 for Legacy, 3 for P2SH. A malformed address never reaches the network.
- Null address detection — The address 0x000...000 is the Ethereum burn address. Sending funds to this address means they are gone forever — permanently and irreversibly. Lumina automatically detects and blocks any attempt to send to this address.
- Self-send detection — Lumina compares the destination address against your own active wallet address. If they match, the operation is flagged for confirmation.
Stage 2 — Real-Time Threat Intelligence
Under 3 seconds. Via GoPlus Security API. EVM chains only.
The second stage connects to GoPlus Security, one of the most comprehensive and widely trusted Web3 threat intelligence platforms available. GoPlus maintains a continuously updated database of malicious addresses and contracts. Lumina queries this database and checks for three specific threat types:
- Blacklisted addresses — Addresses identified and flagged by the security community as belonging to known scammers, hackers, or fraudulent operations. If you are about to send funds to a wallet used in a previous attack, Lumina will know.
- Phishing addresses — Addresses associated with active phishing campaigns — fake websites, fake token airdrops, or impersonation attacks. Cross-referenced against GoPlus's live threat feed.
- Honeypot contracts — Smart contracts engineered to accept incoming funds but make it technically impossible to withdraw them. Frequently disguised as promising token launches or high-return schemes. Lumina identifies them before you interact.
On-chain transaction history — In parallel, Lumina queries the Ethereum RPC directly to check the number of outgoing transactions from the destination address. If the address has never sent a single transaction, a yellow warning is displayed. A brand-new address is not necessarily dangerous — but it is unusual enough to deserve a second look.
The result — clear, visual, unmistakable
| Result | Level | Meaning |
|---|---|---|
| 🟢 Secured | Green | Address is valid, clean, and has a normal transaction history. Safe to proceed. |
| 🟡 Warning | Yellow | Address is valid but has no outgoing transaction history, or belongs to a non-EVM chain where GoPlus data is not available. Proceed with caution and verify with the recipient. |
| 🔴 Danger | Red | Address is blacklisted, linked to phishing, identified as a honeypot, or has an invalid format. Transaction is blocked. |
You always see this result before the confirmation screen. You are never asked to confirm a transaction to a dangerous address without being explicitly warned.
The Transaction & Signature Decoder
What you see is what you sign. Finally.
The problem it solves
When you connect your wallet to a DeFi platform, an NFT marketplace, or any Web3 application, that application will frequently ask you to "sign" something. Most wallets — including MetaMask — display this signing request as a raw block of hexadecimal code:
This is completely unreadable to a normal human being. And that is exactly what hackers count on. They know that most users will simply click "Confirm" without understanding what they are actually authorizing. This is the core mechanism behind wallet drainer attacks — the most costly category of crypto theft in 2024 and 2025.
What Lumina does instead
Lumina's Transaction Decoder reads the raw hexadecimal data, identifies the type of action being requested from the function selector (the first 4 bytes of the calldata), and translates everything into plain, human-readable language before displaying it to you.
ERC-20 Token Approvals (approve)
When a dApp asks you to "approve" a token, it is requesting permission to move that token on your behalf. This is a normal and necessary part of DeFi — but the details are everything.
- Limited approval to a known protocol — The dApp requests permission to move a specific, defined amount of your tokens, and the requesting contract belongs to a recognized, trusted protocol (Uniswap, 1inch, Aave, Compound, Curve, PancakeSwap, OpenSea, Lido, and 20+ others). Displayed in green. Normal DeFi activity.
- Unlimited approval to an unknown contract — The single most common method used by hackers and wallet drainers. The dApp requests permission to move ALL of your tokens — now and forever — with no limit, and the requesting contract is not recognized. If you sign this, that contract can drain your entire wallet balance at any time. Displayed in red with a strong explicit warning.
Permit & Permit2 Signatures (gasless approvals)
These are EIP-712 typed signatures that grant token spending permissions without requiring a blockchain transaction — meaning they cost no gas fees and leave no obvious on-chain trace. This makes them the preferred tool of modern wallet drainers. Lumina parses the typed message, identifies the spender address, and displays a clear warning if the protocol is not recognized.
Native Transfers (eth_sendTransaction)
When a dApp requests a direct transfer of ETH or another native currency, Lumina decodes the transaction and clearly displays the exact amount being sent and the destination address. It also displays a reminder that blockchain transactions are irreversible.
Decentralized Exchange Interactions
Lumina identifies the routing protocol (Uniswap, SushiSwap, PancakeSwap, and others) and displays the native token amount involved. Known DEX routers are displayed in green. Important note: Lumina systematically guarantees the identification of the protocol and the native amount involved. The full decoding of all swap parameters is not guaranteed for every possible routing path, as DEX routing can be highly complex.
Arbitrary Message Signing (personal_sign, eth_signTypedData)
Some dApps ask you to sign a typed or personal message for authentication purposes — this is often legitimate. However, it can also be used maliciously. Lumina always displays an explicit warning before any off-chain signature is applied, regardless of the message content.
The five risk levels — color-coded
| Result | Level | Meaning |
|---|---|---|
| 🟢 Safe | Green | Known protocol, limited approval, or verified interaction. Normal DeFi activity. |
| 🟢 Low | Green | Minor interaction with a low-risk contract. Worth a quick look, but not alarming. |
| 🟡 Medium | Yellow | Unusual request or unverified contract. Verify before signing. |
| 🟠 High | Orange | Potentially dangerous request. Strong caution advised. |
| 🔴 Critical | Red | Known drainer tactic detected — unlimited approval from unknown contract, or malicious Permit2 signature. Do not sign. |
Note: Safe and Low share the same green color. The distinction informs you about the level of interaction, not the level of risk — both are considered safe.
Fake tokens — Blocked at the source
No unofficial token can ever appear in your wallet.
The problem: anyone can create a fake « USDT »
On EVM blockchains (Ethereum, BNB Chain, Polygon, Arbitrum…), any developer can deploy a token named « USDT », « USDC » or « Bitcoin ». Traditional wallets display everything the blockchain sends them — including thousands of spam tokens, sometimes with malicious links hidden in their name or description.
The consequence: you open your wallet one morning, you see « 10,000 USDT » you never bought, you click to sell… and you unknowingly sign a contract that drains your entire wallet.
How Lumina blocks these fake tokens
Lumina identifies every asset by its unique technical signature — the combination of network + official contract address — and NEVER by its name, symbol or logo. The principle is simple: if a token is not on our per-blockchain whitelist, it does not exist for Lumina.
- Strict whitelist per blockchain: only official, verified contracts (USDT, USDC, WETH, DAI, etc.)
- Targeted queries only: our backend only queries whitelisted contract addresses — fake tokens are never discovered
- Double verification: every returned balance is re-checked against the whitelist before display — no unknown contract can slip through
- Name, logo and symbol come from our verified metadata — never from the token's self-declared name
Concrete result
Fake USDT on Ethereum
A token named « USDT » deployed on any contract other than 0xdAC17F958D2ee523a2206206994597C13D831ec7 → will NEVER appear in your Lumina wallet. The real Ethereum USDT has one single official contract address; everything else is filtered out.
Fake USDT on BNB Chain
A token named « USDT » deployed on BNB Chain on any contract other than 0x55d398326f99059fF775485246999027B3197955 → will NEVER appear. Even if it carries the same name, the same logo, the same symbol as the real one — Lumina only looks at the contract + network pair.
This protection is always on, with no setup required. You have nothing to activate, nothing to check. If a token is not on the official whitelist for its blockchain, it will never reach your screen.
What Lumina Does — And What It Doesn't
What Lumina does
- Strict EIP-55 checksum validation (keccak256) for Ethereum and all EVM-compatible chains
- Real-time cross-referencing with GoPlus Security (blacklist, phishing, honeypot)
- Decoding of ERC-20 approve functions, permit and permit2 signatures
- Recognition of 20+ reference DeFi and NFT protocols
- Plain-language display of the requested action before any signature
What Lumina doesn't do — and why honesty matters
Lumina does not simulate the execution of your transaction. Tools like Tenderly or Blockaid can predict the exact impact of a transaction on your balance by running a full simulation before it is broadcast. This level of analysis costs several dollars per transaction in infrastructure and is not compatible with Lumina's self-hosted mobile model. Lumina analyzes declared intentions — not predicted outcomes.
Lumina does not replace your judgment. No scanner is infallible. We give you the tools to make an informed decision. The final call is always yours.
We believe that being transparent about what we do and don't do is itself a form of security. In a space full of products that overpromise, honesty is a feature.
Why Three Layers, Not Ten
We deliberately limited Lumina to these three scanners. Every additional layer would add friction without meaningful benefit for the vast majority of users. These three layers cover the three most common attack vectors in 2026:
- Human error on the destination address → Scanner 2
- Phishing via opaque transaction signature → Scanner 3
- Manual address copying vulnerable to clipboard malware → Scanner 1
Simple. Direct. Factual.
Lumina Wallet — Security without the lies.