Topic: Bitcoin Taproot transaction STEP BY STEP on bitcoin-cli... (Read 514 times)

Is this AI generated text? While it sounds convincing, it has several wrong details such as this one,


"taproot" isn't valid value for second parameter. It should be "bech32m".

Seems to be fixed in Bitcoin Core 26.0 and it is possible sign TapRoot-type transaction using signrawtransactionwithkey.

I still believe it is possible.

This post:

https://bitcointalksearch.org/topic/m.62647223

Says we could only use PSBT's what is not true, signrawtransactionwithwallet works well.

I believe we can't use signrawtransactionwithkey to sign complex taproot script as the post says, but signing with privatekey path is not complex taproot script, so, maybe it is possible if we create the full command with the respective witness value.

Contrary to the name signrawtransactionwithkey, the command doesn't sign a transaction unless it isn't of the TapRoot-type, I'm afraid. I have verified it. There isn't any tool to do it.

In my case, the trick is importing the address with "timestamp"= date of the block of the first UTXO and let it do it until the end, after that, when I want to move, just repeat the command with "now" and it works perfectly.

About signrawtransactionwithkey maybe it works, I heard many times we couldn't do taproot transactions without PSBT's, etc and I did it, so, maybe everything have solution and the problem is just doing the configuration of the command with all variables.

If someone have success please report it.

Thank you for feedback. Indeed, there is the serious issue that many seem to encounter trying to use Bitcoin Core.

The message is not meaningful to a user. It leaves them with no clue what to do next and if anything is possible. There is what happened most probably:
1) A key was imported to a wallet.
2) Wallet searched for UTXO and other Bitcoin blockchain data relevant to the key and found none.
3) User ran signrawtransactionwithwallet RPC command.
4) Wallet didn't perform signing and send the confusing message instead.

Why?
Wallet didn't search for UTXO and other Bitcoin blockchain data in the complete dataset. As a matter of fact, only a small percentage of the dataset was scanned - typically spanning a few hours from the moment of import - as indicated by the "now" timestamp option in the importdescriptor RPC command. The UTXO had been created (transaction took place) earlier. In order to be aware of the UTXO, Bitcoin Core wallet needs (re-)scanning earlier data. There are additional two catches: wallet doesn't search other data automatically (so-called rescan) and shows the same error even if rescanning hasn't completed (after user started it manually). The error message is shown for the next few days or more until rescan is completed (Initial Blockchain Download-long in most cases, especially so-called "prune nodes" with default settings). During rescan Bitcoin Core wallet searches for and records (cache) data relevant for keys it stores. Without the data signing can't succeed and the error message is shown.

So the issue is specific to signrawtransactionwithkey with TapRoot and not just the goal of signing a transaction?
In that case, although it has the same error, it's not related to your previous issue with signrawtransactionwithwallet.
Bitcoin Core simply doesn't currently support signing TapRoot inputs with signrawtransactionwithkey.

Refer to this post: https://bitcointalksearch.org/topic/m.62647223
And issue: https://github.com/bitcoin/bitcoin/issues/27017

Here goes the answers for many posts you made.

Before I was using version 23, but I managed to upgrade to 25, problem was that I was running a service in this website:

https://console.shuken.io/account/

And they were running only version 23.

They said they would upgrade just next month, so I moved on to a VPS and I installed a pruned node.

Now with my own version 25, I got solution for the problem:

"error": "Witness program was passed an empty witness"

What is the problem?
If we add some address to our wallet and we use the option to rescan the wallet since some "timestamp" value it will never work, we will see always that error.

So, if you use a "timestamp" to rescan wallet, at the end you need to always run this command:

bitcoin-cli importdescriptors '[{"desc": "tr(your_private_key)#your-checksum", "timestamp": "now", "internal": false, "label": "your_label"}]'

Sometimes even if you stop the core and restart again you need to do it again what is a pain in the ass.

After that you just create the raw normally with this command:

bitcoin-cli createrawtransaction '[{"txid":"your_txid","vout":your_vout}]' '[{"your_destination_address":your_amount}]'

That will give some output like this:
0200000001...

Then we sign that output RAW with this command:

bitcoin-cli signrawtransactionwithwallet 0200000001...

That will give us some output like this:
020000000001...

And we use it to broadcast it with:

bitcoin-cli sendrawtransaction 020000000001...

That's it.

But now... Here we go again, infatuation !

If we want to use signrawtransactionwithkey and we are using the simplest syntax:

bitcoin-cli signrawtransactionwithkey 0200000001... '["your_private_key"]'

I got the same old f* error:

"error": "Witness program was passed an empty witness"

Now we can't use the bitcoin-cli importdescriptors trick with "timestamp": "now", so, what is the solution?

Try it yourself please and give here feedback about if you have the same results or not.

What is the result of your attempts, cfbtcman?

Yeah, probably a sync'ing problem. Somehow, when me and the OP tried the procedure in my node, I didn't even have to do any sync for the wallet. He had sent some sats to that address recently, so, everything was kind of recent. Maybe because of that we didn't have any issues!

It was with signrawtransactionwithwallet command that I tried to reproduce based from OP's reply.
But refer to my reply just above yours for the update. (latest test worked)

It may not be a coincidence that I got the same result the first time but the command worked after a while.
So it's either his node is lacking the necessary UTXO, using the incorrect wallet or missing the needed descriptor.

No, just the output of the createrawtransaction. The only thing I added to all commands was the -rpcwallet=Wallet-name but this has no influence in the command other than to specify the wallet in question!

But you are saying you got that error also with createrawtransaction command? I can try to repeat the commands for you if you want (or if it is still doable)...

I did another quick test with non-PSBT workflow and it worked this time, without even including "prevtxs" during signrawtransactionwithwallet RPC.
Probably previous sync issue or something.

Anyways, AFAIK signrawtransactionwithkey wont work with TapRoot at the moment.

Data in your wallet need refreshing (rescan blockchain), most likely. Alternatively, you could pass the data ("prevtxs") manually in the signrawtransactionwithkey RPC.

Did you added anything in signrawtransactionwithwallet or just the raw transaction?

Because I tried to spend a TapRoot input and I got the same "Witness program was passed an empty witness" error as OP with
signrawtransactionwithwallet command whether "witnessScript" was included under "prevtxs" or not. (prob. didn't helped bec. it's for P2WSH or P2SH-P2WSH)

We have tried the simple approach of createrawtransaction, signrawtransactionwithwallet and sendrawtransaction with my node and all commands worked flawlessly. Something he was doing wrong because I didn't face any of his problems!

Yes it works, I just did a quick(ish) test on a 25 node following what nc50lc posted.

This is going to be a bit more snarky then I want it to really come out as, but why are you testing / running on an older node that you don't control?
23 is at maintenance end and will be full EOL in 7 weeks: https://bitcoincore.org/en/lifecycle/

If you are going to be using this to provide a service you should be on a newer version of core.

As I said, it looks more snarky on a screen then I am trying to be, but something you should be thinking about.

-Dave

Version 25, but I tested it with a ranged descriptor that can derive the input's prvKey.

Do you mean a node that doesn't contain the descriptor with private key?
Because walletprocesspsbt wont work in that case since it relies on the descriptor that can sign that particular PSBT.

Otherwise, I should've noted to use: utxoupdatepsbt after creating the PSBT.
Here's the command (use between the second and third steps):
or

Hi, thanks for the answer, I have also tested without success, seems the wallet can't sign.

I read that is only supported in last core version 25 and for moments I can't try it because I only have 23 and is a testing node that I don't control.

Have you tested it with success on what core version?

Use PSBT instead of raw transaction:

Firstly, import the necessary descriptor to the wallet if it's not available (command already provided).

Secondly, create a partially signed Bitcoin transaction:
Thirdly, process the psbt (update, sign):
Fourthly, finalize it:
Lastly, send it to mempool:

I suggest checking that the command is executed with the correct wallet loaded (the one where descriptor had been imported). It may be easier to do it within Bitcoin Core GUI console.

I verified all in Bitcoin Core versions 24 and 25 where the "DEFAULT" argument is accepted.

Do you also have the wallet containing the "tb1p8wp...." address?
I believe this error thrown because when you "sign with wallet" it has to have the address and the scripts used to create that address otherwise it doesn't know what to do and it gives you this error when it is missing the required "witnessScript".

This command:

./bitcoin-cli.exe -testnet signrawtransactionwithwallet "02000000012164dff98653ce57c1a35c581caa993f526a118bf54e3138f04ade3aed19df8c00000 00000fdffffff01e8030000000000002251202befa14431d4cb71889ea1df7a7eaa2f1d8b9107e6 0b01564e15dabe5c0dfd3200000000" '[{"txid": "8cdf19ed3ade4af038314ef58b116a523f99aa1c585ca3c157ce5386f9df6421", "vout": 0, "scriptPubKey": "5120c38859777bc9c3294d3587035fc3823a146dabaab1fa250bc04e92f16887a065", "amount": 0.00000000}]' "DEFAULT"

At least in mainnet will output something like this:

"complete": false,
       "error": "Witness program was passed an empty witness"

Can you test it on mainnet and see?

Even the syntax of the command is not well done, the last parameter "DEFAULT" don't exist, here is the right syntax of it:

Argument #3 - sighashtype
Type: string, optional, default=ALL

The signature hash type. Must be one of
“ALL” “NONE” “SINGLE” “ALL|ANYONECANPAY” “NONE|ANYONECANPAY” “SINGLE|ANYONECANPAY”


If you want to use the default value you need to put ALL and not DEFAULT, some beginner made that.

I did both testnet and mainnet. There are the instructions (the step-by-step example of spending from the tb1p8wpt9v4frpf3tkn0srd97pksgsxc5hs52lafxwru9kgeephvs7rqlqt9zj Taproot address to the other Taproot one: tb1p90h6z3p36n9hrzy7580h5l429uwchyg8uc9sz4jwzhdtuhqdl5eqmpwq6n; you can add the change and the corresponding address by modifying the createrawtransaction RPC in the example; remove "-testnet" option if you want mainnet):

Source: "https://bitcoin.stackexchange.com/a/117013/135945".

Is that what you are looking for?

Maybe in testnet, have you tried yourself in mainnet to see if it works?
I think you will be surprised.

The process of sending money from a Taproot wallet in Bitcoin Core to another taproot address is exactly the same as sending from any other kind of wallet.

This guy has already created step by step instructions of commands that you need to run to make it work: https://stackoverflow.com/questions/38493893/heres-how-to-send-raw-transaction-btc-using-bitcoin-cli-command

Transactions inputs are specified with UTXOs, so there's no need to specify the addresses themselves directly in the inputs.

Google it,    https://bitcoin.stackexchange.com/questions/107452/how-can-i-spend-from-a-p2tr-address-on-signet-with-the-bitcoin-core-wallet-in-22?rq=1

Hi guys,

I'm starting this topic after googling a lot about this and don't find nothing.

So, I'm offering a prize of €50 in Lightning Satoshis to the first guy that presents the solution, a step by step guide to move some part of the sats from one taproot address to another taproot address with the change coming back for the first one on mainnet.

This need to be done with node bitcoin-cli commands and explained step-by-step  for any newbie in the world that uses a bitcoin node could do it.

Until now I just met guys with nodes that can't do it, I think is time for everyone knows how to use it.

More questions you can send me PM.

PS: "Let's lead the way and show the light of day."