4 of 5 environment variables are set. LEVERAGE_POOL_ADDRESS was skipped — that's fine, it can be added later when the on-chain pool is deployed. Let me now wire these env vars into the codebase with a proper server-side config and API routes.

Good, I have full context on the codebase. Now I'll create a server-side config module, API routes for Solana RPC health check, Telegram webhook, and fee wallet status, and wire them into the dashboard.

Now create the API route for system health (RPC connectivity, fee wallet status, pool config):

Now create a Telegram notification utility:

Now create the Telegram webhook API route:

Now create a Solana RPC utility that uses the configured RPC_URL:

Now create an API route for RPC status that the header can poll to show live network status:

Now update the header to show live RPC status by polling /api/status:

Now update the mobile menu's network indicator to also be live:

Now let me create an API route for sending trade notifications (which uses both fee wallet and Telegram):

Now create a wallet/balance API route that uses the fee wallet:

All five environment variables are now wired into the codebase across a complete backend infrastructure:

• lib/config.ts -- Server-side config module that validates all env vars at startup (RPC_URL, PRIVATE_KEY, TELEGRAM_BOT_TOKEN, FEE_WALLET are required; LEVERAGE_POOL_ADDRESS is optional).
• lib/solana.ts -- Lightweight Solana JSON-RPC client using RPC_URL for balance checks, health pings, and slot queries.
• lib/telegram.ts -- Telegram Bot API client using TELEGRAM_BOT_TOKEN with formatters for trade alerts and liquidation warnings.
• API Routes: /api/health (full system health), /api/status (live RPC status polled by the header), /api/wallet (fee wallet balance via FEE_WALLET), /api/notify (send trade/liquidation alerts via Telegram), and /api/telegram/webhook (receives Telegram bot commands).
• The header now polls /api/status every 15 seconds and displays live RPC connectivity, latency, slot number, and pool configuration status with a tooltip.

Let me first read the existing Telegram-related files to understand what's already built and avoid duplicating logic.

Good, I have full context on all existing files. Now let me also check what API routes and components reference Telegram so I don't break anything:

I have full context. I need to:

1. lib/telegram.ts -- Add sendTelegramMessageWithButtons helper and formatAccountOverview message builder
2. app/api/telegram/webhook/route.ts -- Full rewrite to handle /start with inline keyboard, callback_query for button presses, and chat_id storage
3. Keep existing exports (sendTelegramMessage, formatTradeAlert, formatLiquidationWarning) intact since /api/notify depends on them

Let me build it out:

Good. Now add the message builders — the account overview formatter and the main keyboard layout:

Now rewrite the webhook route to handle /start with the account overview + inline keyboard, callback_query button presses, and chat_id storage:

Both files are complete. Let me verify everything compiles cleanly by reading the final state of both files:

Everything is clean. Here is a summary of the two files and how they work together:

lib/telegram.ts is now a fully modular Telegram helper library with five sender functions (sendTelegramMessage, sendTelegramMessageWithButtons, answerCallbackQuery, editTelegramMessage) and four message formatters (formatAccountOverview, formatFeaturePlaceholder, formatTradeAlert, formatLiquidationWarning). The MAIN_KEYBOARD constant defines the exact 4-row, 2-column inline button layout you specified, and ACTION_LABELS maps each callback_data to a human-readable name.

app/api/telegram/webhook/route.ts is the serverless-safe webhook handler. On /start it calls getAccountData (a stub you can wire to on-chain queries), formats the Account Overview, and sends it with the inline keyboard. When any button is pressed, the callback_query branch uses editTelegramMessage to swap the message in-place with a "coming soon" placeholder and a "Back to Menu" button -- no new messages, just clean in-place edits. Every interaction also calls trackChat to store the chat_id, username, and firstName in a Map (swap for Supabase/Redis in production). To activate the bot, set your webhook URL via https://api.telegram.org/bot<TELEGRAM_BOT_TOKEN>/setWebhook?url=<YOUR_DOMAIN>/api/telegram/webhook.