Existing Crypto Trading Bot linux module problem and scraping issues

Long term developer needed for ongoing support, update or replace trading module and adding value to established 18 month project.

REQUIRED - experience of AI with trading charts, signals, orders to digital wallet and knowledge of crypto, scraping and API

Main requirment - trading module not hitting Moving Average crosses and needs fixed or replaced, so please only apply if knowledge on syncronising MA signals with VWAP and then buy/sell orders sent to wallet. also issues with scraping website.

-Bot been running for about a year and agents been knocked offline.
-Bot uses chart info from online dex sources via data scraping to assist coin selection process
-Bot also uses AI via OpenAI to anaylse trade opportunities.
-telegram function to display trade info and AI output.
-hosted on 5 linux servers for different functions and 1 windows server that scrapes browser (via crons) for source data.
-trades execute to digital wallet.
-googlesheets function to display all trading info.

Thanks


AI:
My crypto-trading bot has been live for roughly a year across five Linux servers and one Windows box that runs headless-browser scrapers on crons. A recent update on the DEX sites we scrape has broken that data flow: every agent is now offline, Moving-Average/VWAP crosses are no longer detected, and no buy/sell orders are reaching the wallet.

I need someone who is comfortable working long term with AI-assisted trading systems—OpenAI analysis, indicator calculations, Telegram push, Google Sheets logging—and who can dive straight into three priorities:

1. Bring the offline agents back up by adapting or rewriting the scrapers to match the new site structure.
2. Debug or, if faster, replace the trading module so MA/VWAP signals trigger instantly and synchronise with order execution to the wallet.
3. Verify end-to-end flow: data scrape → indicator calc → OpenAI opportunity check → order push → Telegram/Sheets reports.

Stack highlights you should already know: Python (preferred), TA-Lib or similar for technical indicators, REST/WebSocket APIs, Linux shells, Git, and basic Windows automation for the legacy scraper. If you can also suggest more robust exchange APIs or better scheduling, great—just keep downtime minimal.

Acceptance will be simple: agents online, MA crosses firing in time with VWAP confirmation, orders landing in the wallet without delay, and full data appearing again in Telegram and Google Sheets.

If that sounds routine to you, let’s start with a quick code walkthrough and move straight to fixes.