-
We are observing pretty impactful degradation on Moonriver since the deployment of client v0.9.16 on Kusama.
Additionally, we have upgraded few days after Moonriver to support v0.9.16 but it had no i…
-
I'm using `@polkadot/api` v6.8.1 and a chain with metadata v14 (`polkadot-v0.9.11`) whose metadata I retrieved in `parachain.json`. Not sure how to tackle this error on `polkadot-types-from-chain`
``…
-
We can use this for local (and testnet) parachain testing with sudo and a permissive vesting origin.
-
We are getting uncaught errors on the account page: [easily reproducible here](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fapi-kusama.interlay.io%2Fparachain#/accounts).
Personally, I am getting …
-
We are using the orml-tokens pallet for all our token needs on the kintsugi and interlay networks. I think we can show a custom token balance on the accounts page using the `derive` approach. However,…
nud3l updated
2 years ago
-
Having the same issue as #4254 on a custom chain
Snippet:
```
const transaction = api.tx.sudo.sudo(
api.tx.rewards.setItnRewardStatus(itnAddress.publicKey, status)
);
```
Error:
```
A…
-
Using v6.0.5, `.at` queries don't seem to be working. I tried both the old syntax and `api.at`. Below is a usage example, which can be tested on `apps` at `wss://api-dev.interlay.io/parachain` with th…
-
**Describe the bug**
The problem with the withdrawal of tBtc, after conducting about 40 redemptions
![ISSUE#1](https://user-images.githubusercontent.com/90933299/133848118-d74e811e-9d21-4b8a-aeff-ce…
-
cc @polkadot-js/notifications
Some configured chains have outdated types and is determined to problematic as an available chain.
Check the nightly cron output (or via `yarn ci:chainTypes` locally) a…
-
cc @polkadot-js/notifications
Some configured chains have outdated types and is determined to problematic as an available chain.
Check the nightly cron output (or via `yarn ci:chainTypes` locally) a…