Abstract
Our XCM monitor noticed that Litmus was no longer producing blocks.
Due to this, I’m proposing closing the XCM channel between Moonriver <> Litmus.
Details
The proposal will call the XCM Transactor pallet with hrmpManage extrinsic with the close option to shut down the 2023 → 2106 XCM channel (and 2106 → 2023).
Tested with Chopsticks with preimage hash 0x9bd482a9a1bd059a5e1c75d3c96d01e179d036c6bb779ac10c0109e7470eb4b5
I support this proposal to close the XCM channel between Moonriver and Litmus. This is a necessary step to ensure the efficiency and security of the XCM network, given that Litmus has stopped producing blocks. Thanks @AlbertoV19 for initiating this and conducting the associated tests.
Alberto & team, thank you for being our XCM heroes and always catching these kinds of issues. It’s definitely an AYE from me and my delegators
Hey @AlbertoV19 all in favor of closing this XCM. Gotta keep the network clean.
I completely agree with you. And I’m backing it up with my vote.
