d-bis/proxmox
4
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
4f85e0bf0e59e78511998aefc5d2076ed13b0a14
proxmox/rpc-translator-138/WEB3SIGNER_INSTALLED.md
defiQUG cb47cce074 Complete markdown files cleanup and organization 
- Organized 252 files across project
- Root directory: 187 → 2 files (98.9% reduction)
- Moved configuration guides to docs/04-configuration/
- Moved troubleshooting guides to docs/09-troubleshooting/
- Moved quick start guides to docs/01-getting-started/
- Moved reports to reports/ directory
- Archived temporary files
- Generated comprehensive reports and documentation
- Created maintenance scripts and guides

All files organized according to established standards.
2026-01-06 01:46:25 -08:00

3.9 KiB
Raw Blame History

Web3Signer Installation Complete ✅

Date: 2026-01-05
Status: Web3Signer 25.12.0 Successfully Installed and Running

Installation Summary

✅ Web3Signer 25.12.0 has been successfully installed, configured, and is running on VMID 107.

Installation Steps Completed

  1. ✅ Downloaded Web3Signer 25.12.0 from GitHub releases

  2. ✅ Transferred to Proxmox host and extracted to /opt/web3signer-23.10.0/

  3. ✅ Java 21 installed (required per Web3Signer documentation)

  4. ✅ Systemd service configured with eth1 subcommand

    • Command: web3signer eth1 --http-listen-port=9000 --http-listen-host=192.168.11.111 --data-path=/opt/web3signer/data
    • Note: Web3Signer requires eth1 or eth2 subcommand

  5. ✅ Service running and responding

Configuration

Service Details:

  • Container: VMID 107 (web3signer-rpc-translator)
  • IP Address: 192.168.11.111
  • Port: 9000
  • Data Path: /opt/web3signer/data
  • Subcommand: eth1 (for Ethereum SECP256k1 signing)
  • Java Version: OpenJDK 21.0.9

Systemd Service:

[Unit]
Description=Web3Signer
After=network.target

[Service]
Type=simple
User=root
Group=root
WorkingDirectory=/opt/web3signer-23.10.0
ExecStart=/opt/web3signer-23.10.0/bin/web3signer --http-listen-port=9000 --http-listen-host=192.168.11.111 --http-host-allowlist=* --data-path=/opt/web3signer/data eth1 --chain-id=138
Restart=always
RestartSec=5
StandardOutput=journal
StandardError=journal
SyslogIdentifier=web3signer

[Install]
WantedBy=multi-user.target

Verification

Service Status:

systemctl status web3signer
# Should show: Active (running)

Health Check:

curl http://192.168.11.111:9000/upcheck
# Should return: OK

View Logs:

pct exec 107 -- journalctl -u web3signer -f

Important Notes

  1. Subcommand Required: Web3Signer requires either eth1 or eth2 subcommand

    • eth1: For Ethereum SECP256k1 signing (used for our RPC translator)
    • eth2: For Ethereum 2.0 BLS signing

  2. Signing Keys: Web3Signer is now running but needs signing keys configured

    • Keys should be added to /opt/web3signer/data/keystore/
    • Or configure key management (HashiCorp Vault, Azure Key Vault, AWS KMS)
    • See Web3Signer Documentation for key configuration

  3. Configuration: Uses command-line arguments

    • Main options: --http-listen-port, --http-listen-host, --http-host-allowlist, --data-path
    • Subcommand: eth1 (for Ethereum SECP256k1 signing)
    • Eth1 options: --chain-id=138
    • Note: YAML config file was removed (not needed when using command-line args)

Next Steps

  1. ✅ Web3Signer installed - COMPLETE
  2. ⏳ Configure Web3Signer signing keys
    • Add signing keys to enable transaction signing
    • See Web3Signer documentation for key formats
  3. ⏳ Deploy translator service to VMIDs 2400-2402
  4. ⏳ Configure translator .env files
  5. ⏳ Test end-to-end functionality

All Supporting Services Status

Service VMID IP Status Health Check
Redis 106 192.168.11.110 ✅ Running ✅ PONG
Web3Signer 107 192.168.11.111 ✅ Running ✅ OK
Vault 108 192.168.11.112 ✅ Running ✅ Healthy

References

Reference in New Issue View Git Blame Copy Permalink