From: Alex Mizrahi <alex.mizrahi@gmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Trustless Segwit activation bounty protocol (aka. bribing the miners)
Date: Thu, 27 Apr 2017 21:41:17 +0300 [thread overview]
Message-ID: <CAE28kUTQtU17W4xbSgOKvpBWCppoZS1B+iBs_JUAd6nYe=hcgw@mail.gmail.com> (raw)
In-Reply-To: <CACV3+OU3wT6ZZ+ffUOEXpnmu9p0kf42fEBv3fPxnGPJ88BVwAg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
>
> 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
> anyone-can-spend, although this is not an issue since it is a very small
> amount).
>
It's a small amount by itself, but miners who are aware of Bounty Payout
Transaction will try to include both these transactions (and both are valid
both on SW and non-SW chains by definition of SW being a soft fork).
If you set timelock of BPT to (H+1) then you sort of discourage this
behavior because a miner of block H might be not the same as miner of block
(H+1), thus he cannot grab this bounty for sure.
Still, there is a chance that same miner will mine both blocks, so
game-theoretically it makes sense to insert SAT into your block since your
expected payoff is positive.
So I'm afraid miners will just grab these bounties regardless of segwit
activation.
[-- Attachment #2: Type: text/html, Size: 1374 bytes --]
next prev parent reply other threads:[~2017-04-27 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 17:48 Matt Bell
2017-04-27 18:25 ` Alex Mizrahi
2017-04-27 18:41 ` Alex Mizrahi [this message]
2017-04-27 19:45 ` Antoine Le Calvez
2017-04-27 20:10 ` Johnson Lau
2017-04-27 21:05 ` ZmnSCPxj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE28kUTQtU17W4xbSgOKvpBWCppoZS1B+iBs_JUAd6nYe=hcgw@mail.gmail.com' \
--to=alex.mizrahi@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox