The list will be updated/expanded as questions come up, dealing with some common issues that API users find.
# I am getting a "Unknown types found, no types for ..." error
There are 2 causes for this, both related to the version of the API that you are using and the support of types. As explained in the elsewhere, types on Polkadot/Substrate are continuously evolving - the latest version of the API always tries to support types for the latest Polkadot networks, such as Kusama. So for Polkadot public chains, ensure that you are using the latest released API version.
If however you are running against a master branch of either Polkadot or Substrate, you may well be better suited running a beta version, tracking master. If you are connected to a customized chain, you would rather want to register the types either on your own, or via packages that the chain vendor provides.
# I am getting a "Metadata:: failed on MagicNumber" error
Update your version of the API to the latest version. Like types, the metadata interfaces are continuously evolving. For instance with the Polkadot Alexander network, only metadata v3 is available. By the time Kusama launched, this has been bumped to v7. As these versions are added to the Polkadot/Substrate codebase, they are added to the API.
# I would like to sign transactions offline
The API itself is independent on where the signature comes from and how it is injected. Additionally it implements a signer interface, that can be used for external signing - an example of this is the polkadot-js/apps support for signing via extensions and even the polkadot-js/extension support for tools such as the Parity Signer.
As of this writing we don't have an explicit example of implementing the signer interface in these docs, although we do use one in our tests. Additionally, the polkadot-js/tools has an implementation of a very basic offline signer where transactions are generated in one process and signatures in another non-connected process.
# I would like to send a root transaction
Some calls in Polkadot/Substrate can only be submitted as root, these are indicated by
ensure_root(origin) in the Rust codebase. Root here does not refer to the actual account, i.e.
//Alice on a
--dev chain, but rather that it cannot be submitted as a bare user transaction. This restriction applies to chain upgrades, changing balances or anything that modifies the state and/or chain operation.
To submit these transactions, it needs to be send as a wrapped transaction via either
sudo.sudo (assuming you have access on your chain) or
democracy.proposal (which would allow users of the chain to vote on it).
# How do I call a function with a Tuple input
Tuples, as defined in the Polkadot/Substrate types appear as
(TypeA, TypeB). For instance we may have an
(AccountId, u64) input as defined in the metadata or as part of the user types. To specify a Tuple as an input, wrap it is an array format, for instance to call
query.module.get((u32, u64)) where a
(u32, u64) Tuple input is expected, you would do
# How long do transactions live
Polkadot/Substrate supports both immortal and mortal transactions. For immortal, this means that the transaction has an infinite lifetime, for mortals, the transactions expire after a defined period. By default the API sends mortal transactions when no explicit extrinsic era has been specified. This means that all transaction has a limited lifetime and will expire if not included in the period set.
The length for this transaction validity is set to 50 blocks, which translates to 5 minutes assuming a default of 6 second blocktimes. (10 blocks per minute in this default configuration).