Expand description
Message delivery loop. Designed to work with messages pallet.
Single relay instance delivers messages of single lane in single direction. To serve two-way lane, you would need two instances of relay. To serve N two-way lanes, you would need N*2 instances of relay.
Please keep in mind that the best header in this file is actually best finalized header. I.e. when talking about headers in lane context, we only care about finalized headers.
Structs§
- Client
State - State of the client.
- Clients
State - Both clients state.
- Message
Delivery Params - Message delivery race parameters.
- Message
Details - Message details.
- Message
Proof Parameters - Message delivery race proof parameters.
- Nonces
Submit Artifacts - Artifacts of submitting nonces proof.
- Params
- Message lane loop configuration params.
Traits§
- Batch
Transaction - Batch transaction that already submit some headers and needs to be extended with messages/delivery proof before sending.
- Source
Client - Source client trait.
- Target
Client - Target client trait.
Functions§
- metrics_
prefix - Return prefix that will be used by default to expose Prometheus metrics of the finality proofs sync loop.
- run
- Run message lane service loop.
Type Aliases§
- Message
Details Map - Messages details map.
- Source
Client State - State of source client in one-way message lane.
- Target
Client State - State of target client in one-way message lane.