What FLEAT is, how the bot decides to send, and how you interact with it in Phase 1.
No yield promises. Capacity is the product.
01 · What it is
A Solana long-tail strategy bot: atomic arb and small liquidations on thin pools
(Raydium, Orca, Meteora) executed as Jito bundles. Phase 1 runs on operator capital only
with a public race ledger. Vault deposits and $FLEAT mint come later.
02 · How to use it (Phase 1)
Connect wallet on /app — Phantom / Solflare / Backpack. No Telegram bot.
$FLEAT → read tokenomics; stake for seat size when mint is live.
Deposits — only through the on-site vault flow when the cap opens. Anyone DMing a deposit address is not us.
Operators / self-host — .env from .env.example, npm run scan in DRY_RUN until the ledger is clear.
03 · Send rule
Build ≤ 5 transactions (Jito limit).
Simulate the full bundle including tip.
Tip = share of expected profit, floor 1000 lamports.
Send only if net after tip + fees ≥ threshold.
No sim → no send. Ever.
04 · Token safety before entry
Reject freeze authority / mint authority.
Reject Token-2022 transfer hook, permanent delegate, transfer fee.
Depth must sit in the long-tail band (default $25k–$250k) — too thin to exit, too thick = crowded.
05 · $FLEAT (not live yet)
$FLEAT is a seat in the TVL cap, proportional to stake — not a share of vault PnL.
Vault shares = NAV claim. Mixing them is forbidden.
Utility also covers operator bonds, fee discounts for long stakers, TWAP buybacks, and governance over fee ceilings / mandates.
Full breakdown: tokenomics. Interact via wallet app.
06 · Refuse list
Sandwich / toxic flow extraction.
Deposits before a public track record.
APY as the hero metric.
Performance fee on drawdown recovery (high-water mark per depositor).
07 · Live data
The homepage tape is served by /api/market/long-tail, backed by
GMGN Solana trending rank, filtered to the same depth band the bot hunts.
Status: /api/status. Health: /api/health.