Problem description

Looking at ports used on the portal network I see two issues:

1. Clash with beacon chain

The port used by Trin clashes with the discovery port on beacon chain clients. This means that by default there will be clashes if users have a beacon client running. This may become annoying if beacon light clients are coupled somehow with portal clients.

2. No standard portal network port

Users following generic setup instructions may have to configure port-related settings. If there is a standard port, these instructions can be cross-client.

Possible resolution

Decide on a discovery port to converge on for the Portal Network.

Example default ports. | Client | Network | Port | | - | - | - | | Trin, Ultralight | portal | 9000 | | Fluffy | portal | ~~?~~ 9009 | | Teku, Nimbus, Lodestar, Lighthouse | consensus | 9000 | | Prysm | consensus | 13000/12000 | | Geth, Nethermind, Erigon, Besu | execution | 30303 |