Mode Docs
  • Introduction
    • 🟑Introducing Mode
    • βœ…AI Agent Dev Roadmap
  • AI AGENTS
    • Mode AI Terminal
    • 🀷What are AI Agents?
    • πŸ—οΈBuilding your first agent
    • Tutorials
      • Quickstart
    • πŸ› οΈAI Tooling
      • AI Audits
      • AI APIs
      • Frameworks
  • Tools
    • πŸ–₯️RPC
    • πŸͺΆMultisig wallets
    • πŸ”Bridge
    • 🚰Testnet Faucets
    • πŸ•΅οΈBlock Explorers
    • πŸ—‚οΈData Indexers
    • πŸ§™β€β™‚οΈOracles
    • ⛓️Interoperability
    • ⁉️Randomness
    • 🌎General Tooling
  • Tutorials
    • Interacting with Smart Contracts using ethers.js
    • Deploying a Smart Contract
      • Using Hardhat
      • Using Thirdweb
      • Using Foundry
      • Using Remix
    • Verifying your smart contract
      • Using Hardhat
      • Using Foundry
  • User Guides
    • ℹ️Network Details
    • 🦊Add Mode
    • 🏑Contract Addresses
      • Tokens
      • L1/L2 Mainnet Contracts
      • Testnet Contracts
    • πŸŒ‰Bridge
      • ➑️Bridge to Mode
      • ⬅️Bridge from Mode
      • πŸ—οΈBridging to Testnet
    • πŸ“€Move to/from CEX
  • $MODE
    • 🟑MODE Tokenonomics
    • 1️⃣Season 1 (ended)
    • 2️⃣Season 2 (ended)
    • 3️⃣Governance Season 3 (ended)
      • Governance Contract Addresses
    • 4️⃣Mode Governance Season 4
    • 5️⃣Season 5
  • Other Docs
    • πŸ”“General Security
      • πŸ”“Mode L2 Security Model
      • ⛑️Optimism Bug Bounty
      • Security Upgrades
        • 01/08/2024 Bridge Upgrade Fund Rescue
        • 06/08/2024 Mode Mainnet Key Handover
      • πŸ”Audits
    • πŸ”—Official Links
    • 🀘Branding Guidelines
    • ⌨️Node Operators
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. Tutorials

SFS - Sequencer Fee Sharing

Intro to the Sequencer Fee Sharing

When building a layer 2 with the OP stack, block production is primarily managed by a single party, called the sequencer, which helps the network by providing the following services:

  • Providing transaction confirmations and state updates

  • Constructing and executing L2 blocks

  • Submitting user transactions to L1 Until fault proofs are implemented in the OP ecosystem these sequencers are centralized for security and managed by Mode (as every other OP chain) and that’s why Mode benefits from all the sequencer fees generated. That’s where the SFS comes in, giving part of these fees and sharing them with developers that deploy smart contracts.

Developers can earn a share of the network sequencer fees just by registering their contracts in the Fee Sharing Contract. You have to add logic to your smart contract in order to register it in the SFS

The Sequencer Fee Sharing (SFS) contract acts as a registry where all the balances are tracked and stored. Once you deploy your contract and register it in the SFS, you will instantly start earning fees whenever your contract is used. When you register your contract, the SFS mints an NFT as a claim to the earned fees. This NFT is sent to the _recipient that you specify when calling the register function. The SFS NFT allows anyone who possesses it to claim the rewards for that particular smart contract. Whether the NFT is in your wallet or a smart contract, whatever entity tries to withdraw the earnings needs to hold the NFT in order to withdraw funds.

Last updated 1 year ago

Was this helpful?