News / Crypto

Ripple Welcomes New XRP Account on X With a Nod to Ledger Contributors

Original Presence illustration of connected digital asset networks.
Illustration: Presence

An XRP account introduced itself on X on October 19, posting a short written greeting with a ten-second opening video of the token’s logo. A metallic XRP symbol appears against a dark background in the captured post. Ripple and the XRP Ledger Foundation both responded publicly to the introduction, with Ripple’s response arriving within minutes of the opening message.

The screenshot recorded 52,900 views for the debut post, a figure tied to the moment the image was captured. Ripple’s quoted response included the original greeting and video, while describing more than a decade spent building on the XRP Ledger with thousands of other contributors. The foundation paired its welcome with an animated terminal graphic and a reference to a new era.

Commercial services and validator rules

Those welcomes contained no announcement of a product release, token distribution or altered transaction rules for the ledger. Ripple’s commercial services have been the subject of separate reporting: an October 8 examination of its US prime brokerage operation described over-the-counter execution of spot transactions involving XRP, RLUSD and other assets, together with cross-margining against derivatives positions.

That coverage also considered Ripple’s October 6 announcement concerning Brevan Howard funds. The stated arrangement was for the funds to use Ripple Prime for brokerage, clearing and financing across different asset classes. Brevan Howard’s approximately $35 billion in assets under management described the firm’s overall business; it was not a disclosed amount being moved into the Ripple brokerage.

The announcement supplied no XRP allocation for the participating funds. Another part of Ripple’s commercial offering, Delta One, had launched in August with total return swaps linked to US-listed equities, indexes and digital assets. Separately, the market figures accompanying the account’s introduction put XRP at $1.30, up 2.4% over the day, at the time of publication.

Changes to the XRP Ledger’s transaction rules go through an amendment process described in the network’s technical documentation. Validator operators can set how they vote, but amendment approval counts the votes of trusted validators. Activation requires support above 80% to remain in place for two weeks. A drop below that threshold starts the waiting period again.

An August 12 report provides a historical example of that process. Ripple had backed a bundle of protocol corrections called fixCleanup3_3_0. The reported voting snapshot showed eight affirmative votes among 35 trusted validators on the default list, compared with the 29 votes required to move above the 80% approval threshold. Those numbers describe the August snapshot rather than the amendment’s current position.

The proposed changes covered several parts of the ledger: checks and pseudo-accounts were included, alongside vault and lending functions. The package also addressed automated market makers and the permissioned decentralized exchange. A different maintenance amendment, fixCleanup3_2_0, had already activated in July. Coverage dated July 29 recorded 30 supportive votes from 35 trusted validators, or 85.71%, with five validators voting against the change.

Software migration for node operators

XRPScan’s warning about that earlier amendment concerned nodes using software version 3.1.0 or an older release. For those operators, continuing on an affected version would leave a node amendment-blocked; installing newer software was the step needed to address that condition. The report distinguished this requirement for node operators from self-custody holdings: people holding their own tokens did not have to swap the tokens or send their funds elsewhere because of the amendment.

Version 3.2.0 also changed the name of the reference server software, replacing rippled with xrpld. The migration described in the earlier coverage reached beyond the executable name: configuration filenames, database paths, packages, scripts and service settings were among the items involved in the transition. These were software and operational changes associated with that release.

About the author

Presence Editorial is the editorial team behind Presence.