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

Forking relaychain states with a testnet + executing XCM calls to forked instances #112

Open
flipchan opened this issue Nov 22, 2023 · 2 comments

Comments

@flipchan
Copy link
Collaborator

Interesting post by Liam here:
polkadot-fellows/runtimes#83

@flipchan flipchan changed the title Chain for relaychain with XCM calls Forking relaychain states with a testnet + executing XCM calls to forked instances Nov 22, 2023
@flipchan
Copy link
Collaborator Author

If someone else handles the forking and spinning up a testnet. Uptest cli tool could provide functionality to:

  • 1: submit the wasm runtime upgrade
  • 2: wait for the the runtime event to be triggered(https://uptest-sc.github.io/cli/watch_runtime_upgrade.html)
  • 3: execute the XCM call and verify that it worked(someone could use libuptest to just schedule the XCM calls after the runtime upgrade is finished)
  • 4: verify that the xcm call was executed on sender and receiver chain(not implemented)

We do not have any XCM functionality doe, however this could be achieved with subxt that libuptest is compatible with. It could also just use some after runtime upgrade scheduling functionality and execute a subxt pallet call extrinsic. Step 4 remains unimplemented.

@flipchan
Copy link
Collaborator Author

XCM call verifier needs to be implemented

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