Jaco

Request for twox/xxhash

2

First off, this is impressive - I have early branches switching to this https://github.com/polkadot-js/common/pull/1188 (also planning on doing secp256k1 & ed25519 - the first also has a PR, the second...

As per https://github.com/paritytech/substrate/pull/11649 (Needs end-to-end testing once the above is available)

See the ill-fated https://github.com/polkadot-js/api/issues/4874 Effectively when the wrapper is there and detected, apply. (PortableRegistry-only)

Agreeing with the [commenter here](https://substrate.stackexchange.com/a/2955/627) that it should actually be technically [do-able](https://github.com/polkadot-js/api/blob/master/packages/api-base/src/types/storage.ts). Hopefully... (It is never quite simple to fight with the TS type language for extraction magic, but quite...

We should encode with those specific types, just in case of customisation. (No per-string type overrides anymore)

This does add some friction/delays to the sending process, however it is more robust in terms on retrieving the exact on-chain status in terms of hashes (instead of re-calculating it)

The full track configuration would be quite beneficial to be exposed. Specifically this part - https://github.com/paritytech/substrate/blob/b27c470eaff379f512d1dec052aff5d551ed3b03/frame/referenda/src/lib.rs#L184-L190 where `Tracks: TracksInfo` is defined. Without this info is is currently impossible (without duplicating...