Raylz Network
  • Home
  • Fundamentals
    • Architecture
    • Components
      • Privacy Ledger
      • Bridge
      • Commit Chain
      • HSM Custody
        • Multi-Cloud Key Management
    • Value Exchange Network (VEN)
    • Privacy in Raylz
    • Vision
  • Ecosystem
    • MegaVEN
    • Tokenomics
    • Testnet
    • Fees
  • Installation
    • Install Raylz
      • Install Privacy Ledger
      • Install VEN
      • Install HSM Custody
    • Developer tools
      • Implement JSON-RPC server
      • Configure event notifications
      • Performance monitor
  • Guides
    • Private data transfer
    • Private token transfer
    • Private data and token transfer
    • Delivery vs. payment
  • Modules
    • Core
      • Core Capabilities
    • Enterprise Database
    • Privacy Ledger Management Console
      • Compliance manager
      • Client account manager
      • Token manager
    • VEN Operator Governance Console
      • VEN Governance
      • Token governance
      • Member governance
  • Tutorials
    • Deploy a Smart Contract with Remix
  • Reference and Support
    • API Reference
    • FAQ
Powered by GitBook
On this page
  1. Fundamentals
  2. Components

Commit Chain

Last updated 1 year ago

Currently, Raylz supports any EVM-compatible blockchain as a Commit Chain. In the future, we aim to support any smart-contract enabled blockchain.

A Commit Chain is a shared blockchain ledger used to validate and record transactions between Privacy Ledgers. Raylz allows for new and existing blockchains to deploy any EVM-compatible ledger to serve as the system's Commit Chain.

Raylz recommends using Hyperledger Besu as the platform for new projects. Hyperledger Besu is open-source, private, permissioned, and EVM-based, making it a perfect complement to the Raylz system.

The Commit Chain coordinates transactions between Privacy Ledgers and receives updates from each one, providing an immutable record of state updates and transactions. Commit Chains also store public information from participants, accepted tokens on the network, issuers, and the mappings that allow for this level of intercommunication.

Communications between Privacy Ledgers consist of an originator and a recipient. The originator retrieves the recipient's public key from the Commit Chain and sends a message to the Bridge. Transactions are coordinated cryptographically through Bridges and the Commit Chain, ensuring privacy and validity without causing transactional redundancy (or "double spend").

All Privacy Ledgers within a Value Exchange Network must register their public keys to the Commit Chain. Each Privacy Ledger must send state updates to the Commit Chain before communicating with other Privacy Ledgers. State updates are published every 10 second by default, and provide proofs of transactions, states, and token values for validation by the .

Network Operator