acala --helpfor the most up-to-date information.
v0.5.1in the example below):
--wasm-execution Compiled. Note that this uses much more CPU and RAM, so it should be turned off after the node is in sync.
localwith two pre-defined (and definitely not private!) keys known as Alice and Bob.
🏷 Local node identity is: 12D3KooWNHQzppSeTxsjNjiX6NFW1VCXSJyMBHS48QBmmGs4B3B9...shows the Peer ID that Bob will need when booting from Alice's node. This value was determined by the
--node-keythat was used to start Alice's node.
1 peers), they have produced some blocks (
best: #3807 (0x0fe1…13fa)), and blocks are being finalized (
finalized #3805 (0x9d23…20f1)).
sr25519key and address associated with it. This key will be used by Aura for block production.
ed25519key and address associated with the same mnemonic. This key will be used by grandpa for block finalization.
sr25519key which will be used by Aura for block production. Take careful note of the menmonic phrase, and the SS58 address which can be copied by clicking on the identicon in the top left.
ed25519key which will be used by grandpa for block finalization. Again, note the menmonic phrase and ss58 address.
localspec that we used previously.
--chain localwhich is a predefined "chain spec" that has Alice and Bob specified as validators along with many other useful defaults.
customSpec.json. Remember, further details about all of these commands are available by running
babe, you also need to add it to
customSpecRaw.jsonwith your all the other validators in the network.
--aliceflag. Instead we will insert our own custom keys into the keystore through the RPC shortly.
--chainflag has changed to use our custom chain spec.
--nameflag. You may use it to give your node a human-readable name in the telemetry UI.
--rpc-methods=Unsafeflag has been added. As the name indicates, this flag is not safe to use in a production setting, but it allows this tutorial to stay focused on the topic at hand.
curlfrom the command line. This approach may be preferable in a production setting, where you may be using a cloud-based virtual private server.
--bootnodesparameter as Bob did previously.
finalized #0 (0x0ded…9b9d)). Substrate nodes require a restart after inserting a grandpa key. Kill your nodes and restart them with the same commands you used previously. Now blocks should be finalized.