Extrinsic value sometimes is not decoded in latest version
Yuripetusko opened this issue · comments
Example here
https://kusama.subscan.io/extrinsic/0x596a166ee1fb01e6d9f0940340f0b958c6cbcb2d6b21f00408cb2718a7efc4de
extrinsic of type system.remark used to be displayed decoded before but not anymore
@Yuripetusko Hi, system.remark context not decoded because it not ascill
It used to be shown decoded just few weeks ago, by decoded I mean polkadot js hextToString method. Most of the time system remark contains some kind of message so it would be nice to display it here instead of hex. And subscan used to do it not a long time ago,nso it's a new bug
It used to be shown decoded just few weeks ago, by decoded I mean polkadot js hextToString method. Most of the time system remark contains some kind of message so it would be nice to display it here instead of hex. And subscan used to do it not a long time ago,nso it's a new bug
Hey, @Yuripetusko , I check polkadot js https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpub.elara.patract.io%2Fkusama#/explorer/query/9041075, the same is shown here, there may be some characters that cannot be decoded
Oh yeah, you are right. Interesting, will try to investigate this more locally. This is also a new issue with polkadot.js, previously all of the remarks were decoded fine 🤔