-
Notifications
You must be signed in to change notification settings - Fork 54
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
switch minSigners
to f
in RMNRemote & RMNHome
#1495
switch minSigners
to f
in RMNRemote & RMNHome
#1495
Conversation
LCOV of commit
|
f
in RMNRemote & RMNHome
f
in RMNRemote & RMNHomeminSigners
to f
in RMNRemote & RMNHome
@@ -92,10 +92,13 @@ contract RMNRemote is OwnerIsCreator, ITypeAndVersion, IRMNRemote { | |||
Signature[] calldata signatures, | |||
uint256 rawVs | |||
) external view { | |||
(bool enabled, uint64 f) = (s_config.enabled, s_config.f); |
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.
That's pretty non-standard notation. Both are also used only once, does inlining te storage read really add a significant amount of gas?
0cff04e
to
9468868
Compare
Quality Gate passedIssues Measures |
closing in favor of smartcontractkit/chainlink#14817 |
Pull request was closed
Motivation
In CCIPHome we have a requirement on the number of supporting oracles, but on RMNHome we have a laxer requirement of n >= minObservers which is not ideal (this was also in the initial sketch). If we have n=minObservers then liveness is not guaranteed. If we express f=minObservers-1, then we need at least n >= 2f+1 for liveness.
Similar story in RMNRemote for f=minSigners-1, where n >= 2f+1 would also be required for liveness.
Solution
Drop the minObservers/minSigners in favor of f for uniformity with CCIPConfig