Cardano GraphQL 8.2.2

What's Changed

• bump cardano-node, db-sync, ogmios versions by @linconvidal in #893

New Contributors

• @linconvidal made their first contribution in #893

Full Changelog: 8.2.1...8.2.2

Cardano GraphQL 8.2.1

What's Changed

• docs: disclaimer for chainfollower variables added by @Kammerlo in #883
• chore: upgraded db-sync by @Kammerlo in #885

Important Changes

• A new docker service, token-metadata-registry has been added to the docker compose file. This improves the syncing times of the off-chain asset data and overcomes the previous issues with the public Token metadata registry has a limit of daily requests. This brings in following changes when running GraphQL:

Important Upgrade notes

1. Run the new token-metadata-registry service present in the docker compose
2. Make sure the METADATA_SERVER_URI to point to local token metadata registry server
3. The Chainfollower environment variables CHAIN_FOLLOWER_START_SLOT and CHAIN_FOLLOWER_START_ID are currently mandatory. Otherwise the Token registry will get stuck. We will provide a fix as soon as possible.

Known issues

• Token syncing will get stuck, if the environment variables aren't set

Full Changelog: 8.2.0...8.2.1

Cardano GraphQL 8.2.0

What's Changed

• Chore/bump node 9.1 dbsync 13.3 by @Kammerlo in #879
• The cardano-node and the ogmios services are separate services to remove the upgrade dependencies

Note: There is currently a known issue with cardano-db-sync which hinders using a snapshot. We will provide an update once the issue is resolved.

Important Changes

• A new docker service, token-metadata-registry has been added to the docker compose file. This improves the syncing times of the off-chain asset data and overcomes the previous issues with the public Token metadata registry has a limit of daily requests. This brings in following changes when running GraphQL:

Important Upgrade notes

1. Run the new token-metadata-registry service present in the docker compose
2. Make sure the METADATA_SERVER_URI to point to local token metadata registry server
3. The Chainfollower environment variables are currently mandatory. Otherwise the Token registry will get stuck. We will provide a fix as soon as possible.

Known issues

• Token syncing will get stuck, if the environment variables aren't set
• DB-sync Snapshot can crash due to a known issue. Will be fixed as soon as possible.

Full Changelog: 8.1.0...8.2.0

New Contributors

• @Kartiiyer12 made their first contribution in #879 - Thank you very much for this!

Cardano GraphQL 8.1.0

What's Changed

• Fixed parsing of blocktype PR#872
• Added the Token Registry as local service to avoid bottlenecks PR#873
• Fixed read networksynchronization Bug PR#874
• Bumped versions of node (8.9.3) PR #875

Infos for Upgrading

Full Changelog: 8.0.3...8.0.4

Cardano GraphQL 8.0.3

What's Changed

• Bumped versions of db-sync (13.2.0.2) and node (8.9.0)

Infos for Upgrading

Full Changelog: 8.0.2...8.0.3

Cardano GraphQL 8.0.2

What's Changed

• Fixed a bug which led to skipping assets while syncing and the Asset syncing process was stuck at around 10%. This release solves the problem

Infos for Upgrading

Full Changelog: 8.0.1...8.0.2

Cardano GraphQL 8.0.1

What's Changed

• Nixos service updates by @johnalotoski in #815
• Feat/upgrade db sync 13.2.0.1 ogmios 6.1 node 8.7.3 by @Kammerlo in #859
• Added Sanchonet compatibility

Infos for Upgrading

Due to an needed upgrade of postgres from 11 to 14 a resync is needed. Since db-sync isn't working anymore with Postgres 11.

Full Changelog: 8.0.0...8.0.1

Cardano GraphQL 8.0.0

This major release separates the single cardano-graphql process into a http-server and background service, to separate the workload and support horizontal scaling of the external interface. It's tested against Cardano service dependency versions compatible with the upcoming protocol upgrade.

Compatible with:

• cardano-node: 1.35.5
• cardano-ogmios: v5.5.8
• cardano-db-sync: 13.0.5
• hasura/graphql-engine: 2.17.1

⚠ BREAKING CHANGES

• Dropped support for average aggregation fields.
• Aligned GraphQL types to conform with database and Hasura string casts
• api-cardano-db-hasura: separate DB and Hasura management tasks to new process

System Requirements

• DB Sync system requirements
  • The system requirements for cardano-db-sync (with both db-sync and the node running on the same machine are:
    • Any of the big well known Linux distributions (eg, Debian, Ubuntu, RHEL, CentOS, Arch etc).
    • 24 Gigabytes of RAM.
    • 4 CPU cores.
    • 80 Gigabytes or more of disk storage (preferably SSD which are 2-5 times faster than electro-mechanical disks).
  • The recommended configuration is to have the db-sync and the PostgreSQL server on the same machine. During syncing (getting historical data from the blockchain) there is a HUGE amount of data traffic between db-sync and the database. Traffic to a local database is significantly faster than traffic to a database on the LAN or remotely to another location.

The host machine will need at least 32 Gigabytes of RAM to run the full cardano-graphql stack.

Features

• api-cardano-db-hasura: separate DB and Hasura management tasks to new process (8acb58f)
• Improve uncaught exception logging (800a587)

Bug Fixes

• api-cardano-db-hasura: remove VARCHAR limits from Asset table (a4092f8)
• api-cardano-db-hasura: retry initialization of data fetcher (d5a794d)
• server: avoid producing NaN in asset sync percentage calc, and clamp to max 100% (b48e804)
• Aligned GraphQL types to conform with database and Hasura string casts (ad4e736)
• Dropped support for average aggregation fields (3cd6445)

Sign off

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

Cardano GraphQL 7.0.2

This minor release updates the bundled config, and bumps the ogmios and db-sync versions.

Compatible with:

• cardano-node: 1.35.3
• cardano-ogmios: v5.5.7
• cardano-db-sync: 13.0.5
• hasura/graphql-engine: 1.3.3

System Requirements

• DB Sync system requirements
  • The system requirements for cardano-db-sync (with both db-sync and the node running on the same machine are:
    • Any of the big well known Linux distributions (eg, Debian, Ubuntu, RHEL, CentOS, Arch etc).
    • 24 Gigabytes of RAM.
    • 4 CPU cores.
    • 80 Gigabytes or more of disk storage (preferably SSD which are 2-5 times faster than electro-mechanical disks).
  • The recommended configuration is to have the db-sync and the PostgreSQL server on the same machine. During syncing (getting historical data from the blockchain) there is a HUGE amount of data traffic between db-sync and the database. Traffic to a local database is significantly faster than traffic to a database on the LAN or remotely to another location.

The host machine will need at least 32 Gigabytes of RAM to run the full cardano-graphql stack.

Improvements

• bump cardano-configurations (a386938)
• remove upper Node.js engines constraint (7eb733f)

Sign off

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

Cardano GraphQL 7.0.1

This minor release addresses the issues detailed below.

Compatible with:

• cardano-node: 1.35.3
• cardano-ogmios: v5.5.5
• cardano-db-sync: 13.0.4
• hasura/graphql-engine: 1.3.3

System Requirements

• DB Sync system requirements
  • The system requirements for cardano-db-sync (with both db-sync and the node running on the same machine are:
    • Any of the big well known Linux distributions (eg, Debian, Ubuntu, RHEL, CentOS, Arch etc).
    • 24 Gigabytes of RAM.
    • 4 CPU cores.
    • 80 Gigabytes or more of disk storage (preferably SSD which are 2-5 times faster than electro-mechanical disks).
  • The recommended configuration is to have the db-sync and the PostgreSQL server on the same machine. During syncing (getting historical data from the blockchain) there is a HUGE amount of data traffic between db-sync and the database. Traffic to a local database is significantly faster than traffic to a database on the LAN or remotely to another location.

The host machine will need at least 32 Gigabytes of RAM to run the full cardano-graphql stack.

Bug Fixes

• api-cardano-db-hasura: correct close and error handling of Ogmios connection (df82008)
• api-cardano-db-hasura: mitigate unexpected Ogmios socket disconnect (3d81bf5)
• Gracefully handle Ogmios socket disconnection (18bf3e1)
• Mount local config into cardano-node-ogmios (f055378)

Other Improvements

• optimize Cardano & StakePoolOwner views (064e8cb)
• install hasura-cli plugin at build time (b47cf89)

Sign off

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