-
The current devp2p stack provides an inefficient interface to protocol applications that end up having to use a fixed message format to communicate. This is due to the fact that the layers that comp…
-
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…
-
## Incompatibilities detected
A [scheduled test workflow](https://github.com/KILTprotocol/sdk-js/actions/runs/8768622338) using the latest available dependencies matching our semver ranges has failed…
-
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…
-
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 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 …
-
## Incompatibilities detected
A [scheduled test workflow](https://github.com/KILTprotocol/sdk-js/actions/runs/8677120720) using the latest available dependencies matching our semver ranges has failed…
-
Currently with the latest changes to the `IdentityInfo` type there is an error with `api.derive.accounts.info` and reducing the values.
Therefore once it is updated in the api we need to update it …
-
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…
-
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…