Description

This PR aims to fix missing pooled-staking data refreshing when a transaction is confirmed using the redesigned confirmation screens.

Changes:

• Bumped the @metamask/earn-controller dependency to ^11.0.0
• Removed existing calls to refreshPooledStakes in transaction subscription handlers
• Added new TransactionController:transactionConfirmed event to EarnController messengers

Related issues

Fixes:

• [Bug]: Unstaking banners not refreshing after unstaking transaction confirmation #14440
• [Bug]: Pooled-staking claim banner isn't removed after successful claim transaction allowing for multiple claims to be sent #14444

Manual testing steps

Prerequisite:

• Ensure you have ETH to stake.
• Update your local .js.env file to include the following variables

export FEATURE_FLAG_REDESIGNED_STAKING_TRANSACTIONS=true
export FEATURE_FLAG_REDESIGNED_SIGNATURES=true

To test the unstaking flow, we must first stake some ETH. You can skip this part if you have Staked Ethereum already.

1. From the token list home screen, click on Ethereum or Staked Ethereum

2. On the Ethereum token details screen, click "stake" or "stake more"

3. Stake a valid amount of ETH and continue to the confirmation screen

4. Review and confirm your stake

5. To unstake, click on Ethereum or Staked Ethereum from the token list screen

6. Click "unstake" (only visible if you have Staked ETH already)

7. Enter a valid amount to unstake and continue to the confirmation screen

8. Review and confirm your unstake transaction

9. Wait for smart transaction success

10. After your transaction is confirmed, return to the Ethereum token details screen and you should see a new blue unstaking banner.

Screenshots/Recordings

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.