-
### Description
Background:
Currently, if a large block is encountered, the SDK may fail to index properly.
For example, Kusama: 25845986.
It behaves differently under HTTP and WS, and here’s …
yoozo updated
8 hours ago
-
## Problem Definition
I have a local valid Kusama RPC in the form of `wss://kusama.some.domain`.
The endpoint is fine and other tools can connect fine. Rotki however returns:
```
kusama failed t…
-
## Polkadot & Kusama: Exploring the Differences
### Description
Discover the key differences between Polkadot and Kusama, two closely related yet distinct blockchain networks. Learn how each netwo…
-
- Should work with Polkadot, Kusama, Westend & Paseo
- V0: Using RPC urls
- V1: Using substrate-connect
-
Kusama validator panics on:
https://github.com/paritytech/polkadot-sdk/blob/3906c578c96d97a8a099a4bdac4685acbe375a7c/substrate/primitives/state-machine/src/ext.rs#L168-L174
Version deployed: ver…
-
Add:
- Polkadot assethub, kusama assethub, westend assethub, zkverify testnet, shibuya
Remove:
- Turing, Darwinia2, collectives testnet
-
I encontered an error when trying to call polkadot and kusama rpc.
the code:
```js
const validators = await api.query.staking.validators.entries<
ValidatorPrefs,
[Ac…
-
cc @polkadot-js/notifications
Some configured endpoints are not available.
Check the nightly cron output (or via `yarn ci:chainEndpoints` locally) and disable the chains (either with `isDisabled` or…
-
**Is your feature request related to a problem? Please describe.**
Please add support for new XCM Channels (channels with high transactions)
**I. POLKADOT**
- [ ] Moonbeam Bifrost Polkadot
- …
-
### Is there an existing issue?
- [X] I have searched the existing issues
### Experiencing problems? Have you tried our Stack Exchange first?
- [X] This is not a support question.
### Description …