# Besu Configuration Changelog

**Last Updated:** 2026-01-31  
**Document Version:** 1.0  
**Status:** Active Documentation

---

**Date**: 2026-01-17  
**Purpose**: Track configuration changes, versions, and deployments

---

## Configuration Versions

### Version 2026.01.17-v2 (Current)
- **Date**: 2026-01-17
- **Status**: ✅ Deployed to templates
- **Changes**:
  - Removed all deprecated options (11 options removed)
  - Optimized logging levels (WARN for validators/RPC, INFO for sentries)
  - Cleaned empty comment sections
  - Hardened CORS configuration (specific origins for core RPC)
  - All configs validated and passing

### Version 2026.01.17-v1
- **Date**: 2026-01-17
- **Status**: ✅ Deprecated (replaced by v2)
- **Changes**:
  - Initial cleanup of deprecated options
  - Logging optimization started

---

## Configuration Change History

### 2026-01-17: Configuration Cleanup Complete

**Changes Applied**:
1. **Deprecated Options Removed**:
   - `log-destination`
   - `fast-sync-min-peers`
   - `database-path`
   - `trie-logs-enabled`
   - `accounts-enabled`
   - `max-remote-initiated-connections`
   - `rpc-http-host-allowlist`
   - `rpc-tx-feecap="0x0"`
   - `tx-pool-max-size`
   - `tx-pool-price-bump`
   - `tx-pool-retention-hours`

2. **Logging Optimization**:
   - Validators: `INFO` → `WARN`
   - RPC nodes: `INFO` → `WARN`
   - Sentry nodes: `INFO` (unchanged, archive nodes)

3. **CORS Hardening**:
   - `config-rpc-core.toml`: `[]` → `["http://192.168.11.0/24","http://localhost","http://127.0.0.1"]`
   - Specific origins instead of empty arrays or wildcards

4. **Empty Comments Removed**:
   - Cleaned up empty comment sections left after deprecated option removal

**Files Modified**: 16 configuration files

**Validation**: All configs validated and passing

---

## Node-to-Config Mapping

### Validator Nodes (VMIDs 1000-1004)
- **Config File**: `config-validator.toml`
- **Template**: `smom-dbis-138-proxmox/templates/besu-configs/config-validator.toml`
- **Source**: `smom-dbis-138/config/config-validator.toml`
- **Status**: ✅ Cleaned and validated

### Sentry Nodes (VMIDs 1500-1503)
- **Config File**: `config-sentry.toml`
- **Template**: `smom-dbis-138-proxmox/templates/besu-configs/config-sentry.toml`
- **Status**: ✅ Cleaned and validated (archive mode)

### RPC Nodes (VMIDs 2500+)
- **Core RPC (2500)**: `config-rpc-core.toml` ✅
- **Public RPC (2502)**: `config-rpc-public.toml` ✅
- **Permissioned RPC (2501)**: `config-rpc-perm.toml` ✅
- **ThirdWeb RPC**: `config-rpc-thirdweb.toml` ✅
- **Other RPC nodes**: Various configs ✅

---

## Deployment Status

### Template Files
- ✅ All templates cleaned and validated
- ✅ All templates pass validation
- ✅ Ready for deployment

### Running Nodes
- ⏳ Pending: Configs not yet deployed to running nodes
- **Next Step**: Deploy cleaned configs using `scripts/deploy-besu-configs.sh`

---

## Configuration Drift Tracking

### Known Deviations

Currently, all source configs match templates. After deployment, use `scripts/audit-besu-configs.sh` to detect drift.

---

## Configuration Validation

### Validation Status
- ✅ All 16 configs pass validation
- ✅ No deprecated options detected
- ✅ All required options present
- ✅ All option values valid

### Validation Script
```bash
# Validate all configs
./scripts/validate-besu-config.sh

# Generate JSON report
./scripts/validate-besu-config.sh json validation-report.json
```

---

## Audit Reports

### Configuration Audit
```bash
# Audit configs against templates
./scripts/audit-besu-configs.sh

# Generate JSON audit report
./scripts/audit-besu-configs.sh json audit-report.json
```

---

## Next Steps

1. **Deploy cleaned configs** to running Besu nodes
2. **Monitor services** after deployment
3. **Track configuration drift** using audit script
4. **Update this changelog** as changes are made

---

## Related Documentation

- `docs/04-configuration/BESU_CONFIGURATION_GUIDE.md` - Configuration reference
- `docs/04-configuration/BESU_CLEANUP_COMPLETE.md` - Cleanup summary
- `docs/04-configuration/BESU_PATH_REFERENCE.md` - Path structure reference

---

**Last Updated**: 2026-01-17  
**Status**: Active Tracking