[Bug]: Boost fees are not the same on Bitkit and on mempool

[JeanlChristophe]

Describe the bug

I did a transaction https://mempool.space/tx/05b69d8af651208d14b682f75b77c4bc8e9a2a4b40f47adbd291340b6a07ff8a

and I boosted it https://mempool.space/tx/05b69d8af651208d14b682f75b77c4bc8e9a2a4b40f47adbd291340b6a07ff8a

The fees indicated on mempool are 1494sats but on Bitkit it's 5146sats

Reproduce

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Screenshots / Recording

Operating system

GrapheneOS

Bitkit version

118

Log output

No response

[catch-21]

It is by design to show the sum of all fees for the boost activity, so I think it is ok. In this case it is the fee of these two transactions, 1494+3652=5146 :

• https://mempool.space/tx/05b69d8af651208d14b682f75b77c4bc8e9a2a4b40f47adbd291340b6a07ff8a
• https://mempool.space/tx/94290dc7baf3536ebc8d75d8509c2709f6486c04671f7baa9cca6215d03f82ac

[pwltr]

It is by design to show the sum of all fees for the boost activity, so I think it is ok. In this case it is the fee of these two transactions, 1494+3652=5146 :

• https://mempool.space/tx/05b69d8af651208d14b682f75b77c4bc8e9a2a4b40f47adbd291340b6a07ff8a
• https://mempool.space/tx/94290dc7baf3536ebc8d75d8509c2709f6486c04671f7baa9cca6215d03f82ac

I think that assessment is correct. Current implementation looks good to me.