Add support for defining a list of full node peers to connect to

[felixbrucker]

Purpose:

Allow the full node to connect to a list of full nodes configured via config.yaml and automatically reconnect should the connection be interrupted/disconnected.

Current Behavior:

Currently this is not supported, a workaround is to add peers manually via cli, but once not connected anymore they will not automatically reconnect.

New Behavior:

A list of full nodes can be configured via full_node_peers in the config.yaml, the same way other peers are already configured.

[xearl4]

I am very much looking forward to this! We (spacefarmers.io) operate several meshes of full nodes to support pool needs. At the moment, we use a script to interconnect the nodes and keep them connected. I'll be happy to abandon that script :)

[emlowe]

Well, that seems simple enough.

[TheLastCicada]

This will also be very useful if running a small private testnet where all peers are known. Can skip running an introducer potentially.

[danieljperry]

What is the expected syntax when adding a full node peer to the config? For example, something like this?

full_node_peers:
    host: 12.34.56.78
    port: 8444

[felixbrucker]

Almost:

full_node_peers:
  - host: 12.34.56.78
    port: 8444

For multiple:

full_node_peers:
  - host: 12.34.56.78
    port: 8444
  - host: <another host>
    port: 8444

[danieljperry]

I previously tried using a hyphen, but I didn't indent the port initially. Now I have it working. Thanks!

[LCG22]

Does this wallet support these settings?

[felixbrucker]

@LCG22 this PR only affects the full node service, not the wallet service

[LCG22]

此 PR 仅影响全节点服务，不影响钱包服务

Can you let it support the wallet ？

[felixbrucker]

As far as i know this is already possible