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

Suggest using the omni-node #5928

Open
kianenigma opened this issue May 31, 2024 · 1 comment
Open

Suggest using the omni-node #5928

kianenigma opened this issue May 31, 2024 · 1 comment
Labels
docs Related to the docs in general.

Comments

@kianenigma
Copy link
Contributor

This is a bit of a moving target, so I expect some details with the omni-node to change, but it woudl be great if we can already use it in some of our tutorials.

@CrackTheCode016 mentioned in https://forum.polkadot.network/t/polkadot-parachain-omni-node-gathering-ideas-and-feedback/7823/4?u=kianenigma that it is fully possible to run a parachain with the omni node.

In the meantime, I am standardizing the usage in PBA. An example is: https://github.com/Polkadot-Blockchain-Academy/polkadot-sdk-assignment-template.

The general flow, to recap, is:

cargo install staging-chain-spec-builder

then, from a runtime template, you generate the .wasm file

then, you pass the runtime to the chain spec builder to generate the full chain spec

then you pass the chain spec file to omni node with --chain

@kianenigma kianenigma added the docs Related to the docs in general. label May 31, 2024
@CrackTheCode016
Copy link
Contributor

Agreed, do you mean for stuff like template to core type guides?

(I don't seem to have access to the PBA repo btw)

Both are actually as simple as using cargo install - including the polkadot-parachain (from the Polkadot SDK repo) binary for now. When omninode is a published we can update as needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Related to the docs in general.
Projects
None yet
Development

No branches or pull requests

2 participants