Skip to content

Releases: XRPLF/clio

Clio development (nightly) build

01 Nov 05:38
d04331d
Compare
Choose a tag to compare
Pre-release

Note: Please remember that this is a development release and it is not recommended for production use.

Changelog (including previous releases): https://github.com/XRPLF/clio/commits/nightly

SHA256 checksums

3edb6b8c5b29f6386d2cd19dba46631ad0cb59e9b0db3eb8bf38a7937622d936  ./clio_server_Linux_Debug.tar.gz
ac80517ca8a6580c09b449e79c87f1bb453206933b5158eaba1a9afaff024b35  ./clio_server_Linux_Release.tar.gz
6a653ddc6ee082eea00f3f069893abbaff0cc18aa08cb8cd58991099644e749b  ./clio_server_macOS_Release.tar.gz

2.2.5

21 Oct 19:14
2.2.5
Compare
Choose a tag to compare

Introducing Clio version 2.2.5

Version 2.2.5 of Clio, an XRP Ledger API server optimized for HTTP and WebSocket API calls, is now available. This release adds a bug fix and feature

What's Changed

  • Add changes that were included as part of Version 2.2.3 but omitted from Version 2.2.4 in 2.2.4...2.2.3
  • Add counter for total messages waiting to be sent by @cindyyan317 in #1691

Database Migration

If you are currently running Clio 1.0.4 or earlier and upgrading, you must perform a database migration to properly support NFT data. See the clio_migrator branch and its README for instructions.

Full Changelog: 2.2.4...2.2.5

2.2.4

07 Oct 21:54
2.2.4
edefb66
Compare
Choose a tag to compare

Introducing Clio version 2.2.4

Version 2.2.4 of Clio, an XRP Ledger API server optimized for HTTP and WebSocket API calls, is now available. This release adds a bug fix.

What's Changed

Database Migration

If you are currently running Clio 1.0.4 or earlier and upgrading, you must perform a database migration to properly support NFT data. See the clio_migrator branch and its README for instructions.

Full Changelog: 2.2.3...2.2.4

2.2.3

19 Sep 17:30
2.2.3
854749a
Compare
Choose a tag to compare

Introducing Clio version 2.2.3

Version 2.2.3 of Clio, an XRP Ledger API server optimized for HTTP and WebSocket API calls, is now available. This release adds new features and bug fixes.

What's Changed

Database Migration

If you are currently running Clio 1.0.4 or earlier and upgrading, you must perform a database migration to properly support NFT data. See the clio_migrator branch and its README for instructions.

Full Changelog: 2.2.2...2.2.3

2.2.2

22 Jul 04:02
2.2.2
665fab1
Compare
Choose a tag to compare

Introducing Clio version 2.2.2

Version 2.2.2 of Clio, an XRP Ledger API server optimized for HTTP and WebSocket API calls, is now available. This release adds bug fixes.

Bug fixes

Database Migration

If you are currently running Clio 1.0.4 or earlier and upgrading, you must perform a database migration to properly support NFT data. See the clio_migrator branch and its README for instructions.

Full Changelog: 2.2.1...2.2.2

2.2.1

09 Jul 00:13
2.2.1
7b18e28
Compare
Choose a tag to compare

Introducing Clio version 2.2.1

Version 2.2.1 of Clio, an XRP Ledger API server optimized for HTTP and WebSocket API calls, is now available. This release adds a bug fix.

Bug fixes

Database Migration

If you are currently running Clio 1.0.4 or earlier and upgrading, you must perform a database migration to properly support NFT data. See the clio_migrator branch and its README for instructions.

Full Changelog: 2.2.0...2.2.1

2.2.0

27 Jun 05:05
2.2.0
4940d46
Compare
Choose a tag to compare

Introducing Clio version 2.2.0

Version 2.2.0 of Clio, an XRP Ledger API server optimized for HTTP and WebSocket API calls, is now available. This release adds new features and bug fixes.

Notable New Features

  • Price Oracle support, including get_aggregate_price API
  • Forwarding to rippled for feature API
    • Clio-native implementation of feature API is planned for future implementation
  • Improved doxygen documentation
  • TLS 1.3 support
  • C++23 compilers

Amendment Support

The following amendments have been introduced since Clio 2.1.2 and have transaction model changes. Clio 2.2.0 is built with libxrpl 2.2.0, which supports these amendments.

If these amendments are enabled and you have not upgraded Clio to 2.2.0 or newer, the ETL will be amendment blocked and new ledgers will not be processed.

To check the current voting status of these amendments on Mainnet, see the XRPL Amendments Dashboard.

Database Migration

If you are currently running Clio 1.0.4 or earlier and upgrading, you must perform a database migration to properly support NFT data. Instructions for the migration are described https://github.com/XRPLF/clio/tree/clio_migrator%402.0.0

What's Changed

Read more

2.1.2

05 Jun 16:29
c103778
Compare
Choose a tag to compare

Introducing Clio version 2.1.2

Version 2.1.2 of Clio, an XRP Ledger API server optimized for HTTP and WebSocket API calls, is now available. This release adds a new feature.

rippled Dependency on Clio

Clio needs to be updated to 2.1.2 or later before updating to rippled 2.2.0. Clio will be blocked if it is not updated first.

Database Migration

If you are currently running Clio 1.0.4 or earlier and upgrading, you must perform a database migration to properly support NFT data. Instructions for the migration are described https://github.com/XRPLF/clio/tree/clio_migrator%402.0.0

What's Changed

Full Changelog: 2.1.1...2.1.2

2.1.1

23 Mar 03:07
2.1.1
26ed78f
Compare
Choose a tag to compare

Introducing Clio version 2.1.1

Version 2.1.1 of Clio, an XRP Ledger API server optimized for HTTP and WebSocket API calls, is now available. This release adds new features and bug fixes.

New features

  • libxrpl 2.1.0

Bug fixes

  • Bug fix to support new fields for the XRPFees amendment by @godexsoft in #1280
    • Version 2.0.0 of Clio supported the XRPFees amendment, but did not includes updates to the new fee fields
    • If the XRPFees amendment is enabled and you have not upgraded Clio to 2.1.1 or newer, the new fee fields of the SetFee transaction and FeeSettings ledger entry would not be returned and the previous fee fields would return 0. The server_info API includes fee fields; new fee fields would not be returned and and previous fee fields would return 0

To check the current voting status of these amendments on Mainnet, see the XRPScan Amendments Dashboard.

Database Migration

If you are currently running Clio 1.0.4 or earlier and upgrading, you must perform a database migration to properly support NFT data. Instructions for the migration are described https://github.com/XRPLF/clio/tree/clio_migrator%402.0.0

Testing Credits

  • Thanks to @mounikakun and others for testing this release.

Full Changelog: 2.1.0...2.1.1