Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands - CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround - CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check - NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere - MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates - LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference Co-authored-by: Cursor <cursoragent@cursor.com>
2.3 KiB
2.3 KiB
Apply Configuration Changes to Besu RPC Node
Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation
Date: 2025-01-20
Status: ⚠️ ACTION REQUIRED
Configuration Changes Made
The following changes have been made to config-rpc-core.toml:
1. Transaction Pool Configuration
tx-pool-max-size=8192
tx-pool-limit-by-account-percentage=0.5
tx-pool-price-bump=10
2. RPC Timeout Configuration
rpc-http-timeout=120
Action Required
⚠️ Restart Besu RPC Node
The configuration file has been updated, but the running Besu RPC node must be restarted to apply these changes.
Steps to Apply
Option 1: Restart via Systemd (Recommended)
# SSH to Proxmox host
ssh ml110
# Restart Besu RPC service
pct exec 2101 -- systemctl restart besu-rpc-core
# OR restart the container
pct restart 2101
# Verify service is running
pct exec 2101 -- systemctl status besu-rpc-core
Option 2: Restart Container
# SSH to Proxmox host
ssh ml110
# Restart container
pct restart 2101
# Wait for service to start
sleep 10
# Verify RPC is accessible
cast chain-id --rpc-url http://192.168.11.211:8545
Verification
After Restart
-
Check RPC is accessible:
cast chain-id --rpc-url http://192.168.11.211:8545 -
Check block production:
cast block-number --rpc-url http://192.168.11.211:8545 -
Verify configuration loaded:
- Check Besu logs for configuration loading
- Verify timeout behavior (should be 120s)
- Test transaction pool limits
Expected Behavior After Restart
Connection Timeout
- Before: 60 second timeout (default)
- After: 120 second timeout
- Impact: Large deployments should not timeout
Transaction Pool
- Before: Default limits
- After: Explicit limits (8192 max, 0.5 per account)
- Impact: Better pool management
Replacement Transactions
- Before: Default price bump
- After: 10% price bump required
- Impact: Clearer replacement requirements
Status
Configuration File: ✅ UPDATED
Besu RPC Node: ⚠️ NEEDS RESTART
Applied: ❌ PENDING
⚠️ IMPORTANT: Restart the Besu RPC node to apply configuration changes before deploying contracts.