fix(jito): remove output for staking activate #6897
Merged
Conversation
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
haritkapadia
force-pushed
the
harit/fix-jito-tx-not-confirmed
branch
from
68e8fa0 to
61b4587
Compare
noel-bitgo
approved these changes
Sep 5, 2025
haritkapadia
force-pushed
the
harit/fix-jito-tx-not-confirmed
branch
from
61b4587 to
c8ef1e5
Compare
sbplat
approved these changes
Sep 5, 2025
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.
Description
This PR removes the output for StakingActivate instructions when the staking type is JITO. This is because the stake pool account (passed as
stakingAddressandvalidator) doesn't actually receive the funds. Moreover, the user (fee payer, owner of wallet) is not the owner of the stake pool account.Issue Number
Ticket: SC-3015
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
I updated the existing unit test. The change has to then be verified by upgrading wallet-platform and trying to reproduce the bug.