Skip to content

validate communicating with correct sequencer chain #986

@joroshiba

Description

@joroshiba

We should add a check to conductor, composer, and sequencer relayer to validate that the sequencer RPC they communicate with is of the expected Astria sequencer network.

It is possible that RPCs change, or are confusingly named. On startup the services should validate this. There should be an env var specifying the expected chain id and then it can be verified from genesis file.

### Tasks
- [x] composer verify chain id on startup
- [x] sequencer-relayer verify sequencer chain id on startup
- [x] conductor verify sequencer chain id on startup

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions