What happened
David Schwartz, Ripple's chief technology officer and one of the original XRP Ledger architects, said Wednesday he had upgraded his personal XRPL hub to xrpld 3. 2. 0, the latest release of the network's core node software.
Crypto. News reported the move and framed it as a public endorsement of the rename from rippled, the name the client has carried since the ledger launched in 2012. The 3.
2. 0 release retires the rippled binary in favor of xrpld and bundles a set of cleanup fixes that operators have been pushing for since the AMM amendment shipped. Schwartz didn't post a postmortem or a flag on issues encountered during the upgrade, which is itself a signal: hubs running for institutional and tooling traffic don't get flipped quietly unless the operator is confident the build is stable.
The rename is cosmetic at the protocol level. Blocks still validate the same way, amendments still vote the same way, and existing tooling that calls the JSON-RPC interface keeps working. What changes is the binary name, the systemd unit, and the packaging.
Why it matters
The rename isn't trivial editorially. Validator operators have argued for years that calling the open-source client 'rippled' blurred the line between the protocol and the company, a line that became politically expensive during the SEC litigation. Pulling Ripple's brand out of the binary name is the kind of governance signal that makes it easier for non-aligned validators, exchanges, and custodians to run XRPL infrastructure without explaining themselves.