Detail Pow consensus patch ideas
Miners need to mine a patch into the code onto the chain, it only becomes consensus when a super majority adds the patch to their code base, it’s all opt in.
Threats of Violence
Summary of history of threats against big blockers such as Bitcoin XT hard fork support getting Coinbase delisted from Bitcoin Core supporter sites, DDOSing or miners running Bitcoin XT, etc
To prevent threatening miners with DDoS attempts or other threats of violence, it is hidden as to which patches miners have opted into/want merged into consensus. They will only be revealed after a super majority has been reached.
Implementation ideas
- EBPF/WASM modules for Consensus
- Split different sections of the bitcoin node such as policy, consensus, transaction formats etc into separate modules which all can be overridden by miners.
- How miners get their code, whether they outsource the development, open source their code base or develop everything in house is left up to the miner
- The rest of the network will still follow Satoshis vision
When a patch is created, it runs on an internal side chain that never gets published. This allows miners to test their patches in production in an AB-Testing like environment.
Eg. When a transaction comes in, the miner will process it with the current transaction rules and in the background, it will be processed with the patched rules, aggregate into some metrics that miners can get feedback on and adjust the patch before it’s ready for prime time.