This repository contains research and proposals of interest to the blockchain community.
| Number | Title | Version | Owner |
|---|---|---|---|
| BCR-2020-001 | Uniformly Translating Entropy into Cryptographic Seeds | 1.0.0 | Wolf McNally |
| BCR-2020-002 | Bech32 Encoding for Cryptographic Seeds | 1.0.0 | Wolf McNally |
| BCR-2020-003 | Encoding Binary Compatibly with URI Reserved Characters | 1.0.0 | Wolf McNally |
| BCR-2020-004 | The BC32 Data Encoding Format | 1.0.0 | Wolf McNally |
| BCR-2020-005 | Uniform Resources (UR): Encoding Structured Binary Data for Transport in URIs and QR Codes | 2.0.1 | Wolf McNally |
| BCR-2020-006 | Registry of Uniform Resource (UR) Types | 1.0.0 | Wolf McNally |
| BCR-2020-007 | UR Type Definition for Hierarchical Deterministic (HD) Keys | 1.0.0 | Wolf McNally |
| BCR-2020-008 | UR Type Definition for Elliptic Curve (EC) Keys | 1.0.0 | Wolf McNally |
| BCR-2020-009 | UR Type Definition for Cryptocurrency Addresses | 1.0.0 | Wolf McNally |
| BCR-2020-010 | UR Type Definition for Bitcoin Output Descriptors | 1.0.0 | Wolf McNally |
| BCR-2020-011 | UR Type Definition for Sharded Secret Key Reconstruction (SSKR) | 1.0.1 | Wolf McNally |
| BCR-2020-012 | Bytewords: Encoding binary data as English words | 1.0.0 | Wolf McNally |
| BCR-2020-013 | CRC-32 Checksums in CBOR | 1.0.0 | Wolf McNally |
| BCR-2020-014 | URs on E-paper display | 1.0.0 | Gorazd Kovacic |
| BCR-2020-015 | UR Type Definition for BIP44 Accounts | 1.0.0 | Craig Raw |
| BCR-2021-001 | UR Type Definitions for Transactions Between Airgapped Devices | 1.0.0 | Wolf McNally |
| BCR-2021-002 | Digests for Digital Objects | 1.0.0 | Wolf McNally |
| BCR-2022-001 | Secure Messages | 1.0.0 | Wolf McNally |
| BCR-2022-002 | CID: Common Identifier | 0.1.0 | Wolf McNally |
Also see our Testimony and our Wallet Improvement Proposals.
Please number all Bitcoin Research BCRs with a four-digit number representing the current year (YYYY) followed by a three-digit sequence number for that year (SSS). For example: bcr-2020-001 is the first BCR for 2020, bcr-2020-017 is the 17th, and bcr-2021-001 is the first BCR for 2021.
Note that the sequence number reverts to 001 at the start of each year.
Please be sure that your title is concise, yet informative.
When updating BCRs, please use semantic versioning for your version number.
Most briefly: your version number should be of the form X.Y.Z, where X is the major number ("0" for a BCR in progress; "1" for a fully drafted BCR; and "2" or higher for a new version that has introduced a backward-incompatible change), Y is the minor number (for a backward-compatible new feature), and Z is the patch number (for fixing typos and making other clarifications that don't fundamentally change what the BCR means).
But please consult the semantic versioning document for more information and adjust appropriately for the fact that these are textual BCRs, not software.
Please list the person primarily responsible for the BCR, and moving it forward, as the owner. If there are multiple authors, they should be listed on the BCR itself, not on this overview.
Unless otherwise noted (either in this /README.md or in the file's header comments) the contents of this repository are Copyright © 2020 by Blockchain Commons, LLC, and are licensed under the spdx:BSD-2-Clause Plus Patent License.
This research is a project of Blockchain Commons. We are proudly a "not-for-profit" social benefit corporation committed to open source & open development. Our work is funded entirely by donations and collaborative partnerships with people like you. Every contribution will be spent on building open tools, technologies, and techniques that sustain and advance blockchain and internet security infrastructure and promote an open web.
To financially support further development of this research and other projects, please consider becoming a Patron of Blockchain Commons through ongoing monthly patronage as a GitHub Sponsor. You can also support Blockchain Commons with bitcoins at our BTCPay Server.
We encourage public contributions through issues and pull requests! Please review CONTRIBUTING.md for details on our development process. All contributions to this repository require a GPG signed Contributor License Agreement.
The best place to talk about Blockchain Commons and its projects is in our GitHub Discussions areas.
Gordian Developer Community. For standards and open-source developers who want to talk about interoperable wallet specifications, please use the Discussions area of the Gordian Developer Community repo. This is where you talk about Gordian specifications such as Gordian Envelope, bc-shamir, Sharded Secret Key Reconstruction, and bc-ur as well as the larger Gordian Architecture, its Principles of independence, privacy, resilience, and openness, and its macro-architectural ideas such as functional partition (including airgapping, the original name of this community).
Blockchain Commons Discussions. For developers, interns, and patrons of Blockchain Commons, please use the discussions area of the Community repo to talk about general Blockchain Commons issues, the intern program, or topics other than those covered by the Gordian Developer Community or the Gordian User Community.
As an open-source, open-development community, Blockchain Commons does not have the resources to provide direct support of our projects. Please consider the discussions area as a locale where you might get answers to questions. Alternatively, please use this repository's issues feature. Unfortunately, we can not make any promises on response time.
If your company requires support to use our projects, please feel free to contact us directly about options. We may be able to offer you a contract for support from one of our contributors, or we might be able to point you to another entity who can offer the contractual support that you need.
The following people directly contributed to this repository. You can add your name here by getting involved. The first step is learning how to contribute from our CONTRIBUTING.md documentation.
| Name | Role | Github | GPG Fingerprint | |
|---|---|---|---|---|
| Christopher Allen | Principal Architect | @ChristopherA | <[email protected]> | FDFE 14A5 4ECB 30FC 5D22 74EF F8D3 6C91 3574 05ED |
| Wolf McNally | Contributor | @WolfMcNally | <[email protected]> | 9436 52EE 3844 1760 C3DC 3536 4B6C 2FCF 8947 80AE |
We want to keep all of our software safe for everyone. If you have discovered a security vulnerability, we appreciate your help in disclosing it to us in a responsible manner. We are unfortunately not able to offer bug bounties at this time.
We do ask that you offer us good faith and use best efforts not to leak information or harm any user, their data, or our developer community. Please give us a reasonable amount of time to fix the issue before you publish it. Do not defraud our users or us in the process of discovery. We promise not to bring legal action against researchers who point out a problem provided they do their best to follow the these guidelines.
Please report suspected security vulnerabilities in private via email to [email protected] (do not use this email for support). Please do NOT create publicly viewable issues for suspected security vulnerabilities.
The following keys may be used to communicate sensitive information to developers:
| Name | Fingerprint |
|---|---|
| Christopher Allen | FDFE 14A5 4ECB 30FC 5D22 74EF F8D3 6C91 3574 05ED |
You can import a key by running the following command with that individual’s fingerprint: gpg --recv-keys "<fingerprint>" Ensure that you put quotes around fingerprints that contain spaces.