📗
Edge Matrix Documentation
EN
EN
  • 🌐EMC Network
    • Overview
    • Future Roadmap and Development
    • Frequently Asked Questions (FAQ)
    • Tokenomics
      • Token Allocation
      • Token Utility
      • Revenue Model
  • 🌐Products
    • EMC Mainnet
      • Network Information
      • Consensus Mechanism : PoAW (Proof of AI Work)
      • Block Parameters
      • Transaction Performance
      • JSON RPC
      • Bridge
        • Bridge Contracts
        • Bridge Mechanism
        • Supported Cross-Chain Asset Pair
      • DEX
    • EMC Hub
      • EMC Protocol
      • Network Operation and Topology
  • EMC DAO
    • DAO Architecture: Principles and Processes
    • Proposals and Voting: How Token Holders Shape Decisions
    • Community Treasury: Resource Allocation and Incentive Structures
  • Run an EMC Node
    • GPU Mining Guide
Powered by GitBook
On this page
  1. Products
  2. EMC Hub

Network Operation and Topology

PreviousEMC ProtocolNextEMC DAO

Last updated 2 months ago

In the EMC Protocol, transaction accounting is achieved by validator nodes, which package the state machine data into a structure known as a “commitment” and store it on-chain via a smart contract. This process is referred to as “submission.” Once a commitment has been submitted to the contract, the transaction is considered completed—a milestone termed “confirmation.”It is important to note that submission and confirmation occur asynchronously. In other words, there may be a delay between the time a transaction is submitted and the point at which it is fully confirmed on-chain. Nonetheless, from a user’s perspective, once a transaction has been submitted, it is effectively treated as finalized, enabling them to proceed with subsequent actions without waiting for the final confirmation step.

🌐