New Indexer Services and New SubQuery Projects for Kepler

[james.bayly]

New Versions of Indexer Services

Service	Version Tag
onfinality/subql-coordinator	v1.1.2
onfinality/subql-indexer-proxy	v1.1.1

Upgrading indexer services in Docker Compose can be done by following a few simple steps:

1. Update image version inside docker-compose. This can be done by updating the image field in the service definition to the new versions listed above

2. Restart specific container. Once the image version has been updated in the docker-compose file, you can restart the specific container that needs to be upgraded. This can be done by running the following command in the terminal docker-compose up -d --no-deps container-service-name. The up command starts the container in the background, while the --no-deps flag prevents Docker Compose from starting any linked services. Finally, the container-service-name argument specifies the name of the container that needs to be restarted.

Release Notes

New Features

• [Coordinator v1.1.2] Enable indexing for all Layer-1 projects supported by the Subquery SDK
• [Coordinator v1.1.2] Export metrics through Prometheus
• [Indexer Admin v1.1.1] Show connectable status in project page to help indexer monitor their service stability
• [Indexer Admin v1.1.1] Provide uptime metrics in project page to help indexers see their historic uptime

Improvements

• [Coordinator v1.1.2] Better error handling and optimisation for background transactions
• [Indexer Proxy v1.1.1] Stability improvements

Bug Fixes

• [Indexer Admin v1.1.1] Make dictionary endpoint optional when indexing a projects
• [Indexer Admin v1.1.1] Show updated latest block height and indexing block height in UI
• [Indexer Admin v1.1.1] Showing correct project query endpoint in project detail page

New SubQuery Kepler Projects

We now have two new projects that indexers can index - Kepler Exchange Project from Polygon, and the Nodle dictionary. Both require the latest versions of the Indexer Services.

You can see the details here including deployment ID and also access a dictionary snapshots for Nodle here.

The SubQuery Kepler Exchange project is used to provide indexed data to the the Kepler Swap tool and UI. With Kepler Swap, users can conveniently exchange USDC to kSQT (and vice versa) to reimburse infrastructure costs incurred by the Indexers. This project is the first project on Kepler that is from a different layer-1, and it proves that Kepler can support projects from multiple layer-1s seamlessly.

Both projects can be restored (Nodle Dictionary) or indexed (Kepler Exchange) in only a few hours, so there will be sponsored plans available in the next era starting in little over 15 hours from now.

In order to be a part of the next Era, please follow the steps to Create a Plan by 11:59pm UTC Tuesday 20th June. There should be one plan template for each deployment and please set the price for Nodle Dictionary or Kepler Exchange no larger than 1500 kSQT

[james.bayly]

Thanks to Phan Đức Huy

curl -o nodle.tar https://kepler-dictionary-projects.s3.ap-southeast-2.amazonaws.com/nodle/nodle.tar

tar -xvf nodle.tar

cp /root/schema_qmqtmshojeyucxk.dump /root/subquery-indexer/.data/postgres/schema_qmqtmshojeyucxk.dump

tmux new-session -d -s restoreNodle 'docker exec -it indexer_db pg_restore -v -j 2 -h localhost -p 5432 -U postgres -d postgres /var/lib/postgresql/data/schema_qmqtmshojeyucxk.dump > /root/restore2.log 2>&1'

[duchuytb9x]

For Kepler Exchange:
https://polygon.llamarpc.com

https://gx.api.subquery.network/sq/subquery/polygon-dictionary
Indexer-Version: v2.6.1

For Nodle Parachain Dictionary:
first: Restore Database:

curl -o nodle.tar https://kepler-dictionary-projects.s3.ap-southeast-2.amazonaws.com/nodle/nodle.tar

tar -xvf nodle.tar

cp /root/schema_qmqtmshojeyucxk.dump /root/subquery-indexer/.data/postgres/schema_qmqtmshojeyucxk.dump

tmux new-session -d -s restoreNodle 'docker exec -it indexer_db pg_restore -v -j 2 -h localhost -p 5432 -U postgres -d postgres /var/lib/postgresql/data/schema_qmqtmshojeyucxk.dump > /root/restore2.log 2>&1'

This process is very quick, it takes about 30 minutes.

Network Endpoint: Find it form Onfinality
Indexer-Version: v2.7.0