DONOBLOCK_EN
  • 🔵Litepaper
  • 🟢Whitepaper
  • 2. Introduction
  • 3.Background and Strategy
    • 3-1 World Giving Index
    • 3-2 plan to expand the base of donations
  • 4. DonaBlock Vision
  • 5. DonaBlock Giving Protocol
    • 5-1 DonaBlock.1 Brand mall Connect - DonaBlock Brand Mall
    • 5-2 DonaBlock.2 Bazaar Connect - DonaBlock Bazaar
    • 5-3 DonaBlock.3 - DonaBlock Store
    • 5-4 DonaBlock Ecosystem Participants & Contributors
  • 6. DonaBlock.1 Brand Mall Connect
    • 6-1 Dona Brand ShopBack
    • 6-2 Dona Brand ShopGive
    • 6-3 DonaBlock Browser Extension
    • 6-4 DonaBlock Mobile App
    • 6-5 Service Flow
    • 6-6 Donate Crypto
    • 6-7 Sustainable Development Goals -Impact Index Funds map to the United Nations’ Sustainable Develop
  • 7. DonaBlock.2 Bazaar Connect
    • 7-1 Dona Bazaar ShopBack
    • 7-2 Dona Bazaar ShopGive
    • 7-3 Active consumer participation- volunteer
    • 7-4. BLOCK.2- Architecture
  • 8. DonaBlock.3 Offline Store Connect
    • 8-1 PAYMENT CARD SECURITY Oauth 2.0 Protocol Flow
  • 9. DonaBlock Donation Ecosystem
    • 9-1. How to Donate Crypto to Support Charities
    • 9-2 DonaBlock Giving Fund - Index Fund
    • 9-3. DonaBlock Giving Fund -Impact Fund
    • 9-4 Cryptocurrency Donation Flow
    • 9-5 DonaBlock NFT Fundraising
  • 10. Crypto Fundraising Solution
    • 10-1 DonaBlock Crypto Wallet
    • 10-2 Services for volunteer- Create a Fundraiser
  • 11. DonaBlock Dashboard System
  • 12. DonaBlock Fame Evaluation System
    • 12-1. Volunteer Evaluation System
    • 12-2 Method and the variables that determine
  • 13. DonaBlock Service Flow
  • 14. DonaBlock Technology
    • 14-1 System Architecture
    • 14-2 Core Layer
    • 14-3 Commerce Layer
    • 14-4 Application Layer
    • 14-5 Structure of API and Other Infrastructures
    • 14-6 Quantum cryptography & SECURITY
  • 15. DonaBlock Data Architecture
    • 15-1 Core Data : On-Blockchain Data
    • 15-2 Reference Data :
    • 15-3 Data Ownership : Public / Private
    • 15-4 Configuration and Technical Specifications
  • 16. DonaBlock Token Economy
    • 16-1. Token Flow
    • 16-2. DonaBlock Token and DonaGive Token
    • 16-3 Block-Fame
    • 16-4 Volunteers Charity Campaign Reward
    • 16-5 Consumer Rewards
  • 17. Token Economy Strategy & Risk Management
  • 18. DonaBlock Roadmap
  • 19. Token Allocation
  • 20. Partner with The DonaBlock
  • 21. Audit
Powered by GitBook
On this page
  1. 14. DonaBlock Technology

14-2 Core Layer

The Core Layer stores the sales activity information of each participants of DonaBlock Ecosystem on blockchain and distributed repository. The sales activity information is collected from all the activities generated by end users and from transactions of each deals on DonaBlock.

Critical data, such as product information of the deal, "ShopBack" contract between a supplier and an volunteer, sales records from transactions made by customers on each commerce provider's services, other sales related activities by end users, is stored on blockchain network to prevent fabrication, intervention, or fraudulent activities.

Those data play an important role in the ecosystem to evaluate accurate sales performance of each volunteer and to analyze their followers. DonaBlock blockchain network will be built on an existing Mainnet with minimal data at the initial stage, but it aims to be run independently to support full commerce engine by operating Dona Mainnet or side chain in the future.

In addition, detailed activity data of ecosystem participants will be stored on distributed storage as cached, asynchronous data to increase the efficiency of on-chain transactions.

For example, activities generated by volunteer, detailed purchase information of a customer, and identities of participants are stored on separate, distributed data repository rather than a main blockchain network since they are cold data with a low access frequency.

Also, deal contents created by volunteer or product contents provided by suppliers are on the distributed data storage.

The data on this layer is encrypted and can only be viewed by the data owner, or permitted individuals/companies by the data owner.

Previous14-1 System ArchitectureNext14-3 Commerce Layer

Last updated 1 year ago