I was able to find my RBF answer here
https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line/blob/master/05_2_Resending_a_Transaction_with_RBF.md

But do I need a sequence for each input? If I have 4 inputs, do I need 4 sequence fields?

Thank you!
I ran the help for createrawtransaction and I see what you're saying about the sequence field. I also see it references locktime and replaceable fields. Replaceable seems like it would need to be set to True to turn on RBF, correct?

For the sequence number, it can be anything as long as it's lower than 4294967293? (and lol where does that number come from? Now I am curious AF)

Hi all,
I have 2 unrelated questions, but both about how to properly formulate a transaction template.

1. I'd like to know how to add an RBF indicator to the transaction (and any relevant details).

2. I'd like to know how to create a taproot transaction template I can use

Here's my current standard raw transaction template I use;


If there are any resources you can point me to, please let me know.

The software I am using to create, sign, and send transactions is Bitcoin Core QT (console)

Intriguing, what makes someone a full member? What kind of member am I?

I get the same error...now y'all have me curious!

This is all super info, really appreciate it!!!

I...understand. And I appreciate your help and guidance.

I have created a transaction with some null data and it sends fine on testnet, but on mainnet I am getting and error scriptpubkey (code -26)

I did some searching this seems to be an error for a non-standard transaction, but I don't see anything in the Debug log showing why the error.

Using Bitcoin Core QT GUI Console 0.20.1
Windows 10

This is the Transaction template


This is the data I want to include
492c204672616374616c456e6372797074206365727469667920746861742074686520426974636 f696e2046756c6c204e6f6465205363756c707475726520342e3020776173206372656174656420 6f6e204a616e7561727920332c203230323120746f20636f6d6d656d6f726174652074686520313 2207965617220616e6e6976657273617279206f66205361746f736869206d696e696e6720746865 2047656e6573697320426c6f636b2e205468697320434f41207761732063726561746564206f6e2 04a616e7561727920382c203230323120746f20636f6d6d656d6f726174652074686520616e6e69 76657273617279206f6620746865206d696e696e67206f6620426c6f636b20312e0a

Here's the testnet transaction with this data included
https://live.blockcypher.com/btc-testnet/tx/04e4a0d8cdaba44bf34525d361b15e7ffdc69d2e12f4f3d3b3e1ae0e31b394ed/

#1
This worked perfectly,
#2
I love you
# 3
I think you're the coolest!

I am trying to create a transaction using this as my template here (I'm using Bitcoin Core 0.20.1 testnet)

Awesome, thanks! makes perfect sense, and whoops, yes labelled

Thanks!
now I get this...
mrLuuW2hwraLWa3tSjTde9e25xuCk2xyvQ

if I make it say this in the conf;
addresstype=bech32
changetype=bech32

I get this
n2HaJyTFXbBGABtyi5puhCQS6NFw4SxKyB


if I change .CONF to;
addresstype=p2sh-segwit
changetype=p2sh-segwit

I get this;
mmwKf8knfPpFodAcxxMd3dghzLHiNkqCXX

what's the difference between these and the tb1 addresses (and the "2" addresses)?

Wow shit just got exciting!

I have a question about generating new addresses in Bitcoin QT on testnet.

Questions:
1. Can I generate 10 addresses at a time, if so, what's the command?

2. Why can I only create Testnet P2SH addresses in the console?
(when I click the "Create New Receiving Address" button in the receive tab of QT, I get a bech32 address, like this; tb1q5h7tk85rjwwap4jsxlje8kl9mfr20c7qghx6qa)



In the console, when I run getnewaddress, I only get P2SH addresses, am I doing something wrong here?
Here are a few commands and the resulting addresses

• 
  getnewaddress "p2sh-segwit"
  2NGQJDo2aAPE8CHGxEc48BJ4S9GzqQujhVF
  
  getnewaddress "legacy"
  2NAoHS6cfN4oVj9tJrmTgbNEjtHpjyW26RZ
  
  getnewaddress "bech32"
  2N3ppZqJdDKQfQKyFxmbLhoiVSzjk6KfybU
  
  getnewaddress ("bech32")
  2N3e1F587BJBPatxThFBt4oyiU3gPr1zos4
  
  getnewaddress '("bech32")'
  2N2VbaEmjmB2rJ49mgZEYRCunAxG727Xj5a

Bitcoin Client Software and Version Number: Testnet Bitcoin Core 0.19.1
Operating System: Windows 10 64-bit
System Hardware Specs: AMD threadripper 2950x 16-core with 32gb memory
Description of Problem: Unable to create bech32 addresses in testnet QT console
Any Related Addresses: None
Any Related Transaction IDs: None
Screenshot of the problem: NA
Log Files from the Bitcoin Client: NA

Wonderful, will test it out! Thanks for the contribution.

I am very embarrassed, just circling back to share the solution for the community (I'm an idiot).

The above workflow works perfectly. My problem was that I had an incorrect "vout" value in one of my inputs. Basically I was trying to spend money I don't have (/facepalm). As soon as I corrected that, everything worked flawlessly.

Here's my multi-wallet.dat file Coinjoin https://live.blockcypher.com/btc-testnet/tx/537d4f9c49e06916c8f74ad53e52c3389f1654f4dec1014e2335c7ad49e268ab/

I am trying to learn the workflow for manual Coinjoins using PSBTs. I was following Andrew Chow's suggestions in a thread on Bitcoin Stack Exchnage here https://bitcoin.stackexchange.com/questions/57253/how-do-i-spend-bitcoins-from-multiple-wallets-in-a-single-transaction/89169#89169 Where he outlines this flow;

    1. Createpsbt (he suggests using walletcreatefundedpsbt)
    2. Have individual users send their PSBTs to coordinator
    3. Coordinator uses joinpsbts to join the separate PSBTs into one
    4. Coordinator sends joined PSBT back to users to sign with walletprocesspsbt
    5. Once all users have signed/processed the joined PSBT, coordinator uses combinepsbt.
    6. Coordinator uses finalizepsbt and then transmits to the network using sendrawtransaction.

 - I am on having an issue between Numbers 5 and 6 above. I can combine the signed PSBTs, but cannot get them to finalize.
 - I am on testnet using Bitcoin Core version v0.19.0.1 (64-bit)
 - I'm using the console in QT
 - I am using multiple wallet.dat files to simulate different CoinJoin participants. 
 - I've created 2 PSBTs from two separate wallet.dat files, and am able to join them together using joinpsbts

Once I have my joined PSBTs, I was able to sign my PSBT in each wallet, and then combine them into one PSBT using combinepsbt.

When I try to finalizepsbt, I get a return of  "complete": false
I am able to decode the PSBT and view all the correct inputs/outputs, but I must be missing a step to finalize the transaction after combining.

**I believe I need to get finalizepsbt to return a value of true.**


As a sidenote, if I use a single wallet.dat file, I can create multiple PSBTs, join, process, finalize, and send exactly as Andy describes. However when I try to do this in a  more-real-world-situation than "just one user combining his own PSBTs" and then try to combine the PSBTs from different wallet.dat files, then I run into problems (to me, each wallet.dat file = one separate user/Coinjoin participant).

  [1]: https://bitcoin.stackexchange.com/questions/57253/how-do-i-spend-bitcoins-from-multiple-wallets-in-a-single-transaction/89169#89169

Holy moley that did it! THANK YOU! I was messing with this for a long time.

I'm having some trouble with the PSBT workflow on testnet for my first time. I was able to create 2 PSBTs and I can successfully decode them both using decodepsbt but when I try to run joinpsbts I am getting JSON parsing errors.

Help tells me;
joinpsbts ["psbt",...]
Examples:
> bitcoin-cli joinpsbts "psbt"


I have 2 PSBTs, I ran the command, but I must be messing something up...

I have 2 outputs that are basically;
"psbt": "myPSBT1",

and

"psbt": "myPSBT2",
  "complete": true

When I try
> bitcoin-cli joinpsbts "myPSBT1","myPSBT1"

I get;
Error: Error parsing JSON:myPSBT1

Not sure what I am doing wrong, but 1st time, so I'm sure some user error...

EDIT: For clarity, I ran createpsbt and then walletprocesspsbt separately on 2 unique PSBTs. Now I'm having trouble running joinpsbts and/or combinepsbt successfully. Both give the same JSON errors.

Further edit, I used my same 2 original transactions and instead of createpbst, I used walletcreatefundedpsbt and then tried to joinpsbts on those outputs, and no luck either.

Thanks so much for the kind welcome! Crazy to see this come full circle (LOL).

So I ran some simple blockchain analysis on Blockchair, I was looking for (and I believe someone in the thread suggested this) 1000 unique outputs holding exactly 5 BTC (that are still spendable) that were created between July 2014 and April 2015 (I arbitrarily figured these dates may be when WoodCarver would have issued his coins), and I got 630-ish results;
https://blockchair.com/bitcoin/outputs?s=value(desc),time(desc)&q=value(500000000),time(2014-07..2015-04),is_spent(false)#
This means he probably didn't create them during this time, or at least not all of them at once.

Then I ran the numbers back to January, now we have plenty of results, about 1300+ 5 BTC outputs that are still spendable.
https://blockchair.com/bitcoin/outputs?s=value(desc),time(desc)&q=value(500000000),time(2014-01..2015-04),is_spent(false)#

I think we can narrow these results to see if maybe a batch of 1000 was created at once, (via script) it seems that would be the way someone would generate 1000 addresses, or no? Or...in essence we're looking at the funding dates of the addresses, not the creation dates. so how would you think someone would fund 1000 addresses? At once? over time?