Botanix
Visit websiteTry Testnet
  • Welcome!
  • Get to know the Technology
    • Introduction to Botanix Labs
    • Risk warning
    • Terminology
    • Basic knowledge
      • Proof-of-Stake
      • Ethereum Virtual Machine (EVM)
      • UTXO vs Account Based Model
    • Introductory concepts
      • The Botanix EVM
      • The Spiderchain
      • Orchestrator node
      • Deposit & Withdraw
      • Transaction fees
    • Advanced concepts
      • Bitcoin security inheritance
      • Bridging
      • Consensus
      • Finality
        • Finality in a Proof-of-Work (PoW)
        • Finality in a Proof-of-Stake (PoS)
        • Finality on Botanix EVM
      • Forward security
        • Forward security in cryptography
        • The Spiderchain's Forward Security
        • Inventory management
      • FROST
      • Reth
      • Orchestrators
      • Staking
    • Roadmap to Spiderchain
      • Single Node (Testnet)
      • Botanix Federation
        • Consensus - CometBFT
          • Byzantine Fault Tolerance (BFT)
        • Node types
        • Multisig details - FROST
        • Peg-in / Peg-out
      • Botanix Federation with Staking
      • Slashing
      • Spiderchain DynaFed
      • Permissionless staking
      • Fully Decentralized Layer 2
    • Deeper dive: Whitepaper
  • How to use the Botanix EVM
    • Getting started with the Botanix EVM (testnet)
    • Risk warning
    • Step 1 - Set up your wallet
    • Step 2 - Get test funds
    • Step 3 - Send a transaction
    • Step 4 - Use dApps
    • Step 5 - Deploy your first contract / Launch your own token
    • Step 6 - Withdraw
    • FAQ - Testnet V1
  • Build dApps
    • Introduction
    • Risk warning
    • Tools
      • Useful links
      • Development Frameworks
      • Web3 libraries and tools
      • Oracle Tools
      • Block explorer
        • Routescan
      • Indexers
        • The Graph
        • SubQuery
      • WalletConnect
      • Account Abstraction with BTC Connect
      • Muticall3
    • Build on the Botanix EVM
      • Basic Botanix EVM Information
      • Gas fees
      • Develop a new dApp
      • Migrate existing dApps
      • Quickstart - Build a dApp with Botanix (Solidity, Hardhat)
  • Run a node
    • Introduction
    • Run an RPC Node
  • Glossary
Powered by GitBook
On this page
  • Federation members
  • Non-federation members

Was this helpful?

  1. Get to know the Technology
  2. Roadmap to Spiderchain
  3. Botanix Federation

Node types

Federation members

The Spiderchain is operated by 15 federation members - large exchanges, financial institutions, and Bitcoin-focused companies - geographically distributed all over the world. Botanix Labs only serves as one of the 15 federation members. With no single entity in control and a geographically diverse membership, there is no single point of failure.

The federation members are responsible for verifying pegins, verifying pegouts and following the PBFT consensus for block production. Block production is done via a round-robin system.

Non-federation members

Also non-federation members should be able to run a node. There are however a few differences between federation members and non-federation members:

  1. Non-federation members do not have a BTC server

  2. Non-federation members do not produce blocks

If you want to run your own non-federation node, please visit Run a node.

PreviousByzantine Fault Tolerance (BFT)NextMultisig details - FROST

Last updated 9 months ago

Was this helpful?