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
The docs are generated from the substrate runtime, it will be different between versions and actual runtimes you connect to. (All docs, including the newly-added Kusama/Polkadot sections) are based on the master branches and updated weekly. What is actually on-chain could be lagging.
In all cases however - the docs are not done manually, they are extracted from the chain metadata and would reflect what is in that (master branch version) runtime.
If you compare Polkadot & Substrate - the kitchensink substrate runtime contains authorityDiscovery, Polkadot does not. Substrate basically exposes all available pallets (mostly), Polkadot/Kusama/others would have a selection based on the chain requirements.
TL;DR Entirely expected that runtimes would differ - the Substrate section lists all Substrate pallets, it is not chain-specific.
If you follow the API docs here https://polkadot.js.org/docs/substrate/storage#authoritydiscovery and call
api.query.authorityDiscovery.keys()
after connecting to WS provider wss://rpc.polkadot.io, it returnsTypeError: Cannot read property 'keys' of undefined
. This was reported here https://substrate.stackexchange.com/questions/7761/how-to-query-api-query-authoritydiscovery-keys/7789#7789Is it the case that it has been replaced with https://polkadot.js.org/docs/substrate/runtime#authoritydiscoveryapi ?
The text was updated successfully, but these errors were encountered: