Protocol Concepts
dApp
Explains the details of the dApp using the protocol

TRAIN Bridging Interface
Overview
The TRAIN Bridge dApp serves as the central interface for seamless cross-chain transactions. It integrates with the Discovery mechanism to fetch available Solvers and participates in the Solver auction process to determine optimal routes for bridging.
The dApp has three main responsibilities:
- Connecting to the Discovery registry and fetching available Solvers/networks.
- Connecting to the Auction to transmit the user’s intent and get quotes from Solvers.
- Executing an Atomic Swap flow.
Observing the Destination Network
The dApp must observe the destination lock created by the Solver and provide the hashlock
to the user to complete the atomic swap process. Observing this transaction can be done in the following ways, in order of priority:
- Bootstrap a Light Client (e.g., Helios) for the destination chain and read the lock state from it.
- If there is no Light Client available, read and verify the lock state from multiple RPC providers.