[ENG-3471] feat: use estimated fees for stx transactions

[teebszet]

🔘 PR Type

• Bugfix
• Enhancement

📜 Background

https://linear.app/xverseapp/issue/ENG-3458

depends on secretkeylabs/xverse-core#323 and
secretkeylabs/xverse-core#335

🔄 Changes

• update to core version where we use the correct estimateTransaction function for STX transactions (sendStx, sendNft, sendFt)
• update to core version where we have applyFeeMultiplier logic in one place
• applyFeeMultiplier also caps the fee at the thresholdHighStacksFee
• use applyFeeMultiplier in sendFt, sendNft, sendStx, and transactionRequest (popup)

Impact:

• impacts sendFt, sendNft, sendStx
• also impacts dapps which trigger a transaction request popup

🖼 Screenshot / 📹 Video

send stx (estimates are returning high fees. screenshot shows capped at threshold: 1STX):

send nft:

send ft:

✅ Review checklist

Please ensure the following are true before merging:

• Code Style is consistent with the project guidelines.
• Code is readable and well-commented.
• No unnecessary or debugging code has been added.
• Security considerations have been taken into account.
• The change has been manually tested and works as expected.
• Breaking changes and their impacts have been considered and documented.
• Code does not introduce new technical debt or issues.

[dhriaznov]

Good job 👍 left a small ask below :)

[dhriaznov]

Let's also add a check for the tokenTransferPayload.memo here to make the code safer?

[teebszet]

good call. it should be an optional arg in the core function

[teebszet]

but I don't want to refactor the core function to make it optional, because then I should also reorder the args to have memo?: string come after the required params.

maybe a compromise here is to apply the default earlier like tokenTransferPayload.memo ?? ''

[github-actions]

Test with build here: https://github.com/secretkeylabs/xverse-web-extension/actions/runs/7445216412