The Blockchain Commons Community is a central location for discussion and information dispersal for Blockchain Commons stakeholders.
- Blockchain Commons: Create a specific commons that is dedicated to the realization of open infrastructure for secure, compassionate, decentralized systems.
- Open Infrastructure: Define and advocate a specific and actionable notion of “open infrastructure” as a self-organizing approach to collaborative resource generation.
- Architecture: Research, define, and evangelize an interoperable architecture for secure decentralized systems that are resilient, pragmatic, and easy to use.
- Demand: Define and advocate a new techno-social contract of decentralized infrastructure, based on human dignity, respect for the individual, and mutual benefit for all contributors.
- Peers: Increase the demand for, and population of, people who understand the effective development, and use of, secure decentralized systems.
See also our current strategies.
- Repo Creation Conventions - how to create a new repo
- Release Path — what alpha, beta, etc mean
- Release Path Best Practices Standards — what to do at various stages
- Tweetstorms — incomplete list of past tweetstorms
- Best Practices — how to write BCC tweets
We had a successful virtual internship program this summer, and are hoping to repeat it this fall. See BlockchainCommons#17 for more details. The deadline for signups passed on September 28th.
The following servers are currently running Blockchain Commons services. If you need access, please ask.
- BTCPay: 45.79.86.32
- Our secure server, currently used for BTCPay
- Spotbit: 104.200.29.8
- Our services server, currently used for Spotbit (http://h6zwwkcivy2hjys6xpinlnz2f74dsmvltzsd4xb42vinhlcaoe7fdeqd.onion)
- Standupsh: 45.118.132.204
- ?. This may be our default full node for Gordian Wallet
- Research-0: 45.33.43.151
- Our main server for research projects
- Ss-conf: 172.105.248.106
- A temporary research server, currently being used for esplora experimentation
- Current Projects:
- Projects under consideration:
- (TBW)
- P & Q Bulletproofs Reference Implementation
- Sidechain Security & Architecture Review
If you are interested in supporting a specific blockchain FOSS (free and open-source software) project, feature, or bug bounty, or wish to support the Blockchain Commons or open infrastructure in general, please become an ongoing sponsor or if you prefer make a donation to our BTCPay. We are investigating non-profit options (such as working with the Human Rights Founding) but we are not a charitable non-profit at this time, so any contributions are not individually tax-deductible; however, any contributions by businesses are tax-deductible as an expense. See https://github.com/sponsors/BlockchainCommons for details.
- Learning Bitcoin from the Command Line — The best way to learn to learn deeply about bitcoin is to avoid GUIs (even bitcoin-qt), and instead learn it from the command line.
- #SmartCustody — The Use of Advanced Cryptographic Tools to Improve the Care, Maintenance, Control, and Protection of Digital Assets
The Blockchain Commons members are:
-
- Blockchain & Decentralized Identity Architect — Internet Cryptography Pioneer — Co-author TLS Security Standard
- Decentralized Identity Advocate — founder of #RebootingWebOfTrust & co-chair of the W3C Credentials Community
- Former Principal Architect — Blockstream Corporation, Former VP — Blackphone, Former CTO — Certicom
- Technology Leadership — former Faculty in the MBA in Sustainable Systems program at Pinchot.edu
- Blogs at Life With Alacrity, code on Github and on Twitter is @ChristopherA
- Resides in the Bay Area of California, USA
-
- Software Engineer & Independent Bitcoin Protocol Developer
- Specialties include blockchain scalability, privacy enhancing technologies & issued asset extensions to Bitcoin
- Co-Founder & Former Infrastructure Tech Engineer — Blockstream Corporation
- Co-author Pegged Sidechains white paper, Confidential Assets white paper, Strong Federations white paper
- Core developer of demurrage-token based Freicoin
- Code on Github and on Twitter is @MarkFriedenbach
- Resides in the Bay Area of California, USA
The Blockchain Commons maintains the following communication channels:
- Shared Document Repositories (github): https://github.com/BlockchainCommons
- Community Documents (github): https://github.com/BlockchainCommons/Community
- Research Agenda (github): https://github.com/BlockchainCommons/ResearchAgenda
- Twitter: https://twitter.com/BlockchainCmns
- Forum/Mailing List: TBD
More will be added as needed.
The best place to talk about Blockchain Commons and its projects is in our GitHub Discussions areas.
Gordian System Discussions. For users and developers of the Gordian system, including the Gordian Server, Bitcoin Standup technology, QuickConnect, and the Gordian Wallet. If you want to talk about our linked full-node and wallet technology, suggest new additions to our Bitcoin Standup standards, or discuss the implementation our standalone wallet, the Discussions area of the main Gordian repo is the place.
Wallet Standard Discussions. For standards and open-source developers who want to talk about wallet standards, please use the Discussions area of the Airgapped Signing repo. This is where you can talk about projects like our LetheKit and command line tools such as seedtool, both of which are intended to testbed wallet technologies, plus the libraries that we've built to support your own deployment of wallet technology such as bc-bip39, bc-slip39, bc-shamir, Shamir Secret Key Recovery, bc-ur, and the bc-crypto-base. If it's a wallet-focused technology or a more general discussion of wallet standards,discuss it here.
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 the Gordian System or the wallet standards, each of which have their own discussion areas.
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.
- Create Github Community
- Review content with members & patrons
- We need a CONTRIBUTING.md, something along the lines of ParticipatoryOrgs-Community/CONTRIBUTING.md & ipfs/contributing.md
- Review content with members & patrons
- We need a Contributors Agreement (pending legal formation)
- Create website for blockchaincommons.com, maybe blockchaincommons.org (ChristopherA currently holds these domains)
- Legal formation
- Investigate legal formation options (LLC, L4C, etc.) and legal venues (US, Deleware, Wyoming, overseas,etc.)
- Investigate a formal relationship with Software Freedom Conservancy for those US patrons who wish to contribute tax-deductible funds.
- Funding
- Submit proposals to various foundations desiring to support commons activities
Please read the statuses in individual repos. Many projects are still in testing phase and should not be used for production tasks until they have had further testing and auditing.
Unless otherwise noted (either in the README.md for an individual repo or in an individual file's header comments) the contents of this GitHub are Copyright © 2020 by Blockchain Commons, LLC, and are licensed under the spdx:BSD-2-Clause Plus Patent License.
In most cases, the authors, copyright, and license for each file reside in header comments in the source code. When it does not, we have attempted to attribute it accurately tables in individual READMEs.
The 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.
- Tuur Demeester
- Investment analyst, recommended Bitcoin since 2012
- Founder & CEO of Adamant Capital
- Blogs on Medium and on Twitter is @TuurDemeester.
- Originally from Belgium, resides in Austin, TX
- Wayne Vaughan
- Founder/CEO Tierion
- Advisor Blockchain Capital
- Director DIF (Decentralized Identity Foundation)
- Blogs on Medium and on Twitter is @WayneVaughan.
- Resides in the Bay Area of California USA
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.
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 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.
- 2020-12: Community README standardized
- 2020-08: Community README updated
- 2018-05: Community repository started on Github