Lookup Service
Lookup service is the entry point for every of our services to find exact indexes in order to form requests in a proper way.
Here is its protocol:
Everything is returned via async-await
because runtime metadata is considered as endless flow, even though it's supposed to be updated only like once a minute by default. This might be useful if you want to automatically update values on some constants, or storage values to display on your mobile (or not so mobile) application.
To access lookup service simply use this:
Modules
As per our library, modules are defined this way:
This is the core runtime metadata's component, which we rely on for most of our logic.
You're free to use this as much as you want to create your special behavior.
Constants
Constants is the one of the parts of each module/pallet. It's absolutely the same as in Substrate:
Name is the name which you just provided in search, type is its index in metadata, and value as described above: byte representation in SCALE coding of value in it.
Still, play with this as much as you want. But we strongly encourage using our constants service directly.
Storage
Same, as for constants, it's better to use our storage service in case if you want to get actual values. But if you have specific needs, don't hesitate to use it in whatever way you want. Here is its declaration:
You can go deeper to analyze its contents, at least its storage item subtype:
At least for getting names of these items. But storage key generation for RPC calls is not the easiest thing, so again, our storage service is your very best friend here.
Runtime types resolving
If you want to get the declaration of exact type by its index you can definitely use findRuntimeType method. It has a long list of subtypes, so if you really want to dive so deep, please look at this at our API reference website.
Last updated