Closed AurevoirXavier closed 1 year ago
Yes, it (currently) assumes that all AccountId
on-chain are the same from an input perspective, i.e. maps them to the same underlying (single) input.
Which chain is that - since it would be good to have a testcase for any possible 20 + 32 adjustments.
Which chain is that - since it would be good to have a testcase for any possible 20 + 32 adjustments.
It's still a testnet. https://polkadot.js.org/apps/?rpc=ws%3A%2F%2Fg1.dev.darwinia.network%3A20000#/explorer
@jacogr Hey, is there an estimated time? We are considering renaming the struct to make it work.
This is not easily solvable at all - all the Account dropdowns are backed by the keystore which is set to the default account type for the chain. So effectively to support both types we need something completely non-backed.
(The second type will probably end up as something like we have in the validators graph query, i.e. only allow inputs, no pre-defined selections)
(The second type will probably end up as something like we have in the validators graph query, i.e. only allow inputs, no pre-defined selections)
Yes, that's enough for us.
Thanks for your quick response and work.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.
It always truncates the
from
account id 32 to account id 20. I can't input a 32 bytes data.