From: "t. khan" <teekhan42@gmail•com>
To: alp alp <alp.bitcoin@gmail•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Pre-BIP] Community Consensus Voting System
Date: Sat, 4 Feb 2017 16:23:19 -0500 [thread overview]
Message-ID: <CAGCNRJqJ-9RxMpPg7CTyd_+zn-+eR8gKSLRQjR15p8Ubv5pJbw@mail.gmail.com> (raw)
In-Reply-To: <CAMBsKS91EAe=Jk9=QRgaPJ2ev6n=i3OU42F6Pu3eVqS9=P6p=w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]
On Fri, Feb 3, 2017 at 2:22 PM, alp alp <alp.bitcoin@gmail•com> wrote:
> These are non-answers. Someone must decide. Someone must decide what
> kind of company counts (e.g. does a dark market seller count as a
> business? Does some guy who sells $10/year worth of goods using Bitcoin
> count the same as large companies like Coinbase/BitPay/Blockstream).
> Someone must decide which websites are checked for votes or addresses.
> Someone must decide if a rogue employee made a transaction on behalf of the
> company or not.
>
The less centralized decision making there is, the better. All confirmed
votes will be added to each BIP, so everyone can make their own decision as
to whether or not they want to count it. Remember, this is about gauging
community support.
Rogue employees?: The company in question would have to deal with that.
> Registering domain names is trivial and can be automated if the incentives
> were needed for it.
>
Mountains out of mole hills here—if the domain name is registered after
voting is called, that would be a pretty clear indicator it's a fake
company.
> You mention developers who have commit access. This excludes the vast
> majority of developers. You also don't mention which repositories count.
> Do the developers of bcoin count or not?
>
After further consideration, and as the goal of this is to determine what
the community will support, developers won't have a confirmed vote. They
would get a standard vote though, just like everyone else.
[-- Attachment #2: Type: text/html, Size: 2240 bytes --]
next prev parent reply other threads:[~2017-02-04 21:23 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 [this message]
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
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=CAGCNRJqJ-9RxMpPg7CTyd_+zn-+eR8gKSLRQjR15p8Ubv5pJbw@mail.gmail.com \
--to=teekhan42@gmail$(echo .)com \
--cc=alp.bitcoin@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.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