Viction
  • Getting Started
  • General
    • Overview
    • Viction Blockchain
      • PoSV Consensus
      • Comparison
    • Staking
      • Staking Requirements
      • Staking Rewards
      • How to stake on Viction Wallet
    • Network Information
      • Viction Mainnet
      • Viction Testnet
    • Viction RPC API
  • Smart Contract Development
    • Solidity
      • A Simple Smart Contract
      • Solidity by Example
    • Standards & Specification
      • VRC25 Specification
      • VRC725 Specification
    • IDEs and Tools
      • Remix
      • Ethers.js
      • web3.js
      • thirdweb CLI
    • Deployment & Verification
      • Hardhat
      • Foundry
  • DApp Development
    • Integration
      • Exchange/Wallet integration
      • VRC25 Exchange/Wallet integration
      • Viction Staking Governance
      • VIC ZeroGas
      • VRRF
    • Data and analytics
    • Embedded Wallet (MPC)
    • Walkthrough: Build a Dapp on Viction
      • Setup Environment
      • Write the Smart Contract
      • Interacting with the Dapp in a browser
  • Masternode
    • Requirements
    • Run a Full Node
      • Binary
      • Create a Viction Masternode
      • Tmn
      • Docker
    • Apply Your Node
    • Slashing Mechanism
    • Chain Data Snapshots
    • Troubleshooting
  • Viction Wallet
    • User Guide
      • Authentication
      • How to create a new wallet
      • How to restore a wallet?
      • Wallet settings
      • Send & Receive Tokens
      • Add custom token
      • Manage Tokens
      • Send NFT
      • General settings
    • Developer Guide
    • Privacy Policy
    • Term and Services
  • Viction Bridge
    • Spacegate
    • Arken Bridge
    • Hyperlane
  • Viction Data Availability
    • Viction DA RPC API
    • DA Integration Use cases
      • Simple Guide for Integrating OP Stack Rollup with Viction DA Layer
  • How to
    • How to Connect to Viction Blockchain
      • Coin98 Super Wallet
      • Metamask
      • Ledger
    • How to troubleshoot when the node is up but couldn't begin to sync block
    • How to Vote for Viction Saigon Network Upgrade Proposal
    • How to issue a token via VICIssuer
    • How to verify if a contract has been issued via VICIssuer
    • How to deploy the VRC725 contract
    • How to apply ZeroGas for VRC725 contract
    • How to Migrate Dapps from Ethereum
    • How to register Token or NFT logo on Vicscan
    • How to verify a contract on Vicscan
    • How to confirm a project on Vicscan
    • How to check if a token is gas sponsored on Viction
    • How to verify gas sponsored transactions
    • How to create Telegram Mini Apps
    • How to use VictionSafe (Multisig)
  • FAQ
    • APIs
    • General
      • Viction
      • Ecosystem
      • VIC - Economics
      • Contact & Support
    • Masternodes and Voting
      • Masternodes
      • Voter
    • Products
      • VicScan (Explorer)
      • VicMaster
      • VicStats
      • VicIssuer
        • How to Verify & Publish Contract Source Code on VicScan
      • Viction Wallet
      • Viction Data Availability Network
  • Legal
    • Terms of Use
    • Privacy Policy
  • Whitepaper and Research
  • Archive
    • TOMOE
    • How to Deploy a VRC25 Token on Viction
    • How to deploy an ICO smart contract on Viction
    • How to deploy an NFT token
    • An Example of Building a Dapp on Viction
    • Migrate Ethereum Dapp to Viction
    • TomoMasterDAO
      • Introduction
      • Governance model
        • On-Chain vs Off-Chain Voting
        • Board
        • Proposals
        • Voting and Outcome
      • Tokenomics
      • How to utilize and trade tDAO
      • Proposal guidelines for TomoMasterDAO
    • Old Viction Testnet
    • Deploy on Viction
      • CLI Commands
      • Viction Private Testnet Setup
Powered by GitBook
On this page
  • Introduction
  • Viction DA Infrastructure diagram
  • System components context diagram

Viction Data Availability

Viction's Data Availability (DA) represents a groundbreaking initiative to enhance this aspect of blockchain technology.

PreviousHyperlaneNextViction DA RPC API

Last updated 9 months ago

Introduction

Every monolithic blockchain, which is a blockchain where all functions—such as consensus, data availability, and transaction execution—are integrated within a single protocol, includes a data availability layer. This layer ensures that all the necessary data for validating and verifying transactions is accessible to all network participants.

Viction's Data Availability (DA) represents a groundbreaking initiative to enhance this aspect of blockchain technology. By modularizing the data availability layer, Viction decouples it from the core Viction blockchain. This means that instead of being an inseparable part of the Viction blockchain, the DA layer is designed as a separate, standalone module.

This modular DA layer can be utilized as a roll-up solution by developers building on other blockchain networks. Roll-ups are a scalability technique that processes transactions off the main blockchain (off-chain) and then posts the transaction data back to the main blockchain. This reduces the computational load on the main blockchain while still benefiting from its security features.

By offering its DA layer as a modular component, Viction provides an efficient, scalable, and secure way for other blockchains to manage their data availability needs. This pioneering approach not only enhances the scalability of individual blockchains but also promotes interoperability and flexibility across the broader blockchain ecosystem.

Viction DA Infrastructure diagram

Viction DA takes advantage of AWS CloudFormation, a powerful service specifically designed to manage and provision AWS infrastructure using code. This approach allows us to define their cloud resources in simple text files, which can then be used to automatically and consistently create and manage those resources.

By utilizing AWS CloudFormation, Viction DA ensures a deployment model that is highly scalable, meaning it can handle increased load without performance issues. It is also highly reliable, providing a stable and consistent environment, and automated, reducing the need for manual intervention and minimizing the risk of human error. This results in an efficient and effective way to manage cloud resources, ensuring that the infrastructure can grow and adapt as needed.

System components context diagram

This describes the system components that we develop and how it connects to external components.

  1. Users initiate transactions on the Layer 2 (L2) blockchain.

  2. The L2 blockchain/ DA client submits the block data to the Viction DA service.

  3. Viction DA compresses the data, generates unique commitments and IDs, and returns these IDs. These IDs are used to retrieve the original data and associated proofs.

  4. The L2 blockchain sends the IDs back to Viction (Rollup Tx).

  5. Light nodes/ users can use these IDs to fetch the corresponding commitments and proofs from Viction DA.

  6. Light nodes/ users utilize the commitments and proofs to validate the data.

Viction DA infrastructure diagram
Viction DA - System component context diagram