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
{{ message }}
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
In verifyPartnerChainOutboxRoot it should use own chainID to generate outboxKey and use it to verify inclusion of outboxKey on the stateRoot of sending chain.
Actual behavior
In verifyPartnerChainOutboxRoot its using sendingChainID for outboxKey instead of ownChainID
Steps to reproduce
Send CCU using chain connector plugin and observe the Inclusion proof verification error
Which version(s) does this affect? (Environment, OS, etc...)
v6.0.0-alpha.15
The text was updated successfully, but these errors were encountered:
Expected behavior
In verifyPartnerChainOutboxRoot it should use own chainID to generate outboxKey and use it to verify inclusion of outboxKey on the stateRoot of sending chain.
Actual behavior
In verifyPartnerChainOutboxRoot its using sendingChainID for outboxKey instead of ownChainID
Steps to reproduce
Send CCU using chain connector plugin and observe the Inclusion proof verification error
Which version(s) does this affect? (Environment, OS, etc...)
v6.0.0-alpha.15
The text was updated successfully, but these errors were encountered: