Clio 2.8.0 is now available for the XRP Ledger API server optimized for HTTP and WebSocket requests. The release is built with libxrpl 3.3.0 and supports amendments introduced since Clio 2.7.1, including BatchV1_1, ConfidentialTransfer, DynamicMPT, PermissionDelegationV1_1, Sponsor and fixCleanup3_3_0. Those amendments include transaction or ledger-model changes that Clio must understand when serving and processing network data.
The official release notes warn about an operational consequence for older deployments. If one of the listed amendments becomes enabled while an operator is still running a Clio version older than 2.8.0, the ETL process can become amendment-blocked and stop processing new ledgers. The release therefore matters not only for exposing additional API functionality, but also for keeping the data-processing layer compatible as the relevant XRP Ledger changes activate.
Feature work in 2.8.0 includes support for the Lending Protocol and Confidential Transfer fields, transaction filtering by mpt_issuance_id, and broader MPToken ETL handling. The release also adds storage and ETL indexing for mpt_issuance_history. Cluster-related changes include communication used to choose a writer node, recovery from a fallback writer state, a limit on cache loading in a cluster, optional log rotation and a metric for the age of a requested ledger.
The bug-fix list covers several API and operational paths. Clio now addresses forwarded streams that ignored api_version, Loan and LoanBroker filtering in account_objects and ledger_data, UInt64 serialization for MPToken amounts, proxy and client IP resolution, SSL context reuse and response caching behavior. The release also adds retries for transient database errors and fixes cases around cache-file startup, cache flushing and amendment blocking during initial ledger or cache loading.
XRPL provides packaged builds for Linux and macOS, and links the source release and full Clio 2.7.1 comparison through the official XRPLF repository. Its practical scope combines protocol compatibility, expanded API support and reliability fixes across ETL, networking, cache and RPC layers.