Running a Broker
Broker API

Broker API

The Broker API is a standalone client that exposes Broker functionality via a JSON API interface. It can be obtained from the same location as the chainflip-node, i.e. you can install it via apt, use the provided docker image or compile it yourself from the sources on Github.

Brokers need to run the client for the API themselves, as the Broker holds keys used to sign extrinsics and collect any fees set for Deposit Channels. The API client works by pointing it to an RPC node — also run by the same Broker, ideally.

1. Running Broker API locally

Before you do anything, you need to generate a valid signing_key and fund the associated account. If you are planning to use our Docker setup, instructions on how to generate new keys and fund your account are provided in the github repo.

Option A: Using the pre-compiled binaries

Download the chainflip-broker-api software and the chainflip-node:

apt-get install chainflip-broker-api
apt-get install chainflip-node

For a full list of command line arguments, see chainflip-broker-api --help and chainflip-node --help.

To use the default configuration, run:

  • Testnet
chainflip-node --chain /etc/chainflip/perseverance.chainspec.json --rpc-methods=unsafe
chainflip-broker-api --state_chain.signing_key_file /etc/chainflip/keys/signing_key_file
  • Mainnet
chainflip-node --chain /etc/chainflip/berghain.chainspec.json --rpc-methods=unsafe
chainflip-broker-api --state_chain.signing_key_file /etc/chainflip/keys/signing_key_file

Avoid exposing the chainflip-node publicly with these settings, as anyone could redeem your earned fees!

Option B: Running the Broker API with Docker Compose

Alternatively, for a quick start with the Broker API, we have provided a docker-compose setup that runs the Broker API and a State Chain node (required).

2. Registering the account

After being funded, before you can fully interact with the Broker API, your account needs to be registered as a Broker account.

Command line arguments and defaults

  • The state_chain.ws_endpoint should point at a synced Chainflip State Chain RPC node. The default is ws://localhost:9944 — assuming it is run locally.
  • The state_chain.signing_key_file should be the Broker's private key for their on-chain account. The account should be funded. The account type should be set to Broker. The default is /etc/chainflip/keys/signing_key_file.
  • The port is the port on which the Broker will listen for connections. Use 0 to assign a random port. The default is 80.
chainflip-broker-api --help
    chainflip-broker-api [OPTIONS]
    -h, --help
            Print help information
        --port <PORT>
            The port number on which the broker will listen for connections. Use 0 to assign a
            random port. [default: 80]
        --state_chain.signing_key_file <SIGNING_KEY_FILE>
            A path to a file that contains the broker's secret key for signing extrinsics.
            [default: /etc/chainflip/keys/signing_key_file]
        --state_chain.ws_endpoint <WS_ENDPOINT>
            The state chain node's rpc endpoint. [default: ws://localhost:9944]
    -v, --version 
            Print the version of the API

3. Using the Broker: RPC Methods



  • source_asset: Source asset.
  • destination_asset: Egress asset.
  • destination_address: Egress Address.
  • broker_commission: Broker Commission in basis points (100th of a percent or 0.01%). Broker operators can choose to charge a fee for the use of their endpoint, and can be set at any value from 1 basis point to 1000 basis points (0.01% - 10%).
  • channel_metadata: (Optional) Cross-chain message metadata as a JSON object: {"gas_budget": <amount>, "message":<hex_string>, "cf_parameters": <hex_string>}. Where message and cf_parameters are hex encoded strings.
  • boost_fee: (Optional) Maximum accepted boost fee in basis points (100th of a percent).
  • affiliate_fees: (Optional) Array of affiliate brokers (up to 5).

Where every affiliate broker is defined as follow:

	account: AccountId, 
	bps: BasisPoints,

The total broker fee is the sum of the broker_commission + all the affiliate_fees.






  • null if successful, otherwise an error.
curl 'http://localhost/' \
  -H 'accept: application/json' \
  -H 'content-type: application/json' \
  --data-raw '{"id": 1, "jsonrpc": "2.0", "method": "broker_register_account"}' | jq


Withdraw all accumulated fees for a given asset.



  • tx_hash: Hash,
  • egress_id: [ForeignChain, Number],
  • egress_amount: Amount,
  • egress_fee: Amount,
  • destination_address: Address,

Example input:

curl 'http://localhost/' \
  -H 'accept: application/json' \
  -H 'content-type: application/json' \
  --data-raw '{"id": 1, "jsonrpc": "2.0", "method": "broker_withdraw_fees", "params": {"asset": {"chain": "Ethereum", "asset": "ETH"}, "destination_address": "0xabababababababababababababababababababab"}}' | jq

Example output:

  "jsonrpc": "2.0",
  "result": {
    "tx_hash": "0x736c159fec96ea84b8eceb49258019625a17e68ab981a3a674261e1df00a0482",
    "egress_id": [
    "egress_amount": 99998499999503000,
    "egress_fee": 490000,
    "destination_address": "0xabababababababababababababababababababab"
  "id": 1

Working Example

This example assumes the node that is exposing the Statechain RPC's is funded.

  1. Open a terminal and run:
RUST_LOG=info chainflip-broker-api \
    --state_chain.ws_endpoint=ws://localhost:9944 \
    --state_chain.signing_key_file /etc/chainflip/keys/signing_key_file \
    --port 62378 # or whatever port you want to use

It will print 🎙 Server is listening on and continue to run.

  1. Open another terminal and run:

Register as a broker if you are not already.

curl 'http://localhost:62378/' \
  -H 'accept: application/json' \
  -H 'content-type: application/json' \
  --data-raw '{"id": 1, "jsonrpc": "2.0", "method": "broker_register_account"}'
  1. Request a swap deposit address:
curl 'http://localhost:62378/' \
  -H 'accept: application/json' \
  -H 'content-type: application/json' \
  --data-raw '{"id": 1, "jsonrpc": "2.0", "method": "broker_request_swap_deposit_address", "params": ["ETH", "FLIP","0xabababababababababababababababababababab", 0]}'

The result is the hex encoded deposit address, channel id, expiry block, and the issued block:



  • The current API architecture supports only ws and not wss.



Assets are specified as a { chain, asset } object, where the chain is as described below, and the asset is an upper-case string.

Where the chain is unambiguous (for example for the native currencies), the asset can be submitted simply as the upper-case string.

For example, for BTC, "BTC" and { chain: "Bitcoin", asset: "BTC" } are both valid and resolve to the same asset.

Assets returned from the RPCs will always take the explicit form, for example { chain: "Ethereum", asset: "ETH" }


Chains are specified as the full name of the chain, capitalised, for example "Ethereum", "Bitcoin", "Polkadot".


Addresses should be encoded according to their host chains:

  • Ethereum addresses should be encoded as Hex strings, for example "0xfa36e03defc6e4d140cc61fcaab9d1fbef18642f".
  • Polkadot addresses can be encoded using SS58 or Hex strings, for example: "13zyEWmmLDx63Y99TL9SkxBe1DqPVCrcjXytxM3ZHGRyEJV5" or "0x84aec0876dbb3cb7391eeded2eef5fbcf0d1a34f7c9f86f9af205f944b461761"
  • Bitcoin addresses should be encoded using the appropriate bitcoin standard for the address type. For example "tb1qw508d6qejxtdg4y5r3zarvary0c5xw7kxpjzsx" is a valid bech32 address on Bitcoin testnet.