Archway Networks

This repo contains a registry of Archway protocol based networks, IBC connections to these networks.

Schema files containing the recommended metadata structure can be found in the *.schema.json files located in the root directory. Schemas are still undergoing revision as user needs are surfaced. Optional fields may be added beyond what is contained in the schema files.

Adding new IBC paths

If you are a relayer operator and wish to add a new IBC path connecting to Archway Networks, please follow the below mentioned criteria and create a PR after creating the path.

Requirements for the IBC channel

• Archway client's trusting period should be set to 2/3 of unbonding period e.g. for archway-1 (mainnet) the clients trusting period must be 1209600s
• IBC client for the counter-party chain should also have a trusting period set to exactly 2/3 of the chains unbonding period

Steps to create new IBC paths

We recommend using hermes relayer implementation and use this tutorial to create new paths.

Requesting a new IBC path

If you are a builder on the Archway protocol and/or looking to connect Archway Networks to another chain through IBC, but do not have the expertise or the capacity to operate relayers, you can request the desired IBC relayer from archway community:

• Join Arcwhay Discord
• Use "@Mainnet Validator" or "@Relayer" tag on discord to request a new relay path from within Archway Network operators and partners
  • Suitable channel for such requests: "build-together"
  • You may use the "@Community Mods" discord tag for Archway community moderators and/or the "@DevRel" discord tag for Philabs developer relations team, to ask for help in your search of finding a new relayer partner
• Each relayer connecting the cosmos to Archway networks is eligible for a feegrant to pay for IBC transfer on Archway mainnet. Please check feegrants program below for more details

Monitoring IBC paths

Philabs (on behalf of Archway foundation) is building monitoring tools e.g. relayer_exporter and also leveraging existing tools like chainpulse. These monitoring tools will be used to monitor relayers and IBC paths published on this repo for the following metrics

• Client Expiry
• Total IBC packets transmitted
• Fee paid per packet transmitted
• Redundant packets transmitted
• Stuck packets
• Account balances
  • Philabs operated relayers
  • Foundation feegranter account balance (this account is used to provide feegrants for relayers)
  • External relayers account balances

Feegrants Program

All relayers operating IBC paths connecting to Archway mainnet are eligible for a feegrant to pay for IBC transaction fees on Archway network.

To enable feegrants for your relayer use the following fee granter address and configuration docs for your relayer:

Archway fee granter address: archway1ktka5q3cnsy3ar7qwj2huzz6qj9q4ys7h74l9y

Feegrant selection criteria

• Feegrants programs aims to have availability of maximum 2 to 3 relayers on each published path
• Feegrants will be reviewed based relayer performance and renewed periodically
• Relayer must have local full nodes available for both connecting chains
• Relayer must publish its metadata and signer addresses for both connecting chains. Please use ibc_data_schema.json for schema reference.

Active feegrants

All operators published under _IBC have active feegrants e.g. to see active feegrants for archway <> osmosis path are under operator section of archway-osmosis.json