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

Data Availability Certificates​

Data Availability Certificates (DACerts) allow the Sanko Sequencer to circumvent the costs associated with posting transaction data to the settlement layer, resulting in significantly more effective cost-effective transaction processing compared to other rollups.

A DACert contains:

  • the hash of a data block

  • an expiration time

  • proof that N-1 Committee members have signed the (hash, expiration time) pair, consisting of

    1. the hash of the Keyset used in signing

    2. a bitmap saying which Committee members signed

    3. a BLS aggregated signature (over the BLS12-381 curve) proving that those parties signed.

Because of the 2-of-N trust assumption, a DACert constitutes proof that the block's data (i.e., the preimage of the hash in the DACert) will be available from at least one honest Committee member, at least until the expiration time.

PreviousKeysetsNextData Posting Mechanisms

Last updated 1 year ago