Difference between revisions of "MCatalog/Criteria"
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
{{SemanticMarker | {{SemanticMarker | ||
|category=Project/mCatalog | |category=Project/mCatalog | ||
|date_created= | |date_created=2 June 2022 | ||
}} | }} | ||
</noinclude> | </noinclude> | ||
Latest revision as of 09:38, 5 June 2022
- Achieve the same level of data security protected by publicly available blockchain service, initially using Ethereum-based blockchains.
- Represent LKPP-specific business logic using Ethereum-based smart contract technologies.
- Allow LKPP to utilize Ethereum's account management architecture to trace data modification actions of relevant parties.
- Provide programming interfaces to LKPP team to specify and deploy customized user interfaces in popular web browsers.
- Allow all users (buyers/vendors/administrators), to use popular web browsers to read and write digitized products and service description data encoded in Ethereum-based blockchain data publishing infrastructure.
- The user interfaces in popular web browsers should support JavaScript(ECMAScript) runtime environment, so that it can be continuously extended with programmable UI/UX features.
Date Created: 2 June 2022
Last Edited: 5 Jun 2022
Last Viewed: 24 Nov 2024
Display in Timeline: yes