We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What are exactly the tricks that ZN does under the hood? are these documented somewhere?
for example, I can't get a rococo local spec to run locally with
$ polkadot --chain rococo-local.json --tmp --bob --validator --unsafe-force-node-key-generation --insecure-validator-i-know-what-i-do $ polkadot --tmp --chain rococo-local.json --validator --unsafe-force-node-key-generation --insecure-validator-i-know-what-i-do --alice --bootnodes /ip4/127.0.0.1/tcp/30333/p2p/12D3KooWBtdHddFucYNhaY6rA8K5qFYhwjFqv8Ue9mxL3PHpBfwW
but it works with ZN, so I assume it is doing more magic under the hood.
As a user, I like the abstraction, but I also would like to know what is going on.
The text was updated successfully, but these errors were encountered:
pepoviola
No branches or pull requests
What are exactly the tricks that ZN does under the hood? are these documented somewhere?
for example, I can't get a rococo local spec to run locally with
but it works with ZN, so I assume it is doing more magic under the hood.
As a user, I like the abstraction, but I also would like to know what is going on.
The text was updated successfully, but these errors were encountered: