Generate distinct Channel/Connection identifiers when running tests #4062
Labels
channel-upgradability
Channel upgradability feature
needs discussion
Issues that need discussion before they can be worked on
nice-to-have
testing
Testing package and unit/integration tests
Milestone
Summary
Subtle bugs can slip through when we use the same channel/connection (client?) identifiers since many of the verification functions expect those to verify the given proofs. These will work in our testing environment but would fail in the most common real-life case where identifiers are unique.
Case in point: #4052. A similar bug was also found in UpgradeCancel after forcing distinct identifiers for channels.
One possible hacky solution is forcing a channel/connection init in the coordinators functions before actually setting up the connection/channel (hack inspiration #4052 (comment)). This was we ensure distinct connection/channel identifiers for our internal tests.
For Admin Use
The text was updated successfully, but these errors were encountered: