-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create and sign xts in dart #1626
Conversation
…ils. Probably because it can't understand the signed extensions
…insic param functions
} else { | ||
setState(() { | ||
_transferState = TransferState.notStarted; | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was unnecessary, we now change the state to submitting after checking the pin, this makes it easier.
context, | ||
store, | ||
webApi, | ||
store.account.getKeyringAccount(store.account.currentAccountPubKey!), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We now submit the signer, this will make it easier to implement #1469.
Finally, we move the whole extrinsic creation process onto the dart side, and no JS is used anymore while sending extrinsics, closes #1540. However, it does not remove the webView yet, there is some minor clean up ahead: #1627
Relevant changes:
TxBuilder
. This choice makes the extrinsic API much more flexible. For example, we can pass the signer from the outside instead of assuming it to be the current account, which makes Submit txs from non-current accounts #1469 a low-hanging fruit.