You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of the rollout of muxed accounts (addresses in the M... form which combine a G... address alongside a uint64 identifier), we need to make M-addresses supported by default. In #348 we enabled their support via explicit opt-in; now, developers should disable supporting them only via explicit opt-out.
This is (intentionally) a breaking change.
As a reminder, the following fields can contain a muxed account. Note that while the below list should be accurate, the XDR is always an authoritative source:
the SourceAccount of anyOperation
the Destination of the three payment operations: PaymentOp, PathPaymentStrictReceive, and PathPaymentStrictSend
the Destination of an AccountMergeOp
the From of a ClawbackOp
the SourceAccount of anyTransaction
the FeeSource of a FeeBumpTransaction
The text was updated successfully, but these errors were encountered:
As part of the rollout of muxed accounts (addresses in the
M...
form which combine aG...
address alongside a uint64 identifier), we need to make M-addresses supported by default. In #348 we enabled their support via explicit opt-in; now, developers should disable supporting them only via explicit opt-out.This is (intentionally) a breaking change.
As a reminder, the following fields can contain a muxed account. Note that while the below list should be accurate, the XDR is always an authoritative source:
SourceAccount
of anyOperation
Destination
of the three payment operations:PaymentOp
,PathPaymentStrictReceive
, andPathPaymentStrictSend
Destination
of anAccountMergeOp
From
of aClawbackOp
SourceAccount
of anyTransaction
FeeSource
of aFeeBumpTransaction
The text was updated successfully, but these errors were encountered: