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

No DMP messages received in Parachain #631

Closed
NachoPal opened this issue Jan 12, 2024 · 8 comments · Fixed by #633
Closed

No DMP messages received in Parachain #631

NachoPal opened this issue Jan 12, 2024 · 8 comments · Fixed by #633

Comments

@NachoPal
Copy link

When running a Parachain from a genesis file, DMP messages are not received.

Block is built in the Parachain as a response of sending a XCM from the Relay Chain, but parentHead and downwardMessages in setValidationData are empty.

@ermalkaleci
Copy link
Collaborator

as I said last time, starting xcm with genesis won't work because you won't have any parachain registered

@NachoPal
Copy link
Author

NachoPal commented Jan 12, 2024

as I said last time, starting xcm with genesis won't work because you won't have any parachain registered

I manually registered the Parachain and onboarded it before sending the message.

I could try to add it to the Relay's genesis state if you think that will make any difference.

@NachoPal
Copy link
Author

I added the Parachain in the genesis file but same result.

I provide the chain spec
chain-spec-with-para-v1.0.0.json

@ermalkaleci
Copy link
Collaborator

the problem is missing dmqMqcHead, I will see if we can mock it

@ermalkaleci ermalkaleci linked a pull request Jan 15, 2024 that will close this issue
@ermalkaleci
Copy link
Collaborator

@NachoPal can you give this a try? #633

@ermalkaleci
Copy link
Collaborator

ermalkaleci commented Jan 15, 2024

you don't need to do anything extra, just start from genesis. Did test transfer KSM and works

@NachoPal
Copy link
Author

the problem is missing dmqMqcHead, I will see if we can mock it

That was it, now it is working. Let you know that it is not even necessary to add the Parachain in genesis for XCM to work bidirectionally.

I do not know if you can foresee some side effects or something that might not work/malfunction if a Parachain is not registered.

@ermalkaleci
Copy link
Collaborator

Chopsticks intercepts xcm messages produced by runtime execution and triggers block building on the other chain with that xcm message, so it all depends on the runtime if it can produce a message or not. If the runtime strictly required parachain to be registered then it will not produce a xcm message therefore the other chain won't intercept any message

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

Successfully merging a pull request may close this issue.

2 participants