Skip to main content

What Is a Chainflip Broker?

A Chainflip broker is the account that submits swap requests to the Chainflip State Chain on behalf of users. This page explains what a broker does, why brokers pay FLIP, how spam protection works, and the difference between running your own broker and using a hosted one.

For how the swap itself is settled, see How Cross-Chain Swaps Work. Terms are defined in the glossary.

What a broker does​

A broker facilitates starting a swap on behalf of end users. It provides an endpoint to the State Chain, Chainflip's own blockchain, which takes the user's swap details, opens a deposit channel on the State Chain, and returns the extrinsic hash of that request (Chainflip: Brokers). The deposit channel can be verified through a secondary source, such as Chainflip's explorer, before the user sends funds to its address (Chainflip: Deposit Channel Swaps).

Without a broker, users would have to include complex swap metadata in their deposits to Chainflip's vaults, which raises their transaction costs and needs specialised wallets and SDK integrations. Any State Chain account can play the role of a broker (Chainflip: Brokers).

Why brokers pay FLIP​

Each request a broker submits to the State Chain is an extrinsic, a State Chain transaction, and the broker pays a small transaction fee in FLIP, Chainflip's token, for each one; these FLIP transaction fees are burned (Chainflip: Brokers). Chainflip's deposit-channel documentation adds a "Channel Fee" for opening a channel, and suggests funding the broker's State Chain account with 10 FLIP (Chainflip: Deposit Channel Swaps).

The user does not pay these fees directly: the broker pays them on the user's behalf.

Bitcoin vault swaps need one more thing. A broker that offers them must first open a private Bitcoin channel, a persistent deposit channel unique to that broker, and opening it requires a bond of 100 FLIP: the broker must keep at least 100 FLIP on its account until it closes the channel, when the bond is released (Chainflip: Bitcoin Vault Swaps; Chainflip: Broker API requests). Brokers that only offer deposit channels, or vault swaps from other chains, do not need it.

Spam protection​

Because the broker pays for every request it submits, it bears the cost of spam: if its endpoint is abused, it pays the associated transaction fees. Chainflip therefore expects brokers to protect against spam attacks. A private broker, used only by its operator, sidesteps the problem; a public broker must protect its web interface or API and filter the requests it accepts (Chainflip: Brokers).

With a hosted broker such as Broker as a Service, the operator of the broker handles this protection; you do not run a public State Chain endpoint yourself.

Broker fees and affiliates​

A broker can charge a broker fee for the use of its endpoint, in basis points (1 bps = 0.01%). Chainflip limits the broker commission (broker_commission) to 1000 bps, or 10% (Chainflip: Brokers).

A broker can share its commission with affiliates: service providers that offer Chainflip swaps to their users through the broker, without interacting with the network directly (Chainflip: Broker Affiliates). Affiliates are registered on-chain with an Ethereum withdrawal address for their earned commission, and a broker can have up to 256 affiliates registered at once. A deposit-channel request can carry up to 5 affiliate entries, each with its own rate, and the total broker fee is the broker commission plus all affiliate fees (Chainflip: Broker API requests).

Do you need a broker?​

For a deposit-channel swap, yes: a broker submits the request that opens the channel on the State Chain (Chainflip: Brokers).

A vault swap bypasses the deposit channel: the user sends funds directly to a Chainflip vault, or calls the vault contract, with all the swap information encoded in the transaction (Chainflip: Vault Swaps). Building that encoded transaction still needs a tool that knows the format, such as Broker as a Service's vault swap payloads.

Run your own broker or use a hosted one​

Running your own broker means you register and operate a State Chain account as a broker, fund it with FLIP, run the broker endpoint, keep it updated and available, and protect it from spam (Chainflip: Brokers; Chainflip: Deposit Channel Swaps). You control the broker account and set its fee yourself.

Using a hosted broker means another party operates the broker. With Broker as a Service:

  • Broker as a Service operates the broker, its FLIP-funded State Chain account and its endpoint, and handles updates, availability and spam protection (Use Cases).
  • Broker as a Service has opened the private Bitcoin channel and posts its 100 FLIP bond, so you can offer Bitcoin vault swaps without holding FLIP yourself.
  • You get an API key and a dashboard (Getting Started).
  • When you sign up, Broker as a Service registers an affiliate account for you under its broker, paying out to the Ethereum address you enter for your commissions (Register Account). You configure your commission, and it is credited to that affiliate account (migration guide).
  • Broker as a Service adds a 5 bps operating fee to each swap (Pricing).

The trade-offs are control against operational work, how the total fee is split, and the effort of moving an existing integration. If you already run a broker, the migration guide covers moving to a hosted one.

Where BaaS fits​

Broker as a Service is a hosted Chainflip broker. A standard signup registers your affiliate account under it, and you configure your commission in the dashboard. Your application then calls the REST API, or the Chainflip Broker RPC API, a JSON-RPC drop-in for code written against the native broker and the Chainflip SDK. Broker as a Service sets your configured commission on every request, so a client cannot lower it (Use Cases: Commission Protection; Chainflip Broker RPC API).

Sources​

All sources were accessed on 2026-11-18.