From: Prayank <prayank@tutanota•de>
To: laanwj@protonmail•com
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Reminder on the Purpose of BIPs
Date: Wed, 15 Sep 2021 11:50:34 +0200 (CEST) [thread overview]
Message-ID: <MjcrMLe--3-2@tutanota.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1829 bytes --]
> I like the idea of decentralizing the BIPs process. It is a historical artifact that the bips repository is part of the same organization that bitcoin core is part of. But there shouldn't be the perception that standardization is driven by that, or that there is any kind of (non-trivial) gatekeeping.
I had suggested few changes in BIP process and repository yesterday. Meeting was disappointing because of few reasons:
1.Its been 12 years since Bitcoin came in to existence and I am surprised that during such important conversations I still see only 4 people out of which 2 are maintainers.
2.None of the people who participated in meeting agree that we need to create multiple BIP directories and let people decide what works best for them. Reduce dependency on one repository or few people. At the end of the day these are just proposals, implementations are more important and there are so many ways to document things online, archive etc.
Playing ACK/NACK game in 'bitcoin/bips' repository will be a waste of time so I created this as an example:
https://github.com/prayank23/bips/blob/master/README.md
https://prayank23.github.io/bips/
I respect everyone involved in Bitcoin development however neither I trust anyone nor I expect anyone to trust me. Bitcoin is not just another open source software. Its a protocol for decentralized network which can be used to settle payments. We are trying to redefine MONEY, many cypherpunks, activists, hacktivists, privacy advocates etc. are involved and trying to separate money from state. The same money that is needed for almost everything you do in this world from birth to death, love to war and same money that makes some people more powerful. So, I won't be surprised with anything in future and will be prepared for everything.
--
Prayank
A3B1 E430 2298 178F
[-- Attachment #2: Type: text/html, Size: 2409 bytes --]
next reply other threads:[~2021-09-15 9:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 9:50 Prayank [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-23 2:09 [bitcoin-dev] Proposed BIP editor: Kalle Alm Luke Dashjr
2021-04-23 15:34 ` Antoine Riard
2021-04-25 20:29 ` [bitcoin-dev] Reminder on the Purpose of BIPs Matt Corallo
2021-04-25 21:00 ` Luke Dashjr
2021-04-25 21:14 ` Matt Corallo
2021-04-25 21:22 ` Luke Dashjr
2021-04-25 21:31 ` Matt Corallo
2021-04-26 19:43 ` David A. Harding
2021-04-26 20:04 ` Greg Maxwell
2021-04-27 19:43 ` Melvin Carvalho
2021-04-27 9:04 ` W. J. van der Laan
2021-04-27 11:49 ` Erik Aronesty
2021-04-27 11:33 ` John Newbery
2021-04-27 12:16 ` Jorge Timón
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=MjcrMLe--3-2@tutanota.de \
--to=prayank@tutanota$(echo .)de \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=laanwj@protonmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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