Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

In verifyPartnerChainOutboxRoot it should use own chainID #8218

Closed
Tracked by #7210
ishantiw opened this issue Mar 2, 2023 · 0 comments
Closed
Tracked by #7210

In verifyPartnerChainOutboxRoot it should use own chainID #8218

ishantiw opened this issue Mar 2, 2023 · 0 comments
Assignees
Milestone

Comments

@ishantiw
Copy link
Contributor

ishantiw commented Mar 2, 2023

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant