Bitcoins "stuck" in Sparrow Taproot Wallet

[BlockCheney]

I created a Taproot Wallet (Single Sig, BIP39 with 15 Words+passphrase) using Sparrow Wallet. That worked fine and I sent some bitcoins from my other wallet to one of the new bc1p addresses. The problem is now I can't spent the bitcoins from that address. When I try to sign a transaction using the wallet password in Sparrow it doesn't sign for some reason and there is no option to broadcast the transaction. Can someone help me with this? maybe it's a problem to use BIP39 in combination with taproot?

[1715569393]

1715569393

[dkbit98]

Do you run your Sparrow wallet with full node or you are using some electrum server, and do you use it as single or multisig?

Note that Taproot is still in early stages and I wouldn't suggest using it now if you are a normal user, it could be some bug that you could report to Sparrow github page.

You can also try other wallets that support Taproot:

• Bitcoin Core ^{(manual import)}
• Specter wallet
• Fully Noded
• Muun wallet
• Ledger ^{(v2.35+ experimental)}

[BlockCheney]

Do you run your Sparrow wallet with full node or you are using some electrum server, and do you use it as single or multisig?

Note that Taproot is still in early stages and I wouldn't suggest using it now if you are a normal user, it could be some bug that you could report to Sparrow github page.

You can also try other wallets that support Taproot:

• Bitcoin Core ^{(manual import)}
• Specter wallet
• Fully Noded
• Muun wallet
• Ledger ^{(v2.35+ experimental)}

Yeah I think it's a bug, obviously someone else has the same problem https://giters.com/sparrowwallet/sparrow/issues/311

Luckily I only sent like $15 worth of bitcoin. Should better be more careful next time

[dkbit98]

Yeah I think it's a bug, obviously someone else has the same problem https://giters.com/sparrowwallet/sparrow/issues/311

Luckily I only sent like $15 worth of bitcoin. Should better be more careful next time

I don't think you actually lost anything as long as you have your seed words backup and I would personally wait few weeks or month before testing Taproot.
You can follow Taproot usage statistics, and see it's still low.

[pooya87]

Note that Taproot is still in early stages and I wouldn't suggest using it now if you are a normal user, it could be some bug that you could report to Sparrow github page.

Taproot is a couple of years old and is already mature enough. If you use a proper software such as bitcoin core you won't have any issues or concerns about bugs. The problem is with untested or little tested implementations that are sometimes unpopular too.
With a quick look into Sparrow wallet I couldn't find enough tests for the wallet as a whole and no Taproot tests.

[dkbit98]

Taproot is a couple of years old and is already mature enough. If you use a proper software such as bitcoin core you won't have any issues or concerns about bugs. The problem is with untested or little tested implementations that are sometimes unpopular too.

You can't say something is mature enough when it's been activated only few weeks ago.
Maybe you have some top secret information I don't know, so please tell me what wallets could be used with Taproot few years ago in bitcoin mainnet?

[pooya87]

You can't say something is mature enough when it's been activated only few weeks ago.
Maybe you have some top secret information I don't know, so please tell me what wallets could be used with Taproot few years ago in bitcoin mainnet?

I'm talking about the algorithm not the implementation. Taproot as a proposal and the algorithm has been discussed, reviewed and tested for a very long time. It activated on private networks then Signet then Testnet and when it finished maturing it was activated on MainNet. That is how every change should be since immature changes lead to vulnerabilities in protocol.

[HCP]

Yeah I think it's a bug, obviously someone else has the same problem https://giters.com/sparrowwallet/sparrow/issues/311

Luckily I only sent like $15 worth of bitcoin. Should better be more careful next time

It seems that this bug has been fixed in the new 1.5.3-beta1 release: https://github.com/sparrowwallet/sparrow/issues/311#issuecomment-984853015

So, maybe grab the new beta version and see if that works for you.


On a side note, that giters website is dreadful. It doesn't handle the markup in the comments very well