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
I am trying to build a tool that allows a user to do the steps createTx-signTx-SendTx in three separate (in time and location) steps.
I am having trouble with the 3rd step where I have SignerPayloadJSON, registry info and signature saved in a file and I want to recreate the signed tx to be able to send it.
Using signAndSend with injected signer wouldn't work because it would recreate a SignerPayloadJSON with new era and the signature wouldn't be valid anymore.
If you have the full tx constructed already elsewhere, use api.tx(<hex goes here>).signAndSend(...)
If using the standard signAndSend form, the data for era is only retrieved (like the nonce) if not explicitly supplied in the signAndSend options. So if there are existing values that should be used (e.g. already determined in an out-of-bands process), they can just be passed through.
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.
I am trying to build a tool that allows a user to do the steps createTx-signTx-SendTx in three separate (in time and location) steps.
I am having trouble with the 3rd step where I have SignerPayloadJSON, registry info and signature saved in a file and I want to recreate the signed tx to be able to send it.
Using signAndSend with injected signer wouldn't work because it would recreate a SignerPayloadJSON with new era and the signature wouldn't be valid anymore.
This is the PR: moonbeam-foundation/cli-ts-signer#12
The text was updated successfully, but these errors were encountered: