Proposal to Close HRMP Channel with Parallel Finance (Para ID 2012)

Governance Offchain Discussions
1

This proposal seeks to close the HRMP channel between Astar and Parallel Finance parachain (Para ID 2012) in response to the recent Moonbeam attack.

Closing this channel will halt XCM communication between Astar and Parallel Finance, meaning bridged assets will no longer be transferable between the two chains.

It is recommended to keep the channel closed until the Moonbeam attack has been fully investigated and the issues have been resolved.

2 Likes
2

We don’t have a channel opened with them so no action required from our side.

1 Like
3

Ok good to know.
I used subscan to check for open channels but it seems I wrongly interpreted data.
https://astar.subscan.io/xcm_channel/2012-2006

Thanks for the reply!
If there is no open channel, we can close this post :slight_smile:

4

Yes, Subscan is a bit misleading.

Parallel requested to open a channel with us some time ago, but we never accepted.

The XCM transfers that are visible in the log weren’t done directly via Astar<>Parallel channel, but instead using a multi-chain hop approach. E.g. first transfer funds to one chain, then from that chain transfer it to another chain.

1 Like
5

Thanks for the explanation.

This explains why Subscan shows some transfers from Parallel to Astar and shows no message from Astar to Parallel.

We can definitely close this topic :slight_smile:

6

subscan didn’t support parallel now, don’t think there would be xcm between astar and parallel now

7

That’s what I thought, that there was no open channel with Astar, but thanks anyway, we must remain vigilant.

8

Thank you for the information, Guigou, even though we don’t have an open channel.

Is there a process within the Polkadot ecosystem for handling vulnerabilities, where other parachains are notified if an issue arises on one parachain, allowing them to assess their own systems as well?

9

I agree with the proposal to close the HRMP channel between Astar and Parallel Finance as a precautionary measure. It’s essential to prioritize security until the Moonbeam attack has been fully investigated and resolved. This will help protect the assets and stability of both chains.

10

Security must always be our priority. Whether temporary or permanent, we should consider this vulnerability and close the channel. After the problem is solved, we can discuss whether it will be reopened or not.
From here I would like to convey my get well wishes to the moonbeam team, I hope they solve this problem as soon as possible.