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
Currently, to sign transactions, we lean on the "substrate-compat" feature to pull in the substrate deps we need to provide a PairSigner (which plays nice with sp-keyrings AccountKeyring and the Pair trait form Substrate).
Without the Substrate deps (ie if we want to compile to WASM) we have no built-in way to sign transactions.
I'd like us to think through and add a basic API for signing transactions. The goal would be that we can perform basic signing given some public/private keypair, and that we can use the Alice/Bob/Charlie style accounts for signing in example code.
I'd need to investigate to see whether signing algorithms we'd want to support actually compile to WASM or not, and also to see which signing algorithms to support in the first place (the 3 that a MultiSignature can provide signatures for?).
My hope would be that the API can be as simple as possible. In many production cases it may be that we want to lean on external signing approaches (eg handing to parity-signer or using wweb APIs to sign via ledger etc), but having some facility built in that's good enough for simple examples and playing around would be great to keep the barrier to experimenting with this stuff low.
The text was updated successfully, but these errors were encountered:
And also I think If we can enable production wallet signing, Like I Have my PJS account and I can just import that account and use it to sign txn using subxt, I think this can enable CLI-Dapps
Yup for sure! There was definitely an idea in #583 to add the ability to construct transactions to the CLI tool and then potentially sign them via a web interface and wallets connected there, before passing the signed tx back to the CLI tool to finish submitting.
At present it would already be possible to build that facility on top of Subxt such that it could be compiled to wasm, and signing could take place on the JS side to leverage connected wallets. We should eventually add an example to show that in action, though it is a different issue from this :)
Currently, to sign transactions, we lean on the "substrate-compat" feature to pull in the substrate deps we need to provide a
PairSigner
(which plays nice withsp-keyring
sAccountKeyring
and thePair
trait form Substrate).Without the Substrate deps (ie if we want to compile to WASM) we have no built-in way to sign transactions.
I'd like us to think through and add a basic API for signing transactions. The goal would be that we can perform basic signing given some public/private keypair, and that we can use the Alice/Bob/Charlie style accounts for signing in example code.
I'd need to investigate to see whether signing algorithms we'd want to support actually compile to WASM or not, and also to see which signing algorithms to support in the first place (the 3 that a
MultiSignature
can provide signatures for?).My hope would be that the API can be as simple as possible. In many production cases it may be that we want to lean on external signing approaches (eg handing to parity-signer or using wweb APIs to sign via ledger etc), but having some facility built in that's good enough for simple examples and playing around would be great to keep the barrier to experimenting with this stuff low.
The text was updated successfully, but these errors were encountered: