Search

Search for projects by name or address

Butter Network logo
Butter Network

About

Liquidity bridge and messaging protocol using the MAP relay chain (an alt-L1) and its light-client network to verify cross-chain messages.


    Last 24h volume
    $241.41 K
    Last 24h transfer count
    247
    Last 24h top path
    polygonposbsc$105.54 K

    Last 24h avg. transfer time
    1m 50s
    Last 24h avg. transfer value
    $977.37
    Tokens by volume
    USDTUSDCETH

    Transfer size
    Under $100
    $100-$1K
    $1K-$10K
    $10K-$100K
    Over $100K

    Transfer type distribution
    Non-minting

    About

    Liquidity bridge and messaging protocol using the MAP relay chain (an alt-L1) and its light-client network to verify cross-chain messages.

    Top token

    Volume
    $230.22 K
    Transaction count
    237
    Symbol
    Last 24h Volume
    Last 24h transfer count
    Last 24h avg. transfer time
    Last 24h avg. transfer value
    From
    To
    Timestamp
    Tokens
    Value
    Bridge
    Transfer time
    Chains
    2026 August 05, 07:34 UTC
    8changes

    Butter interop protocol init disco: validation checks BLS sigs of a validator set on an external L1 (MAP Protocol). Validators can update the set with the discovered quorum. Each bridge tx verifies a merkle proof agains validator-signed block headers from the external L1. The L1 is supposed to run light clients of all participating chains.

    Initial discovery

    + Status: CREATED
    contract Butter Bridge (base:0x0000317Bec33Af037b5fAb2028f52d14658F6A56) [butternetwork/Bridge]
    +++ description: Butter's Base bridge endpoint. Outbound transfers lock or burn assets and emit messages for the MAP relay chain; inbound transfers execute only after a LightNode-validated receipt proof for the configured MAP relay contract. The bridge can mint configured mintable tokens, release escrowed assets, and invoke receiver callbacks, so compromise of validation, relay configuration, or management authority can lead to loss of bridged funds.
    + Status: CREATED
    contract Butter MAP LightNode (base:0x0001805c0B57DBd48B5c5c26E237a135dDC678ae) [butternetwork/LightNode]
    +++ description: Upgradeable MAP relay-chain light client used by Butter bridges. It verifies relay-chain headers with the stored BLS validator set and verifies receipt Merkle proofs against accepted headers. It is the destination-chain validation boundary for bridged messages.
    + Status: CREATED
    EOA (base:0x386ce1a187eC7329CFb8E467EB02FB07c698256A)
    +++ description: None
    + Status: CREATED
    contract SafeL2 (base:0x9987463102993e177b107e0cE97a0420428D1999) [GnosisSafe]
    +++ description: None
    + Status: CREATED
    contract SafeL2 (base:0xAAAaEE7549a61282F2B4Ca1766f46249D9e71aaA) [GnosisSafe]
    +++ description: None
    + Status: CREATED
    contract Butter AuthorityManager (base:0xACC31A6756B60304C03d6626fc98c062E4539CCA) [butternetwork/AuthorityManager]
    +++ description: OpenZeppelin AccessManager-derived authority for Butter's restricted Bridge and FeeService functions. Its role configuration controls who can change bridge validation dependencies, relay and token settings, fee parameters, pause state, and implementation upgrades.
    + Status: CREATED
    contract Butter VerifyTool (base:0xc3393567DC2F1d071254E880c9f501641491471f) [butternetwork/VerifyTool]
    +++ description: Cryptographic and RLP/Merkle-proof helper contract called by the Butter MAP LightNode to validate relay-chain headers and transaction receipts.
    + Status: CREATED
    contract Butter FeeService (base:0xfeE31a1FD7FcA0E05428ff751242e46F6D5769a6) [butternetwork/FeeService]
    +++ description: Fee configuration contract used by Butter Bridge to calculate cross-chain message fees and select the fee recipient.

    Base Chain

    Actors:

    A Multisig with 3/5 threshold.

    • Can interact with Butter AuthorityManager
      • change AuthorityManager permissions and execute restricted Bridge and FeeService management operations

    A Multisig with 2/3 threshold.

    • Can interact with Butter AuthorityManager
      • change AuthorityManager permissions and execute restricted Bridge and FeeService management operations
    • Can upgrade with no delay
      • Butter MAP LightNode
    • Can interact with Butter MAP LightNode
      • change the pending LightNode administrator or the VerifyTool used by proof verification

    Base Chain

    Butter AuthorityManager0xACC3…9CCA

    OpenZeppelin AccessManager-derived authority for Butter’s restricted Bridge and FeeService functions. Its role configuration controls who can change bridge validation dependencies, relay and token settings, fee parameters, pause state, and implementation upgrades.

    • Roles:
      • adminRole: SafeL2

    Butter’s Base bridge endpoint. Outbound transfers lock or burn assets and emit messages for the MAP relay chain; inbound transfers execute only after a LightNode-validated receipt proof for the configured MAP relay contract. The bridge can mint configured mintable tokens, release escrowed assets, and invoke receiver callbacks, so compromise of validation, relay configuration, or management authority can lead to loss of bridged funds.

    • Roles:
      • authority: Butter AuthorityManager

    Upgradeable MAP relay-chain light client used by Butter bridges. It verifies relay-chain headers with the stored BLS validator set and verifies receipt Merkle proofs against accepted headers. It is the destination-chain validation boundary for bridged messages.

    • Roles:
      • admin: EOA 1
    Can be upgraded by:
    Butter VerifyTool0xc339…471f

    Cryptographic and RLP/Merkle-proof helper contract called by the Butter MAP LightNode to validate relay-chain headers and transaction receipts.

    Butter FeeService0xfeE3…69a6

    Fee configuration contract used by Butter Bridge to calculate cross-chain message fees and select the fee recipient.

    • Roles:
      • authority: Butter AuthorityManager

    The current deployment carries some associated risks:

    • Funds can be stolen if a contract receives a malicious code upgrade. There is no delay on code upgrades (CRITICAL).