<div dir="ltr">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.<div><br></div><div>Registering domain names is trivial and can be automated if the incentives were needed for it.</div><div><br></div><div>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?</div><div><br></div><div>These questions all would need to be answered before any kind of proposal like this can be taken seriously. Without these kinds of answers, this proposal is far from complete.</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 3, 2017 at 12:20 PM, t. khan <span dir="ltr"><<a href="mailto:teekhan42@gmail.com" target="_blank">teekhan42@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Most of these are answered in the BIP, but for clarity:<span class=""><div><br></div><div><span style="font-size:12.800000190734863px">>Who decides on which companies are eligible?</span></div></span><div><span style="font-size:12.800000190734863px">Preferably no one decides. The company would have to exist prior to the vote, and would need a public-facing website. In the event of contested votes (meaning someone finds evidence of a fake company), the admin could investigate and post results.</span></div><span class=""><div><span style="font-size:12.800000190734863px"><br></span></div><div><span style="font-size:12.800000190734863px">>Is there some kind of centralized database that one registers?</span></div></span><div><span style="font-size:12.800000190734863px">No.</span></div><div><span style="font-size:12.800000190734863px"><br></span></div><div><span style="font-size:12.800000190734863px">>Who administers this?</span></div><div><span style="font-size:12.800000190734863px">I don't know. I'm happy to volunteer, if no one else wants to be responsible for it. The only task would be adding the confirmed votes to each respective BIP. From there, everything's public and can be confirmed by everyone.</span></div><span class=""><div><span style="font-size:12.800000190734863px"><br></span></div><div><span style="font-size:12.800000190734863px">>What is to stop someone from creating a million fake companies to sway the voting?</span></div></span><div><span style="font-size:12.800000190734863px">The logistics of doing that prevent it. But let's say 10 fake companies ... first, you'd need to register ten domain names, host and customize the website, all before the vote and in a way that no one would notice.</span></div><span class=""><div><span style="font-size:12.800000190734863px"><br></span></div><div><span style="font-size:12.800000190734863px">>How does a company make it's vote?</span></div></span><div><span style="font-size:12.800000190734863px">Someone at the company sends a very small transaction to the BIP's vote address. Someone at the company then posts what the vote was and its transaction ID on the company's blog/twitter, etc., and then emails the URL to the administrator.</span><br></div><span class=""><div><span style="font-size:12.800000190734863px"><br></span></div><div><span style="font-size:12.800000190734863px">>How does one verify that the person voting on behalf of a company is actually the correct person?</span><div style="font-size:12.800000190734863px"><div></div></div></div></span><div><span style="font-size:12.800000190734863px">They post it on their company blog.</span></div><div><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 3, 2017 at 11:19 AM, alp alp via bitcoin-dev <span dir="ltr"><<a href="mailto:bitcoin-dev@lists.linuxfoundation.org" target="_blank">bitcoin-dev@lists.<wbr>linuxfoundation.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>This proposal seems hopelessly broken.</div><div><br></div>Who decides on which companies are eligible? Is there some kind of centralized database that one registers? Who administers this? What is to stop someone from creating a million fake companies to sway the voting? How does a company make it's vote? How does one verify that the person voting on behalf of a company is actually the correct person?<div><div><div><br></div><div><br></div></div></div></div><div class="m_6338179334032076449gmail-HOEnZb"><div class="m_6338179334032076449gmail-h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 2, 2017 at 7:32 PM, Dave Scotese via bitcoin-dev <span dir="ltr"><<a href="mailto:bitcoin-dev@lists.linuxfoundation.org" target="_blank">bitcoin-dev@lists.linuxfounda<wbr>tion.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div>There are two ideas here for "on-chain" voting, both of which require changes to the software. I agree with David that on-chain solutions complicate things. Both proposals can be effected without any software changes:<br><br>Those who wish to use proof of stake can provide a service for making vanity addresses containing some indicator of the proposal to be supported - 1bigblock or 12mbblk or whatever - based on a supporter-provided secret key, and then supporters can move their bitcoin into their own vanity address and then whoever wants to can create a website to display the matching addresses and explain that this is the financial power in the hands of supporters and how to add your "financial power vote."<br><br></div>Those who simply want to "buy votes" can use their funds in marketing efforts to promote the proposal they support.<br><br></div>This second method, of course, can be abused. The first actually requires people to control bitcoin in order to represent support. Counting actual, real people is still a technology in its infancy, and I don't think I want to see it progress much. People are not units, but individuals, and their value only becomes correlated to their net worth after they've been alive for many years, and even then, some of the best people have died paupers. If bitcoin-discuss got more traffic, I think this discussion would be better had on that list.<br><br></div>notplato<br></div><div class="gmail_extra"><div><div class="m_6338179334032076449gmail-m_-7839396425681813593h5"><br><div class="gmail_quote">On Thu, Feb 2, 2017 at 4:24 PM, Luke Dashjr via bitcoin-dev <span dir="ltr"><<a href="mailto:bitcoin-dev@lists.linuxfoundation.org" target="_blank">bitcoin-dev@lists.linuxfounda<wbr>tion.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Strongly disagree with buying "votes", or portraying open standards as a<br>
voting process. Also, this depends on address reuse, so it's fundamentally<br>
flawed in design.<br>
<br>
Some way for people to express their support weighed by coins (without<br>
losing/spending them), and possibly weighed by running a full node, might<br>
still be desirable. The most straightforward way to do this is to support<br>
message signatures somehow (ideally without using the same pubkey as<br>
spending), and some [inherently unreliable, but perhaps useful if the<br>
community "colludes" to not-cheat] way to sign with ones' full node.<br>
<br>
Note also that the BIP process already has BIP Comments for leaving textual<br>
opinions on the BIP unrelated to stake. See BIP 2 for details on that.<br>
<br>
Luke<br>
<div><div class="m_6338179334032076449gmail-m_-7839396425681813593m_7954997659320911193h5"><br>
<br>
On Thursday, February 02, 2017 7:39:51 PM t. khan via bitcoin-dev wrote:<br>
> Please comment on this work-in-progress BIP.<br>
><br>
> Thanks,<br>
><br>
> - t.k.<br>
><br>
> ----------------------<br>
> BIP: ?<br>
> Layer: Process<br>
> Title: Community Consensus Voting System<br>
> Author: t.khan <<a href="mailto:teekhan42@gmail.com" target="_blank">teekhan42@gmail.com</a>><br>
> Comments-Summary: No comments yet.<br>
> Comments-URI: TBD<br>
> Status: Draft<br>
> Type: Standards Track<br>
> Created: 2017-02-02<br>
> License: BSD-2<br>
> Voting Address: 3CoFA3JiK5wxe9ze2HoDGDTmZvkE5U<wbr>uwh8 (just an example, don’t<br>
> send to this!)<br>
><br>
> Abstract<br>
> Community Consensus Voting System (CCVS) will allow developers to measure<br>
> support for BIPs prior to implementation.<br>
><br>
> Motivation<br>
> We currently have no way of measuring consensus for potential changes to<br>
> the Bitcoin protocol. This is especially problematic for controversial<br>
> changes such as the max block size limit. As a result, we have many<br>
> proposed solutions but no clear direction.<br>
><br>
> Also, due to our lack of ability to measure consensus, there is a general<br>
> feeling among many in the community that developers aren’t listening to<br>
> their concerns. This is a valid complaint, as it’s not possible to listen<br>
> to thousands of voices all shouting different things in a crowded<br>
> room—basically the situation in the Bitcoin community today.<br>
><br>
> The CCVS will allow the general public, miners, companies using Bitcoin,<br>
> and developers to vote for their preferred BIP in a way that’s public and<br>
> relatively difficult (expensive) to manipulate.<br>
><br>
> Specification<br>
> Each competing BIP will be assigned a unique bitcoin address which is added<br>
> to each header. Anyone who wanted to vote would cast their ballot by<br>
> sending a small amount (0.0001 btc) to their preferred BIP's address. Each<br>
> transaction counts as 1 vote.<br>
><br>
> Confirmed Vote Multiplier:<br>
> Mining Pools, companies using Bitcoin, and Core maintainers/contributors<br>
> are allowed one confirmed vote each. A confirmed vote is worth 10,000x a<br>
> regular vote.<br>
><br>
> For example:<br>
><br>
> Slush Pool casts a vote for their preferred BIP and then states publicly<br>
> (on their blog) their vote and the transaction ID and emails the URL to the<br>
> admin of this system. In the final tally, this vote will count as 10,000<br>
> votes.<br>
><br>
> Coinbase, Antpool, BitPay, BitFury, etc., all do the same.<br>
><br>
> Confirmed votes would be added to a new section in each respective BIP as a<br>
> public record.<br>
><br>
> Voting would run for a pre-defined period, ending when a particular block<br>
> number is mined.<br>
><br>
><br>
> Rationale<br>
> Confirmed Vote Multiplier - The purpose of this is twofold; it gives a<br>
> larger voice to organizations and the people who will have to do the work<br>
> to implement whatever BIP the community prefers, and it will negate the<br>
> effect of anyone trying to skew the results by voting repeatedly.<br>
><br>
> Definitions<br>
> Miner: any individual or organization that has mined at least one valid<br>
> block in the last 2016 blocks.<br>
><br>
> Company using Bitcoin: any organization using Bitcoin for financial, asset<br>
> or other purposes, with either under development and released solutions.<br>
><br>
> Developer: any individual who has or had commit access, and any individual<br>
> who has authored a BIP<br>
><br>
> Unresolved Issues<br>
> Node voting: It would be desirable for any full node running an up-to-date<br>
> blockchain to also be able to vote with a multiplier (e.g. 100x). But as<br>
> this would require code changes, it is outside the scope of this BIP.<br>
><br>
> Copyright<br>
> This BIP is licensed under the BSD 2-clause license.<br>
</div></div>______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href="mailto:bitcoin-dev@lists.linuxfoundation.org" target="_blank">bitcoin-dev@lists.linuxfoundat<wbr>ion.org</a><br>
<a href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" rel="noreferrer" target="_blank">https://lists.linuxfoundation.<wbr>org/mailman/listinfo/bitcoin-d<wbr>ev</a><br>
</blockquote></div><br><br clear="all"><br></div></div><span class="m_6338179334032076449gmail-m_-7839396425681813593HOEnZb"><font color="#888888">-- <br><div class="m_6338179334032076449gmail-m_-7839396425681813593m_7954997659320911193gmail_signature"><div dir="ltr">I like to provide some work at no charge to prove my value. Do you need a techie? <br>I own <a href="http://www.litmocracy.com" target="_blank">Litmocracy</a> and <a href="http://www.memeracing.net" target="_blank">Meme Racing</a> (in alpha). <br>I'm the webmaster for <a href="http://www.voluntaryist.com" target="_blank">The Voluntaryist</a> which now accepts Bitcoin.<br>I also code for <a href="http://dollarvigilante.com/" target="_blank">The Dollar Vigilante</a>.<br>"He ought to find it more profitable to play by the rules" - Satoshi Nakamoto</div></div>
</font></span></div>
<br>______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href="mailto:bitcoin-dev@lists.linuxfoundation.org" target="_blank">bitcoin-dev@lists.linuxfoundat<wbr>ion.org</a><br>
<a href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" rel="noreferrer" target="_blank">https://lists.linuxfoundation.<wbr>org/mailman/listinfo/bitcoin-d<wbr>ev</a><br>
<br></blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href="mailto:bitcoin-dev@lists.linuxfoundation.org" target="_blank">bitcoin-dev@lists.linuxfoundat<wbr>ion.org</a><br>
<a href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" rel="noreferrer" target="_blank">https://lists.linuxfoundation.<wbr>org/mailman/listinfo/bitcoin-d<wbr>ev</a><br>
<br></blockquote></div><br></div></div></div></div>
</blockquote></div><br></div>