Skip to content

Releases: IntersectMBO/cardano-db-sync

Cardano DB Sync 13.2.0.2

03 May 09:01
13.2.0.2
Compare
Choose a tag to compare

This release is a minor fix on top of 13.2.0.1. It's meant to provide support for Cardano node version 8.9.1 and better long term support for future node versions that change the conway genesis. This tag will ignore the conway genesis file unless db-sync config has this entry flag "EnableFutureGenesis" : true,

Compatible snapshots:

Network Link to snapshot
Mainnet-13.2 https://update-cardano-mainnet.iohk.io/cardano-db-sync/index.html#13.2/

Documentation for restoring from these files available at state-snapshot.md.

Requires ghc-8.10.x to build.

Associated docker image: 13.2.0.2-docker

Upgrade instructions

Upgradable from 13.0.x.x releases. Read more

Changelog

DBSync ignores the conway genesis unless EnableFutureGenesis is set
Fixed an issue with snapshot restoration 1659

Known issues

  • The new extra migrations are only experimentally supported because they're not very well tested and there are a few known issues with them #1420
  • The epoch table may have some wrong values after upgrading from a previous release.
  • Running the consumed-tx-out migration can be very slow. See more at #1621
  • Logging issues #1623
  • There is an issue where the ma_tx_mint table is disabled by the --disable-metadata flag instead of the --disable-multi-asset.
  • Epochs that are not dense enough may cause missing epoch_stake entries. Affects preprod epochs 13-28.

Documentation

Cardano DB Sync Overview
Building and Running the Cardano DB Sync Node
Schema Management
State snapshot
Smash

Notes

Default docker postgres has been upgraded to 14.10-alpine
There is a postgres requirement for users that don't use docker-compose and have to manually configure postgres:

It is advised to increase the `maintenance_work_mem` from the Postgres configuration to 0.5GB - 1GB (default is 64MB).
Also use the default (2) or higher `max_parallel_maintenance_workers` (this parameter was introduced in `postgres` version 11)

Sign off

Role Approval
Technical Lead 🟢
Cardano Head of Engineering 🟢
Cardano Head of Product 🟢
Test Engineer 🟢
Site Reliability Engineer 🟢

Cardano DB Sync Sancho-4.2.1

18 Apr 13:34
sancho-4-2-1
b0b1ab0
Compare
Choose a tag to compare

NOTE: THIS RELEASE IS ONLY RECOMMENDED FOR USE ON THE SANCHONET AND PUBLIC TEST ENVIRONMENTS (E.G. PREVIEW) AT THIS TIME. IT IS NOT RECOMMENDED FOR USE ON MAINNET UNTIL FURTHER TESTING

Same as sancho-4-2-0, but it fixes broken docker genesis.
Docker image

Cardano DB Sync Sancho-4.2.0

17 Apr 18:55
sancho-4-2-0
3ac426d
Compare
Choose a tag to compare
Pre-release

NOTE: THIS RELEASE IS ONLY RECOMMENDED FOR USE ON THE SANCHONET AND PUBLIC TEST ENVIRONMENTS (E.G. PREVIEW) AT THIS TIME. IT IS NOT RECOMMENDED FOR USE ON MAINNET UNTIL FURTHER TESTING

This release adds support for node-8.10.0-pre. It may be compatible with later node versions, but it hasn't been tested
It is advised to resync from genesis when upgrading to this release

Schema
Docker image

Changelog

  • Added new fields stake_registration.deposit and pool_update.deposit for payed deposits (null for reregistrations or disabled ledger state)
  • Added new fields epoch_param.min_fee_ref_script_cost_per_byte and epoch_param.min_fee_ref_script_cost_per_byte
  • gov_action_proposal.dropped_epoch and gov_action_proposal.expired_epoch are now populated
  • Fixed a bug with gov_action_proposal.enacted_epoch not being updated
  • Renamed instant_reward table to reward_rest
  • Added a new type of rewards proposal_refund, which are inserted in the reward_rest table
  • Unclaimed proposal refunds are logged but not inserted anywhere yet

Cardano DB Sync Sancho-4.1.0

18 Mar 17:57
sancho-4.1.0
d249be0
Compare
Choose a tag to compare
Pre-release

NOTE: THIS RELEASE IS ONLY RECOMMENDED FOR USE ON THE SANCHONET AND PUBLIC TEST ENVIRONMENTS (E.G. PREVIEW) AT THIS TIME. IT IS NOT RECOMMENDED FOR USE ON MAINNET UNTIL FURTHER TESTING

This release adds support for node-8.8.0-pre and probably node-8.9.0. It may be compatible with later node versions, but it hasn't been tested
It is advised to resync from genesis when upgrading to this release

Schema
Docker image

Changelog

  • Moved modularity flags to the db-sync config, documented here
  • Made committee proposals more readable, with the addition of a new table new_committee_member for new members 1633. Also new_committee is renamed to new_committee_info
  • Added a new table committee_hash which is now referenced by other tables instead of using the hash directly. This in particular solves 1571
  • Added support for offchain vote metadata and partial support for CIP-100 and CIP-108
  • Fixed script hash false negative check 1646

Vote offchain data

This release partially follows CIP-100 and proposed CIP-108. It fetches the off chain data, pointed by on chain voting anchors and populates the off_chain_vote_data table or off_chain_vote_fetch_error if fetching or parsing fails. The off_chain_vote_data is extended with all optional or necessary fields as they are described at CIP-100 and CIP-108. Also three new tables are added off_chain_vote_author, off_chain_vote_reference, off_chain_vote_external_update.

The hash and witness validation is not fully implemented, so db-sync will store a warning in almost all cases at off_chain_vote_data.warning and off_chain_vote_author.warning. Users that decide that some metadata are in fact invalid can edit the off_chain_vote_data.is_valid

Users can also directly access the original bytes at off_chain_vote_data.bytes or the original json at off_chain_vote_data.json. In particular the latter is stored in a a Postgres jsonb type, which allow a big number of builtin queries. For example

SELECT * FROM off_chain_vote_data where json ? 'authors'
returns all the metadata which have a build author or

SELECT * FROM off_chain_vote_data where json @> '{"authors":"xyz"}';
returns all metadata with a specific authors. Postgres makes all these queries indexable.

Fetching or parsing errors are inserted into off_chain_vote_fetch_error. These can be 404 "Not Found", expected JSON, but got : "text/html, InvalidUrlException, JSON decode error to name a few.

Cardano DB Sync 13.2.0.1

15 Feb 18:34
13.2.0.1
ed3dc8b
Compare
Choose a tag to compare

This release is compatible with Cardano node version 8.7.3. Newer node versions may also work, but this functionality has not been tested.

The release is compatible with both 13.1 and 13.2 snapshots. They can be found at

Network Link to snapshot
Mainnet-13.1 https://update-cardano-mainnet.iohk.io/cardano-db-sync/index.html#13.1/
Mainnet-13.2 TODO

Documentation for restoring from these files available at state-snapshot.md. For the 13.1 snapshots the Upgrade instructions below are also relevant.

Requires ghc-8.10.x to build.

Associated docker image: 13.2.0.1

Upgrade instructions

Upgradable from 13.0.x.x releases. Read more

Changelog

This release improves syncing speed and significantly extends modularity.
You can check the full changelog and the config options

Known issues

  • The new extra migrations are only experimentally supported because they're not very well tested and there are a few known issues with them #1420
  • The epoch table may have some wrong values after upgrading from a previous release.
  • Running the consumed-tx-out migration can be very slow. See more at #1621
  • Logging issues #1623
  • There is an issue where the ma_tx_mint table is disabled by the --disable-metadata flag instead of the --disable-multi-asset.

Documentation

Cardano DB Sync Overview
Building and Running the Cardano DB Sync Node
Schema Management
State snapshot
Smash

Notes

Default docker postgres has been upgraded to 14.10-alpine
There is a postgres requirement for users that don't use docker-compose and have to manually configure postgres:

It is advised to increase the `maintenance_work_mem` from the Postgres configuration to 0.5GB - 1GB (default is 64MB).
Also use the default (2) or higher `max_parallel_maintenance_workers` (this parameter was introduced in `postgres` version 11)

Platforms

Sign off

Role Approval
Technical Lead ✔️
Cardano Head of Engineering ✔️
Cardano Head of Product ✔️
Test Engineer ✔️
Site Reliability Engineer ✔️

Cardano DB Sync Sancho-3.0.0

21 Dec 11:31
sancho-3-0-0
Compare
Choose a tag to compare
Pre-release

NOTE: THIS RELEASE IS ONLY RECOMMENDED FOR USE ON THE SANCHONET AND PUBLIC TEST ENVIRONMENTS (E.G. PREVIEW) AT THIS TIME. IT IS NOT RECOMMENDED FOR USE ON MAINNET UNTIL FURTHER TESTING

This release adds support for node-8.7.2-pre. It may be compatible with later node versions, but it hasn't been tested
It is advised to resync from genesis when upgrading to this release

Changelog
Schema
Associated docker image

Vote offchain data

This release fetches the off chain data, pointed by on chain voting anchors and populates the off_chain_vote_data table. It is an initial implementation of CIP-100 . It is in general much more lenient, it accepts any data as long as they are parsable to any json format, while CIP-100 assumes some minimal fields. Also DBSync doesn't follow the json-ld canonicalization algorithm that's described in CIP-100. It simply checks the blake2b-256 hash of the fetched metadata and leaves a warning at off_chain_vote_data.warning if there is a mismatch.

The json is stored in a Postgres jsonb type, which allow a big number of builtin queries. For example

SELECT * FROM off_chain_vote_data where json ? 'authors'

returns all the metadata which have a build author or

SELECT * FROM off_chain_vote_data where json @> '{"authors":"xyz"}';

returns all metadata with a specific authors. Postgres makes all these queries indexable.

Fetching errors are inserted into off_chain_vote_fetch_error. These can be 404 "Not Found", expected JSON, but got : "text/html, InvalidUrlException, JSON decode error to name a few.

Sign off

Role Approval
Technical Lead
QA Engineer
Ops
Release Engineer

Cardano DB Sync Sancho-2.3.0

29 Nov 14:32
sancho-2-3-0
0edff13
Compare
Choose a tag to compare
Pre-release

NOTE: THIS RELEASE IS ONLY RECOMMENDED FOR USE ON THE SANCHONET AND PUBLIC TEST ENVIRONMENTS (E.G. PREVIEW) AT THIS TIME. IT IS NOT RECOMMENDED FOR USE ON MAINNET.

This release adds support for node-8.7.0-pre. It may be compatible with later node versions, but it hasn't been tested
It is advised to resync from genesis when upgrading to this release

Changelog
Schema docs

Associated docker image: sancho-2-3-0-docker
Note that the revision of the docker image doesn't match the revision of the tag, due to a docker fix.

Sign off

Role Approval
Technical Lead
QA Engineer
Ops
Release Engineer

Cardano DB Sync Sancho-2.2.0

02 Nov 14:39
sancho-2-2-0
ffde876
Compare
Choose a tag to compare
Pre-release

NOTE: THIS RELEASE IS ONLY RECOMMENDED FOR USE ON THE SANCHONET AND PUBLIC TEST ENVIRONMENTS (E.G. PREVIEW) AT THIS TIME. IT IS NOT RECOMMENDED FOR USE ON MAINNET.

This release adds support for node-8.6.0-pre. It may be compatible with later node versions, but it hasn't been tested
It is advised to resync from genesis when upgrading to this release

Changelog
Schema docs

Associated docker image: sancho-2-2-0

Sign off

Role Approval
Technical Lead
QA Engineer
Ops
Release Engineer

Cardano DB Sync 13.1.1.3

25 Jul 14:08
13.1.1.3
Compare
Choose a tag to compare

This release adds support for Cardano node version 8.0.0 and Cardano node version 8.1.1. Newer node versions may also work, but this functionality has not been tested.

The state snapshot files for this release can be found here:

Network Link to snapshot
Mainnet https://update-cardano-mainnet.iohk.io/cardano-db-sync/index.html#13.1/

Documentation for restoring from these files available at state-snapshot.md.

Requires ghc-8.10.x to build.

Static binaries download

Associated docker image: 13.1.1.3

Upgrade instructions

With this release, we continue our effort to provide easy upgrades from previous releases without the need to resync from genesis. During an upgrade from 13.x, db-sync will change the existing schema and update or fix some of the values that were inserted in the database from previous releases. Read the upgrading docs before upgrading for more details.

Changelog

https://github.com/input-output-hk/cardano-db-sync/blob/6e69a80797f2d68423b25ca7787e81533b367e42/cardano-db-sync/CHANGELOG.md#13112

Added

  • compatibility with Cardano node-8.0.0 and node-8.1.1
  • compatibility with the new format of the CostModel in the Alonzo genesis file
  • a procedure which fixes scripts with wrong cbor during upgrading
  • a procedure to fix ada_pots during upgrading
  • developmental ghc-9.2 compatibility
  • experimental options which turn off parts of the schema to reduce time, memory and storage requirements
  • experimental extra migrations which speed up UTxO queries. Read more consumed-tx-out and prune-tx-out.

Fixed

  • an issue where the ada_pots didn't match exactly the epoch boundary
  • an issue where epoch table didn't rollback
  • an issue with smash returning InvalidUrlException

Improved

  • Takes less snapshots, since big rollbacks are now faster
  • When --disable-ledger is enabled a --state-dir is no longer required

Known issues

  • The new extra migrations are only experimentally supported because they're not very well tested and there are a few known issues with them #1420
  • The epoch table may have some wrong values after upgrading from a previous release.

Documentation

Cardano DB Sync Overview
Building and Running the Cardano DB Sync Node
Schema Management
State snapshot
Smash

Notes

There is a postgres requirement for users that don't use docker-compose and have to manually configure postgres:

It is advised to increase the `maintenance_work_mem` from the Postgres configuration to 0.5GB - 1GB (default is 64MB).
Also use the default (2) or higher `max_parallel_maintenance_workers` (this parameter was introduced in `postgres` version 11)

Platforms

Sign off

Role Approval
Technical Lead ✔️
Cardano Head of Engineering ✔️
Cardano Head of Product ✔️
Test Engineer ✔️
Site Reliability Engineer ✔️

Cardano DB Sync 13.1.0.2

02 Apr 22:08
13.1.0.2
0dd8469
Compare
Choose a tag to compare

Cardano DB Sync 13.1.0.2 is a maintenance release addressing a fix in ledger internal data structures.

There is also a new postgres requirement for users that don't use docker-compose and have to manually config postgres:

It is advised to increase the maintenance_work_mem from Postgres config to 0.5GB - 1GB (default is 64MB).
Also use the default (2) or higher max_parallel_maintenance_workers (this parameter was introduced in postgres 11)

This release is compatible with Cardano Node 1.35.5.

Upgrade instructions

13.1.0.2 is fully compatible with 13.1.0.0, so resyncing or migrating is not necessary.
In order to upgrade from 13.0.x to 13.1.0.2 resyncing is not necessary and requires no special flags from the user. DBSync will automatically spawn a fixing procedure, which fixes old values related to plutus data. After that schema migrations will run on top of the existing db.
Full upgrade details can be found here.

The state snapshot files for this release can be found here:

Network Link to snapshot
Mainnet https://update-cardano-mainnet.iohk.io/cardano-db-sync/index.html#13.1/

Documentation for restoring from these files available at state-snapshot.md.

Requires ghc-8.10.x to build.

Static binaries download

Known issues

  • When --disable-ledger flag is enabled, the --state-dir option still needs to be provided, even though db-sync will completely ignore it.
  • Unhandled DCertGenesis certificate #290

Documentation

Cardano DB Sync Overview
Building and Running the Cardano DB Sync Node
Schema Management
Validation
State snapshot
Smash

Platforms

Sign off

Role Approval
Technical Lead ✔️
QA Engineer ✔️
Ops ✔️
Release Engineer ✔️