Bitcoin - wrong send value in confirm screen

[gomesalexandre]

Summary

Currently seeing wrong send value in confirm screen for BTC sends - it uses the fees as a send value

For reference, this is our pst `.data.globalMap.unsignedTx' path (can't paste the full psbt here for some reason as it doesn't serialize well):

Example

No response

Steps to Reproduce

• Perform a SegWit native (the only currently supported script type) send
• Notice send value is off
• Notice expending it correctly shows the right outputs, including the actual send

Phantom Version

No response

Is there an existing discussion for this?

• I have searched the existing discussions

[adamdelphantom]

Hey @gomesalexandre,

These balances seem correct since you are sending to the same wallet you are sending from.

[gomesalexandre]

Oh I see so that's not so much of taking your input value and using that as a value but rather doing a relative balance - balance after outputs - gas! It makes sense then, given there is no xpub support, I guess self-sends would be quite exotic of a flow and probably used by devs only.

Thanks for the disambiguation @adamdelphantom! That's actually quite a nice way to represent it 🙏🏽