chore(predict): add transfer after claim

[caieu]

Description

• Adds minimum transfer after claim

Changelog

CHANGELOG entry: null

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

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.

---

Note

Adds a balance check and optionally appends a USDC transfer to claim transactions when signer collateral is below a minimum threshold; updates claim transaction shape and tests.

• Polymarket Provider
  • prepareClaim: checks signer collateral via getBalance and sets includeTransferTransaction when balance < MIN_COLLATERAL_BALANCE_FOR_CLAIM.
  • Returns claim transactions as an array (not a single object).
• Safe Utils
  • createClaimSafeTransaction: optionally appends an ERC20 transfer (USDC) to the signer and aggregates via multisend.
  • getClaimTransaction: accepts includeTransferTransaction, using signer address when true.
• Constants
  • Introduces MIN_COLLATERAL_BALANCE_FOR_CLAIM = 0.5 and uses collateral/decimals in transfer encoding.
• Tests
  • Update provider and safe utils tests to expect array-based claim transactions and to cover transfer-inclusion cases across balance thresholds.

^{Written by Cursor Bugbot for commit 8abd446. This will update automatically on new commits. Configure here.}

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[matallui]

Just a comment on updating the top-up calculations, but not blocking for this PR. We can address that later. 🚀

[matallui]

The goal should be to top up the account up to $1, not just add 0.5 when it's below that. I do think this is pretty good for this PR though, just to give something to Confirmations team. We can always update that logic later.

[sonarqubecloud]

Quality Gate failed

Failed conditions
B Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE