Configuring static peers on startup

[IvanWeber42]

I am currently replacing op-geth with op-reth as the execution client. Op-geth used to be configured to have a set list of trusted and static nodes that would serve as trusted and static peers during syncing, however it seems that there is no way to add static peers via configuration file or options parameter.

Trusted peers can be added, and judging from the code this should be enough since a trusted peer is essentially a static peer with additional stuff going on (again, if my reading of the code is correct). If this is so, simply adding trusted peers should be enough.

My questions are as follows:

1. Is there a way to setup static peers in config file or CLI parameter?
2. Is a trusted peer in Reth a static peer with extra stuff going on?
3. If 1 is not possible and 2 is not true, what's the best way to add static peers, with admin_addPeer?

[mattsse]

If this is so, simply adding trusted peers should be enough.

yeah this should do it.

Is a trusted peer in Reth a static peer with extra stuff going on?

yes trusted peer is static and more, for trusted we free up slots and always allow incoming connections

Is there a way to setup static peers in config file or CLI parameter?

the distinction is a bit tricky and only really exists because the rpc api distinguishes between static and trusted, so for this usecase you could always use --trusted-peers