Blockchain//Besu//Self-Reference

- Bootnode configured with its own enode in `--bootnodes` — causes P2P initialization anomalies.

Bootnode configured with its own enode in --bootnodes — causes P2P initialization anomalies.

The node attempts to "discover itself" → enters retry loops → accepts incoming connections only intermittently.

Not a timing issue — the corrupted P2P state persists regardless of how long you wait.

Fix: never include a node's own enode in its --bootnodes list.