public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Sancho Panza <sanch0panza@protonmail.com>
To: Thomas Voegtlin <thomasv@electrum.org>
Cc: "bitcoin-dev@lists.linuxfoundation.org"
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proposal: Soft Fork Threshold Signaling
Date: Thu, 13 Apr 2017 12:35:41 -0400	[thread overview]
Message-ID: <7uA8OvV5lg5Ug8_x4i6kdl9mUk7uNNa04cOc74tWIDBLA7zNNLZ3FOdML0bMoOBUMggpvXyWESZOuX-Sa21J-uZyWnujBLAEtKpsLwTwTSM=@protonmail.com> (raw)
In-Reply-To: <319af712-7d95-d496-55d9-d3ce16e1d075@electrum.org>

[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]

> However, my point is that the threshold should be [...] not fixed in the soft-fork proposal

My proposal makes it configurable (as well as window size, grace period etc.)

> I agree that coinbase space might be a limitation.

I still like the coinbase idea though - more than using up the BIP9 versionbits range for verbose signaling.

BIP9 (and other proposals which use those 29 versionbits) currently assume that the participants on the network will coordinate in some form or other, to agree on what the bits mean (in terms of change deployments).

It would be very easy to also agree on a set of "standard" threshold levels and map those onto e.g. 1 byte.

Then, in the coinbase, one could have pairs of bit numbers and bytes, e.g. "/1A/2B/3C/" where the bytes values corresponding to 'A', 'B', 'C', ... are standardized deployment schedules that people find useful.
So a BIP9 conformant schedule could be A = 95% / 2016 window,
while B = 75%/2016, etc.

This would be quite a compact yet still readable signaling. The space of values is large enough that I doubt we'd see much contention.

Regards
Sancho

[-- Attachment #2: Type: text/html, Size: 1408 bytes --]

  reply	other threads:[~2017-04-13 16:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13 11:36 [bitcoin-dev] Proposal: Soft Fork Threshold Signaling Thomas Voegtlin
2017-04-13 14:17 ` Sancho Panza
2017-04-13 14:55   ` Thomas Voegtlin
2017-04-13 16:35     ` Sancho Panza [this message]
2017-04-13 17:30       ` Thomas Voegtlin

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='7uA8OvV5lg5Ug8_x4i6kdl9mUk7uNNa04cOc74tWIDBLA7zNNLZ3FOdML0bMoOBUMggpvXyWESZOuX-Sa21J-uZyWnujBLAEtKpsLwTwTSM=@protonmail.com' \
    --to=sanch0panza@protonmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=thomasv@electrum.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