VTA Benchmark
HomeVTA vs BTCDashboardBlock ExplorerTX ExplorerP2P AuditConsensus
Deep Technical Audit

DNS / Network Discovery + Peer Address Management

This audit examines how a VTA node can discover peers, resolve network addresses, maintain peer-address information and establish outbound/inbound connections. It separates discovery mechanisms from the later socket/handshake stage.

Peer Discovery

NETWORK

Discovery can come from configured nodes, address databases and protocol-level peer exchange, depending on the release.

Address Manager

NETWORK

Peer addresses need lifecycle handling: learning, selecting, connecting, banning and expiry/retry behavior.

DNS Seeds

VERIFY

A DNS-seed claim must be tied to the exact VTA release and its seed configuration; it should not be inferred from Bitcoin.

Peer Discovery Flow

Seed / Configknown entry points Address Poolpeer candidates Selectionchoose candidate SocketTCP connection Handshake / Peer Stateversion + verack + state Discovery ≠ trust Finding an IP address does not establish that the remote node is honest or that its chain is valid. Protocol validation, peer state and consensus validation remain separate security layers. Previously verified VTA network code ConnectNode / peer limits / banned-address checks inbound/outbound connection management Evidence gap Exact DNS seed list and complete address-manager behavior need release pinning.

Audit Matrix

AreaFindingStatus
Outbound connection limitPreviously reviewed VTA net.cpp defines MAX_OUTBOUND_CONNECTIONS = 8.Source verified
Maximum connectionsPreviously reviewed source sets nMaxConnections = 125.Source verified
Peer connection pathConnectNode() checks existing connections and creates a nonblocking socket for the selected peer.Source verified
Banned addressesThe reviewed network code contains banned-address state and rejects inbound sockets from currently banned addresses.Source verified
Ban durationThe reviewed code uses the -bantime setting with a default of 24 hours.Source verified
Configured addnodesThe node can use explicitly configured peer addresses; exact configuration behavior depends on the release/configuration.Source path
DNS seed listNo release-pinned VTA DNS seed list is asserted on this page.Not established
Address-manager databaseExact persistence/schema and selection algorithm require release-specific source tracing.Needs source pin
Peer discovery diversityNo network-wide measurement of discovery-source diversity was performed.Not measured
Current peer healthThe user's local node snapshot previously showed 2 connections, but that is a local observation, not a network-wide metric.Local evidence only

Release-Pinned Test Plan

1. Pin exact VTA Core release / commit.
2. Locate DNS seed definitions.
3. Locate addnode / connect configuration handling.
4. Trace address insertion and persistence.
5. Trace peer candidate selection.
6. Record duplicate-address handling.
7. Test banned-address rejection.
8. Test inbound/outbound limits.
9. Test peer expiry/retry behavior.
10. Capture handshake success/failure for each discovery source.
11. Compare peer-source diversity on a disposable test network.
Security distinction: Peer discovery only provides candidates. A discovered peer is not trusted merely because it came from DNS, an address database or another peer. VTA consensus validation remains the authority for chain validity.
VTA-specific network claims are limited to previously reviewed source paths. DNS seed and address-manager conclusions require an exact release/source pin.