Muxed accounts (introduced into the protocol in CAP-27 and defined in its string form in SEP-23) should now be supported by default. Previously, we asked that they be hidden behind an opt-in feature flag; now, they should always be supported.
The following fields are muxed accounts and can thus be either a standard G... or a muxed M... address:
FeeBumpTransaction.feeSource
Transaction.sourceAccount
Operation.sourceAccount
Payment.destination
PathPaymentStrictReceive.destination
PathPaymentStrictSend.destination
AccountMerge.destination
Clawback.from
While the list above should be comprehensive, you can always refer to the XDR for an authoritative source of truth.
Refer to the following releases for reference implementations:
Muxed accounts (introduced into the protocol in CAP-27 and defined in its string form in SEP-23) should now be supported by default. Previously, we asked that they be hidden behind an opt-in feature flag; now, they should always be supported.
The following fields are muxed accounts and can thus be either a standard
G...or a muxedM...address:FeeBumpTransaction.feeSourceTransaction.sourceAccountOperation.sourceAccountPayment.destinationPathPaymentStrictReceive.destinationPathPaymentStrictSend.destinationAccountMerge.destinationClawback.fromWhile the list above should be comprehensive, you can always refer to the XDR for an authoritative source of truth.
Refer to the following releases for reference implementations:
horizonclient@v9.0.0stellar-base@v7.0.0andstellar-sdk@v10.0.0java-stellar-sdk@v0.31.0py-stellar-base@v7.0.0Additional documentation is available in the glossary.