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
  1. Build on Signet
  2. Signet SDK

signet-extract

Extraction logic for Signet. This crate contains functions that traverse reth `Chain` objects and extract `Signet`-specific data from them.

Previoussignet-typesNextsignet-evm

Last updated 6 days ago

What's in this crate?

The Extractor object traverses a and produces a Extracts per block. This object contains all relevant events that occured in the block, as well as a populated AggregateFills.

Signet nodes watch Ethereum for specific events, and use these events to trigger actions on Signet. These actions are processed by the Signet EVM during block processing.

There are 4 types of events that trigger actions on Signet:

  • BlockSubmitted - Retrieve builder-submitted transactions from an Ethereum blob, and execute them on Signet.

  • Enter- Mint ETH on Signet.

  • EnterToken - Mint tokens on Signet.

  • Transact - Execute a transaction on Signet.

Another event affects Signet's [conditional transactions]. The Fill event is used to populate the aggregate fills for conditional transactions. This event is emitted by the Orders contract on Ethereum when a trade is executed, and then used to enforce the conditional invariant on Signet.

Chain