The XF autonomous trading swarm and the $XFLY token

Abstract

XF is a swarm of pre-configured auto-trading agents ("flies") that buy and sell memecoins on Robinhood Chain and Solana from a Telegram bot. The Eye — a continuous scanner across three chains — discovers candidates, a proprietary set of structural safety gates rejects the unsafe, a weighted multi-factor scent score ranks what remains, and a fly lands only above a fixed threshold, then leaves through a take-profit ladder with ratcheting floors and a hard swat line. The platform earns on every fill through a basis-point fee routed to a treasury wallet, with a defined share for group owners. The $XFLY token launches on the Pons V2 launchpad on Robinhood Chain quoted in ETH, so its bonding curve, its graduation threshold and its protocol trading fees are all denominated in the chain's native asset.

This document describes the system as implemented on the revision date, with constants quoted from source where they are public. The specific gate thresholds, the scoring model and the ladder levels are proprietary and are omitted from this edition. Items marked shadow, in testing or under design are not live. Nothing here is investment advice.

System overview

The system has four layers, each with a single responsibility. Discovery and gating decide what is allowed. The score decides what is good. A fly decides how much, when, and how to leave. Execution turns that into signed transactions with guards that cannot be loosened from the fly layer.

Figure 1. The pipeline. Every stage can only narrow what the previous stage passed; no stage can re-admit a rejected token.

1.1 The Telegram interface

Users interact through the bot. Each user holds two custodial trading wallets, one on Robinhood Chain and one on Solana, created on first use; the address and the key are shown once at creation and again only on export. Keys are envelope-encrypted, with the master key held only in the worker environment. Funding is ETH on Robinhood Chain or SOL on Solana.

• /release — the hatchery: pick a fly, read its profile and 30-day record, confirm with a tap. Releasing writes the archetype into your Auto configuration; open positions keep their original plans.
• /auto and /autoset — wingload per chain, buy-on-dip depth, swat line, and the exit ladder within validated bounds. Every parameter is user-settable; see 1.2.
• /positions — every open flight with its live price, ladder progress and floors.
• Pasting a contract address returns a chart card with the token's data and buy buttons, in a DM or in any group the bot has been added to; a buy from a group or channel alert routes through the same standard path. See 1.3.

From release onward the worker scans, lands and exits on your behalf within the archetype's limits. You can hand-sell at any time; the position is retired once the external close is confirmed (Section 4).

1.2 Fully custom auto-trade settings

A fly profile is a starting configuration, not a fixed product. Releasing one writes its parameters into your Auto configuration, and every parameter can then be changed independently; the rest of the profile stays as it was. Nothing is locked to the preset.

Table 1. User-settable auto-trade parameters. Each is validated against bounds, and a value outside the profile's replayed loadout is flagged as such at the point of change.

Because the published 30-day record for a fly is a replay of that fly's own loadout, changing a parameter makes the published figures no longer describe what you are flying. The bot says so at the moment of the change rather than silently carrying the old record forward.

1.3 Trading a call by hand, in any group

Automation is optional. The bot can be added to any Telegram group, and it will attach its own buy buttons to the calls posted there, so you can take a trade by hand, at your own size, without releasing a fly at all. The same works in a direct message and from the alerts channel.

Text posted by a third party is treated strictly as untrusted data. The parser extracts only what it can validate by shape — a contract address, and where present a symbol and a market cap — and discards anything it cannot pin to a single valid address. Nothing written in an alert can cause an action on its own: the bot attaches its own buttons, and your tap is the only thing that ever trades. A tap spends your own preset from your own custodial wallet, pays the standard fee schedule, and returns a confirmation in your DM. Group owners who verify their group receive a share of the fee on trades attributed to it (Section 9).

Candidate selection

Discovery runs continuously over a defined market-cap band ($350k–$5M). On Solana the universe is drawn from pool and token feeds. On Robinhood Chain the lane is launchpad-only: a token qualifies only if it was launched through a trusted launchpad whose graduated pools are permanently locked, proven by the launchpad's own on-chain launch event rather than by name or metadata. Robinhood Chain candidates are priced off their own trusted pool, never a proxy.

Every candidate then passes two proprietary layers before a fly may act. A set of structural safety gates rejects tokens with the failure shapes seen in production: thin or fake liquidity, concentrated supply, dead or wash-traded tape, active dumps, name-squatting copies, tokenized-equity trackers, and, on Robinhood Chain, anything the live venue cannot actually route out of. A weighted multi-factor score then ranks the survivors on holder quality, chart structure, order flow, pool structure and age, with a coverage requirement so a candidate cannot score well on missing data. Each lane carries its own candle budget so a quiet chain is never starved by a busy one. The thresholds, weights and factor definitions are the system's edge and are not published.

Flies key their behaviour on the resulting score: high-scoring candidates are landed on immediately; lower-scoring ones are never chased, and a fly instead arms a dip order below the call price that fills only if price comes to it, expiring unfilled otherwise. In the last 30 days the Eye turned away 14,255 targets and called 339.

The swarm

A fly is a saved auto-trade loadout. Five archetypes ship, ordered by risk. All five share the edges confirmed by a retrospective over recorded flights: a near-miss floor, a fixed swat line, a minimum score requirement, and instant entry. They differ in size, concurrency, chains and exit profile. The risk score is exposure × tail depth × swat rate, measured from the record.

Table 2. The swarm at this revision, from the live archetype definitions.

3.1 Next out of the hatchery

Shown, not deployable. Each opens to staking priority once it goes live (Section 8).

3.2 Exits

Every fly leaves through a take-profit ladder: a sequence of gain levels at which a fraction of the remaining position is sold, each locking in a ratcheted floor beneath the rest so a position that has paid out cannot give the move back. The remainder after the final level rides with the highest floor. Two further rules protect against the round-trip: a near-miss rule sells on reversal when price came close to the next level without filling it, and an episode lock prevents a position that has been up from closing at a loss beyond a small bound. Each archetype carries its own ladder; the levels, fractions and floors are proprietary and are not published here.

3.3 The 30-day record

Every figure shown for a fly, on the site and in the bot, is the last 30 days of the Eye's real calls replayed under that fly's own rules: entries taken exactly at the call price, exits taken exactly where its take-profit ladder, floors and swat line would have taken them, after modeled fees. Flights skipped at the concurrency cap and dip orders that never filled are counted as such, not dropped. The suggested deposit is the full wingload (spend × slots) plus a 10% reserve for fees and slippage. It is a record, not a forecast: any change to a preset produces different results, and past results are no guarantee of future performance.

Execution and safety

Fills are signed by the custodial worker through each chain's primary venue. An auto-seller ticks every 10 seconds over open positions in wallet-grouped batches, reads on-chain balances rather than trusting its own ledger, and applies the ladder decision to the live price. A take-profit fires on the second confirming tick, not the first, so a phantom print cannot trigger a sale.

• Sizing floors. An Auto position must clear a minimum notional on each chain; a per-trade native cap bounds the other side. Smaller sizes are eaten by fees and slippage.
• Quote guards. Slippage caps, price-impact caps and quote time-to-live limits sit below the fly layer and cannot be loosened from it.
• Foot-probe. Before any Robinhood Chain buy, a two-way live quote and a simulated sell prove the token can actually be exited at the venue. The probe fails closed: no quote, no landing.
• Send reconciliation. Every EVM transaction is signed locally so its hash is known before it is broadcast. If the send errors, the worker checks the receipt, the mempool and the account nonce before treating the error as retryable, so a transaction that actually landed is never sent twice. A per-wallet lock serialises sends so fee legs and buys cannot race for a nonce.
• Idempotency. HMAC-signed callbacks, partial-unique database constraints and in-process buy locks prevent double fills.
• Dip fills are re-validated against a maximum gap from the armed price before signing.
• External closes (selling by hand) are confirmed over a 3-minute window before the position is retired.
• Repetition guards. A token cannot be re-called for 48 hours after an episode, and no token gets more than two episodes.
• Price integrity. The trading engine reads prices fail-closed; a cached value that came from a failed upstream fetch is never served to a kill-switch, and a feed outage pauses the lane rather than trading blind.
• Withdrawals go only to an address you have pre-confirmed.

Guards live below the fly layer. An archetype can choose a ladder or a stop within validated bounds; it cannot disable the foot-probe, the caps, the reconciliation or the confirmation window. The fee schedule is snapshotted onto each trade record, so a later change never re-prices history.

XF-6: the smart-money signal

Sections 2–4 describe a system built for tokens 12 hours to 30 days old with two hours of chart history. It is structurally blind to the highest-volume regime on Robinhood Chain: same-day launchpad tokens. A backtest over swap-derived candles showed why no exit tuning fixes this. Buy-and-hold on that cohort has a median return near −70%; tighter stops beat wider ones monotonically; scale-out beats hold. The lever is which launches to touch, not how to leave them.

XF-6 ROBBER is the entry-selection answer, currently in testing: it observes, scores and posts to the alerts channel, but never executes. Robber flies hunt from a perch — and so does this one. Its signal is convergence among the best traders on a social trading app whose top-150 leaderboards are public. Each trader's real trading wallet on Robinhood Chain is resolvable through a public wallet index. An on-chain listener polls every few seconds, watches transfers into those wallets, and accepts a transfer as a buy only when its transaction contains a real swap routed through the app's execution contract, which separates real buys from airdropped spam.

A cluster is K distinct smart wallets buying the same token inside a 30-minute window. Every cluster is shadow-tracked from its first buy with a price mark at each K, so one observed series scores "land on the first buy" against "land on the third" from the same data. The production gate stack runs on every cluster and is recorded, not enforced, so its lift is measurable. After each alert the real venue is quoted at several offsets for a standard size and the fill drift is recorded — the data for a future no-chase guard.

5.1 Alert rules under test

Three alert rules are under test on top of the cluster signal: a market-cap ceiling so only launch-sized tokens alert; a caution veto that suppresses an alert when tracked wallets are selling into the cluster; and a pullback entry that holds an alert on an already-extended token and arms an entry near the recent trough, firing only if price returns within a bounded window. Extension above the trough and thin liquidity are stated on the alert as disclaimers, not holds. The specific thresholds are proprietary.

5.2 Exit policies under test

Every shadow episode is scored against several exits from each mark. The candidate rule for XF-6 is a single buy with an early partial take-profit and a held remainder; variants add a stop or a single add-on-dip. The levels are proprietary. Promotion to a live fly requires the shadow record to validate the hit rate, then a per-parameter sign-off, and it will never execute without explicit approval.

5.3 XF-7

XF-7 ASSASSIN is XF-6 for Solana: the same perch-and-strike reconnaissance, watching the top Solana traders instead. It is in testing on the same terms and under the same promotion rule.

The alerts channel

The public Telegram channel carries two kinds of post, both in one plain layout with no emoji and every time in UTC.

• Eye calls. Headed by which flies would have taken the pick at its score and chain (or "no fly"), then the symbol, launchpad and time, the market cap, liquidity and price at the call, the contract address, and the 24-hour price chart. Tracked take-profit hits are announced against the same call.
• XF-6 testing. Tagged as such, with the cluster size ("smart cluster K=3"), the same data line, and the cluster chart: the price path since the 30-minute trough with every smart buy marked. Buttons buy a standard size through the bot's normal path, copy the contract address, or open the chart.

Users who release a fly also receive a DM for every entry, rung, floor and exit on their own positions, named and charted.

$XFLY and the ETH pairing

7.1 Deployment status

7.2 Venue and quote asset

$XFLY launches on Pons V2 on Robinhood Chain, the same launchpad the XF Robinhood lane trusts for its own candidates. Its quote asset is ETH, the chain's native asset. ETH needs no pair-token allowlist and no contract address: the factory prices a native-quoted launch from its own launch config, which fixes the curve's phantom reserve at 1.68 ETH and graduation at 4.2 ETH. Both values were read from the factory on-chain at this revision.

7.3 Mechanics of an ETH-paired launch

Table 3. Launch mechanics. The graduation threshold is fixed in ETH, so its cost in USD floats with ETH.

7.4 Supply and the locked allocation

Total supply is 1,000,000,000, fixed by the launch config. 25% is bought in the launch transaction itself and locked. It is a purchase, not a mint or a reserved pre-allocation: the launch and the buy happen in one transaction through the launchpad's own router, and the tokens are bought off the same curve at the same opening price any other buyer pays, including the curve fee and the creator tax. Nothing is minted outside the fixed supply. The lock is verifiable on-chain in the launch transaction and in the lock contract. This document does not enumerate other holdings and makes no commitment about whether or when any tokens are sold.

7.5 Why ETH

ETH is what a buyer already holds to transact on the chain, so acquiring the quote asset costs nothing extra: no swap into a second token before the first buy, and no dependence on any single stock token's liquidity. It is also the deepest asset on the chain and the one the swarm already denominates its own fees in, which keeps the token's accounting unit and the platform's revenue in the same currency.

7.6 The swarm does not trade its own token

$XFLY is a launch, not a call. It would have to clear every selection gate like any other token before a fly could touch it, and the swarm gets no preference for it. The scoring model also rejects tokenized equities as trading candidates: Robinhood Chain's flagship product is tokenized stock, and the consolidation and structure families reward a tracker's low volatility, so without an equity-tracker gate the model would adversely select them.

Token utility

8.1 Staking

• Revenue reward. A share of platform revenue, paid in ETH on Robinhood Chain, as a reward for supporting the project's economy. Whether it is paid to stakers or to holders, and at what share, is still to be decided. It is not active at launch: the decision follows a research period of up to two weeks after launch, to read both market conditions and how the flies actually perform under a surge of new users. No rate is promised until that period closes.
• Queue priority. Every call has a limited number of fly slots. When more flies queue for a call than it can carry, stakers are served first.

8.2 House flies and the buy-and-burn

The house flies are the platform's own swarm: the same Eye, the same gates and the same laddered exits every user fly flies, run by the platform on its own capital rather than on anyone else's. They are a trading operation, not a treasury policy — and the intended link to the token is what happens to what they make.

When deployed, 100% of house-fly trading profit is intended to buy $XFLY on the open market and burn it. Not a share of it and not a discretionary amount: the whole of what that swarm earns, in a loop that converts the platform's own trading performance directly into permanently removed supply. Every buy and every burn happens on-chain and is verifiable as it occurs.

They are in training today and are not deployed. The house swarm runs against live market data with paper balances — real prices, real executable quotes, no funds moved — and every decision is recorded so the record is a measurement rather than a claim. It goes live only after clearing a written go-live bar on that record, and it flies with real money only from that point.

Two honest limits. The mechanism produces buybacks only when the swarm is profitable: a flat or losing period buys and burns nothing, and no floor under the token follows from it. And the burn rate is not a yield — it varies with trading performance, which is volatile by nature and is not promised here. Section 10 applies to this as it does to everything else.

Revenue streams

Platform revenue is fee income on executed volume, collected as explicit transfer legs to treasury wallets at fill time. There is no subscription and no tier pricing.

Table 4. Bot fee schedule at this revision. Fees are native-asset transfers to the treasury wallet for the chain (ETH or SOL); the schedule is snapshotted onto each trade record so a later change never re-prices history.

Because a fly position always buys once and sells through several rungs, the blended take on a completed round trip is the buy percentage on the way in plus the sell percentage on every rung out, plus one flat leg on entry. Fee income scales with volume and turnover, not with the fly's profit, so the platform's incentive is throughput inside the safety envelope rather than risk.

Once $XFLY graduates, the launchpad protocol charges trading fees on $XFLY/ETH in ETH. The creator-fee setting and fee routing are under design and will be published with the deployment parameters. This is the only stream that pays regardless of bot volume, and it accrues in the same asset as the bot's own Robinhood-chain fees.

Risks and disclosures

• Market risk. The system trades memecoins. Backtests on same-day launches show a median buy-and-hold outcome near −70%; the gates and ladders manage but do not remove this. You can lose what you spend.
• Custody. Bot wallets are custodial. Keys are envelope-encrypted with the master key confined to the worker environment, but custody is a trust relationship. Export your key and keep it.
• Data dependence. Discovery, scoring and pricing rely on third-party feeds. The engine fails closed on price integrity, and a data outage pauses lanes rather than trading blind.
• Tokenized equities. Robinhood stock tokens are tokenized instruments issued by a Robinhood entity and are not offered to US persons. The swarm rejects them as trading candidates, and the $XFLY launch does not use one as its quote asset, so neither requires holding one.
• Launchpad risk. Launchpad security audits may be in progress rather than complete. The graduation threshold is fixed in ETH, so its cost in dollars moves with ETH.
• Impostors. No XFLY contract exists yet. Until an address is published here and in the Telegram channel, any token named XFLY on any chain is fake. Check the contract address, not the name.

None of this is financial advice. The full terms and risk disclosure govern use of the bot.

Glossary

Fly

A saved auto-trade loadout: scent floor, chains, entry mode, exit ladder, swat line, size, concurrency.

Call

The Eye's pick that a fly acts on; one call of one token is an episode.

Flight

One fly's position on one call, from entry to exit.

Landing

The entry itself — the fly settling on a called token.

Swatted

The flight closed at the hard stop before the first take-profit target printed.

Rung / floor

A take-profit level and the ratcheted stop it locks in once filled.

Near-miss

Selling on reversal after price came within a set distance of the next rung without filling it.

Foot-probe

A two-way live quote and simulated sell proving a token can be exited at the venue, failing closed on error.

Wingload

Spend per flight × concurrent flights: the most a fly can have in the air at once.

Graduation

The point at which a bonding-curve launch migrates to a permanently locked pool.

Shadow

A mode that observes, scores and records but never signs a transaction.

Smart cluster

K distinct tracked wallets buying the same token inside a 30-minute window (XF-6).

House flies

The platform's own swarm, flown on its own capital; its profit is the buy-and-burn source.