Coldcard flaw linked to thefts, response draws criticism
- Rob Hamilton linked Coldcard thefts to an entropy flaw, not a failure in Bitcoin itself.
- He reported losses above $100 million; Kevin Loaec criticized the company’s handling of researchers’ reports.
- Simon Dixon warned against using Coldcard, but offered no proof of a deliberate operation.
A flaw in Coldcard’s key and passphrase generation has been linked to Bitcoin thefts from older wallet addresses. Rob Hamilton said on What Bitcoin Did, in its Oct. 20 discussion, that the theft began overnight on July 29 and users were discussing losses by July 30. He said a sweep of old addresses pointed to an entropy flaw, not a failure in Bitcoin’s protocol.
Entropy is the randomness used to generate secret keys and passphrases. Hamilton called the flaw unacceptable and said the available evidence pointed to an engineering error, not a deliberate backdoor. He put the losses above $100 million in that discussion. The dates place the theft after Kimi K3 became open weight on July 27, but Hamilton did not say the AI model caused it.
The criticism extends to how researchers were treated. Kevin Loaec, speaking on Bitcoin Takeover, faulted Coldcard for changing its license and dismissing researchers’ reports, saying that response discouraged further scrutiny. Simon Dixon, in an Oct. 22 discussion, advised against using Coldcard and said the incident could have been a long-term operation, but offered no proof for that theory.
Hamilton argued that self-custody should move beyond relying on one hardware device, toward multisignature setups using different manufacturers or institutions. For ordinary holders, the dispute is about more than whether a flaw was accidental: a wallet’s security also depends on how quickly its makers take reports seriously.
Source Intelligence
- Deep dive into what was said in the episodes
Big Bitcoin, the Financial Industrial Complex & the End of the Petrodollar | Simon Dixon on Bitcoin Archive w/ Archie (13 October 2026 - Interview #4) • Oct 22
- Archie described self-custody as under pressure. Simon Dixon separated the breaches: Coldcard’s passphrase-generation flaw and compromised Ledger reseller devices led to Bitcoin being stolen, while Trezor’s email-vendor breach exposed customers’ personal details, not wallet funds.
- Simon Dixon said the Coldcard breach could have been a long-term operation but offered no proof. He advised against using Coldcard again, citing the breach and the company account’s dismissive response; he judges organizations by their incentives and funding rather than presumed intent.
Also discussed on this episode: (14)
Custody (2)
- Simon Dixon said hardware wallets add third-party risks, including weak entropy, compromised delivery devices, and phishing enabled by leaked customer data. He recommended stronger key practices, such as rolling dice, using multiple keys, or setting up multisig with Bitcoin Core or multiple vendors.
- Simon Dixon said attacks on self-custody will push some holders toward ETFs and custodians, whether or not centralization was the attackers’ goal. He sees AI-driven data centralization as a broader risk and argues that securing Bitcoin keys builds skills for personal sovereignty.
Regulation (1)
- Simon Dixon read new taxes and restrictions as evidence that governments want to capture Bitcoin, not that it is failing. The discussion cited European fines for undeclared wallets, Dutch taxes on unrealized gains, and a Bitcoin market capitalization of $1.6 trillion to $1.7 trillion.
Mining (2)
- Simon Dixon said China remained important to Bitcoin mining despite its ban, partly through mining-equipment production and continuing underground activity. He described the ban as reducing China’s dominance and shifting mining toward American public companies, which at one point held about 40% of hash power.
- Simon Dixon said mining’s thin economics favor operators with cheap energy, financing, or state backing. Public miners are exposed to financial-market pressure, while AI data centers offer better returns; he sees mining spreading among states even as mining pools and equipment supply remain concentrated.
Protocol (1)
- Simon Dixon said Bitcoin’s contentious governance fights can expose centralizing pressures but also fracture the people resisting them. He viewed the Nots debate as useful and said BIP-110 had little chance of passing; Nots node support rising from 0% to 20% was significant.
Social Media (1)
- Simon Dixon said social-media incentives reward conflict and sensationalism, which can turn Bitcoin disagreements into identity battles or divide-and-conquer opportunities. He now blocks abuse, engages with good-faith criticism, and sometimes turns bad-faith comments into educational posts; he cited Lynn Alden as a model of patient replies.
China (2)
- Simon Dixon argued that China’s long leadership horizon supports sustained policy, while Western electoral cycles and finance-driven politics interrupt long-term plans. He said China keeps finance subordinate to the state; in the West, he characterized the system as socialism for banks and capitalism for everyone else.
- Simon Dixon described India as a hybrid that admits private capital through government-connected elites, but said this produces wealth inequality and weaker infrastructure investment than China. He argued that economic education and media narratives are shaped by elite funding, and urged people to question inherited political beliefs.
Macro (1)
- Simon Dixon traced the petrodollar system to the shift away from gold: Nixon ended dollar convertibility in 1971, and the United States established the oil-for-dollar arrangement with Saudi Arabia in 1974. He linked the deal to demand for US debt and military protection for oil producers.
Inflation (1)
- Simon Dixon said rising energy costs and bond yields transfer wealth to oil producers, lenders, and financial institutions, while indebted households and small businesses pay more to borrow and operate. He said tariffs added pressure to small importers, while AI productivity gains may offset some inflation.
Middle East (2)
- Simon Dixon said the Middle East’s energy flows are being rerouted rather than simply stopped: higher insurance and delivery costs change who benefits. He identified Oman’s ties with Iran and its regional neutrality as important, and argued that China, Russia, and Gulf states are gaining leverage as US arrangements are renegotiated.
- Simon Dixon forecast a US military drawdown in the Middle East and greater financial-industrial influence over reconstruction and regional security. He expects a Palestinian state within five years, though he called a two-state solution unlikely, and said Gulf investment could shape rebuilding in Palestine and Iran.
BTC Markets (1)
- Simon Dixon said Bitcoin’s short-term price cannot be reliably explained by one macro correlation, and that large traders may have superior information and capital. He remains confident in Bitcoin if users can self-custody, transact peer to peer, and preserve the 21 million cap; centralizing custody, mining, or development would threaten that view.

Danny Knowles
The Fight to Defend Bitcoin From AI | Rob Hamilton • Oct 20
- Rob Hamilton says the Coldcard theft began overnight after Kimi K3 became open weight on July 27; by July 30, users were reporting losses. A sweep of many old wallet addresses pointed to an entropy flaw, not a Bitcoin protocol failure.
- Rob Hamilton calls the Coldcard entropy flaw unacceptable and says the available evidence points to an engineering error, not a deliberate backdoor. He says maintainers sometimes dismiss reports defensively, and that stronger security culture requires treating reports as useful even when they prove false.
Also discussed on this episode: (15)
Coding (3)
- Rob Hamilton organized a volunteer red team that scanned 650 codebases and logged 10,000 findings, including 1,500 critical or high-severity issues. About two dozen developers worked across the effort, which peaked at $10,000 to $20,000 a day.
- Rob Hamilton says AI scans made security review far faster and cheaper, but expert judgment still matters: specialists can supply context that helps models connect flaws and raise their severity. He says audits that once took weeks and tens of thousands of dollars can now cost hundreds or less.
- Rob Hamilton expects AI to expose software flaws across industries, not only Bitcoin. He sees AI-assisted checks becoming part of development so bugs are caught before release, while formal proofs remain too costly and incomplete to guarantee every code path is safe.
Protocol (2)
- Rob Hamilton found no critical issue in Bitcoin Core or libsecp256k1, the signature library used by Bitcoin Core and hardware wallets. A $20,000 to $25,000 AI-assisted review of libsecp256k1 found no serious weakness.
- Rob Hamilton says Miniscript adds conditional spending paths, time locks, and recovery options without changing Bitcoin’s consensus rules. He sees time as a new security tool: a wallet can offer a cooperative signing path and a later path that works if a provider disappears.
Safety (1)
- Rob Hamilton says Bitcoin attacks are unusually visible because theft moves funds on a public ledger; hacks at banks or hospitals can stay quiet. He expects more public incidents involving utilities or banks as AI-assisted attacks improve, though law enforcement may constrain what thieves can do with stolen funds.
Custody (6)
- Rob Hamilton argues that custody choices should match a person's finances, skills, and tolerance for loss, not a universal balance threshold. People overwhelmed by self-custody can choose an ETF or collaborative custody; people choosing sovereignty must do the work to understand their setup.
- Rob Hamilton says self-custody requires practice: test transactions, verify backups, and rehearse recovery and inheritance. He compares wallet handling to firearms training and warns that weak passphrases, including a single word or “21,” can be cracked.
- Rob Hamilton says single-signature wallets remain viable for informed users, including those using a strong passphrase, but he would not recommend them to family members. He favors multi-signature or collaborative custody for users who want recovery options and protection from one compromised key.
- Rob Hamilton says roughly 50 BTC was moved by white hats to a Wyoming trust intended to return recovered funds to owners. He does not know whether the participants face legal risk and treats recovery of the stolen coins as unlikely by default.
- BitGo advertises institutional custody using distributed keys, offline key generation, and geographically separated vaults. Its ad says the company has secured billions of dollars in Bitcoin for institutions and listed on the New York Stock Exchange in 2026 under ticker BTGO.
- Expat Money promotes a Plan B through residency and access to another country or financial system; founder Mikel says he has been an expatriate for more than 25 years. Bitkey advertises a 2-of-3 key design, while Anchor Watch promotes inheritance planning and U.S. Bitcoin insurance backed by Lloyd’s of London.
Open Source (1)
- Rob Hamilton opposes restricting open-weight AI models, comparing the policy push to the 1990s cryptography debates over making RSA-related mathematics illegal. He argues that banning tools in the United States would not stop other countries from developing or using them.
Models (1)
- Rob Hamilton argues that frontier AI firms have incentives to restrict models and keep valuable discoveries for themselves, while selling metered access is a weak long-term business. He expects firms to pursue proprietary science and cybersecurity services as they seek revenue and prepare for public listings.
Banking (1)
- Ledn advertises Bitcoin-backed loans with published rates, no monthly payments, and no early-repayment penalty; it says loans fund in hours and client Bitcoin is not lent out for yield. Ledn reports eight years of asset protection and more than $11 billion in loans.
S17 E47: Tabconf 8 Livestream with Kevin Loaec, Ekrem Bal, Spaces Protocol & The Bitcoin Pivot (Bonus: Peter Todd) • Oct 17
- Kevin says Coldcard's RNG bug was especially alarming because users assumed a well-known hardware wallet had been reviewed and tested. He faults the company for changing its license and dismissing researchers' reports instead of offering meaningful recognition, which discouraged further scrutiny.
Also discussed on this episode: (35)
Protocol (11)
- Ekrem says Citrea records rare operator challenges in Bitcoin transactions. Its 144-byte longest-chain proofs exceed the 80-byte OP_RETURN limit, so the original design used two unspendable Taproot outputs; one OP_RETURN is cleaner and avoids permanently enlarging the UTXO set.
- Ekrem describes Citrea as a programmable Bitcoin layer that batches Bitcoin transactions into ZK proofs and posts them to Bitcoin. He says compressed state updates can make payment channels more efficient to open than Lightning channels.
- Ekrem says Citrea has operated live for almost a year, with about 110 BTC on the network. Clementine V2 uses succinct garbled circuits to reduce operator collateral requirements by roughly 100 times, which could make withdrawals more live by enabling more operators.
- Ekrem says Citrea's first bridge interface was a difficult command-line tool, so the team built a web app for deposits and withdrawals. Testnet operation and bug bounties helped harden the network, though the team also received incorrect AI-generated bug reports.
- Ekrem says Citrea's ZKVM uses post-quantum STARK proofs but compresses them with Groth16, which is not post-quantum secure. He says switching to STARK batches is feasible, while practical post-quantum bridges and signatures need more expressive Bitcoin scripts or a protocol-level signature scheme.
- Ekrem prefers OP_CAT because it could support both covenants and script-based ZK verification. He says sibling-commitment covenants could remove Clementine's signer set, while CTV offers a less direct workaround; more script expressivity would improve bridge trust assumptions more than proof efficiency.
- Buffer says Spaces Protocol anchors names to Bitcoin with 32-byte commitments rather than putting full records on-chain. Owners sign records such as payment addresses and social handles, then publish them through off-chain cert relays; open-source clients can validate the protocol against a Bitcoin node.
- Buffer says Spaces Protocol limits auctions to 10 new names entering the active process per day, with a 10-day auction that extends when a new bid arrives on the final day. He reports about 3,700 top-level spaces registered and says roughly 1.5 BTC has been burned through auctions.
- Andrew says top-level Spaces names expire if their owner makes no on-chain operation for a year, allowing abandoned names to return to auction; names under the top-level name never expire. Buffer says an at-Bitcoin handle costs about $25, while operators set their own prices.
- Andrew says Spaces Protocol names remain available to competing implementations, so adoption depends on wallets and applications agreeing on the same namespace. He says the protocol is continuing on Bitcoin rather than committing to support a proposed Bitcoin fork.
- Kevin argues Bitcoin's social consensus develops slowly and cannot be replaced simply by declaring a fork the new Bitcoin. He criticizes BIP110 supporters for opposing centralized control while creating a centralized process, and treats other forks as experiments whose value depends on whether users adopt them.
Privacy (11)
- Ekrem says Citrea acquired Crest, a self-custodial privacy wallet that uses a Zcash-style shielded pool. Users can deposit from Bitcoin, Lightning, and other chains, then withdraw to other chains; Crest plans to flag known illicit funds through a proof-of-innocence process.
- Ekrem argues shielded pools can protect ordinary users as well as large holders from transaction tracing, targeted theft, and disclosure of balances. He says users can remain in a shared pool and withdraw smaller amounts over time, while withdrawing the same amount deposited can reveal the link.
- Ekrem says Chainly previously built a proof-of-innocence circuit for Tornado Cash after sanctions, letting users show that withdrawals were not linked to known Lazarus Group hackers without revealing their identity. He says similar checks can keep flagged funds out of Crest without freezing users' funds.
- Ekrem says Citrea chose Taproot as his favorite Bitcoin soft fork because it enables BitVM designs. He argues Bitcoin needs privacy and everyday payment use alongside its store-of-value role, and that actual usage helps demonstrate demand for better privacy.
- Kevin says customer-data leaks can expose hardware-wallet buyers to physical threats, and purchase records can be linked with hotel, travel, or conference data. The host also describes the Entropy Lab dispute as an effort to give users tools to inspect seed-generation entropy without trusting a hardware manufacturer.
- Buffer says users can resolve Spaces handles in Nacho and associate Bitcoin, Lightning, and other addresses with social accounts. Andrew warns against receiving funds at a permanent public address, and describes building tools for silent payments, decentralized web hosting, cert relays, and identity proofs.
- Kevin argues Bitcoin offers people a way to move wealth across borders without carrying physical assets or disclosing balances. He says his optimism comes from Bitcoin's usefulness amid political and financial uncertainty, not from its price, and favors choosing jurisdictions where people are treated better.
- Peter Todd says he joined Zcash's Sprout trusted setup because he could contribute technical care and was willing to take the risk. He traveled across British Columbia, bought a laptop in person, used DVDs to move data, and destroyed the machine after the ceremony.
- Todd says the Zcash ceremony's software undermined its security because the Linux distribution and Rust compiler were not deterministically built. He also says a flaw in Zcash's cryptography let audit-record data support fake proofs, and that the records disappeared before the issue was fixed.
- Todd says Zcash offers a large anonymity set if its cryptography works, but users still face risks from timing and exchange activity, and the chain's growing state limits its ability to scale globally. He contrasts its shielded-pool privacy with Monero's ring signatures, which he says provide a smaller set of plausible senders.
- Todd says Zcash can be useful alongside other privacy tools, especially compared with account-based crypto systems that reuse a single account for incoming and outgoing transactions. He says Zashi's ability to swap between currencies helped make Zcash practical for some users.
Agents (1)
- Ekrem lists lending, borrowing, covenants, multisig vaults, and agentic payments as potential Citrea applications. He describes giving an AI agent a wallet spending limit of $10 per day while a hardware wallet remains the authorizer.
Payments (1)
- Ekrem explains an eCash replay-protection technique: sign a transaction spending Bitcoin with the maximum locktime, making it unconfirmable on Bitcoin while eCash treats the locktime as zero. He cautions users not to risk their Bitcoin on a fork unless they understand the process.
Custody (5)
- Kevin says Liana combines multisig with timelocked recovery or inheritance paths: if the owner stops using the wallet, a recovery key can eventually access the funds. He says vault covenants could make recovery active instead, but users still need to understand the waiting period and manage keys.
- Kevin estimates Liana has a few thousand users, not tens of thousands, and says many Bitcoin holders still choose single-signature wallets despite security risks. He argues custody design should match spending habits: frequent spenders need usable setups, while long-term holders can tolerate more complex recovery paths.
- Kevin says Wizard Sardine stopped developing Revolt, a presigned-transaction vault system, because companies found it too complex and demand was low. He expects covenants to make it more practical; he also favors covenant designs that do not require users to specify an exact deposit amount in advance.
- Stu says he added Sapio script emulation to Bark, enabling script-emulation experiments with VTXOs. Kevin says Sparrow is a capable wallet but does not support Miniscript, while cooperative-custody services can enforce spending limits at the cost of relying on a third party.
- Markowitz and Shirtness describe a path from custodial Bitcoin purchases toward assisted self-custody and, eventually, full self-custody. They say the Pivot will match each credit union with suitable technology partners rather than impose one custody product or setup.
Startups (1)
- Kevin says Wizard Sardine relies on investor funding and monetizes Liana through business infrastructure services rather than individual subscriptions. He is seeking a sales lead and argues that open-source Bitcoin tools need a sustainable revenue model without relying on users' donations.
Adoption (1)
- Jesse Markowitz and Kyle Shirtness say the Bitcoin Pivot advises credit unions on Bitcoin education and adoption. They present credit unions as member-owned, community-focused institutions that already provide financial education and could introduce Bitcoin to people who trust them.
Lightning (1)
- Markowitz and Shirtness say credit unions could support Lightning, Ark, or Fedimint services and use Bitcoin to deepen member relationships. They argue credit unions' education mission and member focus distinguish them from institutions seeking to rehypothecate customer Bitcoin.
Banking (1)
- Shirtness says credit unions face consolidation as liquidity pressures grow, citing industry expectations that roughly one-third could merge by 2030 and another third over the following decade. He sees Bitcoin services as a way for credit unions to adapt and remain relevant to younger members.
War (1)
- Todd says he supports Ukrainian military logistics through donations that help obtain vehicles; he described one armored truck completing 12 combat missions before being hit, with every soldier inside surviving. The host sent Todd one ZEC for the LadaCoin fund during the interview.
Open Source (1)
- The host describes TabConf as a loosely structured developer gathering and says organizers announced this would be its final edition. Andrew says he plans to permanently close the at-TabConf namespace after one final batch of attendee handles.

