Remove redundant Dogecoin configuration examples

- Remove duplicate dogecoin.conf examples from Advanced Configuration
- Simplify to reference make dogecoin-config command
- Keep only essential full node vs pruned mode trade-offs
This commit is contained in:
Russell Ballestrini 2025-09-30 22:43:58 -04:00
parent 9d06903633
commit edb236be60

View file

@ -346,58 +346,11 @@ Regular wallet.dat backups are critical. Store backups in secure, offline locati
## Advanced Configuration
### Performance Tuning
**Dogecoin Node Optimization:**
```ini
# Enhanced dogecoin.conf for high-volume usage
server=1
daemon=1
# RPC optimization
rpcuser=secure_user
rpcpassword=very_secure_password
rpcallowip=127.0.0.1
rpcport=22555
rpcthreads=4
# Memory and connection optimization
maxconnections=125
maxmempool=50
dbcache=512
# Pruned mode with optimal size
prune=2200
# Network optimization
addnode=seed.dogechain.info
addnode=seed.multidoge.org
addnode=seed.dogecoin.com
```
### Alternative: Full Node Mode
If maximum decentralization is required:
If maximum decentralization is required, you can run a full node instead of pruned mode. This requires ~200GB+ storage and 8-12 hours for initial synchronization, but provides complete blockchain history and validation.
```ini
# Full node configuration (removes prune=2200)
server=1
daemon=1
rpcuser=secure_user
rpcpassword=very_secure_password
rpcallowip=127.0.0.1
# Full blockchain storage (~200GB+)
# txindex=1 # Optional: enables transaction indexing
```
**Trade-offs:**
- ✅ Complete blockchain history and full validation
- ✅ Maximum decentralization and independence
- ❌ ~200GB+ storage requirement
- ❌ 8-12 hour initial synchronization time
- ❌ Higher bandwidth and CPU usage
To run a full node, modify the generated configuration to remove the `prune` setting.
## Production Best Practices