feat(tempo)!: remove custom memos - #31
Merged
Merged
Conversation
ksn-stripe
changed the title
ksn-stripe
marked this pull request as ready for review
September 16, 2026 14:36
Committed-By-Agent: codex Co-authored-by: codex <noreply@openai.com>
Committed-By-Agent: codex Co-authored-by: codex <noreply@openai.com>
ksn-stripe
force-pushed
the
fix/tempo-static-memo-hash
branch
from
September 16, 2026 19:38
d521ad5 to
2287db7
Compare
This was referenced Sep 17, 2026
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.
Custom merchant memos bypassed challenge binding, allowing a caller to redeem another payer's unclaimed transaction. Remove custom-memo configuration and request plumbing, and require challenge-bound attribution memos in direct Tempo verification.
Breaking change: remove
TempoMethod.Builder.memo(...)calls andMethod.memo()overrides. Clients use automatic attribution memos. Direct verification rejects explicit memos before any RPC call, including before broadcasting signed transactions. Relay verification remains delegated to the relay; the SDK no longer offers custom-memo configuration for either flow.