From: "t. khan" <teekhan42@gmail•com>
To: Luke Dashjr <luke@dashjr•org>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Pre-BIP] Community Consensus Voting System
Date: Sat, 4 Feb 2017 17:02:00 -0500 [thread overview]
Message-ID: <CAGCNRJp6vpqqaf8=8CwPP6iXB6UULWh8Kezw2i-2GfLn3b1bxg@mail.gmail.com> (raw)
In-Reply-To: <201702030024.10232.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]
On Thu, Feb 2, 2017 at 7:24 PM, Luke Dashjr <luke@dashjr•org> wrote:
> Strongly disagree with buying "votes", or portraying open standards as a
> voting process. Also, this depends on address reuse, so it's fundamentally
> flawed in design.
>
The point of this is it's available right now. It's not ideal, but it will
work. It doesn't require any code and we can do it today.
In case you haven't been paying attention; there's already enough support
for Unlimited to prevent SegWit from ever being adopted. Without
significant community outreach (which is the purpose of the CCVS) and a
compelling solution to max block size, Core as a product is dead.
Also, you need to be pretty paranoid to believe that address reuse is an
issue in this situation.
Note also that the BIP process already has BIP Comments for leaving textual
> opinions on the BIP unrelated to stake. See BIP 2 for details on that.
>
This does nothing for the community in general. Plus there's no way to
measure that sort of feedback.
- t.k.
[-- Attachment #2: Type: text/html, Size: 1615 bytes --]
prev parent reply other threads:[~2017-02-04 22:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 19:39 t. khan
2017-02-02 23:19 ` David Vorick
2017-02-03 0:24 ` Luke Dashjr
2017-02-03 1:32 ` Dave Scotese
2017-02-03 16:19 ` alp alp
2017-02-03 18:20 ` t. khan
2017-02-03 19:22 ` alp alp
2017-02-04 21:23 ` t. khan
2017-02-04 0:57 ` Chris Priest
2017-02-11 15:57 ` Staf Verhaegen
2017-02-14 12:33 ` Peter Todd
2017-02-04 22:02 ` t. khan [this message]
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='CAGCNRJp6vpqqaf8=8CwPP6iXB6UULWh8Kezw2i-2GfLn3b1bxg@mail.gmail.com' \
--to=teekhan42@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=luke@dashjr$(echo .)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