feat(authorize): memoTag field on AuthorizeBody - #11
Merged
Conversation
thomasjsk
force-pushed
the
feat/authorize-memo-tag
branch
from
July 23, 2026 11:05
cfce193 to
dcf6e20
Compare
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Notabene extension to TAIP-4 (TAIP-4 itself has no memo-tag provision): a fallback carriage for XRPL destination tags / Stellar memos on the Authorize message. The primary carriage stays the
:tagsuffix embedded insettlementAddress(what v2 nodes send today); receivers treat the embedded form as authoritative when both are present. Field isomitempty— untagged traffic is byte-identical to before.