LongTermOwnerWallet.RegisterRecipient was an unconditional no-op, bypassing recipient validation #1917#1918
Merged
adecaro merged 1 commit intoJul 15, 2026
Conversation
adecaro
force-pushed
the
fix-LongTermOwnerWallet-RegisterRecipient-unconditional-no-op
branch
from
8ed6bbe to
e1ac101
Compare
adecaro
force-pushed
the
fix-LongTermOwnerWallet-RegisterRecipient-unconditional-no-op
branch
from
e1ac101 to
e39e663
Compare
adecaro
deleted the
fix-LongTermOwnerWallet-RegisterRecipient-unconditional-no-op
branch
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
2 participants
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.
Fix #1917
Description
No registration/binding side effects are added (unlike AnonymousOwnerWallet.RegisterRecipient), since the wallet's identity is already resolved and bound at construction time in NewLongTermOwnerWallet — this method is purely a guard.