Warning
This version requires an (automatic) database migration which will set columns values for existing rows to NULL for all inputs. To maintain backward compatibility, this is handled gracefully by the server which will also provide null JSON values for the relevant fields. However, this means that to get access to the newly introduced transaction_id, input_index and redeemer value for the spent_at fields, a re-sync since the beginning of the Alonzo era is necessary.
Added
v2.10.0
-
Kupo now keeps track of the transaction id and input index that is spending a TxO, as well as the redeemer if any. These now optionally appear under the
spent_atfield for matches. The redeemer is provided as a base16-encoded CBOR Plutus Data, akin to how datums are already provided. -
Add
?resolve_hashesquery flag to GET matches queriesWhen set, this will instrument the server to perform joins on datums and scripts to retrieve any known values associated to hashes. Scripts are returned in the same format as the GET scripts endpoint. Similarly for datums.
Also,
?resolve_hashescauses all match responses to always contain additionaldatumandscriptfields. Those fields can benullif:- The underlying output has no datum or script whatsoever.
- The underlying datum or script isn't known at this point.
The latter is only possible for datums, since they can be published as reference, and only revealed later on in a transaction witness.
Changed
v2.10.0
- Integrate with
cardano-node==10.1.3.
Removed
v2.10.0
N/A
Benchmarks
See benchmarks/README.md.
Snapshots
Docker image(s)
Dependencies
| Dependency | Tested With |
|---|---|
| cardano-node | 10.1.3
|
| ogmios | v6.*.*
|
| hydra-node | 0.16.0
|