From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] BIP: Block signal enforcement via tx fees
Date: Fri, 12 May 2017 19:22:56 +0000 [thread overview]
Message-ID: <201705121922.57445.luke@dashjr.org> (raw)
I've written a new BIP draft for OP_CHECKBLOCKVERSION to allow the community
to put economic pressure on miners to deploy softforks without the extreme of
a UASF.
https://github.com/luke-jr/bips/blob/bip-cbv/bip-cbv.mediawiki
Due to the potential for miners to maliciously block this softfork, it is
suggested that we deploy it using BIP 8 to ensure it eventually activates even
if encountering hostility.
This is intended to be an alternative to BIP 8 in the long term.
It is NOT intended to make BIP 148 obsolete, given the timeframes involved.
An implementation is available (based on top of BIP 115's implementation):
https://github.com/luke-jr/bitcoin/compare/cbah...luke-jr:checkblockversion
Luke
next reply other threads:[~2017-05-12 19:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 19:22 Luke Dashjr [this message]
2017-05-12 22:17 ` [bitcoin-dev] BIP: Block signal enforcement via tx fees ZmnSCPxj
2017-05-12 22:22 ` Peter Todd
2017-05-13 0:49 ` Luke Dashjr
2017-05-13 3:26 ` Eric Voskuil
2017-05-13 3:54 ` ZmnSCPxj
2017-05-13 5:36 ` Eric Voskuil
2017-05-13 5:45 ` Luke Dashjr
2017-05-13 6:43 ` Eric Voskuil
2017-05-13 12:48 ` Peter Todd
2017-05-13 16:42 ` Luke Dashjr
2017-05-13 4:23 ` Russell O'Connor
2017-05-13 5:26 ` Luke Dashjr
2017-05-13 17:11 ` Russell O'Connor
2017-05-15 1:14 ` Rusty Russell
2017-05-20 5:05 ` Anthony Towns
2017-05-14 12:18 ` 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=201705121922.57445.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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