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 10:17:59 -0400	[thread overview]
Message-ID: <4TcKFXkLsQaPwHnC7YdEyVnmeMWN9KFx1HriXCYsScr4t4QotNpiUr61XFVzEKicFfQzc3iF_N4wo6qKbi6xanv_GZTFTCQ0DQnYHh_WukY=@protonmail.com> (raw)
In-Reply-To: <0a38c993-9269-efb5-7790-e49cd4f7987f@electrum.org>

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

Thomas,

I wonder if you've seen my proposal on how to make BIP9 more configurable:
https://github.com/sanch0panza/bips/blob/bip-genvbvoting/bip-genvbvoting.mediawiki

This could be extended with a coinbase signaling feature as you suggest.
This could include parameter information for forks which a miner is signaling, for coordination.

Currently I've not included something like this, but it might make a nice addition.
One problem is the limited space in coinbase for embedding data on the large number of possible independent deployments.

Regards,
Sancho

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

  reply	other threads:[~2017-04-13 14:18 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 [this message]
2017-04-13 14:55   ` Thomas Voegtlin
2017-04-13 16:35     ` Sancho Panza
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='4TcKFXkLsQaPwHnC7YdEyVnmeMWN9KFx1HriXCYsScr4t4QotNpiUr61XFVzEKicFfQzc3iF_N4wo6qKbi6xanv_GZTFTCQ0DQnYHh_WukY=@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