Brotocol
CtrlK
DevelopersUsersGo to App
Developers
Developers
  • Introduction
    • Overview
    • How the Bitcoin Bridge Works
  • Deployments
    • Overview
    • Chains
      • Stacks
        • Chains Information
        • Token Approved Pairs
        • Tokens Information
      • EVM
        • Contract Addresses
        • Tokens Information
  • Integrations
    • Overview
    • Add BroWidget
    • Add a New Chain
  • Bonbori
    • Bonbori Consensus Model
  • Brotocol Contracts
    • Overview
    • Chains
      • Stacks
        • BTC Peg-In Endpoints
        • BTC Peg-Out Endpoints
        • Meta Peg-In Endpoints
        • Meta Peg-Out Endpoints
        • Cross Peg-In Endpoints
        • Cross Peg-Out Endpoints
        • Brotocol Staking Manager
      • EVM
        • Bridge Endpoint
    • Security Audits
  • Resources
    • Official Links
    • BroSDK
      • API Reference
      • Go to GitHub
    • Supported Blockchains and Tokens
    • GitHub Pages site
Powered by GitBook
On this page
Edit on GitHub
  1. Brotocol Contracts

Security Audits

As with all crypto technology, risk is real whether using a centralized or decentralized bridge. Some of the more novel decentralized bridges are relatively untested and even those that have been tested are still subject to exploits.

Brotocol is audited by CoinFabrik, covering both the contracts and the backends.

  • 2022-12 Bridge Endpoints

  • 2023-04 Bridge Backend and Endpoints

  • 2023-10 Bitcoin Oracle and Bridge

  • 2024-11 Brotocol Staking Manager

  • 2024-11 Brotocol Peg-out Endpoints

  • 2024-11 Brotocol Peg-in Endpoints

  • 2025-3 Endpoint Update

  • 2025-4 EVM Endpoints

The smart contracts are also subject to our bug bounty programme on Immunefi.

PreviousBridge EndpointNextOfficial Links

Last updated 2 months ago