From: Oliver Petruzel <opetruzel@gmail.com>
To: Simon Liu <simon@bitcartel.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP 100 specification
Date: Thu, 3 Sep 2015 16:15:58 -0400 [thread overview]
Message-ID: <CALhpmH0POEpJtAXPZdo92onCoiRFx6EwvNs=xpy-49_jRXgBHw@mail.gmail.com> (raw)
In-Reply-To: <55E8A246.7030102@bitcartel.com>
[-- Attachment #1: Type: text/plain, Size: 2207 bytes --]
I agree with Simon's sentiments for question #1, and was actually going to
pose the same question. Non-votes seem like they may poison the well
mathematically, and counting them anyway seems to encourage a lack of
participation at a time when miners really need to be very much involved.
Since we're handing them even more control over the ecosystem with this
BIP, it would be nice to ensure they (all miners) seriously consider their
impact and role on a regular basis.
I'm curious why we couldn't/shouldn't simply drop the non-votes. (There may
be a great reason that I can't think of, but it's eluding me... LOL)
That said, I don't see any issue with counting votes from outside of the
range as the maximum/minimum accordingly (Simon's question #2). In fact,
such votes would be very interesting (worthy of further discussion) if they
begin to lean heavily in either direction.
V/r,
Oliver
On Sep 3, 2015 3:41 PM, "Simon Liu via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hi Jeff,
>
> Thoughts on this part of the proposal:
>
> "Absent/invalid votes are counted as votes for the current hardLimit.
> Out of range votes are counted as the nearest in-range value."
>
> 1. Why should an absent vote be considered a vote for the status quo? A
> non-voter should have zero impact on the result.
>
> 2. Why should out of range votes be counted? They're an invalid vote, a
> spoiled ballot as such, and thus it would be better if they were discarded.
>
> Regards,
> Simon
>
>
> On 09/02/2015 08:33 PM, Jeff Garzik via bitcoin-dev wrote:
> > BIP 100 initial public
> > draft: https://github.com/jgarzik/bip100/blob/master/bip-0100.mediawiki
> >
> > Emphasis on "initial" This is a starting point for the usual open
> > source feedback/iteration cycle, not an endpoint that Must Be This Way.
> >
> >
> >
> >
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 3193 bytes --]
next prev parent reply other threads:[~2015-09-03 20:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 3:33 [bitcoin-dev] BIP 100 specification Jeff Garzik
2015-09-03 4:45 ` Dave Scotese
2015-09-03 7:57 ` jl2012
2015-09-03 11:20 ` Btc Drak
2015-09-03 14:34 ` Jeff Garzik
2015-09-03 15:58 ` Btc Drak
2015-09-03 16:13 ` Jorge Timón
2015-09-03 11:59 ` Tier Nolan
2015-09-03 16:32 ` jl2012
2015-09-03 16:35 ` Jeff Garzik
2015-09-03 17:32 ` Btc Drak
2015-09-03 17:52 ` Peter Todd
2015-09-04 7:53 ` Andy Chase
2015-09-04 15:37 ` Simon Liu
2015-09-04 15:40 ` Btc Drak
2015-09-03 14:35 ` Jeff Garzik
2015-09-03 19:40 ` Simon Liu
2015-09-03 20:15 ` Oliver Petruzel [this message]
2015-09-03 20:34 ` Dave Scotese
2015-09-04 3:50 ` Peter Todd
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='CALhpmH0POEpJtAXPZdo92onCoiRFx6EwvNs=xpy-49_jRXgBHw@mail.gmail.com' \
--to=opetruzel@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=simon@bitcartel.com \
/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