Astar dApp Staking API, Indexer Status, and Historical Data Access

1

Hello Astar Community and Development Team,

We’re currently working on a project that involves extracting dApp staking data from the Astar Network, specifically focusing on historical staker information. We’ve been exploring the available APIs and indexers, and we have a few questions we’d like to ask.

:police_car_light: Known Issues or Service Interruptions with Astar dApp Staking APIs?

We’ve attempted to use both the direct REST API endpoint for current stakers (e.g., api.astar.network/api/v3/astar/dapps-staking/stakerslist/{contractAddress}) and the Subsquid-based GraphQL indexer (e.g., squid.subsquid.io/dapps-staking-indexer-astar/graphql), as used in our Python script (referenced in the astar_dapp_stakers_historical immersive artifact).

Unfortunately, we’ve encountered connection errors (specifically, NameResolutionError for api.astar.network and similar issues when trying to connect to the GraphQL endpoint). This suggests a potential network or API availability issue from our end or with the services themselves.

  • Are there any known issues or ongoing service interruptions with these specific dApp staking API endpoints or the Subsquid indexer for Astar Mainnet?

  • Is the api.astar.network domain currently operational and publicly accessible as expected?

:page_facing_up: Service Level Agreements (SLA) and Rate Limits

For projects requiring consistent and reliable data access, understanding the operational guarantees is crucial.

  • What are the Service Level Agreements (SLA) for the Astar dApp Staking REST API and the GraphQL indexer?

  • Are these public services intended for production workloads, or are there specific rate limits (e.g., requests per second, per minute) that developers should be aware of when querying data?

  • Is there a recommended approach or service for higher-throughput data access if these public endpoints have strict limitations?

:hourglass_not_done: Alternative Indexers for Historical dApp Staking Data

Our primary goal is to retrieve historical staker data over specific time periods for a given dApp. While the Subsquid indexer appears to offer this functionality via GraphQL queries on the stakes entity (filtering by timestamp_gte and timestamp_lte), we’re keen to know if there are other reliable options.

  • Are there any other official or recommended indexers for Astar Network, beyond the Subsquid-based one, that provide reliable and comprehensive access to dApp Staking data, especially historical data?

  • Specifically, are there any indexers that make it easier to query the state of stakers for a dApp at a particular past “era” or block height?

Any insights or guidance from the Astar team or community would be greatly appreciated as we aim to build robust data solutions on the Astar Network.

Thank you!

3 Likes
2

@Dino could you help on this matter?

3

Hello,
to setup a GraphQL indexer, you can take inspiration from mine: GitHub - LuckyDapp/subquery-lucky
This Subquery project indexes data linked to the dApp staking for a given dApp.

Subquery and SubSquid are very similar.

1 Like
4

Thank you, just sent to our developers, I will update you🙏

5

What is your main purpose for wanting to access this historical data? Are you thinking of developing a tool? I’m just asking out of curiosity.

1 Like
6

Hey, Yes, we want to create something interesting for our stakers. Something directly related to the use of the game.

1 Like
7

@tksarah has developed his own dApp Staking dashboard, so he might be able to help.

2 Likes
8

Hey @you425 thank you, yes, seen, our dapp is not there, and I think the data is not updated, or am I wrong?

9

@SFY_Labs

Thank you for taking the time to review the page.

As for the “Staking Amount by dApp Staker” section, the dApp updates haven’t caught up yet. We’ll be adding that shortly.

Additionally, due to potential inaccuracies in the data retrieved from the API, updates to certain pages have been temporarily paused.

1 Like
10

Although the dApp list has been updated to the latest version, it seems that data retrieval via the API is still not functioning correctly. I do understand how to work around the issue, but implementing the necessary code will take some time. For now, this tool will likely remain under maintenance a little longer.

2 Likes
11

When Age Of Chronos will be avaible, please update us :folded_hands:

12

Hi
I am sorry to hear that you have connection problems with api or indexer. This was never reported before and nobody from the team noticed that. We will check that, since Astar portal heavily relies on the api.

To answer your questions

  • There are no know issues on the api or the indexer. api.astar.network is operational and accessible.
  • There is no SLA for the api. The mentioned services are not intended for production workloads, so I wouldn’t recommend relying your production services on it. SubSquid services are production ready ( Pricing | SQD ) so I am quite surprised that you have issues with them. Can you be more specific about errors from SubSquid?
  • I am not aware of alternatives. I hope answers from community members will help you in finding alternatives.
1 Like