Sanko Mainnet Docs
  • Sanko
    • What is Sanko?
    • Sanko Overview
      • AnyTrust and the Data Availability Committee
      • Keysets
      • Data Availability Certificates​
      • Data Posting Mechanisms
      • Data Availability Servers​
      • Sequencer-Committee Interaction
    • Official Links
  • Sanko Mainnet
    • Connect to Sanko Mainnet
    • Bridge to Sanko
    • Native DEXs
      • Sankoswap
      • Camelot Exchange
        • Camelot V2
        • Camelot V3
          • Concentrated Liquidity
          • Customizable Tickspacing
          • Directional & Dynamic Volatility Fees
    • Sudoswap
      • Sudoswap Overview
        • Bonding Curves
        • Royalties
        • Settings
        • Property Checking
        • ERC1155 NFTs
      • User Guide
        • Creating a Liquidity Pool
        • Managing Existing Pools
        • Creating an Auction
        • Managing Collections
    • SankoTools
      • Terminal Elements
        • Research Elements
        • Chaindata Elements
        • Market Data Elements
        • NFT Elements
        • Chart Elements
        • Liquidity Elements
        • Portfolio Elements
        • Utility Elements
    • Run a Sanko node
  • $DMT
    • The Dream Machine Token (DMT)
    • What is $DMT?
      • How to Purchase $DMT on Arbitrum
      • How to Purchase $DMT on Ethereum
    • The Dream Machine
    • Tokenomics
  • Build on Sanko
    • Connect to Sanko Testnet
    • Deploy on Sanko Testnet
      • Foundry
      • Hardhat
      • Remix
    • Testnet Info + Faucet
    • Testnet Bridge
    • Testnet Block Explorer
    • Pyth Entropy (RNG)
  • miscellaneous
    • Sanko Terms of Use
    • Sanko Privacy Policy
    • FAQ
    • Notice
Powered by GitBook
On this page
  1. Sanko
  2. Sanko Overview

AnyTrust and the Data Availability Committee

PreviousSanko OverviewNextKeysets

Last updated 1 year ago

Sanko achieves subcent transaction fees in part by significantly reducing the costs associated with posting transaction data – the largest cost component for most optimistic rollups.

Sanko adopts a minimal trust assumption in the form of the Data Availability Committee – a cohort of validators responsible for storing transaction data and providing it on demand. Rather than posting full data blocks, Committee members post Data Availability Certificates (DACerts) containing the hash of a data block, an expiration time, and proof that a sufficient number of Committee members have signed the pair attesting to the validity of the block.

Sanko assumes that at least two Committee members are honest; thus, if the Committee has N members and N – 1 promise to provide access to transaction data, at least one of the promisers will provide data as needed to ensure the proper functioning of the chain.

Sanko's initial Data Availability Cohort