It is not possible to create a wasp node committee with more than one node.

[iotaledger]

It is not possible to create a wasp node committee with more than one node.

[kape1395]

I will add a command to get the current node's public key and update the docs to reflect the step of making the nodes to trust each other.

[jorgemmsilva]

Adding trusted nodes manually should fix this issue: wasp-cli peering trust <pubKey> <netID>

But it feels that it should be something automatic, done by the chain deploy command.
What are your thoughts on the above @kape1395 @dessaya ?

[kape1395]

The trusted peering is considered a precondition for the chain deploy.
To keep the network safe, a node owner should manually decide, which nodes are trusted.

The wasp-cluster tool (only for testing) makes all the nodes to trust each other on startup.

A single node committee was successfully created, because a node trusts itself by default.

[kape1395]

I hope the updated docs resolve this issue.
Docs and the relevant wasp-cli commands are now in the develop branch.