- Describe BIP152 compact block relay
- Describe why we still need relay networks (what they do that BIP152
can't)
- Drop FALCON relay (never used, AFAIK)
- Minor updates to relay section
- Remove images: these are incorrect and (IMO) not very useful. The
first image is a legend. The second image contains multiple errors or
confusions, such as implying that a miner needs a full copy of the
block chain or that a wallet is a routing node. The third image is a
very busy depiction of a network showing that clients connect to
nodes, which I think is fine to just say in the text.
- Revise text to not reference images.
- Maintain distinction between nodes and peers by not using terms "full
node client" or "SPV node"
- Update the count of reachable nodes
- Remove some dead full node implementations
- We revise sentence about equality among peers to make it clear that
the peers are full nodes. Clients are not peers of a full node.
- Remove clause about "reciprocity" being the incentive for
participation. I think there are varied reasons for operating a full
node, ranging from wanting to validate your own transactions
(requiring only a pruning full node) to wanting to keep mining
decentralized (e.g. by relaying transactions).
- Drop line about non-Bitcoin-P2P protocols being "extended Bitcoin
network". I think that's an unnecessary categorization.
- New introduction to fees
- More detail about how the fee market works
- Adds RBF and CPFP fee bumping
- Adds transaction pinning
- Adds package relay
- Adds CPFP carve out
- Small edits to 'Adding fees'
- Tiny edits to fee sniping
- "Ephemeral key pair" -> nonce; makes it consistent with schnorr
section and better composes with section about avoiding nonce reuse
- Changed variables to be consistent with schnorr section
Bitcoin can do things beyond money, but (as other text in the chapter
notes) this can be controversial. Let's not oversell those other uses
here only to throw shade on them later.
I think this is an overabundance of detail (and I'm not sure it's
correct about a 40-byte release; I think that may have been changed in
the RC phase).
There has also been recent (March 2023) discussion about making this
limit arbitrarily high, so this is something that might become outdated
quickly.
