James Wilson

I've been working on porting over the dynamic-encode-and-decode-into-Value bits into a new crate, https://github.com/paritytech/scale-value, which has plans to be used in subxt for such decoding (and hopefully cargo-contract). I'm not...

> Actually it looks like desub-current compiles to wasm, it's just desub-legacy that does not (and the top level desub crate because it pulls both in). That isn't surprising to...

> T[here](https://github.com/paritytech/substrate-archive/blob/master/substrate-archive-backend/src/runtime_version_cache.rs)'s a nice binary search for metadata versions in substrate archive here that finds where different metadata versions switch, if that helps at all. It was quite fast iirc....

Thoughts on **legacy type decoding**: I'd like to separate the spec/chain stuff from the core type decoding, so that the basic type mappings are just a map from pallet +...

I started working on something like what was described above; a `desub-core` crate which exposed a couple of traits which could be implemented to decode values using either V14 or...

Should we add the `CheckMetadataHash` extension to the kitchensink runtime too?

@josepot and @carlosala raised a couple of good points in a call earlier re this PR, which I want to raise here: ## Extrinsic version number in metadata: keep it...

(I think the bug label was automatically added; apologies if not; this is not a bug but a feature request)

Just to provide some more context for my request: Subxt can be used to construct, sign and submit transactions in Rust. It can also compile to WASM and be used...

I guess the original security concern existed because there was a lack of metadata that was able to decode the bytes given and show the user something more sensible about...