XRPL Clio 2.8.0 Adds Lending and MPT Data Support

THE SHORT VERSION

XRPL Clio 2.8.0, published on August 20, 2026, adds Lending Protocol and Multi-Purpose Token data support to the XRP Ledger API server. The release is built with libxrpl 3.3.0 and supports six amendments introduced since Clio 2.7.1. The release warns that an older Clio instance can become amendment blocked if one of those amendments enables. [1] [2]

Clio is an API and ETL server optimized for HTTP and WebSocket calls. It is separate from the consensus server that validates and applies ledger amendments. Software support in Clio therefore does not mean that any amendment has activated on the XRP Ledger. Amendment activation still follows the ledger’s validator-voting process. [1] [4]

WHAT CLIO 2.8.0 ADDS

The official release materials describe support for Lending Protocol data, Confidential Transfer fields, and filtering by mpt_issuance_id. They also add MPToken ETL support and history indexing. These changes improve the data that Clio can ingest and serve through its API paths. They do not change the amendment state of the public ledger by themselves. [1] [2]

The release also includes cluster writer selection and fallback recovery, optional log rotation, and ledger-age metrics. Those are operator and infrastructure features. They matter for services that run Clio or depend on its indexed data, while ordinary XRP holders do not automatically need to interpret them as a wallet or asset change. [1] [2]

One limitation is important: the mptoken_issuance_history RPC was reverted. It should not be presented as an available Clio 2.8.0 feature. The release notes are the source for distinguishing supported MPT history indexing from that reverted RPC. [2]

THE SIX-AMENDMENT COMPATIBILITY WARNING

Clio 2.8.0 is built with libxrpl 3.3.0 and supports six amendments introduced since Clio 2.7.1. The Clio release warns that if any of those amendments enables while an operator is still running an older Clio version, that ETL path can become amendment blocked. The warning is about software compatibility and service continuity for Clio operators. [1]

XRPL’s 3.3.0 release materials describe the six amendments as BatchV1_1, ConfidentialTransfer, DynamicMPT, PermissionDelegationV1_1, Sponsor, and fixCleanup3_3_0. Publishing xrpld 3.3.0 or Clio 2.8.0 does not enable those amendments. It supplies code that can support the relevant protocol changes if and when the network enables them. [3]

An amendment-blocked server cannot continue normal validation, transaction submission, or voting when it lacks code for an enabled amendment. The documented risk is therefore most relevant to infrastructure providers, validators, and operators maintaining API or ETL services. It is not an automatic statement that every XRP holder must take a market action. [1] [4]

HOW XRPL AMENDMENT ACTIVATION WORKS

The XRPL amendment process requires more than 80% of trusted validators to support an amendment continuously for two weeks before it becomes permanently enabled. The network checks this on flag ledgers at regular intervals. If support falls to 80% or below, the two-week clock resets. A release that contains amendment code is therefore separate from the governance and consensus process that activates the code on the ledger. [4]

The official livenet amendments dashboard is the appropriate place to check current enablement and validator support. Counts, dates, and statuses can change. This draft does not claim that all six amendments supported by Clio 2.8.0 are enabled, and it does not infer a future activation date from the software release alone. [5]

CONTEXT FOR OPERATORS AND READERS

Clio serves data access and indexing workloads. The XRPL reference server, commonly called xrpld, participates in ledger synchronization, validation, and network operation. The two projects are related through shared protocol libraries, but they serve different operational purposes. That distinction explains why a Clio compatibility warning can matter to an API provider without representing a new consensus event. [1] [3]

For a Clio operator, the release notes identify an upgrade boundary tied to possible amendment activation. Operators should compare their deployed version, the release notes, and the current livenet amendment status before deciding how to manage an ETL service. This article does not turn the release warning into a universal upgrade instruction or a prediction about ledger usage.

WHAT REMAINS UNKNOWN

The release materials do not establish that any of the six amendments has enabled since Clio 2.8.0 was published. They also do not establish that every Clio deployment has upgraded, which API clients depend on each new field, or how current dashboard counts will change. Those questions require current release inventories, network status, and operator-specific information. [1] [5]

Support for Lending Protocol data, Confidential Transfer fields, and MPT history indexing does not independently verify a live ledger feature or a particular user balance. It describes what this Clio release can process and expose. The reverted mptoken_issuance_history RPC remains unavailable unless a later release documents it as restored. [2]

WHAT READERS SHOULD WATCH NEXT

Watch the official Clio release page and GitHub release for corrections, follow-up versions, and the status of the reverted RPC. Operators should watch the livenet amendments dashboard for an enabled flag or a change in validator support, then compare that status with their deployed Clio and xrpld versions. [2] [5]

Watch the XRPL amendment documentation for the current two-week support status and any clock reset. Keep software support, API availability, and ledger activation as separate facts when reporting on this release. The verified story is a Clio data and compatibility update, not confirmation that the 3.3.0 amendment wave has activated. [3] [4]

SOURCES AND DISCLOSURES

[1] XRPL.org, “Clio 2.8.0,” published August 20, 2026, including the API-server role, libxrpl version, feature list, upgrade warning, and operator context:
https://xrpl.org/blog/2026/clio-2.8.0

[2] XRPLF Clio GitHub release tag 2.8.0, including release-level implementation details and the reverted mptoken_issuance_history RPC:
https://github.com/XRPLF/clio/releases/tag/2.8.0

[3] XRPL.org, “xrpld 3.3.0,” including the six amendments introduced in the reference-server release:
https://xrpl.org/blog/2026/xrpld-3.3.0

[4] XRPL documentation, “Amendments,” including the greater-than-80% validator threshold, two-week requirement, and amendment-blocking behavior:
https://xrpl.org/docs/concepts/networks-and-servers/amendments

[5] Official XRPL livenet amendments dashboard for current enablement and validator status:
https://livenet.xrpl.org/amendments

Disclosure: This is a sourced report on XRPL software and amendment process records, not investment advice and not a recommendation to buy, sell, or hold XRP. Clio is an API and ETL server, and its release does not activate ledger amendments. Dashboard counts and dates can change. The featured illustration was generated for CryptoWorkPro and is not a documentary image of an XRPL release, validator vote, or ledger event.