Difference between revisions of "MCatalog/Phases of Delivery"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
* TRL 1: Web-based Smart Contract Demonstration: Use [[Smart Contract]]s and [[Ethereum]]-based account classification to perform [[LKPP]]-defined product catalog data update and publication business process. This includes the following features: | * TRL 1: Web-based Smart Contract Demonstration: Use [[Smart Contract]]s and [[Ethereum]]-based account classification to perform [[LKPP]]-defined product catalog data update and publication business process. This includes the following features: | ||
1. Demonstrate that each [[Programmable Account]] represents a self-contained [[LKPP]]-specified business process, each business process would involve a set of explicitly defined roles, such as [[buyer]]s/[[vendor]]s/[[administrator]]s, who are identified by [[Externally Owned Account]]s. | 1. Demonstrate that each [[Programmable Account]] represents a self-contained [[LKPP]]-specified business process, each business process would involve a set of explicitly defined roles, such as [[buyer]]s/[[vendor]]s/[[administrator]]s, who are identified by [[Externally Owned Account]]s. | ||
2. Demonstrate that the code base can | 2. Demonstrate how each [[Programmable Account]] can ensure transparency and non-corruptibility with respect to the security model of [[blockchain]]-based [[Smart Contract]]s. | ||
3. Document the data types and data content categories in terms of what must be made public and what must be encrypted or stored privately. This will be the foundation for establishing a guideline for implementing the evolving business models as they are to be defined incrementally by [[LKPP]] when new requirements and needs reveal themselves. | |||
4. Demonstrate that the code base can switch between public and self-hosted [[Ethereum]]-compatible blockchains. | |||
* TRL 2: | * TRL 2: | ||
Revision as of 15:30, 5 June 2022
Phases of delivery/Technology Readiness Levels(TRLs)
- TRL 1: Web-based Smart Contract Demonstration: Use Smart Contracts and Ethereum-based account classification to perform LKPP-defined product catalog data update and publication business process. This includes the following features:
1. Demonstrate that each Programmable Account represents a self-contained LKPP-specified business process, each business process would involve a set of explicitly defined roles, such as buyers/vendors/administrators, who are identified by Externally Owned Accounts. 2. Demonstrate how each Programmable Account can ensure transparency and non-corruptibility with respect to the security model of blockchain-based Smart Contracts. 3. Document the data types and data content categories in terms of what must be made public and what must be encrypted or stored privately. This will be the foundation for establishing a guideline for implementing the evolving business models as they are to be defined incrementally by LKPP when new requirements and needs reveal themselves. 4. Demonstrate that the code base can switch between public and self-hosted Ethereum-compatible blockchains.
- TRL 2: