LogoLogo
  • Learn About Signet
    • Simplifying the Rollup
    • No Proofs or State Roots
    • Simple sequencing
    • Cross-chain transfers on Signet
  • Build on Signet
    • Smart Contracts
      • Passage
      • Transactor
      • Orders
        • Order Processing
        • Working with Orders
        • Market Participants
        • Bundles and Orders
        • Application Use Cases
      • Zenith
      • Permit2
    • EVM Behavior
    • Signet SDK
      • signet-zenith
      • signet-types
      • signet-extract
      • signet-evm
      • signet-bundle
      • signet-rpc
  • More info
  • FAQ
  • Glossary
  • Twitter
  • Github
Powered by GitBook
On this page
  • Things to know
  • Zenith's enforced conditions:
  • Zenith's state contents:
  • Invariants
  • More information
  1. Build on Signet
  2. Smart Contracts

Zenith

Zenith accepts transaction bundles for Rollup mining, which are submitted by Builders and signed by Sequencers.

Things to know

  • Builders submit RLP-encoded transaction bundles as EIP-4844 blobs with a BlockHeader struct

  • Sequencers sign the hashed bundle contents

  • Zenith contract validates the bundle, then emits data for the Rollup Node to update the Rollup state

Zenith's enforced conditions:

  • Each Rollup block is signed by a permissioned Sequencer key

  • Rollup blocks are submitted within the specified Host block

  • There is at most one Rollup block submitted per Host block

Zenith's state contents:

  • Permissioned sequencer addresses

Invariants

  • At most one BlockSubmitted event in each Host block.

More information

  • For details on permissioned sequencerAdmin and sequencer roles, see Permissioned Roles

  • For deployed Zenith contract addresses, see Chain Configuration Reference

PreviousApplication Use CasesNextPermit2

Last updated 8 months ago

For contract source code, see

Zenith.sol