improve: rename Spoke Pool's hubPool variable to withdrawalRecipient #629
Conversation
This file contains 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
Signed-off-by: bennett <bennett@umaproject.org>
nicholaspai
reviewed
Oct 7, 2024
nicholaspai
approved these changes
Oct 8, 2024
Signed-off-by: bennett <bennett@umaproject.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is meant to generalize the
hubPoolvariable in all spoke pools. ThehubPoolvariable is only used in_bridgeTokensToHubPool, where it is set as the recipient. For spoke pools deployed on L3s, or for spoke pools which may not want to withdraw token to the hub pool (e.g. theBlast_SpokePool), thehubPoolvariable is either a misnomer or unused. This changes the variable to be calledwithdrawalRecipientto better reflect the purpose of thehubPoolvariable.