{"type": "project", "title": "Baseline Protocol", "logoImg": "bafkreifcmebggo7ahlj2cqvpa46okyk3orysjy6tolhek7zkxv4vkbanxq", "website": "https://www.baseline-protocol.org/", "bannerImg": "bafkreidrssup5b46sj5na65lew3jix4kavlhd5qbg5pxrsqrmkwxljviby", "createdAt": 1692243415842, "userGithub": "GoldenBit0", "credentials": {"github": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..XsWPU53iBvc33YGxIZbwcyYZdyhu-I5aagtyAzSX28JhrNm5DqFccQ-P4FcCv61lH-RAyzu8PuBPGJLbEIgjDA", "type": "Ed25519Signature2018", "created": "2023-08-17T04:29:54.766Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2023-08-17T04:29:54.766Z", "expirationDate": "2023-11-15T04:29:54.766Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xd32d7F3d8439249ce0CFe134D22eca7094955524", "hash": "v0.0.0:xzn9/xBkGt5MNHaWRmYvIGTmgxTmTb8R4GSMwZK6fM4=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextGithubOrg#eea-oasis#89866893"}}}, "description": "The Baseline Protocol is a standard designed to enable parties to synchronize complex, multiparty, business princesses using privacy-preserving technologies. \n\nThe [Baseline Protocol](https://www.baseline-protocol.org/) open-source project was conceived as an enterprise solution pattern and a standard for privacy-preserving multiparty business process automation between parties that might not fully trust one another\u2013this is termed \"multiparty zero trust under zero knowledge\". The Baseline Protocol has inspired other standards such as the [Metro Ethernet Forums 114 standard](https://www.mef.net/resources/mef-114-dlt-based-commercial-and-operational-services-framework-billing/) (telecommunications industry) and [Polygon Nightfall](https://polygon.technology/solutions/polygon-nightfall) (an enterprise Ethereum Layer 2 scaling solution).\n\nWithin the context of Ethereum and Web3, the Baseline Protocol can be perceived as an enterprise-ready L2 scaling protocol. It manages business process states and their zero-knowledge proofs of correctness, which are verified and anchored on an EVM-compatible L1 chain.\n\nThe Baseline Protocol currently has two reference implementations ([BRI-1](https://github.com/eea-oasis/baseline/tree/main/examples/bri-1) and [BRI-3](https://github.com/eea-oasis/baseline/tree/main/examples/bri-3)). For full standards compliance, two or more reference implementations must show that they meet the standard\u2019s interoperability requirements. This means they must demonstrate business process automation bridging between two reference implementations representing two distinct business ecosystems. \n\nGrant funding will support the development of a demonstration where at least two reference implementations interoperate with one another. This will showcase how business process automation can bridge two or more distinct ecosystems (one for each reference implementations) with little or no trust assumptions. The reference implementations employ a [Zero Trust framework](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-207.pdf) using [Self-Sovereign Identities](https://en.wikipedia.org/wiki/Self-sovereign_identity) based [W3C Decentralized Identifiers](https://www.w3.org/TR/did-core/), anchored on Ethereum coupled with zero knowledge proofs, in particular [zk-snarks](https://en.wikipedia.org/wiki/Non-interactive_zero-knowledge_proof). These preserve the privacy of business-sensitive data as it passes through a multiparty business process, while simultaneously verifying the correctness of business process execution on the anchoring EVM-compatible L1 chain.\n\n\n# **Roadmap:**\n\nThe Baseline Protocol 2023 Roadmap aims to advance the draft standard to a ratified project specification, as an [Oasis standard](https://www.oasis-open.org/standards/). The Baseline Protocol grant funds will be used to support the 2023 Roadmap items which focuses on interoperability of two Baseline Protocol Implementations (BPIs) demonstrated on a business use case that literally occurs hundreds of thousands of times daily worldwide. This use case typically has limited data privacy and lacks proof of correctness: [verification of the banking data of an enterprise\u2019s customer with the respective customer\u2019s bank](https://github.com/eea-oasis/baseline/tree/main/examples/bpi-interop). \n\nThe innovative approach introduced by the Baseline Protocol  to this global use case ensures that banking data verification can occur under zero knowledge. This means that actual banking data does not need to be shared between the enterprise and the customer\u2019s bank, while being able to prove that both parties executed the business process correctly. While not a classic Web3 use case, banking data synchronization is such a prevalent business process globally. An Ethereum-based method that both enhances and de-risks this use case could meaningfully drive the adoption of Ethereum by enterprises. This would be achieved through the use of multiple dedicated, enterprise-ready L2 solutions that incorporate the Baseline Protocol methodology. \n\nThe Baseline Protocol\u2019s [Technical Steering Committee ](https://github.com/eea-oasis/baseline/blob/main/TECHNICAL-STEERING-COMMITTEE.md)has outlined the high priorities for advancing the standard in 2023, which include the following:\n\n**Technical**\n\n1. Complete Baseline Reference Implementation 3 (BRI-3), which follows a simple and vendor-agnostic approach to enable the subsequent roadmap items, ([read more here](https://entethalliance.org/2023-01-25-new-baseline-protocol-reference-implementation-hits-milestone/)).\n2. Conduct a demonstration of interoperability for Baseline Protocol Implementations (BPIs) for a simple use case to produce results of standard interoperability.\n3. Develop an SDK of out-of-the-box tools for BRI-3 for developers to create a BPI.\n\n**Outreach**\n\n1. Conduct a BPI roadshow through a series of in-person and virtual events to demonstrate BPIs.\n2. Host an interoperability event for BPI interop demonstration.\n\nWe aim to raise up to $100,000 in grant funding to support the work and enable traditional enterprises to synchronize their workflows using Web3 technologies.\n\n\n# **Resources:**\n\n* [Github Repo](https://github.com/eea-oasis/baseline) with implementations, examples, documentation, and more.\n* [Website](https://www.baseline-protocol.org/) with resources, blogs, and information on the open source project operations. \n\n\n# **Reports/blogs:**\n\n* [The BASEics- Baseline Architecture Simplified for Everyone](https://www.baseline-protocol.org/blog/the-baseics/)\n* [The zkEVM: A Natural Execution Framework for Enterprise Baseline Applications](https://www.mesh.xyz/insights/the-zkevm-a-natural-execution-framework-for-enterprise-baseline-applications)\n* [Digital Business at a Crossroads](https://www.baseline-protocol.org/blog/digital-business-at-a-crossroads/)\n* [How the Baseline Protocol Can Secure the Edge of Networks](https://www.mesh.xyz/insights/zero-knowledge-iot)\n* [The Baseline Standard Across Industries: The Case of Mobility](https://www.baseline-protocol.org/blog/the-baseline-standard-across-industries-the-case-of-mobility/)\n* [Global Supply Chain Coordination via Baseline Protocol & The Consensus Controlled State Machine](https://www.baseline-protocol.org/blog/global-supply-chain-coordination-via-baseline-protocol-the-consensus-controlled-state-machine/)\n* [Enterprise Ethereum Alliance- New Baseline Protocol Reference Implementation Hits Milestone](https://entethalliance.org/2023-01-25-new-baseline-protocol-reference-implementation-hits-milestone/)\n* [Proving Secrets Without Exposing Them](https://www.baseline-protocol.org/blog/proving-secrets-without-exposing-them/)\n* [Adrift In An Ocean Of Data](https://www.baseline-protocol.org/blog/adrift-in-an-ocean-of-data/)\n* [Baseline: The Developer Experience](https://www.baseline-protocol.org/blog/baseline-the-developer-experience/)\n* [Baseline Fraud out of Invoice Financing](https://www.baseline-protocol.org/blog/baseline-fraud-out-of-invoice-financing/)", "logoImgData": {}, "bannerImgData": {}, "projectGithub": "eea-oasis", "projectTwitter": "baselineproto"}
Baseline Protocol
The Baseline Protocol is a standard designed to enable parties to synchronize complex, multiparty, business princesses using privacy-preserving technologies. 

The [Baseline Protocol](https://www.baseline-protocol.org/) open-source project was conceived as an enterprise solution pattern and a standard for privacy-preserving multiparty business process automation between parties that might not fully trust one another–this is termed "multiparty zero trust under zero knowledge". The Baseline Protocol has inspired other standards such as the [Metro Ethernet Forums 114 standard](https://www.mef.net/resources/mef-114-dlt-based-commercial-and-operational-services-framework-billing/) (telecommunications industry) and [Polygon Nightfall](https://polygon.technology/solutions/polygon-nightfall) (an enterprise Ethereum Layer 2 scaling solution).

Within the context of Ethereum and Web3, the Baseline Protocol can be perceived as an enterprise-ready L2 scaling protocol. It manages business process states and their zero-knowledge proofs of correctness, which are verified and anchored on an EVM-compatible L1 chain.

The Baseline Protocol currently has two reference implementations ([BRI-1](https://github.com/eea-oasis/baseline/tree/main/examples/bri-1) and [BRI-3](https://github.com/eea-oasis/baseline/tree/main/examples/bri-3)). For full standards compliance, two or more reference implementations must show that they meet the standard’s interoperability requirements. This means they must demonstrate business process automation bridging between two reference implementations representing two distinct business ecosystems. 

Grant funding will support the development of a demonstration where at least two reference implementations interoperate with one another. This will showcase how business process automation can bridge two or more distinct ecosystems (one for each reference implementations) with little or no trust assumptions. The reference implementations employ a [Zero Trust framework](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-207.pdf) using [Self-Sovereign Identities](https://en.wikipedia.org/wiki/Self-sovereign_identity) based [W3C Decentralized Identifiers](https://www.w3.org/TR/did-core/), anchored on Ethereum coupled with zero knowledge proofs, in particular [zk-snarks](https://en.wikipedia.org/wiki/Non-interactive_zero-knowledge_proof). These preserve the privacy of business-sensitive data as it passes through a multiparty business process, while simultaneously verifying the correctness of business process execution on the anchoring EVM-compatible L1 chain.


# **Roadmap:**

The Baseline Protocol 2023 Roadmap aims to advance the draft standard to a ratified project specification, as an [Oasis standard](https://www.oasis-open.org/standards/). The Baseline Protocol grant funds will be used to support the 2023 Roadmap items which focuses on interoperability of two Baseline Protocol Implementations (BPIs) demonstrated on a business use case that literally occurs hundreds of thousands of times daily worldwide. This use case typically has limited data privacy and lacks proof of correctness: [verification of the banking data of an enterprise’s customer with the respective customer’s bank](https://github.com/eea-oasis/baseline/tree/main/examples/bpi-interop). 

The innovative approach introduced by the Baseline Protocol  to this global use case ensures that banking data verification can occur under zero knowledge. This means that actual banking data does not need to be shared between the enterprise and the customer’s bank, while being able to prove that both parties executed the business process correctly. While not a classic Web3 use case, banking data synchronization is such a prevalent business process globally. An Ethereum-based method that both enhances and de-risks this use case could meaningfully drive the adoption of Ethereum by enterprises. This would be achieved through the use of multiple dedicated, enterprise-ready L2 solutions that incorporate the Baseline Protocol methodology. 

The Baseline Protocol’s [Technical Steering Committee ](https://github.com/eea-oasis/baseline/blob/main/TECHNICAL-STEERING-COMMITTEE.md)has outlined the high priorities for advancing the standard in 2023, which include the following:

**Technical**

1. Complete Baseline Reference Implementation 3 (BRI-3), which follows a simple and vendor-agnostic approach to enable the subsequent roadmap items, ([read more here](https://entethalliance.org/2023-01-25-new-baseline-protocol-reference-implementation-hits-milestone/)).
2. Conduct a demonstration of interoperability for Baseline Protocol Implementations (BPIs) for a simple use case to produce results of standard interoperability.
3. Develop an SDK of out-of-the-box tools for BRI-3 for developers to create a BPI.

**Outreach**

1. Conduct a BPI roadshow through a series of in-person and virtual events to demonstrate BPIs.
2. Host an interoperability event for BPI interop demonstration.

We aim to raise up to $100,000 in grant funding to support the work and enable traditional enterprises to synchronize their workflows using Web3 technologies.


# **Resources:**

* [Github Repo](https://github.com/eea-oasis/baseline) with implementations, examples, documentation, and more.
* [Website](https://www.baseline-protocol.org/) with resources, blogs, and information on the open source project operations. 


# **Reports/blogs:**

* [The BASEics- Baseline Architecture Simplified for Everyone](https://www.baseline-protocol.org/blog/the-baseics/)
* [The zkEVM: A Natural Execution Framework for Enterprise Baseline Applications](https://www.mesh.xyz/insights/the-zkevm-a-natural-execution-framework-for-enterprise-baseline-applications)
* [Digital Business at a Crossroads](https://www.baseline-protocol.org/blog/digital-business-at-a-crossroads/)
* [How the Baseline Protocol Can Secure the Edge of Networks](https://www.mesh.xyz/insights/zero-knowledge-iot)
* [The Baseline Standard Across Industries: The Case of Mobility](https://www.baseline-protocol.org/blog/the-baseline-standard-across-industries-the-case-of-mobility/)
* [Global Supply Chain Coordination via Baseline Protocol & The Consensus Controlled State Machine](https://www.baseline-protocol.org/blog/global-supply-chain-coordination-via-baseline-protocol-the-consensus-controlled-state-machine/)
* [Enterprise Ethereum Alliance- New Baseline Protocol Reference Implementation Hits Milestone](https://entethalliance.org/2023-01-25-new-baseline-protocol-reference-implementation-hits-milestone/)
* [Proving Secrets Without Exposing Them](https://www.baseline-protocol.org/blog/proving-secrets-without-exposing-them/)
* [Adrift In An Ocean Of Data](https://www.baseline-protocol.org/blog/adrift-in-an-ocean-of-data/)
* [Baseline: The Developer Experience](https://www.baseline-protocol.org/blog/baseline-the-developer-experience/)
* [Baseline Fraud out of Invoice Financing](https://www.baseline-protocol.org/blog/baseline-fraud-out-of-invoice-financing/)
Baseline Protocol