<aside> 🤑 If you would like Skip to integrate your chain with the Skip API, please fill out the following template to provide us with the necessary information and complete the included configuration steps. The information provided will guide our engineering efforts to facilitate the integration.

</aside>

<aside> 🖨️ This notion doc is intended to serve as a template and a helpful jumping off point for you. You can use the “Duplicate” button to copy it into your own Notion to get started.

</aside>

<aside> 🆘 Getting connected to IBC, Axelar, or Hyperlane can be hard. Even choosing among them is a challenge. We're happy to provide guidance and hands-on support to serious teams early in their journey -- even before they've made a choice of interop protocol if helpful!

Please reach out to [email protected] or tg:@bpiv400 if you need help getting started

</aside>

1. General Information

• Team:
• Team Contact Name:
• Team Contact Telegram:
• Team website:
• Chain Name (if different from team name):
• Chain website (if different from team name):
• Chain Documentation Link (including docs for running a full node):

2. Chain Requirements

• [ ] Publicly available instructions for running a full node, usually including:

  • [ ] Link to genesis file
  • [ ] Full node binary or instructions for building binary from source code
  • [ ] Public peer / seeder node list
  • [ ] Public full node RPC list

• [ ] Chain documented in a popular chain registry (e.g. https://github.com/cosmos/chain-registry) —> PROVIDE LINK

  At minimum a Cosmos chain must have the following information documented in the registry:

  • [ ] chain id
  • [ ] website
  • [ ] chain name (and optionally “pretty name”)
  • [ ] bech32 prefix
  • [ ] slip44 (aka “coin type”)
  • [ ] Fee information (with denom, low price, average price, and high price)
  • [ ] Logo URIs
  • [ ] Persistent peer list
  • [ ] Public RPC list

• [ ] Support for at least one of the following interop protocols:

  • [ ] IBC
  • [ ] Hyperlane
  • [ ] Axelar

  Provide any additional details or documentation links, especially if there is anything bespoke about the support (e.g. The chain does not use IBC-go but uses a different implementation of the IBC protocol)

3. Additional Questions about the chain

• Is the chain built using the Cosmos SDK or is it a standard EVM chain? If not, please provide additional details regarding the details of how the chain is built (e.g. GETH, OP GETH) and additional documentation regarding transaction + message construction, querying IBC state, querying IBC events.
• Does the chain support packet forward middleware (PFM)? We strongly recommend adding this
• Please list all the chains you think your chain will directly interoperate with over IBC