Gateway: GetTransferConfigsForAll

Get transfer configs for cBridge transfer functionality

REST API

Get chains and corresponding tokens supported by cBridge

GET https://cbridge-prod2.celer.app/v2/getTransferConfigsForAll

By using this method, you can find chains' and tokens' information for cBridge testnet transfer, you can use cBridge production endpoint for mainnet configs

200: OK

{
    // Response
}

Request Parameters

None

Response Parameters

Name	Type	Description
chains	Array<Chain>	All supported chains' info
chain_token	Map<Number, ChainTokenInfo>	Supported tokens info for each chain. Key is chain_id
farming_reward_contract_addr	String	cBridge farming reward contract address
pegged_pair_configs	Array<PeggedPairConfig>

Chain

Name	Type	Description
id	UInt32	chain id
name	String	chain name
icon ​ ​	String	chain icon url
block_delay	UInt32	block delay for transaction confirmation
gas_token_symbol	String	gas token
explore_url	String	This chain's browser's url
contract_addr	String	cBridge contract address on this chain

ChainTokenInfo

Name	Type	Description
token_list	Array<TokenInfo>	chain supported token list

TokenInfo

Name	Type	Description
token	Token	token detail
name	String	token name
icon	String	token icon url
transfer_disabled	Boolean	token transfer disabled

Token

Name	Type	Description
symbol ​	String	token symbol
address	String	token address
decimal	Number	token decimal
xfer_disabled	Boolean	token transfer disabled

If transfer_disabled or xfer_disabled is true, we cannot transfer the token on the corresponding chain

PeggedPairConfig

Name	Type	Description
org_chain_id	UInt32	source chain id
org_token	TokenInfo	original token info
pegged_chain_id	UInt32	pegged chain id
pegged_token	TokenInfo	corresponding pegged token on pegged chain
pegged_deposit_contract_addr	String	contract address on pagged chain for mint/deposit
pegged_burn_contract_addr	String	contract address on pagged chain for burn/withdraw
vault_version	Number	0 for OriginalTokenVault, 2 for OriginalTokenVaultV2
bridge_version	Number	0 for PeggedTokenBridge, 2 for PeggedTokenBridgeV2

All data inside the configs should not be edited, otherwise it may lead to failure.