Secure Litecoin Escrow Infrastructure

NOTE : I WILL PROVIDE ONLY SRC CODE WITHOUT ANY TOKENS OR IDS SO YOU MUST OWN A TELEGRAM ACCOUNT NOW TO DO THE TESTS ON AFTER YOU FINISH ALL YOU MUST SEND ME THE UPDATED SRC AND I WONT PROVIDE A VPS OR ANYTHING MOST HAS TO BE FROM UR SIDE I’m rebuilding my Telegram-based Litecoin escrow bot and need an experienced DevOps/SecOps engineer to lock down the production environment on my existing Ubuntu VPS. Treat the box exactly like a mini-bank: the wallet will hold live funds once we go live, so every step must follow security best practice and be documented. Scope of work • Hardening – Close all unnecessary ports, apply least–privilege permissions, configure SSH keys (no passwords), enable a restrictive firewall (UFW/iptables) and add fail2ban or equivalent. • Process management – Run the bot under its own user with PM2 or systemd so it auto-starts on reboot and restarts on crash. • Litecoin Core – Compile or install the latest stable Litecoin full node, prune if needed, and sync on an encrypted volume. RPC must bind only to localhost and require strong auth; the bot will be the sole consumer. • Secrets – Generate a fresh production wallet seed offline, then store it and all API tokens in encrypted at-rest storage (LUKS or vault solution). Only the bot service account may read them. • Backups – Automate encrypted backups of the database and wallet.dat to an off-site location I’ll provide, with key rotation. • Monitoring – Set up uptime, error, disk and node-health alerts (Prometheus + Alertmanager, Grafana, or similar). • Credential hygiene – Revoke every previously exposed Telegram bot / API / session credential and roll new ones. • Final audit – Deliver a written checklist of what was done and any residual risks before real money moves. Acceptance criteria 1. All external scans show only intended ports open. 2. Bot restarts automatically after a forced crash and on reboot. 3. Litecoin RPC rejects connections from anything except the local bot user. 4. Encrypted backups can be restored in a test environment. 5. Monitoring generates a test alert I can see. 6. Documentation allows another engineer to reproduce every step. Please outline your approach, preferred security tools, and similar projects you’ve completed. I’m ready to start as soon as we confirm methodology and timeline.