-
Notifications
You must be signed in to change notification settings - Fork 646
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
polkadot-omni-node
Meta: Tutorials and reference docs.
#5568
Comments
This issue has been mentioned on Polkadot Forum. There might be relevant details there: https://forum.polkadot.network/t/polkadot-parachain-omni-node-gathering-ideas-and-feedback/7823/23 |
21 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Final outcome of the project should be as follows:
polkadot-omni-node
binary, a white-labeled omni-node binary. This will be capable of running most parachains that don't do node side customization.polkadot-omni-node-lib
, allowing teams to build their own omni-node. This enables a teamThe unique property of
polkadot-omni-node
is that it is a node that does not have any dependency on existing runtime, it ingests a chain-spec or a wasm file, and works based off this. 3 other tools have this property:chain-spec-builder
frame-omni-bencher
try-runtime-cli
.The main user story of omni-node-drive-development is then as follows:
polkadot-omni-node --dev
for local testing.chain-spec-builder
to generate your chain-spec fileframe-omni-bencher
to do benchmarkingtry-runtime-cli
to do testing.zombienet
and/orchopsticks
for further types of deployment.polkadot-omni-node --chain spec.json
as final way to deploy a parachain.This should be documented in a reference doc in polkadot-sdk, and advertised to external documentation teams.
EVM Support
..via frontier is not something that we foresee at the moment, and instead would like to suggest using:
pallet-evm
pallet-contract
,revive
, see https://github.com/paritytech/revive-ethereum-rpcThe text was updated successfully, but these errors were encountered: