Error: NetworkKeyNotFound("/tmp/node01/chains/local_testnet/network/secret_ed25519")

[AlphaGamingArcade]

Is there an existing issue?

• I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

• This is not a support question.

Motivation

Why the new solochain template not working now, following this https://docs.substrate.io/tutorials/build-a-blockchain/add-trusted-nodes/ it seems it is now reading the /tmp/node01/chains/local_testnet/network/secret_ed25519 folder, but in the docs it stored inside /tmp/node01/chains/_testnet/keystore folder.

Request

Update docs

Solution

NA

Are you willing to help with this request?

No., Maybe (please elaborate above)

[bkchr]

@AlphaGamingArcade which command exactly are you executing?

[AlphaGamingArcade]

./target/release/node-template key generate --scheme Sr25519 --password-interactive

./target/release/node-template key inspect --password-interactive --scheme Ed25519 "pig giraffe ceiling enter weird liar orange decline behind total despair fly"

./target/release/node-template \ --base-path /tmp/node01 \ --chain ./customSpecRaw.json \ --port 30333 \ --rpc-port 9945 \ --telemetry-url "wss://telemetry.polkadot.io/submit/ 0" \ --validator \ --rpc-methods Unsafe \ --name MyNode01 \ --password-interactive

I'm just following the documentation, it works on the old version I have which is polkadot-v1.9.0 but not to this latest one.

[aurexav]

I encounter the same issue after upgrading to 2407 from 1.7.2.

This only happens with --collator, --alice, --bob etc.

It looks like the node can not generate keys automatically if there isn't one.

I'll take look into this today.

[aurexav]

Okay, this is quite clear. This behavior is expected.

• Prevent accidental change of network-key for active authorities  #3852

Do not auto-generate the network if the network file does not exist in the provided path. Nodes where the key file does not exist will get the following error:

@bkchr I think this can be closed.

[aurexav]

Up.

[BeginArtem]

@aurexav
Do we have any full instruction how to run a node with custom validator keys now?
I've asked the question here about this.
As I understand from this we can now use --unsafe-force-node-key-generation to generate validator keys if we run the node for the first time, but in this case blocks not finalised.

[aurexav]

@aurexav Do we have any full instruction how to run a node with custom validator keys now?

Validator keys is session keys. This issue is talking about network P2P key. They are different things.

I'll take a look of that question later.