Brotocol
Developers
Introduction
Introduction
  • 👊Introduction
    • What is Brotocol?
      • ✨Brotocol 101
    • Getting Started
      • Supported Wallets
        • How to Connect your Wallet
    • What is Bonbori?
      • Why Bonbori?
      • Bonbori Consensus Model
  • 🌉Features
    • BroSwap
      • DEX Aggregation
      • How to swap Non-bridgeable Tokens?
    • BroBridge
      • How Brotocol Bridge Works?
    • Explorer
      • Active Notifications
  • Reserves
    • What is aBTC?
    • What is aUSD?
  • 🎮Developers
    • Smart Contracts
      • btc peg-in endpoint
      • btc-peg-out-endpoint
      • meta peg-in endpoint
      • meta peg-out endpoint
      • cross-peg-in-endpoint
      • cross-peg-out-endpoint
      • brotocol-staking
      • BridgeEndpoint
    • Add a New Chain
    • Supported Blockchains and Tokens
    • Security Audits
    • Integrations
      • Bitcoin
      • Bitcoin L2s or EVMs
  • 🖼️Media Kits
    • Official Links
Powered by GitBook
On this page
  • 🧩 Overview
  • ✅ Integration Requirements
  • 🔧 Integration Steps
Edit on GitHub
  1. Developers

Add a New Chain

PreviousBridgeEndpointNextSupported Blockchains and Tokens

Last updated 21 days ago

Want to bring your chain into the Brotocol ecosystem?

Whether you're an L1, L2, or appchain team, integrating with Brotocol opens your users to native Bitcoin liquidity, cross-chain swaps, and secure bridging—all while preserving Bitcoin as the settlement layer.

Here’s how to get started:


🧩 Overview

To support a new chain, Brotocol deploys a smart contract called an Endpoint, which acts as the entry and exit point for cross-chain asset transfers. These Endpoints are governed by multisigs (e.g. Gnosis Safe, ExecutorDAO) and coordinated through the Bonbori consensus layer.

Once deployed, your Endpoint becomes part of the BroBridge routing network—supporting swaps, payments, and bridging for supported assets.


✅ Integration Requirements

To be eligible for integration, your chain should support:

  • ✅ Smart contract deployment (EVM-compatible or custom logic)

  • ✅ Reliable block finality for message validation

  • ✅ Token standards (ERC-20 or equivalent) for fungible assets

  • ✅ A relayer-friendly RPC interface for transaction submissions

For Bitcoin L2s or non-EVM chains, custom integration paths are available. Reach out to the team for support.


🔧 Integration Steps

1. Contact the Brotocol Team

Reach out via Discord or email to start the process. Provide basic info:

  • Chain name & website

  • RPC endpoints & explorers

  • Token assets you want to support

  • Dev contact for coordination

2. Deploy Endpoint Contract

Brotocol will deploy an Endpoint contract to your chain. This contract:

  • Receives incoming assets

  • Validates cryptographic proofs from Bonbori validators

  • Releases assets to users or contracts

Endpoints are owned by a multisig for security and flexibility.

3. Configure the Endpoint

Once deployed, the following parameters are set:

  • Approved token list

  • Validator set & thresholds

  • Fee structure

  • Supported swap paths (optional)

4. Enable Relayer Support

Brotocol relayers will monitor your chain’s Endpoint and submit proofs to/from other chains.

5. (Optional) Deploy Synthetic Assets

If your chain doesn’t natively support a desired asset (e.g., BTC), a synthetic version (e.g., aBTC or aUSD) may be deployed and mapped to real assets via BroBridge.

🎮