-
Notifications
You must be signed in to change notification settings - Fork 6
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
Feature/plmc 287 parachain information discovery and channel opening #94
Feature/plmc 287 parachain information discovery and channel opening #94
Conversation
13ad46e
to
3ed35dd
Compare
PR is ready for review. |
0f42df5
to
e7cf200
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One "small" step for Contribution Token Migration, one big step for Polimec.
First Round of Feedback:
I really like how we can now instantiate different projects in different rounds effectively. The updated logic for managing and initiating HRMP channels is also really nice.
While my comments address relatively minor points, I'd appreciate a second perspective from @vstam1, particularly on changes related to XCM aspects.
Also, probably a rebase is needed after #93 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great Initial start for the parachain channel opening. I left a couple of comments, together with the comments from Leonardo.
I'm still a bit concerned about the maintainability of the custom xcm-executor. It is definitely something that we should think about, as parity has common updates to the executor code (I personally worked on the transactionality of xcm instructions. The pr has big changes to the xcm-executor code). So we should probably patch our executor on every polkadot-sdk release.
I think it would also be nice if we could move the migration logic to another pallet to decrease the complexity/lines of code in pallet-funding. Let me know what you guys think!
dd31274
to
0e1011a
Compare
fix migration readiness check cargo lock channel open function now included in trait readme on executor fork small fixes (Leo's feedback) save automatic hrmp connection working Genesis instantiator usage and first draft of HRMP connection formatting feature propagation cleanup new node functioning. genesis not yet sure if working new node functioning. genesis not yet sure if working somehow compiling and test passing save save save feat(287): para_id setting extrinsic implemented and tested save same log crate across workspace same log crate across workspace save save save feat(287): changed tight couple of pallet_xcm by extracting sender trait feat(287): first commit feat(285): POC Hrmp automatic acceptance
6a2c7da
to
fe40084
Compare
/bot test pallet-funding |
test: Succeeded! ✅ |
…very-and-channel-opening
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One comment on the robustness of the channel opening. I don't see it as a blocker but would probably be good to implement.
PLMC 287: Parachain information discovery and channel opening
Objective
Add a way for an issuer to add information about its parachain when it launches, and use that to automatically accept their hrmp request (based on certain criteria), and also send an hrmp request to them.
Features
New chain spec called "testing-node" which is only available when compiling with the feature of the same name.
New fields to represent the paraId and the status of the channels.
Fork of XcmExecutor to add our own implementation of the HRMP instructions