-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement v2 sharding and chain ID detection #837
Implement v2 sharding and chain ID detection #837
Conversation
4e99495
to
b79ee72
Compare
keyDefaultChainSetting = "default" | ||
defaultShardID = 0 | ||
minShardCount = 1 | ||
defaultTargetCount = 3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI - default target is 6 https://github.com/forta-network/forta-assigner/blob/9d2091deb6ab51ec0d1657e6607206854afadc39/domain/chain.go#L8
Though I think I want the assigner to switch to 3, but still, it's 6 for now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we deploy a v2 bot in dev right now, we get 3 assignments, not 6, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to be crystal clear that the default is always 3 for every scanned source - can't afford to default to 6 for an unknown reason. Chain ID and shard ID detection is strictly based on how many assignments are expected.
No description provided.