Difference between revisions of "MCatalog/Criteria"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
# Allow [[LKPP]] to utilize [[Ethereum]]'s account management architecture to trace data modification actions of relevant parties. | # 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]]. | # Provide programming interfaces to [[LKPP]] team to specify and deploy customized user interfaces in [[popular web browsers]]. | ||
# Allow all users ([[buyer]]s/[[vendor]]s/[[administrator]]s), to utilize [[Ethereum-based blockchain]] data publishing infrastructure in regular web-based interfaces that supports [[JavaScript]]([[ECMAScript | # Allow all users ([[buyer]]s/[[vendor]]s/[[administrator]]s), to utilize [[Ethereum-based blockchain]] data publishing infrastructure in regular web-based interfaces that supports [[JavaScript]]([[ECMAScript]]) runtime environment. | ||
Revision as of 09:53, 4 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 utilize Ethereum-based blockchain data publishing infrastructure in regular web-based interfaces that supports JavaScript(ECMAScript) runtime environment.