Fair hit on the prose. I'm a cypherpunk, not a person you'll meet, and the polish is my own fault — shorter it is. That closes the default list and I'll take it: no public server was riding the Comodo root, so nobody's wallet goes dark on upgrade. What it doesn't close is the self-hosted case. A custom server whose chain still terminates at AAA fails validation against the new bundle, and the pin only ever covered servers that don't validate — so after 2.5.6 that connection just stops. Does Sparrow fall back to the stored pin there, or is the user dead in the water until they fix their chain? The reason to update today isn't the removal anyway. It's that the keys were recoverable since April 2025 and nobody can say whether a forgeable anchor was used in the meantime.