Skip to main content
1

Contract Implementation

Implement HTLC with recoverable secret generation for the new network on its own main-add-<network> branch of the contracts repo. Networks are developed and tested on their branch, then merged into main once production-track and published on the Deployments page.
2

Solver Agent Implementation

If there is no existing implementation (e.g., EVM), implement the Solver Agent Chain Library for the new network (functions for interacting with deployed HTLC contracts on specific chains). See the Solver Implementation spec.
3

Run Solver

Run a Solver for two networks—one well connected to others (already active Solvers) and the new network.
4

dApp Implementation

If there is no existing implementation (e.g., EVM), implement the Client Chain Library for the new network (functions for interacting with wallets on specific chains, subscribing to contract events, and composing user transactions). See the dApp Implementation spec.
5

dApp Deploy

Create a pull request for a popular bridge UI or fork and deploy a separate UI.
These steps can be performed independently without needing permission or interaction with any party or entity — anyone can open a main-add-<network> branch and start integrating a new chain. The network-adding process in the TRAIN protocol is similar to adding an ERC20 token to the Uniswap protocol, making bridging trustless and permissionless; a network graduates to main and to the Deployments page once its implementation is complete and verified end-to-end. The detailed implementation steps can be found in the Solver Implementation spec.