Support partially-signed trasnactions

[sohrab-]

• Save/export partially-signed transactions
• Load and sign existing partially-signed transactions

For this to work, should be able to:

• Import a partially-signed transaction buffer
• Include existing signatures during the transaction send
• Export data model to store signatures
  • Need to make sure our mappings are precise, otherwise the signature becomes invalid

[yamen]

This also makes the transaction read only... if it's changed the signature is no longer valid

[yamen]

An implication of that is that you don't need to accurately regenerate the serialised version - it must already exist

[josephlabeleven]

just thinking the partial-signed transaction will expire in 150 blocks (approximately 1 min after it is generated), should there be something to indicate the user the expiry time of the transaction? This is so the user is not surprised when transaction expires if they read the instructions too long.

[yamen]

Hmmm really good point. I guess this should really be for nonce transactions. Damn.

On Tue, 25 Oct 2022 at 11:22, Joseph ***@***.***> wrote: just thinking the partial-signed transaction will expire in 150 blocks (approximately 1 min after it is generated), should there be something to indicate the user the expiry time of the transaction? This is so the user is not surprised when transaction expires if they read the instructions too long. — Reply to this email directly, view it on GitHub <#92 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACVTZ32ILJGQUSXUKRJOUDWE4R43ANCNFSM6AAAAAARNORAUE> . You are receiving this because you commented.Message ID: ***@***.***>

-- Sent from Gmail Mobile