You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So far our event design does not accommodate for connecting an e3_id to a particular evm chain_id.
We should some how keep track of this and specify multiple chains on startup to track using cli args
A request that originates on a specific evm chain should end on a specific chain and be clear to the aggregator that is posting to the chain the request came from
The text was updated successfully, but these errors were encountered:
So far our event design does not accommodate for connecting an e3_id to a particular evm chain_id.
We should some how keep track of this and specify multiple chains on startup to track using cli args
A request that originates on a specific evm chain should end on a specific chain and be clear to the aggregator that is posting to the chain the request came from
The text was updated successfully, but these errors were encountered: