Deterministic tx selection for censorship resistance

[ajtowns]

@mcelrath

What is the motivation for doing this? Every tx included this way needs to be transmitted and validated with every share-chain block, so possibly as fast as every 250ms.

Providing an escape hatch for txs to be mined outside of policy, eg RSK’s recovery txs, and to provide a way for pool members to support off-chain tx acceleration without requiring a central coordinator. (Perhaps it would be possible to do off-chain acceleration by revoking unredeemed pool shares though?)

@mcelrath

Braidpool will need to have its own tx acceptance rules (yet to be determined), which will fall somewhere between Bitcoin’s P2P rules and Bitcoin’s block rules,

If Braidpool were to be successful (>30% hashrate?), I’d expect bitcoin core’s relay policy to match braidpool’s (well, probably with a larger backlog) to minimise divergence between actual blocks and expected blocks (ref).