From: Chris Stewart <chris@suredbits.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Requirement for pseudonymous BIP submissions
Date: Sat, 18 Mar 2017 10:23:16 -0500 [thread overview]
Message-ID: <CAGL6+mEnGNdAggHZs=ZM_QHbts63exE1ydstK+w-gUnm=4JLTA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3329 bytes --]
As everyone in the Bitcoin space knows, there is a massive scaling debate
going on. One side wants to increase the block size via segwit, while the
other side wants to increase via hard fork. I have strong opinions on the
topic but I won’t discuss them here. The point of the matter is we are
seeing the politicization of protocol level changes. The critiques of these
changes are slowly moving towards critiques based on who is submitting the
BIP -- not what it actually contains. This is the worst thing that can
happen in a meritocracy.
*Avoiding politicization of technical changes in the future*
I like what Tom Elvis Judor did when he submitted his MimbleWimble white
paper to the technical community. He submitted it under a pseudonym, over
TOR, onto a public IRC channel. No ego involved — only an extremely
promising paper. Tom (and Satoshi) both understood that it is only a matter
of time before who they are impedes technical progress of their system.
I propose we move to a pseudonymous BIP system where it is required for the
author submit the BIP under a pseudonym. For instance, the format could be
something like this:
BIP: 1337
Author: 9458b7f9f76131f18823d73770e069d55beb271b@protonmail.com
BIP content down here
The hash “6f3…9cd0” is just my github username, christewart, concatenated
with some entropy, in this case these bytes:
639c28f610edcaf265b47b0679986d10af3360072b56f9b0b085ffbb4d4f440b
and then hashed with RIPEMD160. I checked this morning that protonmail can
support RIPEMD160 hashes as email addresses. Unfortunately it appears it
cannot support SHA256 hashes.
There is inconvenience added here. You need to make a new email address,
you need to make a new github account to submit the BIP. I think it is
worth the cost -- but am interested in what others think about this. I
don't think people submitting patches to a BIP should be required to submit
under a pseudonym -- only the primary author. This means only one person
has to create the pseudonym. From a quick look at the BIPs list it looks
like the most BIPs submitted by one person is ~10. This means they would
have had to create 10 pseudonyms over 8 years -- I think this is
reasonable.
*What does this give us?*
This gives us a way to avoid politicization of BIPs. This means a BIP can
be proposed and examined based on it’s technical merits. This levels the
playing field — making the BIP process even more meritocratic than it
already is.
If you want to claim credit for your BIP after it is accepted, you can
reveal the preimage of the author hash to prove that you were the original
author of the BIP. I would need to reveal my github username and
“639c28f610edcaf265b47b0679986d10af3360072b56f9b0b085ffbb4d4f440b”
*The Future*
Politicization of bitcoin is only going to grow in the future. We need to
make sure we maintain principled money instead devolving to a system where
our money is based on a democratic vote — or the votes of a select few
elites. We need to vet claims by “authority figures” whether it is Jihan
Wu, Adam Back, Roger Ver, or Greg Maxwell. I assure you they are human —
and prone to mistakes — just like the rest of us. This seems like a simple
way to level the playing field.
Thoughts?
-Chris
[-- Attachment #2: Type: text/html, Size: 5326 bytes --]
next reply other threads:[~2017-03-18 15:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 15:23 Chris Stewart [this message]
2017-03-18 16:57 ` [bitcoin-dev] Requirement for pseudonymous BIP submissions Andrew Johnson
2017-03-18 17:35 ` Chris Stewart
2017-03-18 19:15 ` Luke Dashjr
2017-03-24 2:30 ` Troy Benjegerdes
2017-03-29 8:49 ` Tom Zander
[not found] <mailman.29.1489924803.11420.bitcoin-dev@lists.linuxfoundation.org>
2017-03-19 21:17 ` Steve Davis
2017-03-19 23:43 muyuu
2017-03-24 2:18 ` hozer
[not found] ` <CAGL6+mEceO2D2ueeVgv20r5p6tsofMLSTN1ExWfGysJHuM5XfA@mail.gmail.com>
2017-03-28 1:31 ` Troy Benjegerdes
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='CAGL6+mEnGNdAggHZs=ZM_QHbts63exE1ydstK+w-gUnm=4JLTA@mail.gmail.com' \
--to=chris@suredbits.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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