This guide explains how to connect your Metamorph Bitcoin SV node to the live Bitcoin SV network for real transaction processing and blockchain synchronization.
Your Metamorph node now supports real Bitcoin SV network connectivity with the following capabilities:
- Real P2P Networking: Connect to live Bitcoin SV peers via DNS seed discovery
- Transaction Relay: Receive and validate real Bitcoin SV transactions
- Block Synchronization: Download and validate real Bitcoin SV blocks
- Network Health Monitoring: Automatic peer management and connection health
- Live Mode: Connect to real Bitcoin SV mainnet/testnet
- Demo Mode: Use simulated networking for development and testing
- Seamless Switching: Toggle between modes via environment variables
# Copy the live network configuration
cp .env.live .env
# Edit configuration as needed
nano .env# For Bitcoin SV Testnet (recommended for testing)
export BITCOIN_LIVE_MODE=true
export BITCOIN_NETWORK=testnet
# For Bitcoin SV Mainnet (production)
export BITCOIN_LIVE_MODE=true
export BITCOIN_NETWORK=mainnet# Run with live network connectivity
go run ./cmd/demo/main.go
# Or build and run
go build -o metamorph ./cmd/demo/main.go
./metamorphWhen live mode is enabled, you'll see:
π Sentinel P2P Service: Starting LIVE Bitcoin SV testnet networking...
π NetworkManager: Connecting to Bitcoin SV testnet network...
π NetworkManager: Discovered 12 potential peers
β
NetworkManager: Connected to peer 95.217.161.135:18333
β
NetworkManager: Connected to peer 144.76.118.2:18333
π NetworkManager: Connected to Bitcoin SV testnet network
π Sentinel: Bitcoin SV P2P service started on testnet (LIVE mode)
| Variable | Description | Default | Example |
|---|---|---|---|
BITCOIN_LIVE_MODE |
Enable live network connectivity | false |
true |
BITCOIN_NETWORK |
Network selection | testnet |
mainnet, testnet |
BITCOIN_MAX_PEERS |
Maximum peer connections | 8 |
16 |
BITCOIN_MIN_PEERS |
Minimum peer connections | 3 |
5 |
BITCOIN_NETWORK=testnet- Purpose: Safe testing environment
- Port: 18333
- DNS Seeds: testnet-seed.bitcoinsv.io, testnet-seed.cascharia.com
- Block Explorer: https://test.whatsonchain.com/
BITCOIN_NETWORK=mainnet- Purpose: Live Bitcoin SV network
- Port: 8333
- DNS Seeds: seed.bitcoinsv.io, seed.cascharia.com, seed.satoshisvision.network
- Block Explorer: https://whatsonchain.com/
When connected to the live network, your node will publish these events:
p2p.peer_connected.v1- New peer connectionsp2p.peer_disconnected.v1- Peer disconnectionsp2p.raw_message.v1- Raw Bitcoin SV protocol messagesp2p.network_health.v1- Network connectivity metrics
p2p.raw_tx.v1- Real Bitcoin SV transactions from networktx.validated.v1- Validated transactions ready for processingtx.validation_failed.v1- Invalid transactions rejected
p2p.raw_block.v1- Real Bitcoin SV blocks from networkblock.validated.v1- Validated blocks ready for processing
# Monitor live network activity
tail -f metamorph.log | grep "NetworkManager\|LIVE"
# Monitor peer connections
tail -f metamorph.log | grep "peer_connected\|peer_disconnected"
# Monitor transaction flow
tail -f metamorph.log | grep "raw_tx\|validated"# Check network status via API (if Portal service is running)
curl http://localhost:8080/health/network
# View peer statistics
curl http://localhost:8080/api/v1/peers# Set live mode in deployment configuration
echo "BITCOIN_LIVE_MODE=true" >> .env
# Deploy to Kubernetes with live network enabled
./deploy-to-digitalocean.shapiVersion: v1
kind: ConfigMap
metadata:
name: metamorph-config
data:
BITCOIN_LIVE_MODE: "true"
BITCOIN_NETWORK: "testnet"
BITCOIN_MAX_PEERS: "8"- Testnet First: Always test on testnet before mainnet
- Firewall Rules: Ensure ports 8333 (mainnet) or 18333 (testnet) are accessible
- Resource Monitoring: Live network increases CPU and bandwidth usage
- Bandwidth: Live network requires sustained internet connectivity
- Storage: Blockchain data will accumulate over time
- Memory: Peer connections and message buffers increase memory usage
- Legal: Ensure compliance with local regulations for Bitcoin SV node operation
- Network: Follow Bitcoin SV network protocol standards and best practices
# Check DNS resolution
nslookup seed.bitcoinsv.io
# Check port connectivity
telnet seed.bitcoinsv.io 8333
# Verify firewall settings
sudo ufw status# Monitor resource usage
htop
# Check peer count
grep "Managing.*peers" metamorph.log
# Reduce max peers if needed
export BITCOIN_MAX_PEERS=4# Increase connection timeout
export BITCOIN_CONNECTION_TIMEOUT=30s
# Check network latency
ping seed.bitcoinsv.ioWith live network connectivity enabled, you can:
- Real Transaction Processing: Process actual Bitcoin SV transactions
- Blockchain Synchronization: Download and validate the Bitcoin SV blockchain
- Mining Integration: Connect to mining pools for block production
- Wallet Services: Implement SPV and wallet functionality
- Ecosystem Integration: Connect to Bitcoin SV services and applications
// Add custom peer addresses
customPeers := []string{
"95.217.161.135:8333",
"144.76.118.2:8333",
}// Filter specific message types
messageTypes := []string{"tx", "block", "inv"}# Optimize for high throughput
export BITCOIN_MAX_PEERS=16
export BITCOIN_CONNECTION_TIMEOUT=5s
export ENABLE_MESSAGE_BATCHING=trueStatus: β Live Bitcoin SV network connectivity ready Repository: git@github.com:codenlighten/bitcoin-sv-optimized-node.git Support: Real Bitcoin SV P2P networking with production-grade peer management