/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Researchers expose a flaw in at least three major crypto wallets, Ledger Live, Edge, and Breadwallet, which could be exploited for double spending users' funds

A standard way to transact Bitcoin could be vulnerable to double-spending, new research has found.

CoinDesk Daniel Kuhn

Context & Ripple Effects

This disclosure extends a familiar arc in which Bitcoin's security failures surface at the software layer rather than the protocol. In 2018 alone, Electrum carried a critical flaw for two years that went unpatched for weeks after discovery, while a teenager broke the 'tamper-proof' claims around Ledger's hardware wallets sold by the millions. Five years later, researchers at Unciphered traced a BitcoinJS library flaw to pre-2016 wallets with up to $1B at risk.

What makes this report distinct is the target class: not one app but at least three major wallets — Ledger Live, Edge, and Breadwallet — all exposed through what the research describes as a standard way to transact Bitcoin, meaning the weakness may sit in shared practice rather than any single codebase.

First-order effects

  • Users transacting through Ledger Live, Edge, or Breadwallet face direct double-spend risk on their bitcoin until the flaw is patched, and each vendor must ship fixes and disclose whether exploitation occurred.
  • Ledger's exposure is compounded by its history: the company whose hardware was marketed as tamper-resistant now has its companion software implicated in a second major vulnerability class.

Second-order effects

  • Wallet developers across the market are forced to audit their own implementations of the same standard transaction method, since a flaw this generic suggests other apps built on identical assumptions share it.
  • Merchants and exchanges accepting bitcoin payments bear the cost side of double-spending, pushing them toward more confirmations or third-party risk scoring before honoring transactions — added friction that lands on everyday payment flows.

Third-order effects

  • If the pattern holds — Electrum, Ledger hardware, BitcoinJS, now three wallets at once — the durable lesson is that Bitcoin's end-user security concentrates in wallet software that is often unmaintained or built on shared libraries, making the wallet the industry's recurring attack surface and a likely focus for future audits and regulatory scrutiny of custody practices.

The trend: Bitcoin's security failures keep migrating up the stack from protocol to wallet software, where shared code and slow patching turn individual bugs into industry-wide exposures.

Discussion

  • @lopp Jameson Lopp on x
    Accepting bitcoin transactions without waiting for them to be confirmed is like accepting a check and not waiting to see if it bounces. The whole point of the blockchain is to solve the double-spend problem. https://www.coindesk.com/...
  • @peterktodd Peter Todd on x
    Also, this is just hilarious: “Like other vulnerabilities found in Bitcoin's core codebase, such as timelocked transactions, the RBF function has become a standard way for users to send value back and forth.” Yes, Bitcoin Core runs on exploits. 🤦‍♂️ https://web.archive.org/...