Good morning all,
As other explained, your scheme is broken.
Unless we have a softfork first (OP_CHECKBIP9VERIFY: payment is valid only if a
BIP9 proposal is active), it is not possible to create a softfork bounty in a
decentralised way
On the other hand, hardfork bounty is very simple. You
As other explained, your scheme is broken.
Unless we have a softfork first (OP_CHECKBIP9VERIFY: payment is valid only if a
BIP9 proposal is active), it is not possible to create a softfork bounty in a
decentralised way
On the other hand, hardfork bounty is very simple. You just need to make
On 27/04/17 18:48, Matt Bell via bitcoin-dev wrote:
* No outputs, all funds are paid to the miner
A transaction _must_ have at least one output [1]. You can get the same
effect by adding a 0 satoshis OP_RETURN output.
[1]:
>
> 2B. If Segwit has not activated at height H, Input 1 of the Bounty Payout
> is not valid since it spends a P2WPKH output, preventing the miner from
> including the Bounty Payout transaction in the block. (However, the output
> of the Segwit Assertion tx can be claimed since it is treated as
>
>
> 2B. If Segwit has not activated at height H, Input 1 of the Bounty Payout
> is not valid since it spends a P2WPKH output
>
If SegWit has not activated at height H, P2WPKH is an "anyone can spend"
output.
SegWit is a soft fork, all SegWit transactions must be interpreted as valid
by old nodes.
