Help debug and mitigate Kusama XCM issue
2 years ago
xcm
development
Executed
The new Kusama runtime 1000000 introduced a XCM bug that can result partially executed XCM and stuck of funds.
I worked with Parity devs to debug and identify the root cause of the bug, create a Github issue described action items, a twitter thread explaining the bug, suggestion to parachain teams to workaround the issue. I also created a test script using Chopsticks to reproduce the issue, and use it to verify the fix.
I will also work with Fellowship to setup e2e tests and regression tests for future releases. But this can be considered out of scope of this tip.
Comments (4)
Requested
10.00K DOT
Proposal Passed
Summary
0%
Aye
0%
Nay
Aye (327)0.0 DOT
Support0.0 DOT
Nay (5)0.0 DOT
This tip makes sense to me, but since the account does not have an identity attached, can you add some proof that this is actually Bryan? I see the "HyBryan" in the account name and the fact that this is a quite old account with an index, so I assume it is, but before voting I'd like to see some evidence.
@BILL
Follow-up: I see he referenced this from his Matrix account. That is good enough for me and I will vote in favor.
This is well deserved and your work has saved us hours of debugging for something which has been caused by a relaychain update and potentially affects many if not all parachains