Skip to content

Releases: XRPLF/clio

1.0.4

02 Feb 23:20
0c5a69e

Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 1.0.3...1.0.4

1.0.3

17 Nov 19:58
d2c870d

Choose a tag to compare

What's Changed

Full Changelog: 1.0.2...1.0.3

1.0.2

11 Aug 18:42
dfe18ed

Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 1.0.1...1.0.2

1.0.1

13 Jul 23:36
4468302

Choose a tag to compare

What's Changed

Full Changelog: 1.0.0...1.0.1

1.0.0

29 Jun 22:56
1.0.0
1e76454

Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 0.2.0...1.0.0

0.2.0

25 May 17:40
0.2.0
e7204a5

Choose a tag to compare

What's Changed

Numerous stability improvements and addition of NFT RPCs

  • fix validated_ledger location in server_info by @natenichols in #144
  • return entryNotFound instead of ledgerNotFound by @natenichols in #149
  • Log cleanup by @cjcobb23 in #150
  • add support for account_nfts, nft_buy_offers, nft_sell_offers
  • Fix message queueing in WsSession
  • Fix for offer directory iteration
  • Fix crasher in ledger data
  • Properly catch in ip() when peer has disconnected
  • Fixed server_info to match rippled
  • Round age to zero when negative
  • use 64 bit counters to prevent overflow

0.1.0

23 Mar 01:27
7272af9

Choose a tag to compare

0.1.0

clio is an XRP Ledger API server. clio is optimized for RPC calls, over websocket or JSON-RPC. Validated historical ledger and transaction data is stored in a more space efficient format, using up to 4 times less space than rippled.

clio uses Cassandra or ScyllaDB, allowing for scalable read throughput. Multiple clio nodes can share access to the same dataset, allowing for a highly available cluster of clio nodes, without the need for redundant data storage or computation.

0.1.0 is the first beta of Project Clio. It contains:

  • ./src/backend is the BackendInterface. This provides an abstraction for reading and writing information to a database.
  • ./src/etl is the ReportingETL. The classes in this folder are used to extract information from the P2P network and write it to a database, either locally or over the network.
  • ./src/rpc contains RPC handlers that are called by clients. These handlers should expose the same API as rippled.
  • ./src/subscriptions contains the SubscriptionManager. This manages publishing to clients subscribing to streams or accounts.
  • ./src/webserver contains a flex server that handles both http/s and ws/s traffic on a single port.
  • ./unittests simple unit tests that write to and read from a database to verify that the ETL works.