From: Prayank <prayank@tutanota.de>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] bips.txt format for all Bitcoin projects
Date: Mon, 26 Oct 2020 20:03:21 +0100 (CET) [thread overview]
Message-ID: <MKaHlj_--3-2@tutanota.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1614 bytes --]
Hello Everyone,
What?
Can we request all Bitcoin projects to create a file 'bips.txt' with a format that describes all the BIPs used in the project?
How?
The file can be uploaded to the root of website used for the project. For example: BTCPay can have this file at: https://btcpayserver.org/bips.txt in below format:
BIP78
https://docs.btcpayserver.org/Payjoin/
BIP Number:
Details:
BIP Number
Details:
Why?
Bitcoin Improvement Proposals play an important role in Bitcoin and this will make it easier for users, other devs, journalists, researchers, crawlers etc. to understand all BIPs used in different Bitcoin Projects, their implementation and importance.
Every BIP with details is mentioned here already: https://github.com/bitcoin/bips however I don't think all the devs who initially start researching about Bitcoin or the users really understand their importance, usage etc. So I am also trying to create BIPs gallery which has basic images for each BIP right now and later will include a page to have video links, usage, issues, history, other helpful links etc. later for each.
The discussion started with this question on stackexchange: https://bitcoin.stackexchange.com/questions/98543/any-website-that-explains-most-of-the-bips-in-a-different-way-that-newbies-can-u/ <https://bitcoin.stackexchange.com/questions/98543/any-website-that-explains-most-of-the-bips-in-a-different-way-that-newbies-can-u/98544#98544>
Website that I am working on: https://bips.gallery/
Github repository for it: https://github.com/prayank23/BIPsGallery
--
Prayank
[-- Attachment #2: Type: text/html, Size: 24468 bytes --]
reply other threads:[~2020-10-26 19:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=MKaHlj_--3-2@tutanota.de \
--to=prayank@tutanota.de \
--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