Cardano DB Sync Sancho-3.0.0

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	⏳