Bitcoin VS bips

Ubuntu/Debian: Install LND: https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md#install-lnd Install Bitcoin Core: https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md#linux-instructions

To be able to follow along, you must have both bitcoind and lnd installed.

As mentioned previously, ScriptPubKeys are scripts that embody the locking conditions of bitcoins in a Bitcoin transaction. They are a crucial element of a Bitcoin transaction that specifies the requirements that must be met before an unspent transaction output (UTXO) is used. The ScriptPubKey, combined with the Amount, creates an output of a Bitcoin transaction. Like every other script, ScriptPubKeys are made up of operators and data. During the encoding of a transaction, both data and the operands are represented in hexadecimal format. You can find the hex representation for all operands used in Bitcoin Scripts here.

Here are the release notes: https://github.com/bitcoin/bitcoin/blob/26.x/doc/release-not...

It's blatantly false that "Bitcoin Core was purchased by Blockstream".

It's absolutely not the case. It's more like a conspiracy theory that keeps getting pushed into Bitcoin-related threads at Hacker news (maybe to tilt future analysis?)

If we take a look at the past month of commits from https://github.com/bitcoin/bitcoin/pulse/monthly, the top ten authors are:

- MarcoFalke (ChainCode)

Fun ZeroMQ fact: bitcoind has used zeromq since 2015. This is used by client software including lightning node daemons to get notification of incoming transactions and blocks in a highly reliable and rapid way.

https://github.com/bitcoin/bitcoin/blob/master/doc/zmq.md

I like how the insight can show what exactly been done over time..https://github.com/bitcoin/bitcoin/graphs/contributors

I found this discussion and the OP appeared to gain access when using the version of core from the time the wallet.dat backup was created/encrypted: https://github.com/bitcoin/bitcoin/issues/14461

Bitcoin transactions involve locking funds in scripts, which can only be spent if those locking conditions are met. The part of the script that expresses these locking conditions are called ScriptPubKeys. On the other hand, the part that provides unlocking scripts to satisfy the locking conditions is referred to as ScriptSig for legacy transactions, and ScriptWitness for SegWit Transactions. These scripts are evaluated by a stack-based language called Script. This article will mainly focus on ScriptPubKeys.

The purpose of Bitcoin was not to create a means to keep your wealth in your memory. Seed phrases were proposed and implemented 4 years after Bitcoin’s release in BIP-39.

BIP101 doubles every 2 years with linear interpolation. If we used that, the block size limit as of a couple minutes ago would have been 188,938,289 bytes. That's pretty close to what I think the safe limit actually is right now.

This is a variation of the above but where nodes would accept to automatically execute some adjustment in their consensus-sensitive policies, and in response to coinbase or block header messages. Notable proposal of this category was BIP-0105, and the idea resurfaced in a recent discussion with zawy.

Reference python implementation straight from the BIP https://github.com/bitcoin/bips/blob/master/bip-0340/referen...

I am trying to learn more about the best practices and tools to backup the Bitcoin Secure Multisig Setup (BSMS). When you create a multisig wallet, the coordinator app usually creates a .bsms file with all the descriptors to recreate the wallet. This is described on BIP129: https://github.com/bitcoin/bips/blob/master/bip-0129.mediawiki But having access to that file reveals the funds of the multisig wallet, so I think is not a good idea to store it in plain text. It should at least be encrypted so you can decide who can access it. Splitting the BSMS content into multiple QRs shares would be ideal, so you can distribute each share in different locations.