proxmox/docs/archive/historical/FUNDING_NEW_ACCOUNT_BLOCKED.md

Funding New Account - Blocked by Stuck Transaction

Date: $(date)
Issue: Cannot fund new account because old account is blocked by stuck transaction

---

🔍 Problem

The old deployer account (0x4A666F96fC8764181194447A7dFdb7d471b301C8) cannot send ANY transactions because nonce 23 is stuck. This means:

• ❌ Cannot fund new account from old account
• ❌ Cannot send any transactions from old account
• ❌ All subsequent nonces are blocked

---

💡 Solutions

Option 1: Use a Different Funding Account

If you have access to another account with ETH balance:

# Use a different account's private key
export FUNDING_PRIVATE_KEY=<different-account-private-key>
cast send 0xC13EfAe66708C7541d2D66A2527bcBF9992e7186 \
  --value 10ether \
  --rpc-url http://192.168.11.250:8545 \
  --private-key $FUNDING_PRIVATE_KEY

Option 2: Manual Funding via Validator

If you have access to a validator node, you can manually fund the account:

1. Connect to a validator node
2. Use validator's account to send funds
3. Or use a validator's private key if available

Option 3: Genesis Account

If the network has a genesis account with funds:

# Check genesis accounts
cast balance <genesis-address> --rpc-url http://192.168.11.250:8545

# Use genesis account to fund
cast send 0xC13EfAe66708C7541d2D66A2527bcBF9992e7186 \
  --value 10ether \
  --rpc-url http://192.168.11.250:8545 \
  --private-key <genesis-private-key>

Option 4: Pre-funded Account

If the new account was pre-funded during network setup, check its balance:

cast balance 0xC13EfAe66708C7541d2D66A2527bcBF9992e7186 \
  --rpc-url http://192.168.11.250:8545

Option 5: Wait for Nonce 23 to Clear

If the transaction eventually processes or expires:

• Wait for transaction retention period (6 hours default)
• Or wait for validators to process the transaction
• Then retry funding

---

🎯 Recommended Approach

Use a different funding account that is not blocked by the stuck transaction. This could be:

1. A validator account (if you have access)
2. A genesis/pre-funded account
3. Another deployer account that's not stuck
4. An account funded from an external source

---

📋 Next Steps After Funding

Once the new account is funded:

1. Set NEW_PRIVATE_KEY in .env file
2. Run: ./scripts/configure-ethereum-mainnet-with-new-account.sh
3. Verify: ./scripts/test-bridge-all-7-networks.sh weth9

---

Last Updated: $(date)
Status: ⚠️ FUNDING BLOCKED - NEED ALTERNATIVE FUNDING SOURCE