<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by ERA Wallet on Medium]]></title>
        <description><![CDATA[Stories by ERA Wallet on Medium]]></description>
        <link>https://medium.com/@erawallet?source=rss-45e39c886651------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*I8g1SqRIX7P5LcQPyx1KWA.png</url>
            <title>Stories by ERA Wallet on Medium</title>
            <link>https://medium.com/@erawallet?source=rss-45e39c886651------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 09:00:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@erawallet/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Gonka AI Bridge Exploit: How a Signing Key Change Enabled Unbacked Tokens]]></title>
            <link>https://medium.com/@erawallet/gonka-ai-bridge-exploit-how-a-signing-key-change-enabled-unbacked-tokens-48f6923fc595?source=rss-45e39c886651------2</link>
            <guid isPermaLink="false">https://medium.com/p/48f6923fc595</guid>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[cross-chain-bridge]]></category>
            <category><![CDATA[hacks]]></category>
            <category><![CDATA[cryptosecurity]]></category>
            <dc:creator><![CDATA[ERA Wallet]]></dc:creator>
            <pubDate>Thu, 19 Nov 2026 14:41:12 GMT</pubDate>
            <atom:updated>2026-11-19T14:41:12.952Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GY0Yrlol8I5Hct02Mtruvg.png" /></figure><p>On November 18, 2026, a bridge exploit targeting Gonka AI’s Ethereum bridge led to withdrawals of approximately $884,800 in stablecoins and the minting of 22 million WGNK tokens described as unbacked. <a href="https://x.com/blockaid_/status/2123121171390415065">Blockaid</a> reported that an attacker changed the bridge signing key before the unauthorized operations. Users’ wallet keys were not implicated.</p><h3>What Happened in the Gonka AI Bridge Exploit?</h3><p>Gonka is a decentralized AI computing network whose Ethereum bridge supports wrapped GNK (WGNK) and other assets.</p><p>According to <a href="https://thedefiant.io/news/hacks/gonka-bridge-exploit-drains-stablecoins-mints-wgnk">The Defiant’s examination</a> of Ethereum transactions, an attacker-linked address registered a new epoch signing key on November 18. Withdrawals and token minting followed within minutes. Investigators have not established why the bridge accepted that key.</p><h3>Gonka Bridge Attack Timeline</h3><ul><li><strong>18:00:59 UTC, Key Registration.</strong> An <a href="https://etherscan.io/tx/0xa6b23e579b004e47657fd8f963a1f5732c5063a7d6eb7f9d7b185cd05d487178">Ethereum transaction</a> registered a new BLS group key for the bridge’s epoch.</li><li><strong>18:01 UTC, Stablecoin Withdrawals.</strong> The attacker-linked address received <a href="https://etherscan.io/tx/0x37ac0f3d9b8ed415fa025f04fe61a6305f3569636c5b32e226800106f8d8e492">884,150.87 USDT</a> and <a href="https://etherscan.io/tx/0x7dcbc8fe3a5c47f1d7ca63386d1f9c1850447249701007cd8725afe166c16d58">647.74 USDC</a> from bridge reserves.</li><li><strong>18:02 UTC, WGNK Mint.</strong> The Ethereum contract <a href="https://etherscan.io/tx/0x31dd93ecd452dd0d8ca985b098bfee29fc5b16bc8256dbcc8c889f6538d0b31d">minted 22 million WGNK</a> that Blockaid characterized as unbacked.</li><li><strong>18:05 UTC, Token Burn.</strong> The same address burned 13 million WGNK. That Ethereum transaction alone does not prove that native GNK was released on Gonka.</li></ul><p>Blockaid initially estimated about $1.05 million in realized proceeds across roughly five transactions. This preliminary estimate is not interchangeable with the approximately $884,800 withdrawn in the two identified stablecoin transfers. The final impact remains uncertain.</p><h3>How Crypto Bridges Work and Who Trusts the Signature</h3><p>To understand how crypto bridges work, consider that Ethereum needs evidence of events on Gonka before releasing or minting assets.</p><p>For GNK moving to Ethereum, native tokens are placed in escrow on Gonka and WGNK is minted on Ethereum. For the reverse journey, WGNK is burned and native GNK can be released from escrow. Stablecoin routes use reserves.</p><p><a href="https://gonka.ai/docs/cross-chain-transfers/ethereum-bridge/overview/">Gonka’s official documentation</a> describes a validator-based BLS signature system. Validators collectively authorize outgoing operations, while the Ethereum bridge contract checks those signatures against the currently registered group public key. The contract must trust the correct key.</p><p>That group key changes at the start of each epoch, approximately once a day. The new key is supposed to be signed by the previous epoch’s key, creating a verifiable sequence. Anyone can submit the public update transaction, but the contract is <a href="https://gonka.ai/docs/cross-chain-transfers/ethereum-bridge/bridge-epoch-update/">designed to accept</a> only the next sequential epoch key with an appropriate validation signature.</p><p>Public submission does not authorize arbitrary keys. Why the suspicious update was accepted remains unresolved.</p><h3>Why Gonka Was Different From the Ankr Bridge Exploit</h3><p>The <a href="https://blog.era-wallet.com/ankr-bridge-exploit-valid-signatures-fake-receipts/">Ankr bridge exploit</a> involved a different failure. In November 2026, an attacker submitted forged cross-chain receipts referring to events on Optimism. Those receipts carried cryptographically valid signatures from a trusted signer, and Ankr’s Ethereum bridge released approximately $304,500.</p><p>At Ankr, the signed claims were false even though the signatures were valid. The critical question was whether the claimed source-chain events had actually happened. At Gonka, the observed concern appeared one stage earlier: the public key used to verify authorized bridge operations had changed.</p><p>Bridges must verify both the reported event and the authority attesting to it.</p><p>The <a href="https://blog.era-wallet.com/liquid-network-hack-4000-btc-multisig/">Liquid Network incident</a> offers another illustration of why signature arrangements must be evaluated alongside withdrawal rules. A multisignature structure is not a blanket guarantee that assets cannot leave through an unexpected path.</p><h3>Why Unbacked WGNK Can Still Appear in a Wallet</h3><p>Under Gonka’s intended mechanism, each WGNK created on Ethereum corresponds to GNK locked in escrow on the source network. Redemption depends on that relationship remaining intact. If tokens are minted without matching deposits, their recorded supply exceeds the assets available to redeem them.</p><p>Blockaid described the 22 million newly minted WGNK as unbacked. A token balance may still display normally in a wallet, move between addresses or trade on a market. None of those properties independently establishes that the issuer or bridge can redeem it for the underlying asset.</p><p>A market price does not guarantee redemption, and liquidity may disappear. The <a href="https://blog.era-wallet.com/arcus-accounting-bug-balance-not-proof-of-funds/">Arcus accounting exploit</a> showed a related distinction: a balance recorded by software is not necessarily proof of accessible funds.</p><p>The 13 million WGNK burn does not itself confirm a GNK release on Gonka.</p><h3>What to Check Before Using a Crypto Bridge</h3><ul><li><strong>Signing authority.</strong> Identify who approves withdrawals and how that authority is established. Check whether operators, validators or administrators can replace the keys that the destination contract trusts.</li><li><strong>Multisig and timelocks.</strong> Determine which actions actually require multiple approvals or a delay. A validator BLS group signature should not automatically be treated as an administrative multisig, and neither mechanism eliminates every contract risk.</li><li><strong>Reserves and redemption.</strong> Look for verifiable escrow or reserve balances and understand how wrapped tokens are redeemed. Stablecoin reserves on Ethereum and GNK backing WGNK are separate accounting questions.</li><li><strong>Emergency controls.</strong> Check whether the bridge has withdrawal limits, a pause function and clear procedures for activating them. Emergency restrictions may reduce losses but can also interrupt legitimate withdrawals.</li><li><strong>Incident disclosures.</strong> Prefer projects that publish contract addresses, technical explanations and specific recovery updates. An absence of further suspicious transactions does not demonstrate that the original weakness has been fixed.</li></ul><p>An audit can provide useful evidence about reviewed code, but its scope matters. A contract may verify a signature correctly while relying on flawed assumptions about how trusted signing keys are selected.</p><h3>How to Limit Exposure to Wrapped Assets</h3><p>A test transfer can expose network, destination or redemption errors, but cannot guarantee future security. Check both directions before a large transfer.</p><p>Consider whether a wrapped asset is needed after the intended cross-chain activity ends. Holding it indefinitely means continuing to rely on bridge reserves, key management and redemption mechanisms. Splitting transfers may limit exposure; different interfaces may share one contract.</p><p>Controlling your private keys lets you authorize your own wallet transactions. Once assets are locked in a bridge, their redemption also depends on infrastructure outside your wallet’s control.</p><h3>FAQ: The Gonka AI Bridge Exploit</h3><h3>What Caused the Gonka AI Bridge Exploit?</h3><p>Blockaid reported that an attacker rotated the bridge’s epoch BLS group key before unauthorized transfers and minting. The mechanism that allowed this key update to be accepted has not been conclusively established.</p><h3>How Much Was Taken From the Gonka Bridge?</h3><p>Identified transfers withdrew 884,150.87 USDT and 647.74 USDC. Blockaid separately reported a preliminary estimate of approximately $1.05 million in realized proceeds.</p><h3>What Happened to the 22 Million WGNK?</h3><p>The Ethereum bridge minted 22 million WGNK described by Blockaid as unbacked. An attacker-linked address subsequently burned 13 million WGNK, but the burn alone does not verify redemption on Gonka.</p><h3>What Is Bridging in Crypto?</h3><p>Bridging transfers value between separate blockchains, often by locking an asset on one network and minting a corresponding wrapped representation on another.</p><h3>How to Bridge Crypto More Carefully?</h3><p>Verify the official bridge contract, supported network, signing authority and reserves. Test the transfer and redemption process with a small amount, while recognizing that a successful test cannot rule out future infrastructure failures.</p><h3>The Bottom Line</h3><p>Gonka’s incident highlights a specific bridge security question: how does a contract know that a newly registered signing key is truly authorized? Cryptographic approval cannot secure reserves if the process establishing who may approve withdrawals is compromised.</p><p>Before transferring substantial funds, examine the bridge’s key-update rules, backing and emergency controls. Minimize unnecessary time in wrapped assets, and treat bridge solvency as a separate concern from the security of your own wallet.</p><p>Финальный CTA для Medium (на Publish0x удалить)</p><p>Protect your keys, and examine the infrastructure that holds your assets. Use code ERABLOG20 for 20% off: <a href="https://era-wallet.com/products?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=gonka-ai-bridge-exploit-261119-hk-04&amp;utm_content=crosspost_cta">Explore ERA Wallet</a></p><p>Originally published at <a href="https://blog.era-wallet.com/gonka-ai-bridge-exploit/">https://blog.era-wallet.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48f6923fc595" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Many Crypto Wallets Should You Have? Splitting Funds Without Creating New Risks]]></title>
            <link>https://medium.com/@erawallet/how-many-crypto-wallets-should-you-have-splitting-funds-without-creating-new-risks-dc6085043ee1?source=rss-45e39c886651------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc6085043ee1</guid>
            <category><![CDATA[self-custody]]></category>
            <category><![CDATA[seed-phrase]]></category>
            <category><![CDATA[cryptosecurity]]></category>
            <category><![CDATA[hardware-wallet]]></category>
            <dc:creator><![CDATA[ERA Wallet]]></dc:creator>
            <pubDate>Thu, 19 Nov 2026 14:38:20 GMT</pubDate>
            <atom:updated>2026-11-19T14:38:20.776Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NIuLBdX_X9frwQT0YuripQ.png" /></figure><p>Using one crypto wallet for long-term savings, everyday payments, and experimental DeFi transactions puts very different activities under the same security assumptions. One malicious approval or compromised recovery phrase can expose funds that were never meant to be involved in risky transactions.</p><p>Separating funds can limit the damage. But every additional seed phrase creates another backup to protect, another recovery process to remember, and another opportunity for human error. The useful question isn’t how many wallets you can create. It’s which risks actually need to be separated.</p><h3>Why Separate Your Crypto Wallets?</h3><p>Imagine keeping your savings in the same wallet you use to connect to unfamiliar decentralized applications. When you interact with DeFi, you may grant smart contracts permission to move specific tokens. Some ERC-20 approvals allow spending up to an unlimited amount. As <a href="https://ethereum.org/guides/how-to-revoke-token-access/">Ethereum.org explains</a>, these permissions can remain active until revoked.</p><p>An approval normally applies to a particular token, spender, and wallet address. It doesn’t automatically authorize spending from every address you control. That makes a separate DeFi wallet useful: you can limit its balance and avoid exposing long-term holdings to permissions granted during experimentation.</p><p>However, separate addresses don’t always mean separate secrets. If several accounts come from one recovery phrase, losing that phrase can compromise all of them.</p><h3>Three Wallet Roles Worth Considering</h3><h3>1. Everyday Wallet</h3><p>Your daily wallet handles routine transfers, payments, and smaller transactions. A hot wallet on your phone may be convenient for this role. The tradeoff in the cold wallet vs hot wallet decision is accessibility versus exposure to the connected environment.</p><p>Keep only what you reasonably need for regular activity.</p><h3>2. Long-Term Storage Wallet</h3><p>This wallet holds assets you don’t plan to move regularly. A hardware wallet can keep private keys and signing operations isolated from the general-purpose computer or smartphone used to prepare transactions. That reduces certain malware risks, although it doesn’t prevent someone from approving a malicious transaction.</p><p>For broader security considerations, see our guide to <a href="https://blog.era-wallet.com/hardware-wallet-security-decisions/">five hardware wallet security decisions</a>.</p><h3>3. Experimental Wallet</h3><p>This wallet is for new protocols, NFT mints, unfamiliar dApps, and other higher-risk activities. Set a fixed budget and avoid keeping significant balances there.</p><h3>One Seed Phrase or Multiple Independent Wallets?</h3><p>Hierarchical deterministic (HD) wallets can generate multiple accounts and addresses from one underlying seed.</p><p>The distinction matters for crypto wallet security:</p><ul><li><strong>Different accounts, same seed phrase:</strong> A malicious token approval on one address doesn’t automatically affect another. But someone who obtains the root recovery secret may reconstruct all associated accounts.</li><li><strong>Independent seed phrases:</strong> Each wallet has a separate root secret. Compromising one phrase doesn’t automatically reveal the others.</li></ul><p>The underlying derivation model is described in <a href="https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki">BIP-32</a>. You can also explore <a href="https://blog.era-wallet.com/what-is-a-crypto-private-key/">how private keys are created</a> and our separate article about <a href="https://blog.era-wallet.com/hardware-wallets-multiple-seed-phrases/">hardware wallets supporting multiple seed phrases</a>.</p><h3>The Hidden Cost of More Wallets: More Backups</h3><p>Every independent seed requires a recovery plan. Losing its only backup, confusing it with another phrase, or forgetting an additional passphrase can make the associated funds inaccessible.</p><p><a href="https://bitcoin.org/en/secure-your-wallet">Bitcoin.org’s wallet security guidance</a> covers these practical risks.</p><p>You can maintain a wallet inventory without recording any secrets:</p><ul><li><strong>Long-term: </strong>Purpose, supported networks, public addresses</li><li><strong>Daily: </strong>Purpose and spending limit</li><li><strong>DeFi: </strong>Connected protocols and active use</li><li><strong>Backup: </strong>Coded location reference, not recovery words</li><li><strong>Recovery test: </strong>Date and result of the last successful check</li></ul><p>Never put seed phrases, private keys, wallet passwords, or passphrases into this inventory.</p><h3>Passphrases and Wallet Passwords Are Not the Same</h3><p>A BIP-39 passphrase changes the cryptographic seed derived from the recovery phrase. Different passphrases create different sets of keys and addresses, even when the original recovery words are identical.</p><p>Under the <a href="https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki">BIP-39 specification</a>, the exact passphrase is necessary to reconstruct the intended wallet. Losing it can mean losing access to the associated funds.</p><p>An additional access password isn’t a substitute for an independent seed phrase, while a passphrase introduces another recovery secret you must preserve.</p><h3>How ERA Wallet Device Manages Multiple Independent Wallets</h3><p>ERA Wallet device supports up to 10 wallets, each with its own independent seed phrase. You can separate long-term savings, everyday transactions, and experimental funds without needing a different hardware device for every role.</p><p>Users can <a href="https://guide.era-wallet.com/02-add-another-wallet.html">create or restore wallets</a>, give them individual names, and switch between them on the same device. Each wallet can have its own <a href="https://guide.era-wallet.com/03-wallet-password.html">PIN or password</a>, or you can rely on the device-level PIN without adding another password to that particular wallet.</p><p>Consider a wallet used frequently for payments. You can leave it without an additional wallet password for convenience. When scanning a signing request, <a href="https://guide.era-wallet.com/06-scan-qr.html">ERA Wallet device automatically identifies the matching wallet</a>, provided that wallet doesn’t require separate unlocking. There’s no need to switch wallets manually or enter another password before reviewing the transaction. Signing still requires confirmation on the device.</p><p>Each independent wallet also has its own <a href="https://guide.era-wallet.com/04-backup-overview.html">backup options</a>. Recovery words can be recorded on paper or saved in encrypted form on an ERA Recovery Card. Three ERA Recovery Cards are included with ERA Wallet device.</p><p>You can back up one wallet to a single card or use multiple copies. Alternatively, <a href="https://guide.era-wallet.com/04-shamir-backup.html">Shamir Backup</a> can divide the recovery secret into shares. With a 2-of-3 configuration, any two shares can restore the wallet, while one share alone is insufficient. Each share can be stored on a separate Recovery Card.</p><p>ERA Wallet device also supports a <a href="https://guide.era-wallet.com/03-passphrase.html">BIP-39 passphrase</a>, allowing a distinct set of addresses to be derived from a recovery phrase. Restoring those addresses requires both the original phrase and the exact passphrase.</p><h3>How Many Wallets Are Enough?</h3><ul><li><strong>Long-term holding only: </strong>One wallet with a tested backup</li><li><strong>Holding and regular payments: </strong>Two roles: storage and daily spending</li><li><strong>Holding, payments, and DeFi: </strong>Three roles, including a limited experimental wallet</li><li><strong>Large or complex portfolio: </strong>Multiple independent storage arrangements and recovery procedures</li></ul><h3>FAQ: How Many Crypto Wallets Should You Have?</h3><h3>How Many Independent Wallets Can ERA Wallet Device Store?</h3><p>Up to 10 wallets, each with its own independent seed phrase. They can be named and configured with individual access settings.</p><h3>Does ERA Wallet Device Automatically Select the Right Wallet for Signing?</h3><p>Yes, for supported signing requests when the matching wallet has no separate wallet password. Password-protected wallets require manual selection and unlocking.</p><h3>Can ERA Wallet Device Back Up Multiple Wallets Using Recovery Cards?</h3><p>Yes. Each wallet can have its own card backup, and Shamir shares can be stored on separate cards. ERA Wallet device includes three ERA Recovery Cards.</p><h3>What Is a Crypto Wallet?</h3><p>A tool that manages cryptographic keys used to receive assets and authorize blockchain transactions. The assets themselves are recorded on the blockchain.</p><h3>What Is the Best Crypto Wallet?</h3><p>That depends on how you use crypto. Daily payments prioritize accessibility, while long-term storage places greater emphasis on key isolation, backup reliability, and recovery.</p><h3>Conclusion</h3><p>For someone who saves, spends, and explores DeFi, three wallet roles offer a practical starting structure. They don’t necessarily require three separate seed phrases.</p><p>Use independent keys where compromising one recovery secret would otherwise expose assets that should remain isolated. Then make sure every additional wallet has a recovery method you can actually maintain. The goal is a setup where access, exposure, and recovery remain understandable as your holdings and activities grow.</p><p>Финальный CTA для Medium (на Publish0x удалить)</p><p>Keep independent wallets organized on one device. Use code ERABLOG20 for 20% off: <a href="https://era-wallet.com/products?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=how-many-crypto-wallets-should-you-have-q-261116-02&amp;utm_content=crosspost_cta">Explore ERA Wallet</a></p><p>Originally published at <a href="https://blog.era-wallet.com/how-many-crypto-wallets-should-you-have/">https://blog.era-wallet.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc6085043ee1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Recover a Crypto Wallet With a Seed Phrase]]></title>
            <link>https://medium.com/@erawallet/how-to-recover-a-crypto-wallet-with-a-seed-phrase-213f0027169c?source=rss-45e39c886651------2</link>
            <guid isPermaLink="false">https://medium.com/p/213f0027169c</guid>
            <dc:creator><![CDATA[ERA Wallet]]></dc:creator>
            <pubDate>Wed, 18 Nov 2026 14:33:32 GMT</pubDate>
            <atom:updated>2026-11-18T14:33:32.875Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0myhrjcvVeN94mbApxD7sQ.png" /></figure><p>Losing a hardware wallet doesn’t necessarily mean losing your crypto. A seed phrase can restore access to your assets on a compatible wallet. But recovery doesn’t always end with your familiar balance appearing on screen. Sometimes a wallet accepts all 12 or 24 words, generates new addresses, and shows zero funds.</p><p>The problem may have nothing to do with missing crypto. Additional wallet settings can change which addresses are generated, even when the recovery phrase is correct. Here’s how crypto wallet recovery works, why it sometimes fails, and how to verify that your backup can actually restore access.</p><h3>What Happens to Your Crypto When You Lose a Wallet?</h3><p>Your cryptocurrency isn’t stored inside a hardware wallet. Assets are recorded on the blockchain, while the wallet manages the private keys needed to authorize transactions.</p><p>A recovery phrase allows a compatible wallet to regenerate those keys. If a device is lost, damaged, or replaced, you can typically recover access without asking the manufacturer to restore anything.</p><h3>How to Recover a Wallet Using a Seed Phrase</h3><p>Most wallets use hierarchical deterministic key generation. Under the widely adopted <a href="https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki">BIP-39 standard</a>, a mnemonic phrase, commonly containing 12 or 24 words, is converted into a cryptographic seed.</p><p>A typical recovery process involves four stages:</p><ul><li><strong>Choosing a compatible wallet.</strong> The new device or application must support the original backup format.</li><li><strong>Entering the recovery phrase.</strong> Words must appear in their original order. For hardware wallets, entering them directly on the trusted device is preferable to typing them into a computer.</li><li><strong>Regenerating the keys.</strong> The wallet derives private keys and addresses from the recovered seed.</li><li><strong>Checking the accounts.</strong> The user selects the relevant network and compares the restored addresses with the originals.</li></ul><p>However, a valid 12 or 24 word seed phrase doesn’t guarantee that every address will reappear automatically. Additional passphrases, derivation paths, and account settings may affect the result.</p><h3>Why Does a Recovered Wallet Show a Zero Balance?</h3><h3>1. The Wrong Network or Account Is Selected</h3><p>One seed phrase can generate addresses across multiple blockchains. A wallet application may not automatically display every supported network, account, or token.</p><p>Compare the original public address with the restored one. If they match, investigate the selected network, token visibility, and transaction history.</p><h3>2. The Derivation Path Is Different</h3><p>A single seed can generate many private keys and addresses. The derivation path determines which keys the wallet derives.</p><p><a href="https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki">BIP-44</a> defines one common hierarchical structure, but wallet implementations may use different paths or address formats.</p><h3>3. The Passphrase Is Missing or Incorrect</h3><p>An optional BIP-39 passphrase, sometimes informally called the 25th word, is a separate secret combined with the mnemonic during seed generation.</p><p>The same recovery phrase with different passphrases generates different wallets. Entering an incorrect passphrase doesn’t necessarily trigger an error. Instead, the wallet may display entirely different addresses.</p><p>If the original wallet used a passphrase, the recovery words alone won’t recreate the intended accounts.</p><h3>4. The Wrong Seed Phrase Was Restored</h3><p>Some hardware wallets support several independent seed phrases on one device, each requiring its own backup. We explored this distinction in our <a href="https://blog.era-wallet.com/hardware-wallets-multiple-seed-phrases/">comparison of hardware wallets supporting multiple seed phrases</a>.</p><h3>Can You Recover a Crypto Wallet Without the Complete Seed Phrase?</h3><p>A standard BIP-39 recovery phrase isn’t designed to be restored from an arbitrary incomplete set of words. Missing words can make recovery computationally difficult or practically impossible, depending on how much information remains.</p><p>An alternative is Shamir Secret Sharing, which divides a secret into multiple shares.</p><p>Under a threshold scheme, a predefined number of shares is required to reconstruct the secret. For example, a 2-of-3 configuration allows recovery using any two valid shares from the same set.</p><h3>How ERA Wallet Approaches Wallet Backups</h3><p>ERA Wallet supports several backup methods: standard 12- or 24-word recovery phrases, Shamir Secret Sharing, and ERA Recovery Card.</p><p>ERA Recovery Card stores an encrypted backup on an NFC card protected by a PIN. On a compatible ERA Wallet device, it offers an alternative to manually entering recovery words.</p><p>None of these methods allows the manufacturer to recover an unknown seed phrase or forgotten passphrase. The differences are explained in the <a href="https://guide.era-wallet.com/04-backup-overview.html">ERA Wallet backup guide</a>.</p><h3>Why Crypto Wallet Recovery Attracts Scammers</h3><p>Fake recovery services may promise to recover a lost seed phrase, fix a wallet error, or retrieve a missing balance. Their supposed solution often involves asking users to enter recovery words into a website or send them to a support representative.</p><p>Malicious browser extensions can imitate legitimate wallet applications and capture phrases during the import process. We examined this attack pattern in our <a href="https://blog.era-wallet.com/fake-crypto-wallet-extensions-seed-phrase-theft/">investigation of fake crypto wallet extensions</a>.</p><p>Storing recovery phrases as photographs creates another exposure risk. Malware can scan images for sensitive information, as explained in our <a href="https://blog.era-wallet.com/can-malware-steal-crypto-seed-phrase-from-photo/">analysis of seed phrase theft from phone galleries</a>.</p><p>If you’ve entered a recovery phrase into a suspicious website or application, treat it as potentially compromised. Restoring the same wallet on a new device doesn’t invalidate keys that an attacker may already possess. A newly generated wallet and transfer of remaining assets may be necessary.</p><h3>Why You Should Test Wallet Recovery Before an Emergency</h3><p>Testing while the original wallet is still accessible can expose these problems without requiring a real transaction.</p><p>A compatible spare hardware wallet can reproduce the keys from the backup. Comparing its public addresses with the originals provides evidence that the corresponding secrets and derivation settings were recovered correctly.</p><p>Resetting your only working wallet solely to test recovery introduces unnecessary risk, especially when the backup hasn’t yet been verified.</p><h3>FAQ: Crypto Wallet Recovery With a Seed Phrase</h3><h3>Can I Recover My Wallet on a Different Hardware Wallet Brand?</h3><p>Yes, provided the new wallet supports the original backup format, derivation paths, and other required settings. Using the same number of recovery words doesn’t guarantee complete compatibility.</p><h3>Why Does My Wallet Accept the Seed Phrase but Show No Crypto?</h3><p>Possible reasons include a different network, account, derivation path, incorrect passphrase, or the wrong recovery phrase. Comparing public addresses helps identify the cause.</p><h3>Can I Recover a Lost Crypto Wallet Without a Seed Phrase?</h3><p>Other recovery methods may be available if the original device still works or another valid backup exists. Without access to the necessary keys or recovery material, the manufacturer cannot recreate your wallet.</p><h3>What Is a Crypto Wallet Seed Phrase?</h3><p>It’s a sequence of words used to derive the cryptographic seed from which a wallet generates private keys and addresses. BIP-39 is one commonly used format.</p><h3>How Does a Seed Phrase Work?</h3><p>A compatible wallet converts the mnemonic and any optional passphrase into a cryptographic seed. It then derives the corresponding private keys and addresses using defined derivation rules.</p><h3>Conclusion</h3><p>Successful wallet recovery depends on more than keeping a copy of your recovery words. Passphrases, derivation paths, and account settings determine whether the restored wallet displays the addresses you expect.</p><p>The practical takeaway is to verify your backup while your original wallet is still accessible. Confirming that it reproduces the correct addresses is far easier than troubleshooting an unfamiliar recovery process after losing your device.</p><p>Verify your backup before you need it. Use code ERABLOG20 for 20% off: <a href="https://era-wallet.com/products?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=recover-wallet-seed-phrase-q-261115-04&amp;utm_content=crosspost_cta">Explore ERA Wallet</a></p><p>Originally published at <a href="https://blog.era-wallet.com/lighter-crypto-exchange-hack/">https://blog.era-wallet.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=213f0027169c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lighter Crypto Exchange Hack: $10.4M Lost Without a Smart Contract Exploit]]></title>
            <link>https://medium.com/@erawallet/lighter-crypto-exchange-hack-10-4m-lost-without-a-smart-contract-exploit-49b233a69081?source=rss-45e39c886651------2</link>
            <guid isPermaLink="false">https://medium.com/p/49b233a69081</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[defi-exploits]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[cryptosecurity]]></category>
            <dc:creator><![CDATA[ERA Wallet]]></dc:creator>
            <pubDate>Wed, 18 Nov 2026 14:30:16 GMT</pubDate>
            <atom:updated>2026-11-18T14:30:16.388Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m3R0FtuPk169D6KZbl6iAg.png" /></figure><p>On November 16, 2026, a crypto exchange hack involving decentralized perpetual futures platform Lighter resulted in approximately $10.4 million in USDC leaving the exchange. The attacker exploited compromised trading API keys rather than a smart contract vulnerability. Lighter suspended withdrawals, recovered approximately $5 million from an additional withdrawal attempt, and restricted API permissions.</p><p>The incident exposed a risk that smart contract audits alone cannot address: externally generated trading credentials may grant dangerous privileges even when the underlying protocol operates as designed.</p><h3>What Happened in the Lighter Crypto Exchange Hack?</h3><p>Lighter is a decentralized perpetual futures exchange operating on its own rollup with settlement on Ethereum. Users deposit USDC through an Ethereum smart contract, trade on Lighter’s infrastructure, and withdraw through the settlement contract.</p><p>According to <a href="https://www.bitquery.io/investigations/lighter-hack">Bitquery’s on-chain investigation</a>, 10,393,057 USDC left the Lighter Ethereum contract for a single address at 10:11 UTC on November 16. Within minutes, the wallet swapped approximately $10.36 million in USDC for ETH through CoW Swap. The funds were subsequently distributed across addresses connected to Hyperliquid activity.</p><p>Lighter <a href="https://x.com/Lighter_xyz/status/2122311006604984497">acknowledged the incident</a>, describing a suspected compromise involving an external party. Withdrawals and new public-pool creation were paused during the investigation.</p><h3>Lighter Attack Timeline</h3><ul><li><strong>Nov 16 | Withdrawal.</strong> At 10:11 UTC, an attacker-linked address received 10,393,057 USDC from Lighter’s Ethereum contract.</li><li><strong>10:13–17 | Conversion.</strong> Approximately $10.36 million in USDC was exchanged for ETH through CoW Swap.</li><li><strong>Later | Response.</strong> Lighter activated Guardian Mode and suspended withdrawals and new public-pool creation.</li><li><strong>Nov 16 | Recovery.</strong> Its Security Council returned approximately $5 million associated with a further attempted withdrawal.</li><li><strong>Nov 16 | Restored.</strong> Guardian Mode was disabled and deposits and withdrawals resumed.</li></ul><h3>How Did Compromised API Keys Lead to the Loss?</h3><p>An API key enables trading software to execute authorized operations without manual approval of every order. Market makers use these credentials to automate positions, liquidity, and order management.</p><p>According to <a href="https://x.com/i/article/2122382079644041216">Lighter’s technical postmortem</a>, affected accounts used third-party signing software that reused cryptographic nonces. A nonce is a value that must be unique for each signature. Under vulnerable signature schemes, nonce reuse with the same signing key can expose the key itself.</p><p>Lighter stated that its official SDKs generated nonces securely and were unaffected. The attacker obtained credentials used by external trading software, not the traders’ wallet seed phrases.</p><h3>How the Attacker Used Public Pools</h3><p>The stolen API credentials could not directly withdraw funds to an arbitrary wallet. Instead, the attacker used permissions that allowed transfers into public pools:</p><ul><li>Created a public pool using a compromised trading account.</li><li>Minted pool shares through a separate attacker-controlled account.</li><li>Transferred the victim’s funds into the pool without minting additional shares.</li><li>Redeemed the now more valuable shares and withdrew the proceeds.</li></ul><p>The <a href="https://x.com/i/article/2122382079644041216">incident report</a> describes an abuse of permitted account operations, not an exploit allowing arbitrary changes to smart contract balances.</p><h3>Why Smart Contract Audits Cannot Prevent Every API Key Attack</h3><p>Audits assess contract code, including accounting, authorization, and transaction validation. They do not certify every third-party application that produces cryptographic signatures. In this case, insecure nonce generation occurred outside Lighter’s official software.</p><p>Once the keys were recovered, the attacker submitted operations that appeared authorized under the existing permission model. Lighter subsequently required wallet signatures for transfers into public pools rather than permitting an API signature alone. It also made API signatures non-public and announced IP allowlists, individual key restrictions, and nonce-reuse monitoring.</p><p>API key security therefore requires two separate controls: protect the credentials themselves, and minimize what each credential can do. A similar reliance on external automation appeared in our <a href="https://blog.era-wallet.com/are-telegram-trading-bots-safe-bloom-hack/">analysis of the Bloom trading bot hack</a>.</p><h3>Was the Lighter Loss $10.4 Million or $15.5 Million?</h3><p>Early accounts provided different figures. <a href="https://www.bitquery.io/investigations/lighter-hack">Bitquery recorded</a> an on-chain withdrawal of 10,393,057 USDC. Other researchers suggested that two market-maker accounts had been affected, producing a potential loss estimate of approximately $15.5 million.</p><p>The difference involved another $5.09 million that had not left Lighter’s Ethereum settlement contract when Bitquery reviewed the transactions. Lighter reported that Guardian Mode interrupted an additional withdrawal attempt, allowing its Security Council to return approximately $5 million USDC.</p><p>As <a href="https://www.theblock.co/news/defi/2026-11-17-lighter-reopens-withdrawals-after-traders-api-key-leak-returns-about-5-million-in-usdc-442113">The Block reported</a>, the exchange had not disclosed a definitive total theft figure. The $10.4 million withdrawal is visible on-chain; the $15.5 million number is an estimate of broader potential losses, not a confirmed total theft figure.</p><h3>Centralized vs Decentralized Exchange: Who Controls Funds?</h3><p>The centralized vs decentralized exchange distinction does not fully explain who can authorize trades or stop withdrawals. Lighter settles through smart contracts while also allowing authorized API keys to control trading operations. Its emergency Guardian Mode can temporarily restrict withdrawals.</p><p>That mechanism helped interrupt the additional withdrawal attempt but temporarily limited access for other users. Traders should examine permission models, emergency controls, and the conditions for recovering deposited funds.</p><p>The phrase <a href="https://blog.era-wallet.com/custodial-vs-non-custodial-wallets/">not your keys, not your coins</a> remains relevant. Depositing assets into a trading protocol introduces dependencies on its contracts and operational safeguards even if the original wallet keys remain under the user’s control.</p><h3>How to Protect Trading Accounts From API Key Compromise</h3><ul><li><strong>Review permissions.</strong> Check whether a key permits only trading or also transfers, pool interactions, and account management.</li><li><strong>Use secure signing software.</strong> Official SDKs can reduce implementation mistakes; any custom code must generate cryptographically safe nonces.</li><li><strong>Revoke exposed keys.</strong> Replace credentials if signing software might have reused nonces or otherwise leaked secret material.</li><li><strong>Restrict access.</strong> Use IP allowlists where supported, while recognizing they cannot protect a compromised authorized server.</li><li><strong>Separate activities.</strong> Isolate bots, accounts, and balances instead of granting every strategy the same permissions.</li><li><strong>Limit deposits.</strong> Keep only the capital required for positions, margin, and liquidity on the trading venue.</li></ul><p>Examine a platform’s emergency controls as well. Guardian Mode helped Lighter, but also prevented ordinary withdrawals while active. For another example of operational risk, see the <a href="https://blog.era-wallet.com/arcus-accounting-bug-balance-not-proof-of-funds/">Arcus accounting exploit</a>.</p><h3>Beware of Phishing During Withdrawal Suspensions</h3><p>Suspensions can give impersonators an opportunity to promote fake wallet verification, urgent asset migrations, or emergency recovery links. This is a general risk during exchange incidents, not a confirmed phishing campaign tied to Lighter.</p><p>Check announcements through official channels you open independently. Never share a seed phrase or private key, and do not sign unfamiliar transactions based on messages promising to unlock funds.</p><h3>FAQ: The Lighter Crypto Exchange Hack</h3><h3>Were Lighter’s Smart Contracts Hacked?</h3><p>According to Lighter, no. The incident involved compromised API signing keys generated using unsafe third-party software. Lighter said its protocol and official SDKs were unaffected.</p><h3>How Much Crypto Was Stolen From Lighter?</h3><p>Bitquery identified a withdrawal of 10,393,057 USDC. A higher $15.5 million estimate circulated, but Lighter reported recovering approximately $5 million tied to a further withdrawal attempt.</p><h3>Has Lighter Resumed Withdrawals?</h3><p>Yes. Lighter announced that deposits and withdrawals resumed on November 16, 2026, after Guardian Mode was disabled.</p><h3>What Is an API Key?</h3><p>An API key is a credential that software uses to access a service or perform authorized actions. Trading keys may allow automated orders and other operations according to their permissions.</p><h3>Can Someone Steal Crypto With an API Key Without a Seed Phrase?</h3><p>Yes, if the key permits operations that can move economic value. In the Lighter incident, the attacker used trading credentials and public pools without the wallet seed phrase.</p><h3>Conclusion</h3><p>The Lighter incident shows that protecting trading deposits requires both audited code and narrowly scoped authorization. A compromised key became financially dangerous because the platform permitted it to interact with a mechanism that transferred economic value.</p><p>Traders can reduce exposure by reviewing key privileges, using secure signing implementations, rotating risky credentials, and limiting deposits to operational needs. Correctly executing a signed instruction does not establish that its signer was authorized by the rightful account owner.</p><p>Keep long-term crypto storage separate from exchange trading permissions. Use code ERABLOG20 for 20% off: <a href="https://era-wallet.com/products?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=lighter-crypto-exchange-hack-261117-hk-02&amp;utm_content=crosspost_cta">Explore ERA Wallet</a></p><p>Originally published at <a href="https://blog.era-wallet.com/lighter-crypto-exchange-hack/">https://blog.era-wallet.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49b233a69081" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Optimizely Supply Chain Attack: How 178 Organizations Exposed Crypto Addresses]]></title>
            <link>https://medium.com/@erawallet/optimizely-supply-chain-attack-how-178-organizations-exposed-crypto-addresses-9487c2972d6d?source=rss-45e39c886651------2</link>
            <guid isPermaLink="false">https://medium.com/p/9487c2972d6d</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[ERA Wallet]]></dc:creator>
            <pubDate>Wed, 18 Nov 2026 14:27:28 GMT</pubDate>
            <atom:updated>2026-11-18T14:27:28.752Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2h6lETQJJxnivjVZ_ZF50g.png" /></figure><p>On November 16, 2026, a supply chain attack turned trusted websites into potential tools for stealing cryptocurrency. Malicious JavaScript delivered through Optimizely affected 178 organizations, including BBC, CNN, Zoom, Salesforce, and GitLab. The script could replace wallet addresses with attacker-controlled ones, allowing visitors to copy payment details from legitimate pages and unknowingly send funds to someone else.</p><p>The attacker exploited third-party code trusted by websites; HTTPS could not validate a copied destination.</p><h3>How the Optimizely Supply Chain Attack Unfolded</h3><p>Optimizely Web lets companies run A/B tests and personalize websites by loading JavaScript from Optimizely’s infrastructure. The code runs in visitors’ browsers with access to page content.</p><p>Security researcher Scott Helme of Report URI <a href="https://report-uri.ghost.io/worlds-largest-brands-infected-with-malware-via-optimizely/">identified 188 infected JavaScript files</a> associated with 178 organizations after examining 1,611 Optimizely scripts.</p><p>The infected scripts loaded track.js from the attacker-controlled domain 1688360.cc. The additional payload contained several functions:</p><ul><li><strong>Crypto address replacement:</strong> Substituting attacker-controlled wallet addresses in page content and copying operations.</li><li><strong>Payment card theft:</strong> Capturing card numbers, expiration dates, and security codes from accessible payment forms.</li><li><strong>Browser data collection:</strong> Extracting accessible cookies and screenshots under certain conditions.</li><li><strong>iOS targeting:</strong> Loading additional components on iPhones and iPads, including infrastructure associated with exploit chains.</li></ul><p>Investigators confirmed the delivery of malicious code through third-party scripts. The initial method used to change the files has not been publicly established.</p><h3>How the November 16 Attack Developed</h3><p><a href="https://www.stepsecurity.io/blog/optimjack-optimizely-hosted-scripts-crypto-clipper-card-skimmer">StepSecurity’s analysis</a> documented changes to the payload throughout November 16.</p><ul><li><strong>08:28 UTC · First Public Capture:</strong> A public scan recorded contact with the malicious payload server.</li><li><strong>16:02 UTC · Payload Analyzed:</strong> A captured version contained approximately 28.9 KB of malicious JavaScript.</li><li><strong>17:56 UTC · Expanded Payload:</strong> An updated version included additional functionality and iOS-related infrastructure.</li><li><strong>21:32 UTC · Cleanup Underway:</strong> Researchers observed the count of infected files declining.</li><li><strong>21:52 UTC · Most Files Cleaned:</strong> Only one of the 188 identified files remained infected in Report URI checks.</li></ul><p>Because the malicious functionality loaded remotely, the operator could update its behavior without modifying every affected website again.</p><h3>How Clipboard Hijacking Crypto Attacks Work</h3><p>Imagine sending Bitcoin to an address published on an official website. You check the domain, recognize the page, and click Copy. A clipboard hijacker can intercept the copied value and substitute the attacker’s address. The destination pasted into your wallet then differs from the one you intended.</p><p>The Optimizely payload went further. According to <a href="https://www.stepsecurity.io/blog/optimjack-optimizely-hosted-scripts-crypto-clipper-card-skimmer">StepSecurity</a>, it could replace addresses in page text, inputs, links, copy events, clipboard functions, and certain requests. Its targets included Bitcoin, Ethereum, TRON, Solana, TON, Litecoin, Bitcoin Cash, and Dogecoin.</p><p>The displayed address and copied address could both be malicious. Comparing them would produce a match without proving that either belonged to the intended recipient.</p><h3>Why HTTPS Doesn’t Prevent a JavaScript Supply Chain Attack</h3><p>HTTPS protects a connection but does not certify every third-party script loaded by the page. External scripts can interact with website content.</p><p>This differs from crypto address poisoning, in which attackers commonly plant lookalike addresses in transaction histories. It also differs from traditional clipboard hijacker malware installed on a computer: this malicious behavior could run within an open browser page.</p><h3>How Much Crypto Was Stolen?</h3><p>StepSecurity <a href="https://www.stepsecurity.io/blog/optimjack-optimizely-hosted-scripts-crypto-clipper-card-skimmer">estimated approximately $6,600</a> in cryptocurrency receipts and holdings associated with identified attacker wallets. This is not a confirmed campaign loss: some wallets had earlier activity, and blockchain records cannot attribute each transfer.</p><p>Card data theft, browser exfiltration, and possible iOS compromises would not appear in those balances. The delivery method could reach visitors to unrelated organizations.</p><h3>How to Protect Your Crypto Wallet From Address Replacement</h3><h3>1. Verify the Recipient Independently</h3><p>For a payment to another person, confirm the receiving address through a separate, previously trusted channel. Do not use the same potentially compromised page as both the source and reference.</p><p>For a transfer to your own hardware wallet, generate the receiving address through your device’s receiving workflow. Our guide to <a href="https://blog.era-wallet.com/verify-crypto-receiving-address-hardware-wallet/">verifying a crypto receiving address</a> explains how to compare it with the address displayed in the application.</p><h3>2. Compare the Complete Address</h3><p>Checking only the first and last characters may catch simple errors, but sophisticated lookalike addresses can share them. Compare the full destination with independently verified details wherever practical, and confirm the asset and blockchain network.</p><h3>3. Understand What You’re Signing With ERA Lens</h3><p>Even when a browser or clipboard contains a substituted address, the transaction must still be reviewed before signing. On ERA Wallet device, <a href="https://guide.era-wallet.com/06-sign-overview.html">ERA Lens</a> is an offline transaction decoder and analysis system that turns supported raw transaction data into readable information on the device’s screen.</p><p>Instead of relying on opaque transaction data, users can inspect the recipient, amount, network, fee, and available warnings. ERA Lens also analyzes supported smart contract interactions, including token approvals, multicall operations, and account delegation through EIP-7702. Potentially risky permissions and other recognized concerns can be highlighted before signing.</p><p>Its <strong>Overview</strong> displays essential transaction actions and warnings; <strong>Details</strong> provides technical fields. In an address-substitution scenario, this gives users a separate screen on which to inspect the actual destination and compare it with an address obtained independently, rather than relying entirely on the browser or software wallet.</p><h3>4. Test a Transfer, Then Check Again</h3><p>A small test transaction can confirm that funds reached a particular address, but does not verify the destination of the next payment. If you copy the address again, the larger transfer could still be redirected. Our explanation of <a href="https://blog.era-wallet.com/bitcoin-test-transaction-safe-large-transfer/">Bitcoin test transactions</a> covers what a successful test does and does not establish.</p><h3>What If You Visited an Affected Website?</h3><p>Visiting an affected page does not establish that funds were stolen or a device compromised. Exposure depends on which code loaded and what actions were performed.</p><p>If you copied payment details from a potentially affected page, inspect the destination in your outgoing transaction history and compare it with independent records. If you entered card details, review activity and contact your bank if you suspect compromise. iOS users should install available security updates.</p><h3>Checklist Before a Large Crypto Transfer</h3><ul><li><strong>Recipient:</strong> Confirm the address through an independent source.</li><li><strong>Network:</strong> Check that the asset and blockchain match.</li><li><strong>Destination:</strong> Compare the complete address wherever practical.</li><li><strong>Signature:</strong> Review recipient, amount, and other available details on the signing device.</li><li><strong>Test:</strong> Verify the destination again before the main transfer.</li></ul><h3>FAQ: The Optimizely Supply Chain Attack</h3><h3>Which Websites Were Affected by the Optimizely Attack?</h3><p>Report URI identified 188 infected JavaScript files associated with 178 organizations, including BBC, CNN, Zoom, Salesforce, and GitLab.</p><h3>Was Optimizely Itself Hacked?</h3><p>Malicious code was delivered through Optimizely-hosted JavaScript, but the initial method of modifying the files has not been publicly established.</p><h3>How Much Cryptocurrency Was Stolen?</h3><p>StepSecurity identified approximately $6,600 in related cryptocurrency receipts and balances. Losses attributable to the campaign remain uncertain.</p><h3>How to Stop Clipboard Hijacking?</h3><p>Verify the destination against an independently obtained address and review the actual transaction details before signing.</p><h3>Can a Hardware Wallet Prevent Clipboard Hijacking?</h3><p>A trusted signing screen helps detect a wrong destination before signing. It does not stop replacement in the browser or verify who owns an address.</p><h3>The Bottom Line</h3><p>The Optimizely incident showed how malicious third-party JavaScript can alter information presented on legitimate sites without changing their domains or accessing cryptocurrency private keys. Before authorizing a transfer, compare its actual destination against independently obtained information. Matching details from the browser and clipboard alone do not establish who controls an address.</p><p>Check the destination independently before signing. Use code ERABLOG20 for 20% off: <a href="https://era-wallet.com/products?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=optimizely-supply-chain-attack-261117-hk-01&amp;utm_content=crosspost_cta">Explore ERA Wallet</a></p><p>Originally published at <a href="https://blog.era-wallet.com/lighter-crypto-exchange-hack/">https://blog.era-wallet.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9487c2972d6d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kava Lend DeFi Hack: How a Dormant BUSD Market Lost $3.8 Million]]></title>
            <link>https://medium.com/@erawallet/kava-lend-defi-hack-how-a-dormant-busd-market-lost-3-8-million-9d3c21f0a2d7?source=rss-45e39c886651------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d3c21f0a2d7</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[news]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[kava]]></category>
            <dc:creator><![CDATA[ERA Wallet]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 09:03:42 GMT</pubDate>
            <atom:updated>2026-11-17T09:03:42.513Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v8oAYHOLW7hXXbC4Dyg-dg.png" /></figure><p>On November 14, 2026, a DeFi hack drained approximately $3.8 million worth of KAVA from HARD Lend, the lending protocol in the Kava ecosystem. The attacker did not need to steal private keys or mint new tokens. Instead, a calculation flaw in a nearly empty BUSD market allowed a small deposit to be treated as collateral worth roughly $1.25 billion.</p><p>The exploit exposed a particular kind of smart contract risk: users can protect their signing keys and still lose access to funds deposited into vulnerable protocols.</p><h3>What Happened in the Kava Lend Hack?</h3><p>Its BUSD market had become largely inactive after Paxos stopped minting new BUSD in 2023, but the market’s accounting functions continued operating.</p><p>According to <a href="https://www.theblock.co/news/defi/2026-11-14-kava-lend-loses-roughly-3-8-million-to-hack-sending-kava-token-down-nearly-40-440350">The Block’s investigation</a> and <a href="https://bitquery.io/investigations/kava-hack">Bitquery’s on-chain analysis</a>, the attacker manipulated this accounting system and repeatedly borrowed KAVA against collateral whose recorded value had become disconnected from reality.</p><h3>Timeline of the Attack</h3><ul><li><strong>November 8–10: Preparation.</strong> On-chain researchers identified repeated small BUSD deposits, loans, and withdrawals that appeared to test the mechanism.</li><li><strong>November 14, 04:01 UTC: Manipulation.</strong> A small BUSD loan reduced the market’s net supply to an extremely small positive amount.</li><li><strong>04:01–04:04 UTC: Collateral Inflation.</strong> The BUSD supply interest index increased approximately 243,000-fold, making the attacker’s deposit appear extraordinarily valuable.</li><li><strong>04:04–05:42 UTC: The Drain.</strong> Two associated wallets completed 127 borrowing and liquidation cycles, extracting KAVA from the lending pool.</li><li><strong>Later That Morning: Cross-Chain Transfers.</strong> Approximately 49.2 million KAVA moved to BNB Chain through LayerZero.</li><li><strong>November 14: Emergency Response.</strong> Kava acknowledged the incident, restricted Axelar bridge operations, and reported precautionary exchange withdrawal suspensions.</li></ul><h3>How Did a Nearly Empty BUSD Market Become Worth $1.25 Billion?</h3><p>Lending protocols calculate how much a user can borrow based partly on the recorded value of deposited collateral. If that value is wrong, the system can authorize loans that the underlying assets cannot support.</p><p>According to <a href="https://github.com/Kava-Labs/kava/blob/master/x/hard/keeper/interest.go">Kava’s public source code</a>, the calculation uses the market’s net supply as a divisor. The code handles a supply of exactly zero, but a tiny positive value can still produce an extremely large result.</p><p>By reducing net BUSD supply to approximately $0.00000002, the attacker caused a small amount of accrued interest to produce a massive increase in the supply index. Within three minutes, the index multiplied by roughly 243,000.</p><p>The protocol then valued previously deposited BUSD at approximately $1.25 billion. No corresponding billion-dollar deposit had arrived. The accounting system had simply inflated the value assigned to the existing position.</p><p>A similar separation between recorded balances and actual assets appeared in the <a href="https://blog.era-wallet.com/arcus-accounting-bug-balance-not-proof-of-funds/">Arcus accounting exploit</a>. The important failure in both cases was not transaction authorization. It was an incorrect financial state that other protocol functions subsequently trusted.</p><h3>Why Did the DeFi Hack Require 127 Loans?</h3><p><a href="https://bitquery.io/investigations/kava-hack">Bitquery reconstructed the transactions</a> and found that one wallet borrowed KAVA while associated liquidation operations removed the resulting debt. The cycle freed capacity for another loan, allowing the process to continue.</p><p>The inflated BUSD valuation made these operations possible. Meanwhile, the liquidation mechanism failed to recover sufficient real collateral to compensate the lending pool.</p><p>Across 127 cycles, the wallets borrowed roughly 55.2 million KAVA. Bitquery found that approximately 1.3 million KAVA was used to repay other borrowers’ debt, leaving about 53.9 million KAVA with the attacking wallets.</p><h3>What Happened to the Stolen KAVA?</h3><p>The attacker moved approximately 49.2 million KAVA to BNB Chain through LayerZero. Most of the transferred tokens were then sold for BNB and USDT.</p><p><a href="https://www.theblock.co/news/defi/2026-11-14-kava-lend-loses-roughly-3-8-million-to-hack-sending-kava-token-down-nearly-40-440350">The Block reported</a> that those sales generated approximately $2.09 million, substantially below the pre-attack valuation of the drained KAVA.</p><p>KAVA traded near $0.042 when The Block published its November 14 report, approximately 39% lower over the preceding 24 hours.</p><p>Partner exchanges suspended KAVA deposits and withdrawals, while Kava paused its Axelar bridge despite the attacker having used LayerZero for the transfers.</p><p>Bitquery additionally identified approximately 612,416 USDT in suspected proceeds blocked at Relay.</p><h3>What Does This Reveal About DeFi Lending Risks?</h3><p>That distinction matters because control of a wallet does not guarantee the solvency of a protocol receiving deposits. When users supply assets to a lending pool, their ability to withdraw depends on the pool’s liquidity and accounting rules. Even a correctly authorized withdrawal may fail if the assets have already left.</p><p>A hardware wallet can help protect private keys and authorize transactions in a separate environment. It cannot repair a lending protocol’s collateral calculation or restore liquidity drained by an exploit.</p><p>For more context, see our guide to <a href="https://blog.era-wallet.com/custodial-vs-non-custodial-wallets/">custodial and non-custodial wallets</a>, or the <a href="https://blog.era-wallet.com/liquid-network-hack-4000-btc-multisig/">Liquid Network incident</a>, which examines another case where cryptographic authorization and underlying system integrity were different security questions.</p><h3>Is DeFi Safe? What Users Should Check Before Lending</h3><p>There is no universal answer to whether decentralized lending is safe. Effective risk management begins by examining those dependencies.</p><ul><li><strong>Audits and deployed code.</strong> Check whether security reviews cover the current version and its collateral, interest, and liquidation mechanisms. An audit reduces uncertainty but does not guarantee the absence of vulnerabilities.</li><li><strong>Dormant markets.</strong> Look for legacy assets that remain active in protocol calculations, even when trading and deposits have largely stopped.</li><li><strong>Concentration.</strong> Avoid making an excessive share of your assets dependent on one lending protocol or a single pool.</li><li><strong>Emergency controls.</strong> Review borrowing limits, pause mechanisms, anomaly monitoring, and who has authority to activate them.</li><li><strong>Withdrawal conditions.</strong> Examine available liquidity and whether emergency restrictions could prevent timely withdrawals.</li></ul><p>For users evaluating DeFi lending risks, the Kava incident raises one especially useful question: Can an accounting error in a small, inactive market affect the assets held in a much larger pool?</p><h3>FAQ: The Kava Lend DeFi Hack</h3><h3>What Caused the Kava Lend Hack?</h3><p>An accounting vulnerability in the dormant BUSD market allowed the attacker to inflate the recorded value of collateral. Associated wallets then used repeated borrowing and liquidation operations to extract KAVA.</p><h3>How Much Crypto Was Lost in the Kava Lend Hack?</h3><p>On-chain analysis identified approximately 55.2 million KAVA borrowed through the exploit, with about 53.9 million retained by the attacking wallets. The initial pre-attack valuation was approximately $3.76 million.</p><h3>Were Kava Users’ Private Keys Compromised?</h3><p>There is no published evidence that user private keys were stolen. The reported vulnerability involved lending-market accounting rather than private-key security.</p><h3>What Is DeFi Risk Management?</h3><p>DeFi risk management involves assessing smart contract vulnerabilities, liquidity, capital concentration, and emergency controls before committing assets to a protocol.</p><h3>Can Cross-Chain DeFi Protocols Be Hacked?</h3><p>Yes. Vulnerabilities may exist in lending applications, bridges, or other connected components. In this incident, the exploit originated in HARD Lend, while LayerZero was used afterward to transfer assets to another blockchain.</p><h3>The Lesson From Kava Lend</h3><p>The BUSD market had very little activity, yet its accounting logic remained capable of influencing loans against KAVA. A tiny denominator was enough to turn an ordinary interest calculation into a collateral valuation large enough to drain most of a lending pool.</p><p>The practical lesson is to evaluate the systems holding your assets, not just the tools securing your keys. Before pursuing lending yields, consider the protocol’s remaining legacy markets, the independence of its risk controls, and whether funds can actually be withdrawn during an emergency.</p><p>Protect your keys, and examine the protocol risks before lending. Use code ERABLOG20 for 20% off: <a href="https://era-wallet.com/products?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=kava-lend-defi-hack-261115-hk-03&amp;utm_content=crosspost_cta">Explore ERA Wallet</a></p><p>Originally published at <a href="https://blog.era-wallet.com/">https://blog.era-wallet.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d3c21f0a2d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Can You Recover Stolen Crypto? What Tracing Can and Can’t Do]]></title>
            <link>https://medium.com/@erawallet/can-you-recover-stolen-crypto-what-tracing-can-and-cant-do-10d62e14bc96?source=rss-45e39c886651------2</link>
            <guid isPermaLink="false">https://medium.com/p/10d62e14bc96</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[ERA Wallet]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 08:46:39 GMT</pubDate>
            <atom:updated>2026-11-17T08:46:39.756Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-KCqO3NrSoLuiVzijnqRFQ.png" /></figure><p>If you’re trying to recover stolen crypto after a wallet compromise or crypto scam, the first question is whether the money can still be reached. Blockchain investigators may be able to follow stolen assets across multiple addresses and networks. But tracing the funds and recovering them are different processes. The outcome depends on who controls the assets, whether they can be frozen, and what legal action is available.</p><h3>Why Blockchain Transparency Doesn’t Make Transactions Reversible</h3><p>Bitcoin and Ethereum maintain public transaction histories. With a wallet address or transaction hash, anyone can examine transfers, amounts, destinations, and subsequent movements.</p><p>What the blockchain doesn’t automatically reveal is who owns an address.</p><p>Confirmed transactions also cannot simply be canceled by contacting a blockchain network. If an attacker controls the private keys to the receiving address, the victim has no built-in mechanism to reverse the transfer.</p><p>The distinction matters after a <a href="https://blog.era-wallet.com/ankr-bridge-exploit-valid-signatures-fake-receipts/">crypto hack involving a vulnerable protocol</a>. In the Ankr bridge exploit, forged cross-chain receipts caused assets to be released despite valid cryptographic signatures.</p><h3>What Blockchain Tracing Can Actually Reveal</h3><p>Blockchain tracing starts with known addresses and transaction hashes. Investigators follow subsequent transfers, identify patterns between addresses, and look for interactions with identifiable services.</p><ul><li><strong>Direct wallet transfers.</strong> Transfers between public addresses can usually be followed through on-chain records.</li><li><strong>Centralized exchanges.</strong> Once assets reach an exchange, transfers may continue through internal accounting systems that aren’t visible on the blockchain.</li><li><strong>Cross-chain bridges.</strong> Investigators must connect activity across different networks, sometimes involving wrapped assets or multiple intermediary transactions.</li><li><strong>Mixers.</strong> These services obscure relationships between incoming and outgoing transfers. Analysis may still produce leads, but confidently linking individual transactions becomes harder.</li></ul><p>A tracing report may identify a destination exchange, a cluster of associated addresses, or a possible cash-out route.</p><h3>When Can You Recover Stolen Crypto?</h3><p>In November 2025, the <a href="https://www.justice.gov/usao-sdga/pr/us-attorney-heap-announces-forfeiture-cryptocurrency-and-return-fraud-proceeds-victim">U.S. Department of Justice announced</a> that approximately $84,327 had been returned to a Georgia victim who had lost around $124,000 in cryptocurrency. The FBI traced much of the stolen value, seized assets, and worked through civil forfeiture proceedings before returning the proceeds.</p><p>In March 2026, the <a href="https://www.justice.gov/usao-me/pr/department-justice-return-470735-victims-cryptocurrency-investment-scheme">DOJ announced another recovery</a> involving approximately $470,735 for two victims of an investment scam. Investigators seized 470,773 USDT associated with the victims’ payments. The DOJ acknowledged Tether’s assistance in transferring the assets.</p><ol><li><strong>Exchange intervention.</strong> A centralized exchange may restrict an account under its internal procedures or in response to legal process.</li><li><strong>Token issuer intervention.</strong> Certain centrally issued tokens support address freezing or other administrative controls, subject to the issuer’s policies and applicable law.</li><li><strong>Legal seizure and forfeiture.</strong> Authorities may identify and seize assets, then return proceeds to eligible victims through the relevant legal process.</li></ol><p>None applies universally. Bitcoin held in an attacker-controlled self-custody wallet cannot be frozen by an exchange that doesn’t control it.</p><h3>What to Do If Crypto Is Stolen</h3><p>The first hours after crypto theft are about preserving what remains and improving the chances of an effective investigation.</p><ol><li><strong>Identify the compromise.</strong> A leaked seed phrase, malicious token approval, and compromised exchange account require different responses. Avoid generating replacement keys on a device that may be infected.</li><li><strong>Secure remaining assets.</strong> If a private key or seed phrase was exposed, create a new wallet with fresh keys in a trusted environment and transfer any remaining funds. Don’t reuse the compromised recovery phrase.</li><li><strong>Revoke token approvals where appropriate.</strong> If a malicious contract received spending permissions, follow <a href="https://ethereum.org/guides/how-to-revoke-token-access/">Ethereum’s guide to revoke token approvals</a>. Revocation can prevent further use of that permission, but it cannot reverse previous transfers or protect an exposed private key.</li><li><strong>Preserve evidence.</strong> Record transaction hashes, wallet addresses, networks, token amounts, timestamps, suspicious websites, and relevant communications.</li><li><strong>Report the incident.</strong> Contact any exchange that received the assets through its verified support channels, and file a report with the appropriate authorities. U.S. victims can report cryptocurrency fraud through the FBI’s <a href="https://www.ic3.gov/PSA/2023/psa230824">Internet Crime Complaint Center</a>.</li></ol><h3>How Crypto Recovery Scams Target Victims Twice</h3><p>After a crypto theft, victims may encounter people advertising crypto recovery services.</p><p>The <a href="https://www.ic3.gov/PSA/2023/PSA230811">FBI warned in August 2023</a> that fraudulent recovery companies collect upfront fees, disappear, or provide incomplete tracing reports before demanding additional payments.</p><ul><li><strong>Guaranteed recovery.</strong> A promise of a successful outcome before the case has been investigated.</li><li><strong>Unlocking fees.</strong> Requests for taxes, verification deposits, or additional payments to release supposedly recovered assets.</li><li><strong>Seed phrase requests.</strong> An investigator doesn’t need a victim’s private keys or recovery phrase to analyze public transactions.</li><li><strong>Fake authorities.</strong> Impersonation of FBI agents, lawyers, exchange investigators, or regulatory officials.</li><li><strong>Imitation websites.</strong> Fraudulent portals designed to capture personal information, wallet credentials, or additional payments.</li></ul><p>In July 2026, the <a href="https://www.ic3.gov/PSA/2026/PSA260720">FBI described</a> scammers using AI-generated videos impersonating agency personnel and fake IC3 websites to target previous fraud victims.</p><p>Legitimate blockchain analysis and legal representation do exist. Before hiring anyone, independently verify the firm’s registration, professional credentials, contact details, and contract terms.</p><h3>How to Reduce the Risk Before a Theft Happens</h3><p><strong>Review what you’re signing.</strong> A transaction may authorize more than a simple token transfer. ERA Lens on the ERA Wallet device <a href="https://guide.era-wallet.com/06-sign-overview.html">decodes supported transaction details</a> into readable fields before signing, including amounts, recipients, fees, and token information. This helps users review what they authorize, but it cannot establish that every smart contract is safe or free from hidden vulnerabilities.</p><p><strong>Verify receiving addresses.</strong> Compare addresses in your wallet application with those displayed independently on the hardware device. The ERA Wallet device lets users <a href="https://guide.era-wallet.com/03-receive-deposit-address.html">view and verify deposit addresses on its screen</a>.</p><p><strong>Separate high-risk activity from savings.</strong> Use distinct wallets and keys for long-term holdings, routine transactions, and experimental DeFi activity.</p><p>These precautions address user-controlled risks. They cannot prevent a protocol accounting failure like the <a href="https://blog.era-wallet.com/arcus-accounting-bug-balance-not-proof-of-funds/">Arcus exploit</a>, where incorrect internal balances enabled unauthorized withdrawals without a reported private-key compromise.</p><h3>FAQ</h3><h3>Can Stolen Crypto Be Recovered After It Reaches a Scammer’s Wallet?</h3><p>Sometimes. Recovery may be possible if assets later enter a platform capable of restricting them or become subject to lawful seizure. Simply identifying the address does not grant control over the funds.</p><h3>Can a Confirmed Bitcoin or Ethereum Transaction Be Reversed?</h3><p>Not through an ordinary cancellation process. Recovering value generally requires a new transfer by the controlling party or an applicable legal seizure process.</p><h3>What if the Stolen Crypto Reaches a Centralized Exchange?</h3><p>Contact the exchange’s official security team immediately with the relevant addresses and transaction hashes. Report the theft to law enforcement as well. Freezing depends on the exchange’s control over the assets and its applicable procedures.</p><h3>How to Find a Legitimate Crypto Recovery Service?</h3><p>Verify the company’s registration, professional credentials, and written terms independently. Avoid guaranteed outcomes, unsolicited offers, seed phrase requests, and demands to pay fees to unlock alleged recovered assets.</p><h3>How Long Does Crypto Recovery Take?</h3><p>There is no standard timeline. Tracing may identify an address quickly, while investigations, court proceedings, and victim compensation can take months or longer. Some cases never result in recovery.</p><h3>Conclusion</h3><p>After a theft, prioritize securing remaining funds, preserving transaction evidence, and contacting organizations with the ability to act. Paying an unknown intermediary to supposedly unlock recovered assets can turn one loss into two.</p><p>Blockchain records can reveal where stolen crypto traveled. Getting it back requires a separate technical or legal mechanism. The most useful investigation is therefore one that identifies not just a destination address, but whether anyone with legitimate authority can intervene.</p><p>Verify before signing, and act quickly when funds are stolen. Use code ERABLOG20 for 20% off: <a href="https://era-wallet.com/products?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=recover-stolen-crypto-q-261116-03&amp;utm_content=crosspost_cta">Explore ERA Wallet</a></p><p><em>Originally published at https://blog.era-wallet.com</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10d62e14bc96" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How an Accounting Bug Cost Arcus $2.23 Million]]></title>
            <link>https://medium.com/@erawallet/how-an-accounting-bug-cost-arcus-2-23-million-1f79d86911b4?source=rss-45e39c886651------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f79d86911b4</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[hacking]]></category>
            <dc:creator><![CDATA[ERA Wallet]]></dc:creator>
            <pubDate>Thu, 12 Nov 2026 14:31:18 GMT</pubDate>
            <atom:updated>2026-11-13T08:23:54.877Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://blog.era-wallet.com/tag/crypto-security/">Crypto Security</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-4rH5OfzAlu5Y7eHIAzE8w.png" /></figure><p>Arcus lost 2.23 million USDG after an accounting bug inflated a user’s balance. Here’s how it happened and why a withdrawal limit prevented further losses.</p><p>An accounting bug, not a reported private-key compromise, let a new Arcus account withdraw funds it didn’t actually hold. The incident is a useful lesson in the limits of balances, transaction validity, and automated withdrawal controls.</p><h3>How can someone withdraw money they don’t have?</h3><p>Imagine a bank account with $100. You move $40 from the main account to a savings subaccount. After the transfer, the main account should show $60 and the savings account $40. The total is still $100.</p><p>Now imagine the system credits the savings account with $40 but fails to reduce the main account. Its records say you have $140, even though only $100 exists.</p><p>This is an illustration, not a reconstruction of the exact Arcus bug. The company has not published the specific triggering conditions or code path. But it captures the essential failure: <strong>an internal balance can stop representing the assets actually available.</strong> If withdrawals rely on that mistaken figure, the error becomes more than a display problem.</p><h3>What happened at Arcus?</h3><p>At approximately 03:07 UTC on November 10, 2026 (10:07 p.m. Eastern on November 9), an attacker exploited an accounting flaw at Arcus, a decentralized trading platform. According to <a href="https://arcus.xyz/blog/arcus-incident-report-november-9-2026?ref=blog.era-wallet.com">Arcus’s incident report</a>, a newly created account used transfers between its own subaccounts to produce a recorded balance substantially larger than its real holdings.</p><p>The account then requested withdrawals against the inflated balance. The result was a completed on-chain withdrawal of 2,234,391 USDG, a dollar-denominated stablecoin. A further roughly $3 million in withdrawal requests was caught by the bridge’s rate limit and subsequently reversed. That additional amount was never paid out, so it should not be added to the realized loss.</p><p><strong>Actually withdrawn: </strong>2,234,391 USDG</p><p><strong>Further requests blocked: </strong>approximately $3 million</p><p>The underlying mechanism and the distinction between paid and blocked withdrawals are also documented in <a href="https://www.0xcert.com/advisory/0xCERT-2026-0338?ref=blog.era-wallet.com">an independent incident advisory</a>. No evidence in these disclosures establishes a stolen private key as the cause.</p><h3>Where did the system go wrong?</h3><p>A DeFi trading platform can represent the same assets at several different layers. Each layer answers a different question:</p><ul><li><strong>On-chain assets. </strong>Which tokens are actually held by addresses, bridges, or smart contracts?</li><li><strong>Internal account balances. </strong>How much does the protocol record as belonging to a particular user or subaccount?</li><li><strong>Withdrawable funds. </strong>How much will the platform allow that account to move out, after applying its rules and constraints?</li></ul><p>These figures are related, but they are not interchangeable. Open positions, collateral requirements, pending transfers, and withdrawal restrictions can all change the amount a user is entitled to withdraw.</p><p>One invariant should remain true for an ordinary transfer between a user’s own subaccounts: moving funds internally must not increase the total amount owned by that user. Arcus says the accounting of such transfers was flawed, allowing an account to request funds beyond its actual balance.</p><p>The public report does not identify the exact operation that incorrectly updated the records, so claims such as ‘the system forgot to debit the sending subaccount’ would go beyond the evidence. The defensible conclusion is simpler: <strong>a withdrawal mechanism can execute a perfectly real transaction based on an incorrect accounting state.</strong> The chain records that assets moved; it cannot by itself verify that the platform calculated the user’s entitlement correctly.</p><h3>Why did the withdrawal limit matter more than response speed?</h3><p>Arcus’s published incident timeline, converted to UTC, shows two different kinds of defense at work:</p><ul><li><strong>03:07 — November 10 </strong>Exploit activity begins.</li><li><strong>03:10 </strong>The bridge rate limit caps payouts, holding back about $3 million in additional requests.</li><li><strong>03:15 </strong>Monitoring flags the suspicious withdrawals and the team begins investigating.</li><li><strong>04:07 </strong>Platform-wide withdrawals are paused.</li><li><strong>04:37 </strong>The accounting fix is deployed.</li><li><strong>09:26 </strong>Withdrawals reopen.</li><li><strong>17:28 </strong>Arcus Labs covers the shortfall from its company treasury.</li></ul><p>The sequence matters. Monitoring caught unusual activity, and the team investigated and deployed a fix. But by then more than $2.23 million had already left. The bridge limit had acted earlier, without waiting for a person to identify the bug.</p><p><strong>Monitoring and incident response </strong>help a team notice a problem and intervene after suspicious behavior begins. <strong>A withdrawal rate limit </strong>places a predefined ceiling on how much value can leave over a given interval. These controls solve different problems.</p><p>A rate limit does not repair flawed accounting or guarantee safety: attackers can still extract substantial assets before it activates. In this incident, however, it contained further damage. Good system design has to consider not only how to prevent failure, but also <strong>how far one failure is allowed to spread.</strong> The detailed timeline is independently reproduced in <a href="https://www.cryptotimes.io/2026/11/11/robinhood-chain-dex-arcus-loses-2-23m-to-accounting-bug/?ref=blog.era-wallet.com">The Crypto Times coverage</a>.</p><h3>If user funds weren’t affected, is that a happy ending?</h3><p>Arcus said that the exploit involved one account and did not affect other users’ balances, positions, or orders. The company also stated that it covered the full 2,234,391 USDG shortfall from the Arcus Labs treasury.</p><p>That outcome is important, but two terms should not be confused:</p><ul><li><strong>Covering a shortfall </strong>means replacing the missing value with funds from elsewhere, such as a company’s own reserves.</li><li><strong>Recovering stolen assets </strong>means the assets transferred out during the exploit are actually returned or seized and restored.</li></ul><p>Covering a shortfall is not the same thing as recovering the original withdrawal. In its report, Arcus said it was tracking the withdrawn funds. An <a href="https://publicaml.org/arcus-hack/?ref=blog.era-wallet.com">on-chain review published November 11</a> traced subsequent transfers but did not establish their recovery. The available findings therefore support a distinction: Arcus says it made the protocol whole; they do not prove the attacker returned the assets.</p><p>For users, the company’s reported outcome was reassuring. But it depended on Arcus choosing to deploy its own capital. That should not be mistaken for a guarantee that another protocol would, or could, do the same.</p><h3>How can DeFi users reduce this kind of risk?</h3><p>Most people cannot personally audit every line of protocol code. They can, however, get more precise about the risks they accept.</p><ul><li><strong>Treat audits as evidence, not a warranty. </strong>Check which contract versions and components were reviewed, whether meaningful changes followed, and whether the platform has disclosed unresolved issues.</li><li><strong>Look for damage-limiting controls. </strong>Withdrawal rate limits, anomaly detection, emergency pauses, and transparent incident procedures can matter as much as prevention. Also ask who can operate these controls and what new trust assumptions that creates.</li><li><strong>Avoid concentrating more funds than necessary in one protocol. </strong>Assets exposed to a trading platform are subject to its accounting, contract, operational, and governance risks even if your own key management is sound.</li><li><strong>Separate active trading from long-term holdings. </strong>Funds that do not need to participate in a protocol should not automatically share its exposure to failures.</li></ul><p>The practical question is not only whether an interface displays your balance, but where the assets actually sit and which systems must work correctly for you to get them back.</p><h3>The real lesson from Arcus</h3><p>In crypto, ‘don’t trust, verify’ is often discussed in terms of addresses, private keys, and transaction signatures. The Arcus incident points to another layer: the financial logic deciding whether a withdrawal is justified.</p><p>A balance can look legitimate. A withdrawal can be correctly formatted. A blockchain can process it exactly as instructed. The payout may still be unauthorized because the accounting was wrong before the transaction reached the chain.</p><p><strong>A blockchain can confirm that funds moved. It does not automatically prove that the account had the right to withdraw them.</strong> This is why security is not one perfect check, but multiple independent controls with different failure boundaries.</p><p>A related distinction appears in <a href="https://blog.era-wallet.com/ankr-bridge-exploit-valid-signatures-fake-receipts/">our analysis of the Ankr bridge exploit</a>, where cryptographically valid approvals did not prove that the events described by those approvals had happened.</p><p>Security starts with understanding what you are trusting. Explore the <a href="https://era-wallet.com/products/era-wallet?utm_source=era_blog&amp;utm_medium=referral&amp;utm_campaign=news26-13-arcus-accounting-bug&amp;utm_content=article_end_cta">ERA Wallet device</a> for clearer transaction confirmation. Code ERABLOG20 for 20% off.</p><p><em>Originally published at </em><a href="https://blog.era-wallet.com/arcus-accounting-bug-balance-not-proof-of-funds/"><em>https://blog.era-wallet.com</em></a><em> on November 12, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f79d86911b4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hardware Wallets with Multiple Seed Phrases: 2026 Comparison]]></title>
            <link>https://medium.com/@erawallet/hardware-wallets-with-multiple-seed-phrases-2026-comparison-5fa13807181c?source=rss-45e39c886651------2</link>
            <guid isPermaLink="false">https://medium.com/p/5fa13807181c</guid>
            <category><![CDATA[cold-wallet]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[ledger]]></category>
            <category><![CDATA[tangem]]></category>
            <category><![CDATA[bitcoin]]></category>
            <dc:creator><![CDATA[ERA Wallet]]></dc:creator>
            <pubDate>Thu, 12 Nov 2026 12:47:02 GMT</pubDate>
            <atom:updated>2026-11-12T13:29:52.447Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://blog.era-wallet.com/tag/hardware-wallets/">Hardware Wallets</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*TPuYpJM6zg9ZxhTWVxgQFQ.png" /></figure><p>Which hardware wallets support multiple independent seed phrases? Compare ERA Wallet, Keystone, COLDCARD, Ledger, Trezor, and Tangem.</p><p><strong>One hardware wallet, one seed phrase? Not necessarily.</strong></p><p>Imagine you use crypto for long-term savings, everyday transfers, and DeFi. You want to separate those funds not just into different addresses, but into wallets controlled by entirely different keys.</p><p>You do not necessarily need a separate hardware device for each one. Some hardware wallets with multiple seed phrases can hold several distinct recovery secrets on a single device.</p><p>ERA Wallet device, Keystone 3 Pro, and COLDCARD are three examples. But their limits, storage models, and wallet-switching workflows are not the same.</p><p>Here is how the available approaches compare, why independent seeds are different from extra accounts and passphrase wallets, and when the distinction matters.</p><h3>What Are Multiple Independent Seed Phrases?</h3><p>A seed phrase, also called a recovery phrase, is a sequence of words used to recover a wallet’s cryptographic keys. Wallets following BIP-39 commonly use 12 or 24 words.</p><p>A single seed can generate many addresses and accounts. Those accounts, however, still share the same underlying secret.</p><p><strong>Multiple independent seed phrases mean that a device can generate or import several separate root secrets.</strong></p><ul><li><strong>Wallet A:</strong> long-term savings, seed phrase #1.</li><li><strong>Wallet B:</strong> everyday transactions, seed phrase #2.</li><li><strong>Wallet C:</strong> DeFi activity, seed phrase #3.</li></ul><p>If the phrases were generated independently, compromising one seed does not, by itself, reveal the keys derived from the others. Each wallet can also be restored separately from its own backup.</p><h3>Market Overview: Different Approaches to Multiple Wallets</h3><p>Hardware wallets handle multiple sets of keys in different ways. Some store separate root seeds; others provide multiple accounts or additional wallets derived with a BIP-39 passphrase.</p><p>All three approaches can produce different addresses and balances, but they are not technically interchangeable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Gp-tvCgKGqZPTRzt9fAhXA.png" /><figcaption><em>Specifications last checked: November 11, 2026. Features may vary by model and firmware.</em></figcaption></figure><h3>ERA Wallet: Up to 10 Independent Seed Phrases</h3><p>ERA Wallet device can create or import up to ten separate wallets, each with its own seed phrase, on one physical device.</p><p>Every wallet can have its own name, recovery backup, and optional access protection. This makes it possible to manage distinct sets of keys without changing hardware every time you switch between tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/954/1*5ouNe0CzfJWuiajPP71P3w.png" /></figure><h3>Quick Sign: Less Switching Between Active Wallets</h3><p>The more wallets you use, the more important the signing workflow becomes.</p><p>Suppose you transact from three different wallets throughout the day. Ordinarily, you might need to find and open the right wallet before every signature.</p><p><strong>Quick Sign</strong> simplifies that flow. Instead of requiring you to select a wallet first, ERA Wallet device identifies a matching wallet from the information in the signing request.</p><p>A typical QR-signing flow looks like this:</p><ol><li>Create a transaction in a compatible software wallet.</li><li>From the ERA Wallet device home screen, tap SCAN QR and scan the signing request.</li><li>Quick Sign identifies the matching wallet among those it can access automatically.</li><li>The device opens its transaction-review screen and displays the selected wallet’s name.</li><li>Review the details on the device and approve the signature.</li></ol><p>For frequently used wallets, there is no need to open the right seed manually before scanning. See the <a href="https://guide.era-wallet.com/06-scan-qr.html?ref=blog.era-wallet.com">Quick Sign workflow</a> for the precise signing behavior.</p><h3>NFC Signing: Tap Sign</h3><p>Alongside QR signing, <strong>Tap Sign</strong> is a planned NFC signing option for ERA Wallet device and ERA Wallet app. It will let a user send a transaction to an unlocked device by tapping the phone against it, rather than scanning a QR code.</p><p>From the home screen or wallet list, the device can use Quick Sign to determine which wallet matches the request. The user still reviews and approves the transaction on the device, then taps the phone a second time to collect the signature.</p><p><strong>Availability note:</strong> The official <a href="https://guide.era-wallet.com/06-tap-sign.html?ref=blog.era-wallet.com">Tap Sign guide</a> states that Tap Sign is not yet visible in the current ERA Wallet app version. Until the relevant app release, QR signing remains the available workflow. Tap Sign is designed for ERA Wallet app; other software wallets continue to use QR codes.</p><p>ERA Wallet device also separates two access controls:</p><ul><li><strong>Device PIN or password:</strong> the required protection that unlocks the physical device.</li><li><strong>Individual wallet PIN or password:</strong> optional protection set independently for a particular wallet.</li></ul><p>For example, frequently used wallets can remain without an additional wallet-level password and work with Quick Sign, while a long-term savings wallet can have its own PIN or password.</p><p>Quick Sign does not bypass a protected wallet. If the request belongs to one, the user must select and unlock it; a BIP-39 passphrase may also need to be entered. This is documented in the <a href="https://guide.era-wallet.com/03-wallet-password.html?ref=blog.era-wallet.com">wallet password guide</a>.</p><p>The result is a flexible balance between fast access to active wallets and extra protection for those used less often.</p><h3>Keystone 3 Pro: Up to Three Seed Phrases</h3><p>Keystone 3 Pro can generate or import up to three sets of seed phrases on one device. Each set functions as a separate wallet with its own access password.</p><p>When adding a wallet, the user creates its password, chooses whether to generate or import a seed, and saves the relevant backup. To use a different wallet, the user switches to it with the corresponding password.</p><p>This workflow is documented in <a href="https://keystone3.com/en/docs/3-seed-phrase-wallet-options/?ref=blog.era-wallet.com">Keystone’s guide to managing three seed phrases</a>.</p><h3>COLDCARD: Temporary Seeds and Seed Vault</h3><p>COLDCARD offers a different way to manage multiple cryptographic secrets. Its <strong>Temporary Seeds</strong> feature lets users activate another secret without replacing the device’s main seed.</p><p>That temporary secret can be imported, generated separately, or derived using a standard such as BIP-85. In the usual temporary mode, it remains in RAM rather than being permanently installed as the main secret in a Secure Element.</p><p><strong>Seed Vault</strong> adds the option to retain several temporary secrets in encrypted settings and later activate one using `Use This Seed`.</p><p>Its architecture differs from a set of independent permanent seed slots: Seed Vault records are encrypted with key material tied to the device’s main seed, and some stored secrets may themselves be derived from another secret.</p><p>These mechanics, including the supported secret sources, are covered in <a href="https://coldcard.com/docs/temporary-seeds/?ref=blog.era-wallet.com">COLDCARD’s Temporary Seeds documentation</a>.</p><h3>Ledger, Trezor, and Tangem: Other Ways to Manage Multiple Wallets</h3><p>These popular hardware wallets also support multiple crypto accounts, but the distinction lies in how the keys are derived and restored.</p><p><strong>Ledger</strong> lets users create multiple accounts from a recovery phrase, as well as additional wallets using a <a href="https://www.ledger.com/academy/passphrase-an-advanced-security-feature?ref=blog.era-wallet.com">BIP-39 passphrase</a>. In standard operation, this is different from keeping several independently generated recovery phrases available simultaneously.</p><p><strong>Trezor</strong> supports multiple accounts and <a href="https://trezor.io/guides/backups-recovery/advanced-wallets/what-is-a-passphrase?ref=blog.era-wallet.com">passphrase wallets</a>. Each passphrase produces a different wallet with its own addresses, but recovery requires both the original wallet backup and the exact passphrase.</p><p><strong>Tangem</strong> supports <a href="https://tangem.com/en/blog/post/multi-accounts/?ref=blog.era-wallet.com">up to 20 accounts within one wallet</a>. The accounts have separate addresses, balances, and histories, but share the same root secret and backup system. Tangem app can also manage separate hardware wallets backed by different sets of cards.</p><p>In short, multiple accounts in an app do not automatically mean that one hardware device stores multiple independent seed phrases.</p><h3>Multiple Seed Phrases vs. Passphrase Wallets</h3><p>Multiple accounts, passphrase wallets, and independent seeds may look similar on screen: separate addresses, balances, and transaction histories. Under the hood, they work differently.</p><h3>What Is Key Derivation?</h3><p>Most modern wallets use <strong>hierarchical deterministic (HD) key derivation</strong>. The name sounds technical, but the idea is straightforward: one root secret can generate many private keys and addresses.</p><p>Think of it as a tree:</p><ul><li><strong>Seed phrase:</strong> the root.</li><li><strong>Accounts:</strong> the branches.</li><li><strong>Addresses:</strong> the smaller branches growing from them.</li></ul><p>Each branch can have different assets and balances, but the branches still come from the same root. Twenty accounts, therefore, do not necessarily mean twenty independent seed phrases.</p><h3>How Do Passphrase Wallets Work?</h3><p>Under <a href="https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki?ref=blog.era-wallet.com">BIP-39</a>, a user can add a secret text string called a passphrase. The same mnemonic phrase paired with different passphrases produces different cryptographic wallets:</p><ul><li>Seed phrase + passphrase A = Wallet A</li><li>Seed phrase + passphrase B = Wallet B</li><li>Seed phrase + passphrase C = Wallet C</li></ul><p>Each wallet has different keys, addresses, and balances. But restoring any one of them requires <strong>both the original mnemonic and the exact passphrase</strong>.</p><p>With genuinely independent seed phrases, each wallet has its own root secret and can be restored without needing another wallet’s recovery phrase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/988/1*B_Bly4bGFwjTAk6QcGGPwA.png" /></figure><p>There is one further distinction: <a href="https://github.com/bitcoin/bips/blob/master/bip-0085.mediawiki?ref=blog.era-wallet.com">BIP-85</a> can derive new seed phrases from a master secret. Those phrases can be used in separate wallets, but they are not independent of that master secret. Anyone with the master secret and the relevant derivation details can reproduce them.</p><p>That is why a comparison of multiple independent seeds should distinguish freshly generated or independently imported root secrets from derived ones.</p><h3>Who Needs Multiple Seed Phrases on One Hardware Wallet?</h3><p>Multiple seed phrases are useful when you want to separate keys by purpose without carrying a different physical signer for every activity.</p><p><strong>Long-term savings and everyday payments.</strong> Keep your long-term holdings under one seed and regular spending under another.</p><p><strong>Personal and business funds.</strong> Separate personal assets from the crypto used for invoices, business expenses, or other work.</p><p><strong>DeFi and Web3.</strong> Keep a dedicated wallet for smart-contract interactions instead of using the same keys as your long-term savings. You still need to inspect every transaction you sign.</p><p><strong>Existing wallets.</strong> Import independently created seed phrases into a compatible device rather than switching between several physical signers.</p><p><strong>Shared workflows and Bitcoin multisig.</strong> Consider a 2-of-3 Bitcoin multisig arrangement in which two of three signatures are required. A team in one office could, in principle, use separate seed-backed wallets and individual wallet passwords on a shared ERA Wallet device, enrolling each as a distinct cosigner in a compatible coordinator. Each participant would select and unlock their own wallet to sign their part of a PSBT.</p><p>ERA’s <a href="https://guide.era-wallet.com/07-multisig-overview.html?ref=blog.era-wallet.com">Bitcoin multisig guide</a> documents cosigner key export, descriptor import, and PSBT signing with coordinators such as Sparrow and Nunchuk. The guide describes the cosigner workflow; it does not present a shared-device, multi-employee configuration as a substitute for independent signer hardware.</p><p><strong>Distinct keys are not the same as distinct devices.</strong> Sharing one signer introduces a common physical and firmware risk, even when each cosigner uses a different seed phrase and wallet password. For security-critical multisig setups, physically separate devices and custody arrangements remain the stronger model.</p><p>Each independent wallet also needs its own reliable recovery backup. For practical backup hygiene, see <a href="https://blog.era-wallet.com/can-malware-steal-crypto-seed-phrase-from-photo/">how recovery phrases can be exposed through photos</a>.</p><h3>How to Choose a Hardware Wallet with Multiple Seed Phrases</h3><p>Start by deciding whether you actually need cryptographically separate root secrets or simply different accounts with separate balances.</p><p>If key independence matters, check whether the device can create or import several separate seed phrases. Then look at the daily workflow: how do you switch wallets, how does the device pick a signing key, and what access controls can you configure?</p><p>Finally, make sure you understand how to back up and recover each wallet on its own.</p><blockquote><strong><em>The best option is the one whose mechanisms you understand and can use simply and safely.</em></strong></blockquote><p><strong>Want to manage separate seed phrases without switching devices?</strong> Explore <a href="https://era-wallet.com/hardware-wallet?utm_source=era_blog&amp;utm_medium=referral&amp;utm_campaign=hardware_wallets_multiple_seed_phrases_2026&amp;utm_content=article_end_cta">ERA Wallet device</a>, which supports up to ten independently seeded wallets. Code ERABLOG20 for 20% off.</p><h3>Frequently Asked Questions</h3><h3>Can a hardware wallet store multiple seed phrases?</h3><p>Yes. Some hardware devices support several root secrets at once. ERA Wallet device supports up to ten separate seed-backed wallets, Keystone 3 Pro supports up to three, and COLDCARD can work with multiple additional secrets through Temporary Seeds and Seed Vault.</p><h3>Which hardware wallet supports the most independent seed phrases?</h3><p>Among the devices in this comparison with a documented fixed number of wallets, ERA Wallet device supports up to ten and Keystone 3 Pro up to three. COLDCARD uses a different storage model with Seed Vault, so a direct slot-count comparison would be misleading. This is not an exhaustive ranking of every hardware wallet on the market.</p><h3>Can I use multiple crypto wallets on one hardware device?</h3><p>Yes. Depending on the product, you can use multiple accounts, passphrase wallets, or wallets with different seed phrases. The key question is whether those wallets share a root secret and what information you need to recover them.</p><h3>What is the difference between multiple seed phrases and passphrases?</h3><p>A passphrase wallet is derived from the combination of a shared mnemonic and an additional secret string. Independently generated seed phrases create separate roots, allowing each associated wallet to be recovered without the recovery material for the others.</p><p><em>Originally published at </em><a href="https://blog.era-wallet.com/hardware-wallets-multiple-seed-phrases/"><em>https://blog.era-wallet.com</em></a><em> on November 12, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5fa13807181c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Check Your Crypto Receiving Address]]></title>
            <link>https://medium.com/@erawallet/how-to-check-your-crypto-receiving-address-ecc038d0cc7a?source=rss-45e39c886651------2</link>
            <guid isPermaLink="false">https://medium.com/p/ecc038d0cc7a</guid>
            <category><![CDATA[cryptosecurity]]></category>
            <category><![CDATA[self-custody]]></category>
            <category><![CDATA[hardware-wallet]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[malware]]></category>
            <dc:creator><![CDATA[ERA Wallet]]></dc:creator>
            <pubDate>Wed, 11 Nov 2026 05:23:29 GMT</pubDate>
            <atom:updated>2026-11-11T08:48:45.295Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://blog.era-wallet.com/tag/crypto-security/">Crypto Security</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3V_P0q0KYQe1skBB0vRH2Q.png" /></figure><p>Your private keys can be safe while your crypto goes to the wrong address. Learn how to verify your wallet app, hardware device, and receiving address.</p><p>You are transferring Bitcoin from an exchange to your hardware wallet. You open the app, copy the receiving address, paste it into the withdrawal form, and confirm. Everything looks right. But what if the address belongs to someone else?</p><p>Malware can replace a copied crypto address or alter what appears on a phone screen. Your private keys may remain untouched while the funds go to an attacker. Protecting keys is only part of the job: you also need to verify where your crypto is going.</p><p>A hardware wallet keeps private keys separate from your phone or computer. Its companion app can still show balances, transaction history, and receiving addresses without holding those keys. That convenience creates a different trust boundary: the screen and clipboard on your everyday device can be compromised.</p><p>For example, clipboard malware can replace a Bitcoin address with one controlled by an attacker. A convincing replacement may even share the first and last characters. The exchange sends the funds exactly where you told it to. No private key has to be stolen.</p><p>A hardware wallet with its own screen offers an independent way to check the receiving address. But before relying on that comparison, it makes sense to verify the tools involved.</p><p>Using ERA Wallet as an example, the process covers three different questions: Is the app genuine? Is the device genuine? And does the receiving address match?</p><h3>1. Verify the ERA Wallet app</h3><p>A familiar-looking interface is not proof that an app is authentic. ERA Wallet app (version 1.12 and later) includes Settings → Verify app, which works with a separate browser verification service. Open <a href="https://verify.era-wallet.com/?ref=blog.era-wallet.com">verify.era-wallet.com</a>, scan the site’s QR code or enter its challenge code in the app, and review the result in your browser.</p><p>The app submits hardware-backed attestation evidence tied to the challenge. The service evaluates that evidence rather than asking the app to simply declare itself genuine. This is an authenticity check, not a guarantee that the phone is free of every possible threat. Always verify that you are using the legitimate website.</p><h3>2. Check the ERA Wallet device</h3><p>A genuine app does not automatically prove that the physical device is genuine. ERA Wallet device supports an Authenticity Check based on a cryptographic challenge-response exchange.</p><p>In ERA Wallet app, open Settings → Authenticity Check. On ERA Wallet device, go to Settings → Authenticity. The app displays a challenge QR code; the device scans it and produces a signed response as another QR code. The app verifies the response. The check is included in initial setup and can be repeated later.</p><p>For the complete sequence, see the <a href="https://guide.era-wallet.com/01-authenticity-check.html?ref=blog.era-wallet.com">official authenticity-check guide</a>. A successful result verifies the expected cryptographic response, not the absence of every conceivable security issue.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FciwAIEMsPNE%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DciwAIEMsPNE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FciwAIEMsPNE%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/cebba64bcf04a93ad5544d6de17890d3/href">https://medium.com/media/cebba64bcf04a93ad5544d6de17890d3/href</a></iframe><h3>3. Compare the receiving address on the device</h3><p>Now verify the destination itself:</p><ol><li>On ERA Wallet device, open the intended wallet, select DEPOSIT, and choose the network (for example, Bitcoin). The device displays the receiving address as text and a QR code.</li><li>In ERA Wallet app, open Receive for the same wallet and network.</li><li>Compare the entire address, character by character, on both screens. Do not rely only on the beginning and end.</li></ol><p>If the addresses differ, stop and investigate before sending funds. If they match, you can share the device-displayed QR code or use the address from the app. When copying, check the address again after pasting it into the exchange withdrawal form: clipboard malware can change it during the transfer.</p><p>A QR code is only a way to encode an address. It does not prove ownership. A malicious app can generate a perfectly valid QR code for an attacker’s address.</p><p>See the <a href="https://guide.era-wallet.com/03-receive-deposit-address.html?ref=blog.era-wallet.com">ERA Wallet receiving-address guide</a> for the full device flow.</p><p>A mismatch is not automatically an attack. Bitcoin wallets can derive multiple receiving addresses from one wallet; using a fresh one helps privacy. A different address number, Bitcoin format (such as Native SegWit, Taproot, or Legacy), account, or passphrase can also change the displayed result.</p><p>Make sure the app and device are using the same wallet and address settings. Until the discrepancy is explained, do not send funds.</p><p>A hardware wallet helps isolate your private keys, but it cannot make every value shown on a compromised phone trustworthy. Checking the app, checking the device, and comparing the receiving address address different risks. None offers absolute protection; together they replace several assumptions with concrete checks.</p><p>Your keys can be safe while your funds are sent to the wrong place. Verify the destination before you send.</p><p><em>Originally published at </em><a href="https://blog.era-wallet.com/verify-crypto-receiving-address-hardware-wallet/"><em>https://blog.era-wallet.com</em></a><em> on November 11, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ecc038d0cc7a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>