-
Notifications
You must be signed in to change notification settings - Fork 2
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
Accept home chain selector id in commit plugin factory #140
Conversation
@@ -358,6 +358,7 @@ type OCR3Config struct { | |||
F uint8 `json:"F"` | |||
OffchainConfigVersion uint64 `json:"offchainConfigVersion"` | |||
OfframpAddress []byte `json:"offrampAddress"` | |||
RmnHomeAddress []byte `json:"rmnHomeAddress"` |
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.
This will cause all tests to fail because this is not on-chain yet. I think we should remove this for now and maybe add later when its finally in there?
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.
Would it be just empty? We are not using it (under the rmn feature flag).
It seems like ccip integ test are passing here: smartcontractkit/chainlink#14500
Test Coverage
|
|
Accept the hom chain selector id in the under the
rmnEnabled
flag (otherwise integration test will fail as the RMNHome contract is not ready + RMNHomeAddress is not yet defined in OCR3Config.The Commit factory will instantiate a
RMNHome reader
per plugin instance as thermnHomeAddress
is part of the OCR3Config, hence not uniquely defined (1 per don id)The build of
chainlink
is failing: here is the PR to mirror the interface changes made in this PR: smartcontractkit/chainlink#14500.