<oembed><type>rich</type><version>1.0</version><author_name>npub1lf5jdpupmcelz945y09tzawew6pqs5wkkp6dppeujgxxnqltgufsmzuul6</author_name><author_url>https://nostr.ae/npub1lf5jdpupmcelz945y09tzawew6pqs5wkkp6dppeujgxxnqltgufsmzuul6</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2017-03-18&#xA;📝 Original message:I think this is an excellent idea. I consider myself to be extremely&#xA;data-driven and logical in my thinking, and have still fallen victim to&#xA;thinking &#34;oh great, what&#39;s &lt;person I&#39;ve been annoyed by in the past&gt; on&#xA;about now?&#34; when seeing something posted or proposed.&#xA;&#xA;And vice versa, it prevents people from being more partial to a bad or not&#xA;so great idea simply because it was posited by someone they hold in high&#xA;regard.&#xA;&#xA;Simple, yet effective.  I would actually even go a step further and say&#xA;that all BIPs should be done this way as a matter of procedure, I can&#39;t&#xA;think of a downside.&#xA;&#xA;&#xA;On Sat, Mar 18, 2017 at 10:46 AM Chris Stewart via bitcoin-dev &lt;&#xA;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&#xA;&gt; As everyone in the Bitcoin space knows, there is a massive scaling debate&#xA;&gt; going on. One side wants to increase the block size via segwit, while the&#xA;&gt; other side wants to increase via hard fork. I have strong opinions on the&#xA;&gt; topic but I won’t discuss them here. The point of the matter is we are&#xA;&gt; seeing the politicization of protocol level changes. The critiques of these&#xA;&gt; changes are slowly moving towards critiques based on who is submitting the&#xA;&gt; BIP -- not what it actually contains. This is the worst thing that can&#xA;&gt; happen in a meritocracy.&#xA;&gt;&#xA;&gt; *Avoiding politicization of technical changes in the future*&#xA;&gt;&#xA;&gt; I like what Tom Elvis Judor did when he submitted his MimbleWimble white&#xA;&gt; paper to the technical community. He submitted it under a pseudonym, over&#xA;&gt; TOR, onto a public IRC channel. No ego involved — only an extremely&#xA;&gt; promising paper. Tom (and Satoshi) both understood that it is only a matter&#xA;&gt; of time before who they are impedes technical progress of their system.&#xA;&gt;&#xA;&gt; I propose we move to a pseudonymous BIP system where it is required for&#xA;&gt; the author submit the BIP under a pseudonym. For instance, the format could&#xA;&gt; be something like this:&#xA;&gt;&#xA;&gt; BIP: 1337&#xA;&gt;&#xA;&gt; Author: 9458b7f9f76131f18823d73770e069d55beb271b at protonmail.com&#xA;&gt;&#xA;&gt; BIP content down here&#xA;&gt;&#xA;&gt; The hash “6f3…9cd0” is just my github username, christewart, concatenated&#xA;&gt; with some entropy, in this case these bytes:&#xA;&gt; 639c28f610edcaf265b47b0679986d10af3360072b56f9b0b085ffbb4d4f440b&#xA;&gt;&#xA;&gt; and then hashed with RIPEMD160. I checked this morning that protonmail can&#xA;&gt; support RIPEMD160 hashes as email addresses. Unfortunately it appears it&#xA;&gt; cannot support SHA256 hashes.&#xA;&gt;&#xA;&gt; There is inconvenience added here. You need to make a new email address,&#xA;&gt; you need to make a new github account to submit the BIP. I think it is&#xA;&gt; worth the cost -- but am interested in what others think about this. I&#xA;&gt; don&#39;t think people submitting patches to a BIP should be required to submit&#xA;&gt; under a pseudonym -- only the primary author. This means only one person&#xA;&gt; has to create the pseudonym. From a quick look at the BIPs list it looks&#xA;&gt; like the most BIPs submitted by one person is ~10. This means they would&#xA;&gt; have had to create 10 pseudonyms over 8 years -- I think this is&#xA;&gt; reasonable.&#xA;&gt;&#xA;&gt; *What does this give us?*&#xA;&gt;&#xA;&gt; This gives us a way to avoid politicization of BIPs. This means a BIP can&#xA;&gt; be proposed and examined based on it’s technical merits. This levels the&#xA;&gt; playing field — making the BIP process even more meritocratic than it&#xA;&gt; already is.&#xA;&gt;&#xA;&gt; If you want to claim credit for your BIP after it is accepted, you can&#xA;&gt; reveal the preimage of the author hash to prove that you were the original&#xA;&gt; author of the BIP. I would need to reveal my github username and&#xA;&gt; “639c28f610edcaf265b47b0679986d10af3360072b56f9b0b085ffbb4d4f440b”&#xA;&gt;&#xA;&gt; *The Future*&#xA;&gt; Politicization of bitcoin is only going to grow in the future. We need to&#xA;&gt; make sure we maintain principled money instead devolving to a system where&#xA;&gt; our money is based on a democratic vote — or the votes of a select few&#xA;&gt; elites. We need to vet claims by “authority figures” whether it is Jihan&#xA;&gt; Wu, Adam Back, Roger Ver, or Greg Maxwell. I assure you they are human —&#xA;&gt; and prone to mistakes — just like the rest of us. This seems like a simple&#xA;&gt; way to level the playing field.&#xA;&gt;&#xA;&gt; Thoughts?&#xA;&gt;&#xA;&gt; -Chris&#xA;&gt;&#xA;&gt;&#xA;&gt;&#xA;&gt; _______________________________________________&#xA;&gt; bitcoin-dev mailing list&#xA;&gt; bitcoin-dev at lists.linuxfoundation.org&#xA;&gt; https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev&#xA;&gt;&#xA;-- &#xA;Andrew Johnson&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170318/a41a9a1a/attachment.html&gt;</html></oembed>