Solana LP Agent · Version 0.1

LP opportunity dashboard

Tracked pools, score history, strategy simulation, Telegram alerts and server-side mini DB.

Checking Solana RPC…—
Best candidate—
Visible pools—
Highest vol/liquidity—
Market mode—

Bot strategies recap

Time graph for Conservative / Balanced / Aggressive paper portfolios.

Loading bot state…

Live simulation controls

Start the live simulated bot. It scans on the global check interval, can hard-exit on the next scan, and sends Telegram alerts if enabled.

Simulation not started yet.

Run simulation on collected data

One-shot backtest/replay using saved DB snapshots. It does not start the live bot or change Telegram alert state.

Run simulation to calculate strategy results from collected data.

Allocation timeline

Use the slider to travel back through saved simulation points and see how each strategy allocated cash vs tracked LP pools.

Run simulation to load allocation timeline.

Pool score history

Interactive chart from server-side snapshots. Bands follow your ENTER/HOLD/WATCH/AVOID thresholds.

Pool Settings

Choose what pools are tracked on the Dashboard. Discovery helps find candidates; tracking makes them active.

Pool discovery

Controls the discovery table below. Dashboard only shows pools you explicitly Track and keep active.

Tracked custom pools

Only active tracked pools appear on the Dashboard. Use Track below to add pools from discovery.

Auto top pools discovery

Discovery only: nothing appears on the Dashboard until you click Track. Columns are sortable and include score, estimated fee APR, IL24h and fee tier used.

Add / update pool

Use exact symbols to avoid BNSOL/SOL-style mistakes. Example: base SOL,WSOL, quote USDC.

Strategy Settings

Configure fee model, score formula and action thresholds.

Fee estimate model

Instant uses only current 24h volume. Rolling averages saved snapshots over N days. Weighted gives more importance to recent data.

Fee APR formulafeeAprPct = (smoothedVolume24h / liquidityUsd) × feeRate × 365 × 100

Action thresholds

These decide the label shown on each pool. Keep them ordered: Enter > Hold > Watch.

Editable scoring formula

The score is always capped at 100. Positive sliders rebalance to exactly 100.0/100.

AMM base rulex × y = k

For a classic constant-product pool, x is token A, y is token B, and k stays constant during swaps.

Impermanent loss estimater = 1 + change24h / 100
IL24h = | 2 × √r / (1 + r) − 1 | × 100

This compares AMM value after price moves versus simply holding the original tokens. It does not include earned fees.

Main score formulascore = clamp(base + feePotential + liquidityQuality + activityQuality + correlationBonus − trendPenalty − ilPenalty − ghostPenalty − lowFeePenalty, 0, 100)

Positive score budget = 100 max points

Scaling and penalties

Simulation Settings

Configure timing, hard exits and strategy risk appetite. Telegram has its own Settings subpage.

Hard exit conditions

The server checks tracked pools every X minutes. Hard exits can force an immediate simulated exit on the next scan.

Strategy risk profiles

Caps are used only when Allocation mode is Dynamic with cap. Equal mode ignores score weighting after pool selection and splits deployed capital evenly across selected pools.

Conservative

Balanced

Aggressive

How the simulation works

Allocation rulepick top pools where score ≥ minScore, capped by maxPools; keep reserve % in cash; weights follow allocation modeLP fee estimate per intervalfeePnl ≈ allocatedUsd × (feeAprPct / 100) × (hours / 24 / 365)Directional LP market exposurelpValueRatio ≈ √(priceNow / pricePrevious)

The server checks tracked pools every configured X minutes and saves snapshots. The simulated bot can hard-exit immediately on any scan if risk thresholds are hit. New entries and normal rotations happen on the rebalance cadence.

Telegram bot options

Automatic trade updates fire whenever a strategy enters/exits during a market scan. Reports are separate scheduled summaries.

Chart images use an external chart image URL and are optional. Keep off if your hosting blocks external requests.

Security note: Telegram secrets are read only from server environment variables and are not stored in the DB or exposed to the frontend.

DB Management

Control the local server DB. Default mode should be Continue DB universe: after the first scan, the bot keeps collecting the same discovery pools after restart.

Export DB JSON

Discovery universe

Continue DB universe = keep using the discovery pools already saved in DB. Best for consistent ML data. Rescan every scan = always refresh top pools from API; useful only if you want the universe to change continuously.

Global check interval. This value controls how often the server scans the market, writes snapshots to the DB, evaluates simulation/strategy decisions, and triggers Telegram trade alerts. It overwrites the old Simulation Settings check interval because the whole system uses the same scan loop.

Cleanup tools

Use these only when you intentionally want to reduce DB size or restart the simulation. Snapshots are the valuable AI dataset, so do not clear them casually.

Delete data for one saved pool

Use this if one pair polluted the dataset. You can delete only its snapshots while keeping the pool config, or delete snapshots and remove it from the discovery/custom universe.

DB Visualizer

Interactive admin browser for snapshots, pools, settings and simulation state.

Click a row to inspect/edit JSON. Save replaces that DB row; Delete removes it after confirmation. Cost fields show API vs fallback gas/swap estimates when available.

Choose a table and refresh.

Rows

Compact table view.

Selected row editor

Raw record for verification/debug. Advanced: edit carefully.