Awesome
Gordian Developer Community
Mission
Gordian Developer Community is a community of cryptocurrency & identity wallet developers, sharing best practices for paritioned interoperability among multiple vendors on multiple platforms. These best practices include support for hot, cold and multisig cryptographic wallets, research & proposals for data formats and protocols, usage of gaps such as airgaps and torgaps, security and UX for multisig work flows, and other key management and signing issues and topics, particularly those that support the Gordian Principles of independence, privacy, resilience, and openness.
Meetings
Much of our collaborative work is conducted through Meetings. Please sign up for our Gordian Developer lists to be informed of when they occur and please see our meetings page for info from meetings to date.
Technologies
Blockchain Common's Gordian technologies include architectural designs, apps, and specifications. The architectural designs, apps, and the general overview of the system can be found in the Gordian repo while developer-level docs can be found in the Crypto Commons repo. Finally, original research specifications can be found in the Research repo.
The following is a general listing of topics in the three repos, but visiting the individual repos' READMEs can provide more up-to-date information
Gordian Repo:
Crypto Commons Repo:
Research:
URs
One of our most successful interoperable specifications to date has been ur:. Following is a table of usage.
Please submit PRs if you are aware of different usages or to make corrections.
| Publisher | Wallet | Animated PSBT | ur:crypto-psbt | ur:crypto-* | Future |
|---|---|---|---|---|---|
| BlueWallet | BlueWallet | ? | ? | bc-urv1 | |
| Casa | Casa Wallet | YES | YES | -hdkey (-request/response for health check) | |
| Cobo | Cobo Wallet | ? | ? | bc-urv1 | |
| DIYBitcoin | DIY Hardware Wallet | YES | ? | ? | |
| Denton Development | Fully Noded | YES | YES | ? | |
| Blockstream | Jade | YES | ? | ? | |
| Blockchain Commons | keytool-cli | NO | YES | -hdkey, -request, -response, -seed | |
| Keeper | Keeper Wallet | YES | YES | -account | |
| Keystone | Keystone Essential/Pro | YES | YES | ? | |
| Foundation | Passport | YES | YES | (-request/response with Casa for health check) | -account |
| Meteor Software | SeedSigner | YES | ? | ? | |
| Blockchain Commons | Seed Tool | YES | YES | -account, -address, -bip39, -hdkey<br/>-output, -seed, -sskr | |
| Blockchain Commons | seedtool-cli | NO | NO | -seed, -sskr | |
| Craig Raw | Sparrow | YES | YES | -account, -address, -bip39, -hdkey,<br/>-output, -seed | |
| SeedHammer | SeedHammer | NO | NO | -output |
More info on PRs can be found in our research papers and in our UR docs.
Discussions
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).
We also have a Signal group and a low-volume announcement mailing list.
Members
- Blockchain Commons (open source repos: GitHub/BlockchainCommons twitter: @BlockchainComns )
- Wallets & Major Projects
- People:
- Christopher Allen (github: @ChristopherA twitter: @ChristopherA )
- Peter Denton (github: @Fonta1n3 twitter: @Fonta1n3)
- Wolf McNally (github: @WolfMcNally twitter: @WolfMcNally)
- + multiple interns and other contributors
- Keystone (open source repos: GitHub/Keystone twitter: @KeystoneWallet )
- Projects
- People:
- Aaron Chen (github: @aaronisme twitter: @Aaron Chen )
- Lixin Liu (twitter: @BitcoinLixin)
- Sora Li (github: @soralit)
- + multiple other contributors
- Cobo Vault (open source repos: GitHub/CoboVault twitter: @CoboVault )
- Products - Cobo Vault
- Foundation Devices (open source repos: GitHub/Foundation-Devices twitter: @FOUNDATIONdvcs )
- Projects
- Passport (public repos coming this Fall)
- Python UR Library
- People:
- Ken Carpenter (github: @FoundationKen twitter: @KenOfFoundation )
- Zach Herbert (github: @zachherbert twitter: @zachherbert )
- + interns and other contributors
- Projects
- Sparrow Wallet (open source repos: GitHub/Sparrow Wallet twitter: @SparrowWallet )
- Projects
- Sparrow Wallet (https://github.com/sparrowwallet/sparrow)
- Hummingbird - Java UR library (https://github.com/sparrowwallet/hummingbird)
- People:
- Projects
Archived Info
The following folders in this repository contain other information:
- Proof of Concept: 2019 - In 2019 Blockchain Commons did a proof-of-concept of air-gapped signing between two airgapped devices, one written in Swift for iOS, the other using Java on macOS Desktop. Full code and information is available here.
Status - Work in Progress
Gordian Developer Community is by definition a work-in-progress, as it contains active discussions among its members.
Origin, Authors, Copyright & Licenses
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.
Financial Support
Gordian Developer Community 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 $projectname 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.
Contributing
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.
Other Questions & Problems
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.
Credits
Thank you to all our members and contributors!
Responsible Disclosure
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.
Reporting a Vulnerability
Please report suspected security vulnerabilities in private via email to ChristopherA@BlockchainCommons.com (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.