How create an ExtrinsicPayload and sign it on another machine.
See original GitHub issueHello,
- basically I just want to create the
ExtrinsicPayload
onmachine A
connected to my node - then send it over the network (http) to
machine B
which has access to my keys for signing - then pass again the signature to
machine A
for sending the transaction.
I tried to pass the signerPayload.toPayload()
from A to B it works fine as it is JSON.
But I’m missing the api.registry to createType(registry, "ExtrinsicPayload", payload, { version: payload.version }).sign(keys);
.
I tried to play with Codec to encode on A and decode on B, but same problem, I’m missing the api.registry .
Any suggestions ?
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
how to transfer to another account without using api.tx ...
and I created a payload and signed , I got the data and signature after createType('ExtrinsicPayload', payload, { version: payload.version }) ...
Read more >Transaction Construction and Signing - Polkadot Wiki
Construct an unsigned transaction. Create a signing payload. Sign the payload. Serialize the signed payload into a transaction. Submit the ...
Read more >What are the Steps for Encoding an Extrinsic in Substrate?
Format the signature by combining the sender's account ID + the signature from (2) + the extra data. Encode the formatted signature. Encode...
Read more >Day in the Life of a Substrate Extrinsic - Unit 410
The signer payload is first hashed (in some cases, twice) and handed to the appropriate signing function to get the final signature. This...
Read more >Can I send transactions async using polkadot-js - Stack Overflow
I want to know if I can split the signAndSend method into two and execute at different machines. like in a client machine,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes. So machine A has a connection, machine B just needs a way to get access to the hex payload, it never connects to sign.
Mortals are always recommended. However, if you wish to forgo protection it provides, you can (in the above tools) pass
--blocks 0
and it will create an immortal on construction.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.