Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make channel openings to system chains permissionless #325

Closed
Tomen opened this issue May 23, 2024 · 1 comment
Closed

Make channel openings to system chains permissionless #325

Tomen opened this issue May 23, 2024 · 1 comment

Comments

@Tomen
Copy link

Tomen commented May 23, 2024

Currently, HRMP channel openings to system chains require acceptance of OpenGov. I believe this is not in line with the general design of the Polkadot protocol.

System chains are part of the runtime and their primary function is to optimize the configuration of the network towards lowering costs for users. If the relay/JAM is the kernel, then system chains form the operating system. In the words of @joepetrowski, they are an implementation detail.

Parachain access to relay chain features is permissionless, and by extension access to system chain features should be permissionless. System chain features offer basic functionality that should not be denied parachains on a per-case basis.

If parachains would have to request access to system chains via channels, they could get cut off features they already depend on once these features move out of the relay. This would not be consistent.

Thus I propose to fix this design issue by making channel openings to system chains permissionless.

@Tomen
Copy link
Author

Tomen commented May 23, 2024

This issue was apparently already brought up by @xlc here: polkadot-fellows/RFCs#82

closing

@Tomen Tomen closed this as completed May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant