Antonio

Hi guys. Just pinging here to know the status of this issue. It is particularly important in the context of CAIP-19 identifiers, where an NFT (especially EVM-based) might only require...

Just my two cents: we are working on a DID specification that wraps around CAIP-19 identifiers, and because the [spec](https://www.w3.org/TR/did-core/#did-syntax=) also does not allow `/` characters, we are replacing them...

I am not too deep into how things are supposed to work, but I also do not see the benefit of SCALE-encoding a payload which is supposed to be interpreted...

I guess your point makes sense. It is not possible to UTF-8 encode generic extrinsics, as far as I know.

I guess your point makes sense. It is not possible to UTF-8 encode extrinsics, as far as I know.

Hey, update. I tried westend, the example Dock, and also KILT, none of them succeeded. Tried different networks, different configurations (VPN on/off, custom DNS on/off), no luck. I could not...

Plus, I never had issues connecting to any of those RPC endpoints previously, via simple command-line scripts.

It works if I run the executable with sudo, which is definitely not secure. But it might have to do with permissions to access system certificates, somehow. Not sure. Might...

Yeah, building and then running as two separate steps is a good workaround. Should I close the issue for now?

Latest version, 5.0.0. What I mean by raw payload is, as I recently found out, the function that the polkadot extension exposes in https://github.com/polkadot-js/extension/blob/master/packages/extension-base/src/background/RequestBytesSign.ts. What it does, is to wrap...