v2.2.1

Added

v2.2.0

• (:bulb: @alessandrokonrad) Results now contain a new field datum_type only present when datum_hash is not null. It indicates whether the datum in the output is inline or only a hash reference.

  See GET /matches/{pattern} → 📖 API Reference

Changed

v2.2.1

• 📌 #86 (:bug: @nielstron) - Fix start-up configuration check to not fail when providing twice the same pattern on restart.

• Fix Ogmios' parser for non-Babbage eras in the presence of collaterals without collateral return.

• Provide better error message when starting Kupo with a misconfigured network. This is a pretty common case and the message used to be a bit cryptic. Kupo now detects that and inform the end-user properly.

v2.2.0

• (:bug: @errfrom) Fixed a bug where utxo entries from collateral returns (on phase-2 failed transaction) would be missing from the index. In fact, Kupo does not index outputs from failed transaction, but since the Babbage era, failed transactions may contain an extra field "collateral return" which becomes a legitimate transaction output on-chain. These are now properly indexed as well.

Removed

N/A

Benchmarks

See benchmarks for v2.1.0.

Snapshots

In the release artifacts, you can find two snapshots (kupo.sqlite3-{mainnet}.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 the mainnet archive is split in two parts; the original archive can be recovered as such:

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

Then, verify the archive's integrity using md5, it should match the checksum below:

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

Dependencies

Dependency	Tested With
cardano-node	1.35.x
ogmios	v5.5.x

Details

v2.1.0...v2.2.1