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