Promise and RxJS APIs around Polkadot and Substrate based chains via RPC calls. It is dynamically generated based on what the Substrate runtime provides in terms of metadata.
seems to be so heavy that I get a RPC-CORE: queryStorageAt(keys: Vec<StorageKey>, at?: BlockHash): Vec<StorageChangeSet>:: -32999: RPC rate limit exceeded error message when I'm connected to a public endpoint. Kusama node (v1.13.0).
If I set withClaimedRewardsEras: false it works on a Kusama public endpoint (i.e. wss://kusama-rpc.polkadot.io/), but of course I'm missing info
I can get past to this issue when I'm connected to my internal node, withClaimedRewardsEras: true, but still it takes roughly 13 seconds for 1 address
Polkadot doesn't seem to have the same issue: I can make the query with withClaimedRewardsEras: true set on internal and public endpoints with no problems
Not sure that's expected, so I'm opening this issue...
related to https://github.com/polkadot-js/api/issues/5859
seems to be so heavy that I get a
RPC-CORE: queryStorageAt(keys: Vec<StorageKey>, at?: BlockHash): Vec<StorageChangeSet>:: -32999: RPC rate limit exceedederror message when I'm connected to a public endpoint. Kusama node (v1.13.0).withClaimedRewardsEras: falseit works on a Kusama public endpoint (i.e. wss://kusama-rpc.polkadot.io/), but of course I'm missing infowithClaimedRewardsEras: true, but still it takes roughly 13 seconds for 1 addresswithClaimedRewardsEras: trueset on internal and public endpoints with no problemsNot sure that's expected, so I'm opening this issue...