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
As @dlipicar suggested, it would be good to have a link between HealthChecker statuses and RPCProviders we store in networks.
HealthChecker aggregates RPC client states per chain and per provider. Currently, it stores a map of provider statuses with a circuitName key, which is not convenient for mapping status to actual RPC providers.
Ideally, the RPCProvider should have a unique ID. Currently it's Name + ChainID
The text was updated successfully, but these errors were encountered:
friofry
changed the title
Add RPCProvider Name to HealthChecker results
Add RPCProvider unique ID to HealthChecker chain statuses
Jan 17, 2025
As @dlipicar suggested, it would be good to have a link between HealthChecker statuses and RPCProviders we store in networks.
HealthChecker aggregates RPC client states per chain and per provider. Currently, it stores a map of provider statuses with a circuitName key, which is not convenient for mapping status to actual RPC providers.
Ideally, the RPCProvider should have a unique ID. Currently it's Name + ChainID
The text was updated successfully, but these errors were encountered: