<div dir="ltr"><div><div><div>This seems like a good place to point out that attempts to identify individuals (either by name or simply as an individual human being) are futile as well as destructive. "1%" usually means "one out of every 100 people" but this requires identification of individuals as individuals. One person can look like many in Bitcoin, which is why such an effort is futile. Additionally, one person may be far more affected by a decision than others, which is why it's destructive.<br><br></div>I like the idea of measuring consensus, and there are proto-ideas in my head about how that can be done, based not on individual people, but on amounts of bitcoin. Many will argue that we don't want the system to be controlled by those who hold the most bitcoin. I understand that sentiment, but A) I simply disagree, and B) Finding something better seems impossible to me.<br><br></div>A simple method is the following:<br></div>A message can be constructed saying: "As of block X, the holder(s) of Y BTC controlled by [public key] agrees that Z," where X, Y, Z, and the [public key] are the only things that change. This message can be signed by the private key matching the [public key] in the message. Anyone interested in measuring consensus on anything relative to bitcoin holders can advertise for such signed messages to be sent to a repository of their choice which would validate each message (that [public key] (still) holds Y BTC and that the signature is valid) and provide a measure of agreement about Z. Change your mind? Just move your BTC to a different address.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 18, 2016 at 6:12 PM, Luke Dashjr via bitcoin-dev <span dir="ltr"><<a href="mailto:bitcoin-dev@lists.linuxfoundation.org" target="_blank">bitcoin-dev@lists.linuxfoundation.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Saturday, September 05, 2015 9:19:51 PM Andy Chase wrote:<br>
> Okay for sure yeah writing another proposal that reflects the current state<br>
> of affairs as people see it might provide some interesting perspective on<br>
> this proposal. I would welcome that.<br>
<br>
Are you saying your proposal is intentionally not intended to reflect the<br>
reality? I wasn't talking about a "current state of affairs" for BIPs as much<br>
as that that the acceptance of BIPs is *defined by* the state of affairs.<br>
<br>
Overall, I think something *similar to* this proposal is a good idea, but I<br>
disagree with how this proposal currently approaches the problem. Instead,<br>
what I would recommend is a specification based on BIP 123 that specifies the<br>
conditions under which a proposal is *known to be* accepted by the community<br>
(ie, discerning, not deciding), and establishes a way for a committee to<br>
review the BIP and *determine* if these conditions have been met. This would<br>
avoid a "disconnect" between the "official status" and reality, making the BIP<br>
process more useful to everyone.<br>
<br>
Reviewing your current proposal:<br>
<br>
> * It sets up '''committees''' for reviewing comments and indicating<br>
> acceptance under precise conditions.<br>
<br>
As mentioned, IMO a committee shouldn't be indicating acceptance, as much as<br>
it should be *determining* acceptance.<br>
<br>
> ** Committees are authorized groups that represent client authors, miners,<br>
> merchants, and users (each as a segment). Each one must represent at least<br>
> 1% stake in the Bitcoin ecosystem.<br>
<br>
1% seems like an awful lot to dedicate to BIP status changes.<br>
<br>
> A committee system is used to organize the essential concerns of each<br>
> segment of the Bitcoin ecosystem. Although each segment may have many<br>
> different viewpoints on each BIP, in order to seek a decisive yes/no on a<br>
> BIP, a representational authoritative structure is sought. This structure<br>
> should be fluid, allowing people to move away from committees that do not<br>
> reflect their views and should be re-validated on each BIP evaluation.<br>
<br>
That sounds very time consuming. And what happens if these committees don't<br>
represent the community? What about when only part of the community - let's<br>
say 10% - decides to adopt a BIP that doesn't require consensus? Logically<br>
that BIP should still proceed...<br>
<br>
> ** Proof of claim and minimum 1% stake via:<br>
> *** Software: proof of ownership and user base (Min 1% of Bitcoin userbase)<br>
<br>
But the Bitcoin user base is completely unknown, and tracking software user<br>
base is a privacy violation.<br>
<br>
> ** Merchant: proof of economic activity (Min 1% of Bitcoin economic<br>
> activity)<br>
<br>
Bitcoin economic activity is also unknown, and it seems likely that merchants<br>
consider their own activity confidential.<br>
<br>
> Mining: proof of work (Min 1% of Hashpower)<br>
<br>
This needs a proper specification. How do miners express their positions?<br>
<br>
> A BIP Process Manager should be chosen who is in charge of:<br>
<br>
Chosen how, and by whom?<br>
<br>
> == Conditions for activation ==<br>
><br>
> In order for this process BIP to become active, it must succeed by its own<br>
> rules. At least a 4% sample of the Bitcoin community must be represented,<br>
> with at least one committee in each segment included. Once at least one<br>
> committee has submitted a declaration, a request for comments will be called<br>
> and the process should be completed from there.<br>
<br>
Until this BIP is active, its rules do not apply, so this would be a form of<br>
circular reasoning. I like the idea of putting conditions for activation in<br>
the BIP text, but I don't think we can just let the author set any conditions<br>
they like either...<br>
<br>
Luke<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" rel="noreferrer" target="_blank">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_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>
</div>