Kubesmane

Coldcard just lost ~$38M (ongoing, increasing) because a 2021 code change quietly swapped their hardware RNG call for a broken software path, and nobody caught it for five years. Wallet looked secure. Marketing said secure. The actual entropy going into key generation wasn't.

This is not normal, and it is not OK.

XRP Ledger 3.2.1 is now available. This fixes the manifest flood observed on Friday, July 31. The XRPL continued closing ledgers normally throughout. A post-mortem will follow soon for the community. Nodes previously accepted, stored and re-broadcast an unlimited number of manifests from unknown validator keys. 3.2.1 adds four limits: 1) Size cap per manifest - any single manifest larger than expected is rejected. 2) Receive cap - incoming batches over the limit are discarded, instead of breaking the peer connection. 3) Send cap - the bulk manifest greeting sent to each new peer is now bounded. 4) Cache cap - once 100 unknown keys are held, new ones are refused. We also no longer persist manifests from unknown keys to disk, so a flood cannot survive a restart. Please update immediately by following these steps: 1) Update normally to XRPL 3.2.1 2) Wait 1–2 min, confirm xrpld is running, it does not need to be in status full or proposing. 3) Restart xrpld again - very important.