Hiro Whitepaper
  • 🚏Platform Summary
    • 1.1 Market Status & Trends
    • 1.2 Market Problem
    • 1.3 Hiro Solution
  • 🚀Hiro Service Introduction
    • 2.1 Service feature
    • 2.2 NFT Service(Planned)
    • 2.3 Service value proposition
    • 2.4 Vision and scalability
    • 2.5 Service goals
  • ⏺️Hiro Ecosystem
    • 3.1 Decentralized ecosystem
    • 3.2 Game Incubator
    • 3.3 NFT Usage and Marketplace (Planned)
  • 👨‍💻Hiro Technology
    • 4.1 Hiro Platform Mainnet (DANGNN)
    • 4.2 Algorithm
    • 4.3 Architecture
    • 4.4 Data structure
  • 💹Market
    • 5.1 Game market Size
    • 5.2 NFT game market
  • ⛳Distribution
    • 6.1 Service roadmap
Powered by GitBook
On this page
  1. Hiro Technology

4.3 Architecture

Previous4.2 AlgorithmNext4.4 Data structure

Last updated 10 months ago

A. Generating events through smart contracts - registered in blockchain semi-structured data format

B. Several columns of the event may have the same value, and the smart contract, the variables for which the user-defined event make up the rest of the column values

C. Access and query by extracting transactions from the web front end created for testing

D. Saving as State Variables, Event format

E. When the register function is executed with a smart contract, a registered event is generated, and data is stored in the blockchain. It transfers msg.sender, the information that users want to save as an input parameter of the registered event along with a hash value, which is a key value that can be associated with the data and records on the blockchain.

👨‍💻