Corrections: what our pages said, and what they say now

Last reviewed:

When a page on this site turns out to say something wrong, we fix the page and record the change here: what it said, what it says now, why, and the source we checked. If you spot an error, write to hello@knowingbitcoin.com with the page address and, if you can, a link to the original source, such as the release notes or the maker’s own page.

How to use this log

  • Did you act on an older version? If an entry touches something you did, for example you created a seed on a Coldcard or you run a Knots node, open the corrected page and follow its current steps.
  • Need to act on a security problem? Problems that need action from you are collected in our security advisories.
  • Want to cite an entry? Each one has its own link: the # sign next to its title.
What counts as a correction

We list changes to facts: dates, version numbers, prices, what a product does, what a specification or another source says, and what we said about our own testing. Rewording, layout changes, new sections and changed web addresses are not listed.

The log covers corrections since May 2026. The first one is from . The change reference at the end of each entry identifies the edit in our version history. We checked every source linked on this page on 3 and 4 November 2026.

How to test that your written seed backup is correct #

Corrected on · 1 page

Page corrected
What the page said
The guide said you could confirm your paper backup by comparing a public key or address shown by the same device that already holds the seed in memory. That check passes even if a word on the paper is miscopied. It also suggested typing the seed into a computer as one way to test.
What it says now
The guide now tests the paper itself: restore from the paper on a wiped device or a second device and compare the wallet fingerprint or first receiving address with the original, or use the backup check built into your device. It warns never to type the words into a website or program, and that if you find a mistake you should not reset the device you have before moving your funds to a new, tested seed.
Why
A test that reads the seed from the device's own memory cannot catch a copying mistake on the paper, and typing the seed into a connected computer is a leading cause of theft.
Source

Bitcoin Core and Bitcoin Knots now follow different chains #

Corrected on · 2 pages

Pages corrected
What the pages said
Our comparison, written in June 2026, said Core and Knots share the same consensus rules and “will never fork the chain”, so choosing between them was only a question of relay policy. A second page suggested switching to Knots for its stricter filters, as if that were only a relay setting.
What they say now
Relay settings on their own still cannot split the chain. Consensus changes can, and in August 2026 one did. Knots nodes enforcing BIP-110 split from the chain Bitcoin Core follows on 8 August 2026, and Knots 29.4.1 (2 September 2026) moved to a separate chain with a different proof of work, BLAKE2b. The comparison now opens with this update and shows how to check which chain your node is on. It also notes that Bitcoin Core no longer updates its 29.x versions, the code base current Knots releases are built on.
Why
BIP-110 is a consensus rule, not a relay setting. The pull request that marked it Closed in the BIPs repository, merged on 10 August 2026, says it “split to a new chain and stalled”. Knots’ own 29.4.1 release notes list “Hardfork: New BLAKE2b proof-of-work algorithm”. Bitcoin Core’s 32.1 release notes say versions 29.x and older are at “End of Life”.
Sources
Change reference
935a24e, 64b2c10

If you run Knots: how to check which chain your node is on

Coldcard seed flaw: fixed firmware for every model #

Corrected on · 4 pages

Pages corrected
What the pages said
Our advisory of 31 July 2026 said there was no fixed firmware for the Mk2 and Mk3, dated the flaw from version 4.0.0, and described the Mk4, Q and Mk5 as a “disputed group”.
What they say now
Every affected model now has fixed firmware: 4.2.0 for the Mk2 and Mk3, 5.6.0 for the Mk4 and Mk5, 1.5.0Q for the Q, and 6.6.0X or 6.6.0QX on the Edge track. On the Mk2 and Mk3 the affected public releases are 4.0.1 to 4.1.9. Coinkite now says seeds made on the Mk4, Q and Mk5 before the fix are affected too. New firmware does not repair an old seed: if yours was created before the fix, the coins still need to move to a new seed, unless you added at least 50 private dice rolls when you made it.
Why
Coinkite’s advisory now says “Fixed firmware is now available for every affected model and release track” and “Seeds generated on Mk4, Q and Mk5 before the fixed firmware releases are also affected, with about 72 bits of entropy rather than the expected 128 bits.” The same advisory says a seed made with at least 50 fair, private dice rolls is not at risk from this flaw alone. Coinkite’s list of historical disclosures describes version 4.0.0 as unreleased.
Sources
Change reference
935a24e, 0ad8e64, 64b2c10

Who is affected and exactly what to do

Electrum 4.8.3: servers that show fake transactions #

Corrected on · 1 page

Page corrected
What the page said
Our Electrum lesson had no warning about this attack. Its comparison with Sparrow also credited Sparrow with CoinJoin through Whirlpool, and it gave the size of the blockchain as 500+ GB.
What it says now
The lesson warns that some public Electrum servers were exploiting a flaw: right after you broadcast a transaction, a malicious server could show your wallet a fake one in its place and wait for you to raise its fee, which pays the attacker. Electrum 4.8.3 fixes it, so update. A wallet connected only to a server you run yourself was not affected. The comparison now lists Sparrow without CoinJoin, and the blockchain at about 780 GB (October 2026).
Why
Electrum’s security advisory GHSA-6jp4-8v48-cc5v (published 24 October 2026, severity High) covers every version below 4.8.3 and says “some servers are performing this attack in the wild”. Electrum’s release notes date version 4.8.3 to 23 October 2026. Sparrow’s 1.9.0 release notes say “Remove Whirlpool client”.
Sources
Change reference
935a24e

Lightning wallets: Mutiny, Breez and Wallet of Satoshi #

Corrected on · 17 pages

Pages corrected
Show the other 12 pages
What the pages said
Our February 2026 ranking named Mutiny the best web wallet and Breez the best wallet for merchants. Several Lightning pages described Wallet of Satoshi as custodial, which means the company holds your bitcoin for you.
What they say now
Mutiny and the original Breez app are no longer ranked. Mutiny shut down at the end of 2024. Breez now publishes a different app, Glow, which we have not reviewed. Wallet of Satoshi now says it is self-custodial, with a 12-word recovery phrase that only you hold. We have not checked how it works, so it stays out of our self-custody ranking until we do.
Why
Mutiny announced on 5 August 2024 that it would shut the wallet down “at the end of the year”, and mutinywallet.com now returns “not found”. Breez’s own recovery tool exists “so funds stay recoverable after the Breez app leaves the app stores”, and Glow is listed on the App Store by Breez Development Ltd. Wallet of Satoshi’s home page says “You hold a 12-word recovery phrase that only you know.”
Sources
Change reference
935a24e, 64b2c10

BOLT 12 offers: recurring payments are not in the specification #

Corrected on · 1 page

Page corrected
What the page said
Said BOLT 12 includes native support for recurring payments and subscriptions.
What it says now
Recurring payments were in early drafts of BOLT 12 but were left out of the version merged into the Lightning specification in September 2024. A proposal to add them back is still open, so the page now describes them as a possible future feature. It also mentions payer proofs, added to the specification on 27 July 2026, which let a payer prove they paid a specific invoice.
Why
The merged specification lists “Re-add recurrence” among possible future changes. The offers pull request (#798) was merged on 24 September 2024. The pull request to re-add recurrence (#1240) was still open on 4 November 2026.
Sources
Change reference
935a24e

How much randomness a seed phrase really has #

Corrected on · 5 pages

Pages corrected
What the pages said
Said the real risks to your bitcoin “have nothing to do with brute-force attacks on entropy”, told readers that generating the seed on a hardware wallet takes care of randomness, and said self-custody wallets “have no comparable incident history”.
What they say now
Twenty-four words can hold 256 bits of randomness, but only if the device really fills them with randomness. So the word count sets the maximum, not what you actually got. A firmware flaw disclosed in July 2026 made some Coldcard devices create seeds that could be guessed. The pages now recommend adding your own randomness: 99 or more rolls of a fair die give about 256 bits, because each roll adds about 2.6 bits.
Why
Block’s analysis puts the number of possible seeds on an affected Mk2 or Mk3 at about 2^40.7 at most (roughly 1.8 trillion) if the attacker knows the device’s ID, a number a computer can search through. CoinDesk reported that about 594 BTC was swept from around 500 wallets on 31 July 2026.
Sources
Change reference
935a24e

Keystone 3 Pro: battery, USB and claims we could not support #

Corrected on · 1 page

Page corrected
What the page said
The review said the Keystone 3 Pro runs on removable AAA batteries and transfers no data over USB, cited an “EAL 5+” certification without a source, and called it “the only device” that combines its features.
What it says now
It has a built-in rechargeable lithium-ion battery (1,000 mAh). Its USB-C port charges the device and can also carry data. You can switch data off in the settings to make it charge-only. The certification claim is gone. “The only device” became “one of the few”, since other air-gapped devices for many coins exist. The verdict did not change.
Why
Keystone’s store lists “Rechargeable Battery: Li-ion” and “Capacity: 1000 mAh / 3.7 Wh”. Keystone’s guide says the 3 Pro “supports secure USB data transmission” and shows how to turn it off for “charge-only mode”. ELLIPAL sells the Titan 2.0, also an air-gapped wallet.
Sources
Change reference
0ad8e64, 64b2c10

Phoenix does work with RoboSats #

Corrected on · 1 page

Page corrected
What the page said
Since our update of 22 June 2026, the RoboSats tutorial said Phoenix does not work with RoboSats because it cannot hold an invoice, and that Phoenix dropped self-custodial Lightning in version 2.5. Both statements were our error: on RoboSats’ compatibility page, the remark about version 2.5 belongs to a different wallet, SBW.
What it says now
The tutorial lists Phoenix as a wallet that works for RoboSats trades.
Why
RoboSats’ wallet compatibility page says Phoenix “does support invoice lock” and lists Phoenix 2.7.15 in its test table. The line “From 2.5 it doesn’t support lightning anymore” is in the SBW entry.
Source
Related correction
Change reference
64b2c10

The umbrelOS licence, and how StartOS runs apps #

Corrected on · 4 pages

Pages corrected
What the pages said
The Umbrel review said umbrelOS uses a proprietary “Umbrel License”, and the comparison said “PolyForm Shield or similar”. The comparison also said StartOS runs services in Docker containers. Our lesson comparing node platforms called all four of them open source, and another node guide said StartOS apps run as native services.
What they say now
umbrelOS is published under the PolyForm Noncommercial License 1.0.0: you may read, use and change the code for personal and noncommercial purposes, and commercial use needs Umbrel’s permission. The lesson now says the platforms’ licences differ and names umbrelOS’s. StartOS runs each service in its own LXC container.
Why
The licence file in Umbrel’s repository is the PolyForm Noncommercial License 1.0.0. The StartOS repository says “Services run in isolated LXC containers”.
Sources
Change reference
0ad8e64, 935a24e, 64b2c10

Products no longer sold, and out-of-date prices #

Corrected on · 16 pages

Pages corrected
Show the other 11 pages
What the pages said
Several pages recommended products that are no longer sold: the Foundation Passport Core (our “best overall” pick), the Coldcard Mk4 and the Start9 Server Pure. Prices came from earlier in the year: Coldcard Q $239, Trezor Safe 3 $79, Start9 Server Pure about $600.
What they say now
Products that are no longer sold are marked that way, and the Passport Core’s “best overall” place is under review instead of being handed to another device. Prices now carry the month they were checked (November 2026): Coldcard Mk5 $269 ($219 on sale), Coldcard Q $369 ($319 on sale), Trezor Safe 3 $59, Start9 Server One $899 to $1,399, Foundation Passport Prime €388.95. The order of our recommendations did not change.
Why
Foundation’s Passport Core page and Start9’s Server Pure page now return “not found”. Coinkite’s store sells the Coldcard Mk5 and Q only. The other prices come from each maker’s own store.
Sources
Change reference
0ad8e64, 64b2c10

Running a node on a Raspberry Pi: umbrelOS 2.0 and drive size #

Corrected on · 9 pages

Pages corrected
Show the other 4 pages
What the pages said
Our node guides described the older umbrelOS setup on a Raspberry Pi: a small 16 GB microSD card for the system, with the blockchain going onto an SSD. They called a 1 TB drive enough, and gave older figures for the size of the blockchain, such as “600+ GB”.
What they say now
umbrelOS 2.0 (22 September 2026) changed this. It runs from a microSD card of 32 GB or more and keeps your apps on that card. An SSD you plug in later is extra storage, so you move the Bitcoin Node app onto it before the blockchain syncs. Many Raspberry Pi 4 boards need a bootloader update first. The blocks took about 779 GB on 28 October 2026 and grow by about 80 GB a year, so the guides now recommend a 2 TB drive: a 1 TB drive has room for less than three more years of blocks.
Why
Umbrel’s Raspberry Pi guide (updated 22 October 2026) says: “We recommend running umbrelOS from a microSD card, 32 GB or bigger. Your apps and files are stored on the card too, and any USB drive you plug in later works as extra storage.” The chain size comes from blockchain.com’s daily chart.
Sources
Change reference
935a24e, 64b2c10

What we said about our own testing and our affiliate earnings #

Corrected on · 3 pages

Pages corrected
What the pages said
The Umbrel vs Start9 comparison said “We tested both extensively” and that the page “earns the same whichever platform you pick”. The hardware wallet guide said “After testing and reviewing all the wallets above”, and the Lightning wallet ranking said we had tested each wallet by sending and receiving payments.
What they say now
Each page now says how it was put together and when the facts were checked. The node comparison and the hardware wallet guide are based on official documentation, release notes and independent reviews. The Lightning ranking says it first ran in February 2026, and that in November 2026 we re-checked which wallets are still available and how each company describes custody, without new payment tests. The Umbrel vs Start9 page says both links can earn us a commission and that the amounts differ.
Why
We had no record of hands-on tests to back those sentences, and the two affiliate programmes pay differently. See our affiliate disclosure.
Change reference
0ad8e64, 935a24e

A security notice on pages that recommend Coldcard #

Corrected on · 4 pages

Pages corrected
What the pages said
These pages recommended Coldcard devices and said nothing about the seed-generation flaw disclosed in July 2026.
What they say now
Each page opens with a notice that links to our incident page, which explains who is affected and what to do. The notice was brought up to date on 3 November 2026 (see the entry on fixed firmware above).
Why
Some Coldcard models generated seeds with far less randomness than intended, and CoinDesk reported that about 594 BTC was swept from around 500 wallets. A page that recommends a device needs to say when that device has a known flaw.
Sources
Related correction
Change reference
1e8a61e

Who is affected and exactly what to do

Whirlpool and Samourai Wallet described as tools you could still use #

Corrected on · 38 pages

Pages corrected
Show the other 33 pages
What the pages said
37 posts and one lesson described Samourai Wallet’s Whirlpool CoinJoin as something you could still use. Some gave step-by-step instructions, and some said Sparrow Wallet could run Whirlpool. Five of those pages also presented the Wasabi Wallet coinjoin coordinator run by zkSNACKs, which shut down in 2024, as still operating.
What they say now
The step-by-step tutorial is now kept as a historical record. The other pages explain what happened and point to alternatives that were still running when we checked in July 2026. Sparrow is still described as a wallet, without Whirlpool. The pages now say that zkSNACKs shut down the Wasabi coordinator in 2024.
Why
US authorities seized Samourai’s web servers and domain and charged its founders on 24 April 2024. Sparrow removed its Whirlpool client in version 1.9.0. The lesson was corrected first, on 23 June 2026.
Sources
Change reference
0ef95a8, 2aff8e8, 15e76bd, 5ee190e, 9cbbc53, e66014f, 19ec246, c0e5c02

Ledger security incidents listed out of order #

Corrected on · 1 page

Page corrected
What the page said
The timeline put the December 2023 Connect Kit attack before Ledger Recover, which Ledger had announced earlier that year.
What it says now
The two 2023 incidents are now in date order, Recover first, and both headings give the month.
Why
Ledger’s own incident report dates the Connect Kit exploit to 14 December 2023, and Ledger’s post explaining Recover is dated 25 July 2023.
Sources
Change reference
dc5d926

Multisig diagrams that showed every key coming from one backup #

Corrected on · 6 pages

Pages corrected
What the pages said
Six diagrams carried the heading “One source, many branches — all from one backup”. Five of them show how the keys of a multisig wallet are spread out, where that heading suggests all the keys come from a single backup.
What they say now
The multisig diagrams are headed “Independent keys, distributed”, and the sixth carries a heading that matches what it shows. In a 2-of-3 multisig each key has its own seed and its own backup, kept in different places. That is the point of multisig: a thief who finds one backup cannot spend, and losing one backup does not lock you out.
Why
One backup that could recreate every key would be a single point of failure, which is exactly what multisig removes. Sparrow’s best-practices guide describes multisig as several hardware wallets whose backups are stored safely, “ideally in different locations”.
Source
Change reference
a941e12

Checking a Bitcoin Core download: the wrong key fingerprint #

Corrected on · 1 page

Page corrected
What the page said
On 22 June 2026 we added steps for checking the signature of a Bitcoin Core download. They imported one key by its fingerprint and called it the key of fanquake, one of the people who sign releases. The fingerprint was in fact the key of another signer, Wladimir van der Laan. Before 22 June, the page told you to check the signature without importing any signer’s key, and gave the size of the blockchain as 550 GB.
What it says now
The page tells you to import the whole set of signer keys from the bitcoin-core/guix.sigs repository, check that SHA256SUMS.asc has a good signature from them, and then check your file with sha256sum --ignore-missing --check SHA256SUMS. It gives the size of the blockchain as over 700 GB.
Why
The fingerprint we printed, 71A3 B167 3540 5025 D447 E8F2 7481 0B01 2346 C9A6, belongs to the key in laanwj.gpg, whose owner is Wladimir J. van der Laan. fanquake’s key in the same repository is E777 299F C265 DD04 7930 70EB 944D 35F9 AC3D B76A. Importing the full set avoids depending on one hand-copied fingerprint. blockchain.com’s chart put the blocks at about 749 GB on 22 June 2026.
Sources
Change reference
d4a2832, 26e621d

Silent Payments: no Bitcoin Core release has a Silent Payments wallet #

Corrected on · 1 page

Page corrected
What the page said
Said Bitcoin Core 28.0 and later can send and receive Silent Payments, and listed Sparrow among wallets still considering support.
What it says now
No released version of Bitcoin Core ships a Silent Payments wallet. Sparrow supports Silent Payments.
Why
The wallet tracker at silentpayments.xyz lists Sparrow among wallets with support. When we checked in November 2026, it said of Bitcoin Core: “The base BIP352 code was merged into Bitcoin Core’s master branch in September 2026, but sending and receiving are still in open PRs and haven’t shipped in a release yet.”
Source
Change reference
d4a2832

Sparrow multisig tutorial: the right Coldcard export #

Corrected on · 1 page

Page corrected
What the page said
Under Export XPUB in the Coldcard’s Multisig Wallets menu, told you to choose a “Generic JSON” export format.
What it says now
Says that Export XPUB writes the file for the multisig wallet on its own, names that file, and tells you not to use the Coldcard’s separate Generic JSON export for this.
Why
Coldcard’s multisig documentation says Export XPUB “Creates a file on the MicroSD” holding this Coldcard’s keys, and that the file is used in the next step to create the multisig wallet. Coldcard’s microSD documentation lists Generic JSON among the options of a different menu, Export Wallet.
Sources
Change reference
d4a2832

RoboSats: fees, and Mutiny #

Corrected on · 2 pages

Pages corrected
What the pages said
Said makers pay no fee and takers pay 0.2%, and suggested Mutiny Wallet as a wallet to use.
What they say now
RoboSats charges 0.2% of the trade, split as 0.025% for the maker and 0.175% for the taker. Mutiny is described as shut down. The lesson was corrected on 23 June 2026.
Why
RoboSats’ fee page says it “charges a 0.2% fee of the total trade amount; this fee is distributed between the order maker and the order taker who pay 0.025% and 0.175%, respectively.” Mutiny announced its shutdown on 5 August 2024. This update also said Phoenix does not work with RoboSats. That was wrong, and we corrected it on 3 November 2026.
Sources
Related correction
Change reference
d4a2832, 0ef95a8

Keystone review: what Keystone publishes as open source #

Corrected on · 1 page

Page corrected
What the page said
Said the Keystone’s hardware schematics are not open source.
What it says now
Keystone publishes the Keystone 3 firmware and its hardware schematics on GitHub.
Why
The README of Keystone’s firmware repository says its hardware folder “contains hardware-related files and schematics for the Keystone3 device”.
Source
Change reference
1c68938

Found something we got wrong?

Write to hello@knowingbitcoin.com. Tell us the page address, the sentence and what you think is wrong. A link to a primary source, such as release notes, a specification or the maker’s own page, lets us check it fastest. When we correct a page, the change appears here.

Never send seed words, a passphrase, a PIN or private keys to us or to anyone else. Nobody needs them to check a correction.

Last reviewed: