CardanoSolutions/kupo v2.8

v2.8.0

on GitHub

Added

v2.8.0

Added

• (💡 @scarmuega) A new mode --read-only which can be used to boot-up an HTTP server with only read access to the underlying database. This option comes as an alternative to the other options for chain producers (e.g. --node-socket and --node-config). The replica can only reply successfully to GET queries with the exception of queries under /metadata. The latter must go through the master server.

• Automatic restart and setup indexes when --defer-db-indexes is provided and the tip of the chain is reached.

• A new field configuration.indexes to the health object that indicates whether the server is still deferring the installation of lookup indexes or has already installed them.

Changed

• (🔨 @klarkc + @sorki) Integrate with cardano-node==8.7.2 including the (preliminary) Conway era.

• (💡 @eMCeee89) The server now returns:

  • 503 from /health if the connection_status is "disconnected";
  • 202 if the server is connected but far away from the node's tip (i.e. still syncing)

• Reinstate WAL journal mode for SQLite main writer. This should allow setting up more concurrent readers on top of the same database.

• Fine-tune some internal constraints around database connections management for better performances. In particular, the maximum number of concurrent readers have been increased.

Remove

• 'Content-Length' header on some of the server responses which turned out to be already handled by the underlying server when necessary (according to the original HTTP specification).

Benchmarks

See benchmarks/README.md.

Snapshots

In the release artifacts, you can find multiple snapshots (kupo.sqlite3-{mainnet, preview, preprod}.tar.gz). These snapshots were obtained from the following options:

• --match *
• --since origin
• --prune-utxo

They can be used as starting points to get started quickly. Note that large archives are split in multiple parts; the original archive can be recovered using cat. For example, for mainnet:

❯ cat kupo.sqlite3-mainnet.tar.gz.part_* > kupo.sqlite3-mainnet.tar.gz

It is recommended to also check the archive's integrity using md5. It should match the digests below depending on the network. For example, for mainnet:

❯ md5 kupo.sqlite3-mainnet.tar.gz
MD5 (kupo.sqlite3-mainnet.tar.gz) = 972da57c519a281561c4d6b904a82301

Docker image(s)

cardanosolutions/kupo:v2.8.0

Dependencies

Details

v2.7.2...v2.8.0