flywithu/Learning-Bitcoin-from-the-Command-Line
1
1
Fork 0
mirror of https://github.com/ChristopherA/Learning-Bitcoin-from-the-Command-Line.git synced 2026-02-16 22:22:58 +00:00
Code Issues Releases Wiki Activity
Learning-Bitcoin-from-the-C.../TODO.md
Shannon Appelcline 144538cca5
Update TODO.md
2026-01-15 15:06:48 -10:00

11 KiB
Raw Blame History

Todo List for v3.0 of Learning Bitcoin

The following TODO items are intended for a 3.0 version of Learning Bitcoin from the Command Line

Medium-Scale Updates

The following updates involve updates or the creation of new chapters, but their additions are generally bounded and known.

  1. General Update: Consider replacing testnet with signet
  2. Big changes to defaults
  3. New Interlude: Creating QR Codes (after 3.3)
    • New Subsection: Creating a QR
    • New Subsection: Creating a Quick Connect QR
  4. Revise Section: Understanding the Descriptor (3.5)
    • New Content: Descriptor Wallets
    • Possibly also remove legacy wallets (3.3) and replace them entire with descriptors
    • New Content: Complex Descriptors
    • Consider: Breaking into Two Sections
  5. New Interlude: Creating Animated QR Codes (after 7.1)
    • New Subsection: Understanding Uniform Resources
    • New Subsection: Creating an Animated QR
    • New Subsection: Creating an Animated QR of a PSBT
  6. New Chapter: Using Other Command-Line Tools (between 8+9)
    • 9.1: Using seedtool
    • 9.2: Using keytool
    • 9.3: Using bytewords-cli
  7. Revise Section: Understanding Timelock Options (11.1)
  8. New Chapter: Using Miniscript Command-Line Tools (between 13+14)
    • 15.1: Using miniscript
    • 15.2: Using Bitcoin Dev Kit (BDK)
    • 15.3: Planning for the Future
  9. New Content: Expand the PSBT Libwally Content (17.4) into Two Sections
    • 17.4: Signing PSBTs in Libwally
      • Explanation: Contains the current info on importing a PSBT, and shows how to sign it
    • 17.5: Creating PSBTs in Libwally
      • Explanation: Contains the current info on creating a PSBT, and shows how to export it
  10. New Chapter: Talking to Bitcoind with Swift (between 17+18)
    • 19.1: Accessing Bitcoind with Swift (existing section)
    • 19.2: Using Swift with Bitcoin Lib [Wolf's library]
    • 19.3: Using Swift with Libwally [Wolf's shim]

Large-Scale Updates

The following updates involve the large-scale work done on Schnorr and Taproot in Bitcoin Core 0.21 and 22. This represents a first cut at how to layout the work, but revision and expansion will likely be needed as everyone's understanding of these new technologies matures.

Chapter X: Expanding Bitcoin Transactions with Schnorr (probably between chapters 6+7)

  • New Section X.1: Understanding Schnorr Signatures
    • New Subsection: Understanding the Math of Schnorr
      • Explanation: Add + subtract for one signature
    • New Subsection: Supporting MuSig
    • New Subsection: Understanding the Use of Adapter Signatures
    • New Subsection: Knowing the Advantages of Schnorr
      • Explanation: size, 64 bytes vs 72, better for multisigs
      • Explanation: speed, linear, validate a million-sig multisig in 2 minutes
      • Explanation: privacy, no difference between MuSig and sig, no detection of Lightning
      • Explanation: also better security, non-malleability
      • Reference: https://github.com/bitcoin/bips/blob/master/bip-0340.mediawiki
  • New Section X.2: Using Schnorr Signatures
    • New Subsection: Signing with Schnorr
    • New Subsection: Adding a Schnorr Signature
    • New Subsection: Reading a Schnorr Signature
    • New Subsection: Using Schnorr with Taproot
  • Update Chapter 6 (Multisigs) to Integrate with Schnorr

Chapter Y: Improving Bitcoin Scripts with Taproot (probably between chapters 13+14, possibly expanding to two chapters)

  • New Section Y.1: Understanding MAST
  • New Section Y.2: Understanding Taproot
  • New Subsection Y.3: Creating a Taproot Script
    • New Subsection: Defining a Taproot Script
      • Explanation: Segwit v1, 32-byte program, not P2SH wrapped, leaf version is 0xc0
    • New Codes: OP_CHECKSIGADD and OP_SUCCESS
    • Cut Codes: OP_CHECKMULTISIG and OP_CHECKMULTISIGVERIFY
    • Reference: https://twitter.com/pwuille/status/1459778730369368067
  • New Subsection Y.4: Importing a tr Desciptor
  • New Subsection Y.5: Using Taproot in Practice
    • New Subsection: Making a Taproot Payment
    • New Subsection: Validating a Taproot Script
  • Update Chapter 9 to Integrate with Taproot
    • Mention Taproot in 9.1 or 9.2
    • Add New Section 9.6: Scripting a P2TR (mostly a pointer to Chapter Y)

Further Updates

The following updates could be part of v3.0 or could be further future, depending on interest and funding.

  1. New Graphics: Animated GIFs for key demos.
  2. New Chapter: Talking to Lightningd with C (after chapter 20)

--

Listing of Updates

Legacy Updates

  • Segwit
    • Segwit is now old enough that we should teach it as the default. That means that sections 3.1-4.5 should be rewritten to use Segwit as the default and 4.6 should be removed (with perhaps a bit of the information about the different types of addresses being preserved).
    • It's possible that the same should occur with 10.5, but it should first be reviewed to see if it's a meaningful building block in the scripting process (or not).
  • Signet
  • Descriptor Wallets
  • Fees
    • There was some question of if mintxfee is still current, or if paytxfee should be used. I haven't seen any evidence of obsolence, but it'd be good to check this and make sure we're still on the best practices.
    • This is discussed in 4.1

27.0 Updates

  • v2 transport becomes default

26.0 Updates

  • v2 transport update

25.0 Updates

See Bitcoin Mag and release notes

  • args parameter for RPC

24.0 Updates

See Bitcoin Mag and release notes

  • Miniscript
  • sendall RPC
  • RBF is now default

23.0 Updates

See also #575 and of course the Bitcoin Core 23.0 release notes.

  • Schnorr & Taproot
    • Obviously, the biggest update. We'll need to teach the basics of both and why they're exciting. The main question here is: what commands actually take advantage of Schnorr & Taproot, and how can we show this off.
    • If there's just a little bit of functionality right now, it can go into chapter 8, probably in two new sections: 8.3 & 8.4, on Schnorr and Taproot. If there's already a lot of functionality, it should go into its own chapter, and 8 (and everything beyond it) should be shifted back.
  • Descriptor Wallets
    • Descriptor wallets are now the default. There's some unfortunate lack of integration with multisigs, but we should otherwise give them more attention. What can we do new about inputting and outputting descriptor wallets? Are there any other functions of note?
    • This will likely go in 3.5, though it's possible it go split into two chapters: Understanding the Descriptor and Understanding the Descriptor Wallet. See the 0.21 release notes at the bottom for everything about Descriptor Wallets. But note that we explicitly turn them off in 3.2, so any discussions explicitly about descriptor wallets will require creating a new wallet for that purpose
  • Freezing Coins
    • This is an interesting new ability that allows you to prevent UTXOs from being automatically selected when transactions are created.
    • This would probably fit well into 4.5 as a final header-section.
  • CJDNS Network
    • I'm not familiar with CJDNS, but it sounds like a privacy option that would fit in with Tor and i2p
    • If that's correctly, this would be a good 15.2, with the 15.0 chapter renamed "Using Other Privacy Options" or something like that
  • RPC Changes
    • The following RPC commands have had changes to their output and any examples should be rerun. If they are part of a sequence of commands (e.g., building out a transaction), then the whole sequence should be rerun.
    • createmultisig,
    • addmultisigaddress,
    • listunspent,
    • getblockchaininfo
    • Updated RPCs may or may not exist in the text. The best way to find out is to search.

22.0 Updates

See release notes.

  • New External Signer Commands
  • RPC Changes
    • Again, these commands should be reoutput.
    • getpeerinfo,
    • gettxout,
    • getrawtransaction,
    • decoderawtransaction,
    • decodescript,
    • getnodeaddresses

0.21.0 Updates

See release notes.

  • Signet
    • Signet is considered more controlled and reliable than testnet, and so should be used as our test network, along with an explanation of what it is and how it differs from other networks.
    • The setup and explanation of networks appears in 3.1. That should be changed, and with the change of the alias there, we should mostly be used Signet. Then the rest of the course can be searched for any references to testnet.
  • RPC Changes
    • As usual, these may or may not be used, but if they are, outputs should be redone.
    • getnetworkinfo