$XRP kept running normally through a network issue Friday.
Here’s what happened.
Some nodes were being flooded with validator identity messages called manifests. The software was accepting, storing, and rebroadcasting too many of them from unknown validator keys. That could waste resources and create problems for node operators.
The ledger itself never stopped. It kept closing every 3.8 to 4 seconds and processed close to 723,000 transactions during the latest 24-hour window.
The fix is already out. XRPL 3.2.1 adds limits on how many manifests nodes can receive, store, send, and keep in memory. It also stops unknown manifests from being saved to disk.
The update shipped within about 24 hours.
Node operators need to install 3.2.1, make sure xrpld is running, and restart.
The issue was found. The ledger stayed online. The fix was shipped fast.
Everything is running normally now. Ledgers are still closing in under four seconds, throughput is holding steady, and the network is operating without disruption.
@ryanfazio our town was caught spending 550K on flock cameras without the knowledge or consent of the people who live there. you better have some RADICAL ideas for stopping spending that infringes on our right to privacy and come up with a refund.
@GuntherEagleman you should be able to say "no i don't want that even if it will save my life" ..."No" is the most important word we can understand and act on. It's not maybe let me see the ingrediants and allow you time to try and convince me, its...that isn't for me get off my porch!
@MinusWells Canton is not a public network. you can only buy into their chain not run infra. it has an infinite supply. yes its great for the private companies and obviously a direction we knew was coming but for me it a money grab not what i could actually spend time building on.
@cz_binance Our ideas are simply to make extremely simple UI for dad mom and grandma and grandpa. Features are cool but retirement money doesn't know how to get itself there.