Routing ISM #5
Routing ISM #5
Conversation
|
|
||
| When relayers detect a `RoutingIsm`, metadata should be formatted in accordance with the `ISM` type being routed to. | ||
|
|
||
| `RoutingIsms` should avoid conditioning on frequently-changing state, as this may result in a relayer formatting metadata for the wrong `ISM`. |
There was a problem hiding this comment.
Is it necessary to call this out here? This feels like an implementation detail of a relayer.
There was a problem hiding this comment.
Unless you have a workaround to suggest, this seems like good practice, and worth calling out.
There was a problem hiding this comment.
Maybe it's just me but I think RoutingISMs should do whatever they want and relayers should account for their fetching for metadata being out of date by retrying
|
|
||
| `RoutingIsms` should avoid conditioning on frequently-changing state, as this may result in a relayer formatting metadata for the wrong `ISM`. | ||
|
|
||
| ### **Rationale** |
There was a problem hiding this comment.
I assume these sections are to be filled out?
There was a problem hiding this comment.
Tbh not really sure what there is to put, I can't think of any design decisions that merit discussion
There was a problem hiding this comment.
If none apply maybe just a small N/A or something like that would be nice to assert completeness
No description provided.