You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are type registry JSON files in a type_registry directory. It seems like very few of them are provided by projects developers. Could you reveal how you create these JSONs? It could help to contribute to the project. Thanks!
The text was updated successfully, but these errors were encountered:
There is some history for those type registry files. Since Substrate introduced MetadataV14, it contains an embedded type registry with all types used in the calls and storage functions. Before that, types were just mere strings how they were named in the RUST code of the runtime. So back then there was a need to manually administer a type registry to describe the type decomposition in primitives.
For networks like Kusama those registries were already maintained by PolkadotJS (example), so I could gratefully re-use those.
But for other networks that don't provide an own registry file, you basically have to analyse the RUST source and create a type registry manually:
TL;DR: Probably you don't need to create/maintain a type registry file, unless the Substrate runtime still utilises MetadataV13 or lower (check substrate.get_metadata() and substrate.implements_scaleinfo()).
Hi there 👋
There are type registry JSON files in a type_registry directory. It seems like very few of them are provided by projects developers. Could you reveal how you create these JSONs? It could help to contribute to the project. Thanks!
The text was updated successfully, but these errors were encountered: