Emerald Web3 Gateway 1.6.0

Upgrade procedure:

This release contains a migration that creates a missing index on the receipts table. For deployments running without pruning and full network history, expect the migration to take some time (2-5 minutes in internal testing on testnet and mainnet states), during which the emerald-web3-gateway gateway will be offline. Migration is initialized automatically on start.

If you want to avoid the few minutes of downtime, manually create the index before upgrading to the new release. To create the index run the following statement on your postgresql instance at any time before updating the emerald-web3-gateway deployment:

CREATE INDEX CONCURRENTLY IF NOT EXISTS receipt_on_round ON receipts USING btree (round);

This is a non-breaking database change, which can be applied while previous version of the emerald-web3-gateway is running. Note the CONCURRENTLY keyword which is required in order to create the index without locking the table, meaning emerald-web3-gateway will be able to use the database while the index is being created.

Once the index is created, update the emerald-web3-gateway normally. The migration will skip creating the index as it already exists and it will complete almost instantly.

Changelog

New Features

• c34e4aa: feat: use higher DB timeouts for migrations (@ptrus)

Bug fixes

• f1456ce: fix: add index on round to receipts table (@ptrus)

Full Changelog: v1.5.0...v1.6.0

Running the gateway

https://github.com/oasisprotocol/emerald-web3-gateway/blob/v1.6.0/README.md#running-the-gateway-on-testnetmainnet