The record

Publisher-dated 30 July. Revised to add Mk4/Q/Mk5 scope and later the Mk3 4.2.0 fix; exact revision times are unresolved.

The original narrow advisory. Stated Mk4/Q/Mk5 'not affected based on our early analysis'.

Coinkite's publication index, retained to detect additional incident material.

Coinkite's own chronology of public security research, coordinated disclosures, paid private reviews, internal findings and advisories affecting COLDCARD, announced in the vendor's 4 August public-record post (coldcardwallet-2084731768632991801). At first capture…

The vendor's own post on a temporary change to its customer-data retention and blanking practices after the incident. Registered 7 August 2026 because the record already held the 2 August…

Which firmware is actually being offered, and when it appeared.

Live submission portal used to check the public client-code, fee and submission interface described on the threshold-wallet migration page.

Official OpenAPI description captured through its stable JSON endpoint. It documents admission rules, best-effort handling and the request schema.

Terms of Sale. Caps aggregate liability at the purchase price, disclaims warranties, reserves arbitration at Coinkite's sole option, waives class actions and selects Ontario law. Quoted on /response/legal/ alongside sections…

Primary Debian advisory for CVE-2008-0166, including the affected release period and instruction to regenerate cryptographic key material.

Primary Android statement on improper PRNG initialization affecting some cryptographic applications, including Bitcoin wallets.

The statement adds that a COLDCARD-generated seed imported into a Passport remains at risk.

The article the twelve-post FAQ thread points at. Covers who may need to move funds, how Trezor backups are generated, and the related scam wave.

The pre-incident entropy description: hardware TRNG from transistor noise, a PRNG XOR'd into it, SE1/SE2 boot seeding, SHA-256 whitening, and the line that dice add "to the 256 bits of…

Published five weeks before this incident, about a physical-mail campaign using a post-quantum firmware-upgrade pretext. States that Coinkite would never send a paper letter, that the mail is a scam…

Registered on 2 August 2026 after a public claim that the store had been updated to disclose that remaining stock ships with affected firmware rather than sales being halted. Whether…

Unchained's help-centre article on replacing vault keys, updated with incident-specific guidance: it names the July/August 2026 Coldcard vulnerability, tells clients with two Coldcard-generated keys to consider broadcasting via Slipstream, and…

Casa's standing Coldcard support document. As of 3 Aug 2026 Casa has published no blog post on the incident; its only public statements are two X posts (casa-incident-guidance, nneuman-casa-migration-video). Registered…

Watch page. As of 3 Aug 2026 the newest post is 15 days old and there is no incident post; registered so the appearance of one is captured with timing.

Block's full vendor report on the Bitkey relationship-enrollment bug reported by 1440000bytes: enrollment secrets and 2nd-generation action-proof nonces came from kotlin.random.Random, a non-cryptographic generator, so a compromised service observing enough…

OpenSats' own 6 August announcement, by Gigi and the organisation, that red team applications will be prioritised for the foreseeable future, with a dedicated path at opensats.org/red and reimbursement of…

Ledger chief technology officer Charles Guillemet's primary incident article, covering Ledger's account of the mechanism, entropy, certification, source availability and AI-assisted exploitation. Held directly rather than through the Reddit relay…

Charles Guillemet's follow-up position on open source and security, published in the incident's aftermath and promoted by Ledger's already registered social post. Held as the direct article behind that response…

Ledger's official incident FAQ, linked from its stickied community-moderator statement. Held as a primary competing-vendor response and as the direct support document behind the moderator post. Security and product claims…

Official current consolidation used for the application, non-waiver, arbitration and class-proceeding provisions summarised on the legal-context page.

Official statute page used to check commencement status. The page stated on 1 August 2026 that the Act was not yet in force and would commence by proclamation.

Official vulnerability record for the Trust Wallet browser-extension generator, affected versions, 32-bit entropy bound and reported exploitation period.

Independent binary-level comparison of vulnerable and fixed Mk3 firmware, with a synthetic proof of concept. The repository deliberately excludes enumeration, wallet-recovery and fund-targeting capability. Its candidate-state analysis is the author's…

Rapidly updated independent postmortem built from frozen chain data and public reports. It documents its derivation and attribution rules, but its wave grouping, entity attribution and counterfactual conclusions remain the…

Independent re-derivation of fix commits, on-chain movements and vulnerable versus patched firmware symbols. Its README excludes real-seed recovery and labels unfinished work explicitly; deeper repository files include public transaction identifiers…

Read-only security audit published as a gist on 2 Aug 2026 and dated 17 June 2026, weeks before the incident became public. Weak RNG was in its stated scope and…

Primary Randstorm disclosure describing vulnerable BitcoinJS-derived browser wallets and the browser- and date-dependent attack surface.

Primary disclosure for CVE-2023-39910, including the 32-bit MT19937 seed funnel, partial impact accounting and comparison with the Trust Wallet incident.

Long-form post-mortem by the Liana wallet vendor: section 1 addresses Liana users and descriptor game theory, the rest reconstructs the flaw and argues that imported and dice-generated seeds remain exposed…

Wizardsardine's second incident analysis, a deeper technical autopsy than its 1 August post-mortem: the announced scope is the actual entropy level of the affected generator, the collision risk, and each…

Praveen Perera's follow-up to his Wave 1 key-reconstruction work: what he tried against the final 153 unreconstructed addresses, checked against the published Galaxy victim lists. First-person account of independent reproduction…

Dustin Dettmer's walkthrough of the COLDCARD firmware commit history tracing how the predictable generator path was introduced. Published on the bitcoin++ Insider Edition substack; its commit-level claims are checkable against…

Reimplements the MicroPython fallback and the libngu mixer, generates a synthetic victim wallet through the affected path, then recovers its mnemonic by searching the timer and skip space. The victim…

Two offline tools: a collision simulation over the reduced search space, and a static scanner that flags the defined-ness guard in a firmware source tree. The scanner reads source directories…

Greg Maxwell (nullc), commenting on the bitcoin++ Insider writeup, disputes the framing of the defect as a small build-flag change and states the mechanism differently: the commit added the whole…

James Check's subscriber PSA with step-by-step owner guidance. Held as independent incident-response guidance from an analyst, not a custody provider; registered in this section because it circulated as the kind…

Primary source behind the VULN-109 prior-discovery claim. States that a September 2025 private audit flagged the single-source RNG class (SE TRNG disabled at the source, ae.c:666) and was never submitted…

mempool.space Research's incident guide, published after the first four drain waves. It separates affected firmware and seed-generation cases, recommends migration steps and links its technical and funds-accounting claims to primary…

The method behind cktripwire-honeypot-monitor, linked from the scoreboard and registered separately so the experiment's stated design is held as a document rather than inferred from its results. It describes how…

Blockchain Unmasked's first-hand account of investigating earlier victim reports and warning Coinkite and public agencies before the July 2026 sweep. It describes its own 2024 investigation, correspondence and hypothesis development…

Commit-level reading of b18723dd (1 March 2021), the libngu integration, which the report says moved only seed.py and random.py from the ckcc.rng hardware API to ngu.random while backups and file…

Attribution argument that the pseudonymous GitHub account switck and Peter D. Gray of Coinkite are one person, resting on a 2020 public exchange read through the GitHub API and on…

Orange Surf publishes a technical analysis of the COLDCARD key exposure, documenting the author's understanding of the vulnerability and its implications. Held as a dated independent technical account. The analysis…

Migration protocol plus a warning about scam recovery services.

Newsletter #416 led with the incident. It carries the unitemised estimate 'exceed 1,000 BTC' and dates the theft transactions to 29 July, possibly consistent with a US-local date; the newsletter…

Reference write-up carrying 594.48 BTC (~US$38M) confirmed and 1,082.59 BTC if the earlier set is linked. KeychainX is a wallet-recovery firm and says so on the page; that commercial context…

Colin Crossman's 6 August op-ed arguing that machine-readable code ends security through obscurity: Coinkite's move from a free-software licence to source-available terms changed the economics of finding the bug, not…

Jameson Lopp's 6 August essay for Casa, and two things at once: a restatement of the incident for a general reader, and Casa's account of its own security practice. It…

Luke Childs publishes a writeup on Anzen, a wallet design presented as a response to Bitcoin's self-custody trilemma in the wake of the COLDCARD incident. Held as a dated product…

Citadel21 publishes an article titled The Paranoid Wallet, discussing wallet design in the context of the COLDCARD entropy incident. Held as a dated commentary on post-incident wallet architecture and trust…

First-hand report with a photograph of the June 2026 physical letter impersonating Coinkite: post-quantum security-update pretext, 30 June 2026 deadline, personalised QR code, forged CEO signature. The poster asks whether…

Second first-hand report of the June 2026 letter campaign, with a photograph of a slightly reworded variant carrying the same 30 June deadline and QR pretext. The thread title states…

A discussion thread claiming an LLM prompted only to "check for vulnerabilities" surfaced the defect after eight minutes, and asserting the theft exceeded $100m. Both figures are the thread's own…

The earliest incident thread identified on Stacker News: Murch relaying the first Reddit drain report while the recipient address was still collecting, the evening before Coinkite's disclosure. The drain claims…

itsrealfake's device-and-firmware breakdown of which COLDCARD models and firmware ranges carried the RNG defect. The post body is a single image, which this text-only capture does not hold; the comment…

itsrealfake arguing that dice-roll seed generation was safe from the RNG bug and urging owners not to retreat to exchanges. Bears on the dice and mitigations pages; the safety claim…

Stacker News co-founder k00b relaying the vulnerability announcement, citing Block's report for the affected model and firmware ranges. The main announcement thread on the site and a principal venue for…

itsrealfake's technical walkthrough of the entropy failure, stressing that a firmware update does not repair an already-generated weak seed. The technical claims are the author's; where they overlap the vendor…

sime arguing that airgapping protects against exfiltration, not against generating a bad seed, so a connected wallet mixing host entropy could have fared better. A design-philosophy dispute relevant to the…

Scoresby asking how owners' spouses responded to the vulnerability. Community colour on how the incident landed inside households; part of the response record. Captured through the site's public GraphQL API…

schmidty linking Bitcoin Optech newsletter #416, which warned about the COLDCARD vulnerability. The newsletter itself is registered as optech-416; this source holds the Stacker News discussion of it. Captured through…

Wumbo asking whether emergency sweeps to new wallets would move mempool fees on day one. Small thread, held because fee impact is part of the incident's measurable fallout and Galaxy's…

Scoresby crowdsourcing a short migration guide for COLDCARD owners, with the author warning he would delete it if stackers found serious flaws. Community guidance drafted in public on day one…

SimpleStacker's Pleb Economist column on the incident and the law of large numbers: with enough users, rare weak-entropy events become certainties. Opinion, attributed to the author. Captured through the site's…

HardMoney asking whether self custody can scale to the masses when seasoned users doing most things right were still exposed. Part of the self-custody-tractability debate the incident reopened. Captured through…

Scoresby reposting NVK's 'To all Coinkite users and the entire Bitcoin community' statement, urging owners to move funds before reading further. The statement text is NVK's; this source captures it…

hasherstacker's essay 'The False Promise of Commercial Hardware Wallets', arguing the incident indicts the product category rather than one vendor. Opinion, attributed to the author. Captured through the site's public…

Bitcoiner1 asking whether Coinkite is legally responsible for the lost funds. Early community framing of the liability question; no legal reasoning here is endorsed. Captured through the site's public GraphQL…

HardMoney asking what hardware wallets should replace a COLDCARD. A migration-destination thread; mention of any product here is the posters', not a recommendation by this project. Captured through the site's…

Scoresby checking exchange social accounts and finding no COLDCARD warnings, with screenshots. Held as evidence of provider silence in the first day, complementing the custody-coverage record; the screenshots themselves are…

Aeneas on the media coverage of the incident and AI-generated commentary, engaging with Coinkite's technical backgrounder. Opinion and media criticism, attributed to the author. Captured through the site's public GraphQL…

siggy47 describing an email Swan sent clients about the incident. Provider communications that reach clients by email rather than public posts are otherwise uncapturable; this thread is the public trace…

HardMoney's 'Coldcard Sweep Watch', tracking the draining address via an X post by bradytc_. Community chain-watching during the active theft window; figures quoted are the cited sources', not verified here…

chungkingexpress's 'Can we have a serious talk about the LARP in Bitcoin', a long criticism of how Coinkite and NVK handled and framed the incident. One of the largest discussion…

fanis linking a guide: 'Critical Coldcard flaw: what happened, who is affected, and what to do'. Link post; the value captured is the discussion. Captured through the site's public GraphQL…

Scoresby relaying Galaxy Research's identification of a third wave of drains, 207.7294 BTC, taking the estimated observed total to 1,367.05 BTC. The numbers are Galaxy's reported figures; Galaxy's own publications…

Scoresby discussing Dusty Daemon's code analysis 'When random.bytes() runs but doesn't work', on the failed attempt to override the RNG in C. Technical discussion of the root cause; the analysis…

BITC0IN's PSA with owner advice, including the Mk3-without-passphrase case. Community guidance from the response window; specific claims are the author's and partly contested in replies. Captured through the site's public…

realBitcoinDog describing setting up a BitKey because of the incident and disliking the multisig custody trade-offs. A migration-experience account; the product criticism is the author's and this project does not…

chungkingexpress requesting comment on unbroadcast transactions as a failsafe, prompted by owners who were away from their seeds or devices during the emergency. A design discussion arising directly from the…

billytheked noting Zero Hedge's coverage, among the first mainstream financial press pickups, quoting its third-wave loss figure. Part of the media-spread record; the figures are the outlets' reported numbers. Captured…

desertdave collecting hot takes on the incident. Link-and-comment thread held as a sample of community sentiment. Captured through the site's public GraphQL API: the rendered pages crash the capture tab…

Lobotomite relaying Lopp's report of COLDCARD firmware updates bricking devices during the emergency update push. The bricking reports are secondhand here; they matter to the record because update risk shaped…

hyperfree reporting an OP_RETURN message offering money laundering to the drainer. Part of the record of on-chain messages to the operator; the message's authenticity is not established. Captured through the…

0xbitcoiner quoting a comparison that 39.6K BTC moved on 31 July, the most in a day since the FTX collapse, attributed to the incident's sweep traffic. Reported chain statistic; the…

siggy47 warning about Foundation-themed phishing during the incident. Part of the scam-wave record: lookalike warnings and phishing attempts proliferated while owners were frightened. Captured through the site's public GraphQL API…

theonceler asking at what point the attack can be considered over: when remaining affected addresses have either moved or been drained. Frames the endgame question the chain monitors' numbers bear…

justin_shocknet reporting that NVK stepped down from the OpenSats board. The OpenSats statement is registered as opensats-nvk-board-departure; this source holds the Stacker News discussion of the governance fallout. Captured through…

sime resurfacing a 2020 aantonop talk on trust, seed generation and system complexity as prescient for this incident. Discussion of where trust sits in self custody. Captured through the site's…

gmd reporting that GLM-5.2 found the vulnerability easily, following a similar demonstration with Claude Code linked via Reddit. Part of the record of AI tools independently locating the defect, which…

supratic relaying that MARA Slipstream opened as a permissionless public good with no client code requirement, relevant to getting rescue transactions mined. The Slipstream materials are registered separately (mara-slipstream-portal, mara-slipstream-permissionless)…

FlorFina asking whether blockchain analysis could mistakenly blacklist clean coins after the exploit. Part of the record of feared long-term fallout for unaffected owners. Captured through the site's public GraphQL…

Scoresby on Rob Hamilton spending $10k scanning Bitcoin projects and finding multiple vulnerabilities, with the poster noting Hamilton's AnchorWatch markets a related service. The disclosure of that conflict in the…

raw_avocado's 'Dear podcasters & influencers', absolving recommenders who had pointed audiences at COLDCARD. Part of the recommender-responsibility debate; opinion, attributed to the author. Captured through the site's public GraphQL API…

kepford's 'ColdCard and Personal Responsibility', on DYOR and trust in confident people. Part of the responsibility-framing debate the site's dice and passphrase pages must not prejudge. Captured through the site's…

jimmysong linking Bitcoin Tech Talk #512, which covers the COLDCARD RNG among other topics. Link post; the newsletter is the primary, this source captures any discussion. Captured through the site's…

justin_shocknet reporting Boltz and ZeusLSP temporarily shutting down swap services, with screenshots and a Zeus X post. Incident fallout on Lightning swap infrastructure; one of the largest response threads. Captured…

tuma linking 'The COLDCARD Incident, Last Week in Bitcoin (Jul 27 - Aug 02)'. Link post to a weekly roundup; held for the discussion and as a pointer to secondary…

hasherstacker linking 'Everything You Need to Know About the COLDCARD Hack'. Link post to secondary coverage; held for the discussion. Captured through the site's public GraphQL API: the rendered pages…

HardMoney linking the Bitcoin Policy Institute's explainer of the bug. Link post; the explainer is the primary and may warrant its own registration, this source captures the Stacker News discussion…

anon relaying the peerswap maintainer's advice to disable peerswap temporarily while the project is audited by AI. Incident-adjacent fallout on adjacent software, driven by the AI-audit wave the incident accelerated…

An anonymous satirical post asking how to privately spend 1367 BTC 'given to me by NVK's friends'. Held as a sample of community sentiment and gallows humour toward Coinkite; it…

anon asking how 100 dice rolls could be attacked or botched, assuming verified seed phrases. Directly relevant to the dice-mitigation guidance the site carries. Captured through the site's public GraphQL…

itsrealfake describing a personal test of a COLDCARD's dice-roll seed generation against the computer's randomness, posted the day after disclosure with the aside "DYOR, and all that." The body carries…

IjawMan arguing the incident has a bright side: a mass awakening to wallet hygiene, update habits, seed entropy and passphrases. Replies correct the decentralisation framing and debate passphrase strength, with…

Mate2237 relaying CoinDesk's 31 July coverage of the drains at roughly 600 BTC and about 38 million dollars, and asking whether custodial wallets are really safer. The one reply points…

YellowSwap opening a lessons-learned thread on the Bitcoin Discussion board, drawing one of the longer forum discussions of the incident's takeaways for holders. A community response and sentiment record alongside…

flatfly opening the forum's main incident thread on the Bitcoin Discussion board, tallying the drains at 1360.23 BTC and still rising; other registered threads on the forum point here as…

SaddamoftheWest arguing the incident is a turning point for Bitcoin and self custody, framing the reaction as an assault on self custody by latecomer influencers. Replies dispute the revolution framing…

UchihaSarada writing an incident-motivated explainer on seed entropy and optional passphrases, arguing a passphrase cannot repair a weakly generated seed. The post links coinkite-mk3-advisory and coinkite-backgrounder, quotes btcsessions-passphrase-loss-report as evidence…

SimpleStacker posting an investigative history of the COLDCARD entropy bug. A substantial retrospective discussion of the vulnerability and disclosure history; the historical account and technical claims are the author's, not…

bennet examining what the incident says about the limits of the “don't trust, verify” framing. A community debate about code review, product trust and self-custody practice, alongside stackernews-personal-responsibility and stackernews-dear-podcasters…

UncleJim21 asking whether the incident resembles the vendor's historical “retirement attack” concept. Documents post-incident scrutiny of earlier COLDCARD material, alongside coldcard-retirement-attack-claim and reddit-retirement-attack-resurfaced. Any implication of intent is speculation by…

denlillaapan linking Matt Levine's Money Stuff coverage of the COLDCARD heist. A link post held for the discussion and as a pointer to mainstream financial coverage; claims and characterisations belong…

seed-cat drafting self-custody best practices in direct response to the incident, arguing the technical community failed to standardise practices that balance complexity and security: 2-of-2 multisig, multi-vendor signing extended to…

satscraper opening a discussion of whether wallet software should warn users about low-quality entropy while generating a seed. A distinct prospective design question raised in the COLDCARD incident's aftermath, rather…

Scoresby linking Coinkite's official 4 August investigation statement, separately held as coldcardwallet-2084731768632991801. The link post's eight-comment discussion records community reception of that statement; the vendor's claims remain attributed to Coinkite…

raw_avocado asking readers to preserve NVK's public interactions amid a reported deletion of posts, with an eight-comment discussion. A record of the community's preservation response during the incident, not confirmation…

nerd2ninja arguing that a CTV-enabled vault could have given an owner time to claw funds back after a drain, and contrasting that proposed design with multi-vendor multisig and dice-generated entropy…

ignaciob relaying an alleged Pathfinder COLDCARD Mk3 test in which WatchGuard detected a sweep and raced it with a pre-signed replace-by-fee transaction, naming a transaction and fee amounts. This is…

dim_mak5 asking how holders can verify, rather than trust, the entropy of any hardware wallet, framing the COLDCARD hack as proof of the problem and ranging into quantum, AI and…

justin_shocknet linking Fireship's video coverage of the COLDCARD incident, which is not separately registered or captured here. A link post held as minor colour marking the incident's arrival in mainstream…

babo relaying a Telegram debate over casino-grade dice for seed generation, citing what another user describes as a 1971 Harvard study of 219 commercial dice that found bias worth at…

BitcoinHandsOn2 publishing a printable dice-to-seed-phrase worksheet, explicitly motivated by lost trust in hardware-wallet entropy after the incident, and asking for feedback on its logic. A small community-built artefact of the…

lloyddunne in October 2023, praising the COLDCARD yet naming seed-generation trust as the thing that kept them up at night, and proposing normalised offline seed generation with dice and independent…

Oshosondy relaying a Bitcoin Magazine report that US spot bitcoin ETFs took in a claimed $626 million of fresh cash after the hack, citing Farside Investors, and asking whether fear…

efrat interviewing Trezor CTO Tomáš Sušánka days after the Coldcard hack, covering entropy, Trezor's RNG design, open-source review limits, and multisig. A vendor competitor's perspective on the incident and what…

mkmloom comparing BTC lost through exchange failures and insolvencies against the Coldcard incident, claiming Coldcard accounted for 0.081% of the amount and arguing for diversification and self-custody. A community reframing…

Scoresby relaying and critiquing Coinkite's public correction to Jack Mallers, in which the vendor says the weak PRNG was not an intentional fallback but inherited behaviour from MicroPython that became…

barrysty1e proposing an audio-based entropy wallet after recent hardware-wallet entropy flaws, with discussion of microphone preprocessing, frame-selection determinism, entropy measurement and mixing independent sources. A community-driven mitigation proposal in the…

Natalia posting a merchant-oriented BTCPay Server setup guide framed around improving security after recent hacks, comparing xpub deposit workflows, Lightning receive options and third-party plugins. Incident-contextual guidance for merchants; the…

Abiky asking how the COLDCARD incident will affect the self-custodial industry, whether users will abandon hardware wallets for CEXs or ETFs, and how long the trust damage will last. Replies…

k00b relaying a detailed postmortem that claims the Mk3 and Mk4 candidate spaces are smaller than previously reported, estimates sweep costs and collision probabilities, and compares device-class vulnerability. The numerical…

hasherstacker links to a MARA Foundation announcement that 9,000 bitcoin were rescued from Coldcard multisig setups. Held as a link-post record of a claimed large-scale rescue operation during the incident…

Scoresby links Praveen Perera's analysis of the 1,082 BTC Coldcard drain, focusing on 153 swept addresses that researchers have not been able to reconstruct seeds for. Perera describes a search…

Nittany asks whether rolling dice to provide user entropy produces safe seeds on COLDCARD Mk4, Mk5 and Q devices in the wake of the ongoing incident. The thread documents an…

Scoresby relays Galaxy Research's 14 August update on the Coldcard investigation: 190 victim contacts, 1,778.84 BTC ($112.7m) stolen from more than 8,600 addresses, and a possible total of 2,417.35 BTC…

Carries the 4.2.0 entry and the do-not-generate banner.

The #ifndef guard and the generator. On 5 Aug 2026 upstream merged #61, replacing Yasmarang with a SHA-256 Hash-DRBG and rejecting reseeds under 32 bytes; the guard's presence test is…

Incident-response PR open with no maintainer response present in the 1 Aug 2026 capture. Retained to record later review or status changes.

Patch content for the open incident-response proposal. Kept separately from the conversation and review-state capture.

Broad incident-response PR. On 1 Aug the maintainer called the diff too large and the author offered a three-PR split.

Patch content for the open incident-response proposal. Kept separately from the conversation and review-state capture.

Open incident-response proposal to absorb a bytes-like seed into all Yasmarang state words. Companion to Coldcard/firmware PR #691.

Patch content for the open full-width reseed proposal. Kept separately from the conversation and review-state capture.

The live upstream proposal after #59 and #60 were closed by their authors on 1 August. Replaces the generator with a SHA-256 Hash-DRBG and requires a reseed seed of at…

Patch content for the current upstream proposal. Kept separately from the conversation and review-state capture.

First of the three-PR split of #59 that its author offered on 1 August, and the only one closed: at first capture on 7 Aug 2026 the page shows jgmontoya…

Patch content for #62. Kept separately from the conversation and review-state capture.

Second of the three-PR split of #59, open at first capture on 7 Aug 2026 with one commit. Registered from its own page rather than from the title shown on…

Patch content for #63. Kept separately from the conversation and review-state capture.

Third of the three-PR split of #59, open at first capture on 7 Aug 2026 with three commits: rejecting two-word entropy cycles, hardening entropy backend boundaries, and gating the backend…

Patch content for #64. Kept separately from the conversation and review-state capture.

Merged 7 Aug 2026. Referenced from Coldcard/firmware PR #707 as a required libngu change for the external RNG get path. Registered during the 7 Aug 2026 claim sweep to fill…

Patch content for #68. Kept separately from the conversation and review-state capture.

Merged 6 Aug 2026. Referenced from Coldcard/firmware PR #707 over flash-space concerns with the updated libngu dependency. Registered during the 7 Aug 2026 claim sweep to fill a source the…

Patch content for #56. Kept separately from the conversation and review-state capture.

Open incident-response proposal to remove the firmware-side four-byte truncation. Depends on the libngu PR #60 change.

A seven-commit proposal in the vendor's own firmware repository, open at first capture on 7 Aug 2026, opened by scgbckbone from a branch named improve_seed_gen-public. Its commits mix secure-element entropy…

Patch content for #707. Kept separately from the conversation and review-state capture.

Opened by scgbckbone 7 Aug 2026 and explicitly aims to replace PR #707. It improves #707's mash method by hashing microsecond-resolution timing at the raw key edge, requires 128 presses…

Patch content for #713. Kept separately from the conversation and review-state capture.

Closed unmerged 5 Aug 2026. Referenced from the Coldcard/firmware PR #707 page as the earlier full-width reseed proposal; the page says it was superseded by #707. Registered during the 7…

Patch content for #697. Kept separately from the conversation and review-state capture.

Patch content for the open firmware-side full-digest proposal. Kept separately from the conversation and review-state capture.

Community proposal (Silexperience210, 3 Aug 2026) arguing the 31 July hotfix leaves the STM32 RNG latched after a single seed/clock error, so every later call faults forever; proposed a recovery…

Patch content for the TRNG error-recovery proposal. Kept separately from the conversation and review-state capture.

Bugfix (scgbckbone, 3 Aug 2026) detecting the STM32 RNG status error flags, retrying safely and failing closed. Named by Coinkite's 4 Aug 2026 notice as the fix for the post-hotfix…

Patch content for the RNG error-flag detection and retry proposal. Kept separately from the conversation and review-state capture.

Merged source-level Mk3 hotfix. Captures the pull-request provenance and merged source commit associated with 4.2.0; the signed release record is separate.

Patch content for the merged Mk3 v4-legacy hotfix. Kept separately from the pull-request conversation capture.

Merged Edge source and release-history integration. Captures the pull-request provenance behind the published 6.6.0X and 6.6.0QX releases.

Patch content for the merged Edge hotfix. Kept separately from the pull-request conversation capture.

Immutable patch for the direct mainline source commit contained in the normal Mk4/Mk5 v5.6.0 and Q v1.5.0Q release histories.

Merged community-response record. Bitcoin.org removed its COLDCARD and COLDCARD Q listings under the site's published wallet-listing criterion after the incident.

Open downstream response prompted by the COLDCARD disclosure. The author reports that SatSigner's default path was sound and proposes fixes for separate optional dice and coin paths.