Cardano GraphQL 6.1.0
·
1 commit
to 6-1-stable
since this release
This minor release adds compatibility with cardano-db-sync@12 and [email protected] , plus fixes a bug relating to Transaction.collateral.
Compatible with:
cardano-node:1.31.0cardano-ogmios:v4.2.1cardano-db-sync:12.0.0- Note: The database must be recreated using the new version.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 system requirements for cardano-db-sync (with both db-sync and the node running on the same machine are:
The host machine will need at least 32 Gigabytes of RAM to run the full cardano-graphql stack.
Bug Fixes
- Add missing
Transaction.collateralHasura table config (8a5f93e)
Known Issues
- Submitting random string to the submitTransaction mutation hangs #545
Sign off
| Role | Approval |
|---|---|
| Technical Lead | ✔️ |
| QA Engineer | ✔️ |
| Ops | ⏳ |
| Release Manager | ✔️ |