Unable to send BTC on phantom wallet

[MBMaria]

Overview

Getting an error when trying to send BTC on phantom wallet

References and additional details

https://jam.dev/c/a3d35509-dba4-4c42-a0fe-265d70bb7055

Acceptance Criteria

Should be able to send BTC on phantom

Need By Date

No response

Screenshots/Mockups

No response

Ownership

• If my bounty needs engineering or needs product I have added the respective labels on the right
• As the sponsor of this bounty I will review the changes in a preview environment (ops/product) or review the PR (engineering)

Estimated effort

No response

Sponsor / Stakeholder

No response

Bounty Hunters

• Join our discord
• Include an expected timeline for you to complete work in the work plan when you apply for this bounty!
• Please refer to this link for some basic info
• Please do not start work on this issue until you are approved in Gitcoin.

[woodenfurniture]

Confirmed the issue persists after release #8198 went out (which includes #8197)
https://jam.dev/c/42ee1d49-5107-4815-8ffa-06213220dc99

[gomesalexandre]

@MBMaria @woodenfurniture Couldn't repro on latest develop and prod (tested on develop locally, and upstream on prod), is this still happening for you guys? And if so, can I haz the address you're trying to send to to try to send to it as well?

Develop:

https://live.blockcypher.com/btc/tx/8e081db5f1252d706f9cfd89cda8bf71e9379b1e4aec6c45f45e963afdb46725/

Prod:

https://live.blockcypher.com/btc/tx/21aa9701ad5fdaa8c97d315cb5acbbdd0a53621922b6101a577d2930dbcbcfdb

[MBMaria]

Was able to recreate again now with a different address.
1st one: 166fG6tESGgUDm53oSAm2cGB2rByzXQG5e
2nd one: bc1qqax70hx8x026y6uv74lewqt9le3n8r56w7s8ng

[gomesalexandre]

Was able to recreate again now with a different address. 1st one: 166fG6tESGgUDm53oSAm2cGB2rByzXQG5e 2nd one: bc1qqax70hx8x026y6uv74lewqt9le3n8r56w7s8ng

https://live.blockcypher.com/btc/tx/64e6f666324700847e876616dfe08aac882fdea438a0b96805ede1cf2a562690/
https://live.blockcypher.com/btc/tx/421a1b3fae466a957e4b8104da655a75e204f703454b7ca4fd171d3c104efc2d/

Was able to send to these two addies on develop, requested Foxcrypt of seed to try and repro with affected account 🙏🏽

[gomesalexandre]

Repro'd in develop.shapeshift.com after getting @MBMaria's seed and trying a send to 166fG6tESGgUDm53oSAm2cGB2rByzXQG5e and as confirmed, this is not an us issue but it is thrown by Phantom:

However, regardless of how many times I try this again on upstream develop or while running web locally, I can't get to this error anymore for debugging.

See myself retrying with a fully cleared cache and MbMaria's account:

https://jam.dev/c/30fb10e8-bad3-46e9-a9aa-627e82f71004

Disregard all above. I can consistently reproduce sending to 166fG6tESGgUDm53oSAm2cGB2rByzXQG5e:

https://jam.dev/c/c9d9f363-b7dd-464b-8f08-b846829350d3

Tx input:

{
    "coin": "Bitcoin",
    "inputs": [
        {
            "addressNList": [
                2147483732,
                2147483648,
                2147483648,
                0,
                0
            ],
            "scriptType": "p2wpkh",
            "amount": "18743",
            "vout": 1,
            "txid": "447eceea134ee90f5f126f3ab462846daf1b263d468309420b4a1a8675603567",
            "hex": "redacted"
        }
    ],
    "outputs": [
        {
            "addressType": "spend",
            "amount": "1042",
            "address": "166fG6tESGgUDm53oSAm2cGB2rByzXQG5e"
        },
        {
            "addressType": "change",
            "amount": "15893",
            "addressNList": [
                2147483732,
                2147483648,
                2147483648,
                1,
                0
            ],
            "scriptType": "p2wpkh",
            "isChange": true
        }
    ]
}

[gomesalexandre]

Update: There's not so much about 166fG6tESGgUDm53oSAm2cGB2rByzXQG5e being borked to send to, but rather all sends failing when sending from Maria's seed. @woodenfurniture you could confirm here but pretty sure any send - including self-send, would fail for you as well.

Going deeper into the rabbit hole, debugging not only our implementation but running devtools on Phantom extension itself, stay tuned...

[gomesalexandre]

@MBMaria I've tried a send to 166fG6tESGgUDm53oSAm2cGB2rByzXQG5e through Phantom's UI (pretty sure any send, self or not, would solve things out as well) and it seems to have unblocked things, now sends are happy in app - couldn't see anything wrong in how the Tx was previously formed, though I suspect there is something Phantom didn't like in the previous UTXO set.

@woodenfurniture if you want to try this as well, though careful, this means you won't be able to repro anymore as that effectively solves things. Raised the issue in Phantom discussions https://github.com/orgs/phantom/discussions/323 since I was able to capture the error in Phantom devtools and we now know that this is coming from scure-btc-signer package Phantom uses - since our payloads are not malformed, and things work as they should after a send within Phantom, I'm pretty confident this is an upstream issue within Phantom extension itself, which struggles with some UTXO sets.

[gomesalexandre]

Moving to blocked as issue has been raised upstream. For the time being, solution is to proceed to (any) send through Phantom UI itself, which I assume reconciliates the UTXO set for the address (not xpub, Phantom only consumes address_index 0 and doesn't do next receive addy business) in a way that it's then happy with when we call signPSBT() the next time around

[gomesalexandre]

Confirmed with @woodenfurniture and @MBMaria we're g2g here as we have effectively a fix to tell users for the time being. Closing, to be updated if/when there are changes fixing this upstream in Phantom build.