Bugs & outdated docs we've found while building on Astar | tracking thread

About this thread

Hello community!! :raising_hands:

Im from the Aradia team. This thread will serve as a centralized place where we post bugs and outdated documentation we find during development.

Every issue listed here will have a corresponding GitHub issue in the
appropriate repo. We post them here for visibility and in case other devs are running into the same problems.

We’ll keep updating this thread as we find more.

1: /stakerslist/ returns incomplete staker data

GitHub issue:
/stakerslist/{contractAddress} returns incomplete data missing most stakers · Issue #34 · AstarNetwork/dapps-staking-indexer-v3 · GitHub

The /stakerslist/{contractAddress} endpoint returns only a small
fraction of the actual stakers for any dApp. Our contract has 34 stakers on-chain
but the endpoint only returns 9. Tested with other projects and the problem is
the same across the board no dApp gets the full list back.

The on-chain data is correct (both /stakerscount/ and /chaindapps report the
right numbers), so the issue is specifically in how the indexer builds the staker list.

2: Dead links and undocumented API limitations in developer docs

GitHub issue: Dead links and undocumented API behavior in developer docs · Issue #791 · AstarNetwork/astar-docs · GitHub


OnFinality NFT API dead service still listed in docs

The page OnFinality Unified NFT API | Welcome to Astar

still promotes OnFinality’s Unified NFT API as an available indexer for Astar.

The service is completely down:

  • nft-beta.api.onfinality.io → shows “API Deprecated” message

  • nft-beta.onfinality.io/public → DNS doesn’t resolve at all

Should be removed or marked as deprecated.


dApp Staking API no response limits or pagination documented

The API docs at The API and the Indexer | Welcome to Astar list

endpoints but don’t document:

  • Response size limits (/stakerslist/ silently truncates results see issue #1)

  • Pagination parameters (if they exist)

  • Rate limits for the public endpoint

  • Response schemas

The page says “restricted usage” and warns about “excessive use” without defining

what that means. Developers need concrete numbers to build reliable integrations.

4 Likes

Thank you for your great contributions—feel free to share them on our Discord server too! That way, more developers can see them.
Also, @Juminstock , could you help us fix these bugs? Thanks,sir.

2 Likes

Thank you for reporting this @0xNigromante! Our team is already aware of it, and we’ll be working on a fix

1 Like