TBD’s first projects are open for collaboration.
The team is at Bitcoin2022 in Miami, and we’ve just closed our first Milestone deliverable: contributor readiness. Like our company, these projects are young works in progress.
But it’s important we get out there, and get out there early. Open source is not a publishing platform. It’s a conversation.
In this post we’ll take a tour of what’s available. First I’ll talk a little bit about our approach to bootstrapping this community with you.
I’ve long disagreed with open source projects that are designed and built behind closed doors, only to be released once they’re deemed “ready” by some minimum standard. It robs folks of the opportunity to guide fundamental architectural decisions, and it robs the project of innovation from outside the founding team. Many popular projects have gone this route, and I can’t argue with their success. I can, however, take issue with the premature calcification this introduces. I prefer a tight feedback loop that allows us to course correct from the start. It encourages developers to be less attached to the code and more open to potential improvements.
The infrastructure we’re building is a shift in mindset from a centralized world into a decentralized one. It’s some of the most modern web technology being created today. It’s innovative. And you cannot have innovation without failure.
We won’t try to prevent failure; we’re going to embrace it as part of the process. We’ll be proud of it. We will try new things, test them out, and toss them as we discover better approaches. It’s the scientific method.
All projects in the TBD family are in early prototyping. New contributors should expect a pace of development consistent with nascent technology: larger commits, frequent refactoring, changing APIs, and incomplete featuresets. These projects are open from the start to welcome your interest, invite discussion, identify early issues, and advise on design. An early adopter mindset will work well until these projects mature further.
The Discussion forums and Issue trackers are likely the best way to get involved now. Our project leads may be able to guide your efforts and incorporate your feedback in ways that will be most meaningful to you and the project’s goals.
In particular, we want to ensure the New Contributor Experience is as smooth as possible. You should be able to:
- Understand each project’s goals and scope
- Install prerequisite dependencies
- Clone and build the project
- Run the tests
- Join the conversation in Discussions and Issues
There are now four projects in the TBD family:
|ssi-sdk||Go||Standards-based primitives for using Decentralized Identifiers and Verifiable Credentials.|
|ssi-service||Go||An in-a-box service that handles the full Verifiable Credentials lifecycle, including issuance, verification, revocation, and more.|
|dwn-sdk-js||TypeScript||An implementation of DIF’s emerging decentralized personal datastore standard.|
|tbdex-protocol||Java||A playground as we iterate our way to a robust protocol. Mostly composed of tbDEX message schemas/formats and a mock PFI (Primary Financial Institution) implementation.|
This suite supports development of the tbDEX protocol described in our whitepaper released last November.
The team’s done remarkable work over the past 8 weeks to make these real. They started from ideas and broke them down into components, then got to coding. Our Head of Decentralized Identity, Daniel Buchner, is the visionary behind our non-blockchain approach to identity and decentralization. Gabe Cohen leads our self-sovereign identity efforts including credential issuance and verification. Hellen Dou leads our tbDEX Message Formats and mock implementations for financial institutions. And Moe Jangda is the trailblazer across several efforts and kicked off our reference implementation of Decentralized Web Nodes.
Our most recent Milestone outlines the deliverables released this week.
In my first post I discussed the importance of an inclusive environment, and how we’ll design for it. TBD projects follow a common:
At the close of Bitcoin2022 we’ll be scoping the next milestone, and that will be publicly available in the collaboration repository’s roadmap once done. Let’s get talking.
See you on GitHub. 🤘