What the record shows: book values, failure reasons and signed queries
Evernorth carries Ripple's XRP at zero, Core Lightning starts saying why a forward failed, and a Kusama endpoint ties each payment to one query with a signature.
Crypto news, read from the protocol's own record
Evernorth carries Ripple's XRP at zero, Core Lightning starts saying why a forward failed, and a Kusama endpoint ties each payment to one query with a signature.
Three changes on 16-17 November did not alter how software behaves; they made its description match: BIP-379's status, rippled's cache counters and EIP-8151's split between mempool and consensus.
Three items from 16 November describe checks that reported success while the thing they were meant to confirm had not happened.
Three incidents and fixes from 13 to 16 November sit outside the core protocols, in tools and corners that most users never look at.
Three fixes merged or released on 13 and 14 November trace back to the same gap: code that could not tell a missing or malformed value from a legitimate one.
Three items from 12 and 13 November concern a second route around a control: a recovery signing path, a nonce the device chooses and a number type that silently rounds.
On 12 November the Justice Department, DTCC and the White House each made a move that shapes crypto markets more than any protocol release did.
Two urgent releases this week asked operators to upgrade on trust. What each project did publish shows how to judge the risk while the details are withheld.
CVE-2025-62859, 62860 and 62861 were fixed in autumn 2025 and published on 10 November 2026, two weeks after 29.x reached end of life; the Tor whitelist bug hit thousands of nodes.
Three technical items from this week move signing rules between the protocol and the layers above it, and each names the cost of the move.