Chapter 5 of learning bitcoin from the command line is about transactions that get stuck, usually because too low of a fee. I’m going to do a side tangent today of learning as much as I can about tx replacement, rather than blowing through the chapter.
mattoshi
mattoshi@stacker.news
npub1hylk...76k4
Worked through the first 4 chapters of Learning bitcoin from the command line (https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line). I couldn’t figure out setting up a node on Linode, so just ram bitcoin locally on regtest. Overall, the chapters were good and I learned a bunch, though were some parts that were a little rough and out of date. Keeping guides/docs up to date is super hard, especially when they are for free. I think there will be a large bitcoin technical teaching industry in 5-10 years
Having a party at my apartment tonight. The goal is to not bring up bitcoin unless someone asks. And if they do, be encouraging but not too crazy sounding. After a few drinks this gets very hard
Stay curious
Some bomb tacos 

It looks like swan and river both offer only recurring buys, rather than direct deposit. Recurring buys just don’t hit the same as direct deposit. I think I will wait until Strike is back to operational for DD rather than switch.
Damn. I loved direct deposit with strike. I could withdraw instantly. Guess I will try to set up with river. 

Second one much better. Proper ratio and the water to dissolve 

Drinking an old fashioned for my back pain. Messed it up though and didn’t add water so the sugar didn’t dissolve enough. 

My biggest question was how OP_CHECKMULTISIG matches up the provided signatures with the corresponding public keys. The answer is that it just loops through the public keys and tries to verify the signatures! In my mind I thought there would be some type of mapping. It was also surprising to me that even if you have a threshold of valid signatures, they need to be in the right order.
These resources together did a great job explained the nitty gritty:

P2MS | Pay To Multisig
P2PK (Pay To Multisig) is a locking script that requires multiple signatures from multiple public keys to unlock it.
Bitcoin Stack Exchange
CHECKMULTISIG a worked out example
I was wondering if somebody could point me to or give me a worked out example of how OP_CHECKMULTISIG works behind the curtains?

I expect ...
GitHub
bitcoin/src/script/interpreter.cpp at master · bitcoin/bitcoin
Bitcoin Core integration/staging tree. Contribute to bitcoin/bitcoin development by creating an account on GitHub.
I need to up my multi sig knowledge. Plan of attack
- OP_CHECKMULTISIG
- psbt
- what changed in taproot
- musig
- frost
If anybody has recommendations lmk!
I got this white noise machine and now it feels like I go into another realm when I sleep. Maybe I just wake up less or something. It’s great
#[0] I got 1000 sats on Penn. you in?
Doing some bitcoin today
People do not think critically enough of about their driving. There are so many little things you can do to avoid a bad situation. Stay safe out there friends
Put your zap where your mouth is. Probably should be zapping 10x more than posting imho