SEP-10: muxed account and memo support

[JakeUrban]

SEP-10 Muxed Account & Memo Support

SEP-10 now supports authenticating users of shared, pooled, or omnibus Stellar accounts.

These users are either represented using a muxed account (an M... address) or a Stellar account (G...) accompanied by an ID memo.

Changes

buildChallengeTx() or the equivalent function

• Allow muxed accounts as client account parameter values
• Add a optional memo parameter that accepts a 64-bit integer representation and attach it to the challenge transaction returned
  • If your language does not support optional parameters, this may be a breaking change
• Disallow muxed client accounts and memos to be passed in the same call; they are mutually exclusive parameters

readChallengeTx() or the equivalent function

• Allow muxed accounts as source accounts of the first operation within challenge transactions
• Add a 64-bit integer representation memo to the return value if present in the challenge transaction
  • Depending on the data type of the return value, this may be a breaking change
• Disallow muxed client accounts and memos to be present in the challenge transaction; they are mutually exclusive

Implementations

The JS and Python SDKs have implemented this functionality, please use them as references:

• (SEP-10: muxed account & memo support stellar/js-stellar-sdk#709)[https://github.com/SEP-10: muxed account & memo support stellar/js-stellar-sdk#709] included in release v8.3.0
• (SEP-10: Add muxed account and memo support StellarCN/py-stellar-base#521)[https://github.com/SEP-10: Add muxed account and memo support StellarCN/py-stellar-base#521] included in release v4.2.0

[JakeUrban]

stellar/stellar-protocol#1056