We should add the Agglayer as a new monitor card so we can track the status of bridges into and out of the network.
The monitor usually follows one of two approaches: consume a status endpoint or run a network workflow itself.
In this case, there’s no status endpoint we can consume directly, and running full bridge-in/out workflows from the monitor would require handling Ethereum-side transactions and events.
After discussing this with Pablo Vigara (didn't found its GH user), we came up with a separate component that runs these workflows and exposes the status of the latest execution. The monitor would only need to consume that endpoint.
A couple of open questions:
- Where should this component live? IMO, it deserves its own repository.
- Which token should the workflows use: the native token, a dedicated test token, or a configurable token?
We should add the Agglayer as a new monitor card so we can track the status of bridges into and out of the network.
The monitor usually follows one of two approaches: consume a status endpoint or run a network workflow itself.
In this case, there’s no status endpoint we can consume directly, and running full bridge-in/out workflows from the monitor would require handling Ethereum-side transactions and events.
After discussing this with Pablo Vigara (didn't found its GH user), we came up with a separate component that runs these workflows and exposes the status of the latest execution. The monitor would only need to consume that endpoint.
A couple of open questions: