In the multisig example located in the developer documents everything is listed in sequence in a single client "session" so to speak.


The way I understood multisig to be useful is that 'rootKeypair' (person A) is able to enable multisig on the account with 'secondKeypair' (person B).

Then a week later (for example) 'rootKeypair' creates a payment. Following that 'secondKeypair is able to sign the transaction N minutes later from a separate client when they're ready to approve.

Is this correct? If so, how does the transaction get moved between clients? Does it happen on the network?

1 Answer 1


Maybe this flow is working on the backend process. You create transaction with signed rootKeypair and save transaction object somewhere else waiting for person B to signed that transaction ?

  • 1
    I was thinking about that as well. Wondering if you can serialize the transaction to XDR and pass the payload off to another client.
    – Ross Bates
    Jan 24, 2018 at 4:43
  • @RossBates yes, you can easily serialize XDR of the transaction envelope to base64 encoded string. Jan 24, 2018 at 15:04
  • @BartekNowotarski awesome thanks, that's good to know. So would this be an approach for "sending" a transaction to a co-signer before submitting it to the network? This is all assuming that I don't have access to the second key, someone else has it and will be signing the transaction on a separate client.
    – Ross Bates
    Jan 24, 2018 at 15:12
  • 3
    Yes, it's not possible to submit transaction to the network without all required signatures so you have to use another channel. Jan 24, 2018 at 15:15

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.