Frequently Asked Questions
There is no Baseline Protocol token.
The Baseline Protocol is a standardized framework, with requirements outlined in the Baseline Protocol Standard, which is undergoing ratification to become an OASIS Open Standard.
Being open-source, open-standard means that anyone is free to build any application or service implementing the protocol. Those applications or services may or may not have their own tokens.
The Baseline Protocol Standard and source code are available under the CC0 1.0 Universal public domain dedication. For the full license text, refer to license.
- Baseline Core Devs: Baseline Core Devs are the backbone of the Baseline Protocol open source community and have an active role in advancing the Baseline Protocol and/or related projects. Join the next generation of top blockchain developers leading the rise of ubiquitous sync services to state machines everywhere!
- Outreach Team: Outreach members communicate, advocate, and educate the world on the advantages of using and contributing to the protocol. Several working groups create enablement materials, devise industry-specific use cases, and document the significant work being done in the community.
- Standards Team: Members of the team work to define and contribute to the specifications of baseline compliance. The Standard is currently in the ratification process to become an official Oasis Standard.
Baseline Protocol v1.0 Core: If you want to build with the Baseline Protocol from scratch, you can get started with v1.0 core that provides a set of 'vanilla' packages. You can get started here.
Reference Implementations: You can also choose to build on top of existing reference implementations.
We recommend starting with BRI-1, this reference implementation of the core interfaces specified in the v1.0 release has been developed by individuals and companies including Provide, EY, Nethermind, ConsenSys Mesh, and others. It heavily utilizes the core Provide application stack and is compatible with Shuttle, an on-ramp for baselining. NATS and the Nethermind Ethereum client (the first client to implement the Baseline Protocol RPC) are opinionatedly used by default. You can get started with BRI-1 here.
Developer Resources: To help you build with the Baseline Protocol, you can use the implementation guide and other developer resources available here.
While 'baselining' as a technique is not restricted to commercial use cases, a Baseline Protocol Implementation (BPI) as specified in the Baseline Protocol Standard requires at least two organizations to come together to synchronize their respective systems of record.
A group of companies interested in 'baselining' can either deploy their own implementation using their in-house resources or they can choose to work with third-party partners (product and service providers).
Get in touch with one of our sponsors for Baseline platforms, tools, solutions, and developer education here.
Any system of record can be baselined without requiring modification to legacy systems. A Baseline Protocol stack is required to manage all messaging and transactions between counterparties and their agreed common frame of reference.
Distributed Ledger Technology, often referred to as a Consensus Controlled State Machine (CCSM) is the foundational enabler of a Baseline Protocol Implementation (BPI). A compliant BPI requires conformance to the CCSM specification of the Baseline Protocol Standard.
While much of the initial work on the Standard and the code was done by companies and individuals in the Ethereum development community, any CCSM that conforms to the CCSM specification of the Baseline Protocol Standard can be used in a compliant Baseline Protocol Implementation (BPI).