Martin Rieke

Results 4 comments of Martin Rieke

PolkaJS unable to decode valid block

Hi, this issue still occurs regularly for us, so I've spent some more time investigating it. I believe it boils down to the following discrepancy: a) In the type registry,...

PolkaJS unable to decode valid block

For your information, it is possible to hack this to work, by not relying on the outputTypeName to be unique and instead constructing the lookup name. in polkadot/rpc-core/bundle.js you could...

Ensure rpc-core can correctly decode types, even if multiple types share the same name

you are correct. this only fixes the issue that storage items with the same type name could not be decoded. for calls/extrinsics, more work is needed.

Ensure rpc-core can correctly decode types, even if multiple types share the same name

would it still be possible to merge this fix?