Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support muxed addresses (SEP-23) by default. #397

Closed
Shaptic opened this issue Jan 6, 2022 · 0 comments · Fixed by #399
Closed

Support muxed addresses (SEP-23) by default. #397

Shaptic opened this issue Jan 6, 2022 · 0 comments · Fixed by #399
Assignees

Comments

@Shaptic
Copy link
Contributor

Shaptic commented Jan 6, 2022

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 any Operation
  • the Destination of the three payment operations: PaymentOp, PathPaymentStrictReceive, and PathPaymentStrictSend
  • the Destination of an AccountMergeOp
  • the From of a ClawbackOp
  • the SourceAccount of any Transaction
  • the FeeSource of a FeeBumpTransaction
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants