Operator Finder · RH Pipeline

Operators

—

Mirror

—

2x Fib

—

Edge

—

Loading…

Should I copy this downline?

Track record

Plays — 2x fib vs lead mirror

Token	Fired	Mirror	Fib	Edge	Peak

This operator

—

Seeds & funding back-trace

—

Winner wallet	Token	Peak	Found	Trace	Tries	Funder / relay	Cluster

Funded burner wallets

—

Address	Operator	Funded	ETH	Window	Fired	Lead	Mirror	Fib	Copy

Shadow-sim plays

—

Token	Operator	Fired	State	Mirror	Exit	Fib	Fib exit	Edge	Peak	Hold

Event wire

—

When	Operator	What happened	Token	Wallets	Block

Copy engine

—

Arm

Mode Dry run runs the whole slot lifecycle and only logs what it would tell Maestro — no Telegram traffic, no order. Off opens nothing; slots already open still drain.

off dry run

This page offers off and dry run only — there is no live control here, and saving from this page can never arm live mode.

Maestro chain button (Robinhood) The verbatim label Maestro shows for the Robinhood chain in its Telegram menus, e.g. HOOD. maestro_client.CHAIN_BUTTON_NAMES has no Robinhood entry and a guessed label breaks navigation mid-flow, so live mode refuses to act until this is set. Read it off the Maestro chain menu and copy it exactly, spacing and emoji included.

Size

Max buy per burner — ETH Operator Finder's sizing knob, in ETH. The per-wallet buy cap handed to Maestro for each relay burner this engine adds on the Robinhood chain. This is not Copy Trade's ct_default_max_buy_usd, which is in USD and sizes Maestro copy wallets on Base/BSC/Solana. Two systems, two knobs, two units — setting this one changes nothing about Copy Trade, and vice versa.

ETH

Max slots Concurrent copy slots across all operators. Maestro's copy list is bounded (~12 entries) and it is shared with nothing else on this chain.

slots

Burners per play How many burners of one funded batch to claim when an operator with no per-operator override fires. Every burner in a batch buys the same token within seconds, so this buys redundancy against one burner being missed, not extra exposure to a different token.

burners

Exit

Stale after A slot that never saw its operator's exit is released after this long, so a dead play cannot squat a slot (or a Maestro copy entry) forever.

hours

Open slots & action feed

—

Detection & discovery

—

Look

Detection The monitor's master switch. Off stops every sweep; tracked relays keep their state and nothing is forgotten, we simply stop looking. This is not the copy engine — that has its own mode on the Copy engine tab.

off on

Poll interval Wall-clock gap between sweep cycles. A cycle itself takes as long as it takes — under Blockscout degradation a full funding sweep has been measured at ~16 minutes — so this is the pause after one, not a promise about cadence.

seconds

Burner sweep TTL How stale a burner's token history must be before it is re-fetched. Lower means a fire or sell is noticed sooner; higher means less Blockscout load, which is the resource the whole sweep contends for. Was settable only by SQL despite the source describing it as tunable.

seconds

Find

Discovery Back-traces graded winners to the relay that funded them. Off leaves the tracked fleet exactly as it is; nothing new is found and nothing existing stops.

off on

Minimum multiple How big a winner has to be before it is worth back-tracing. Every trace is a chain of Blockscout calls, so this is the knob that decides how much of the sweep budget discovery spends.

×

Discovery interval Gap between discovery sweeps. Discovery runs on its own thread, so this is independent of the poll interval above.

seconds

Grow

Drip-hub auto-track Whether a funder that drip-feeds several graded winners is tracked automatically. This one adds relays — every relay it tracks is swept every cycle forever after — so it is the knob that decides how fast the fleet grows. Was settable only by SQL.

off on

Read operator history Reconstructs plays from a tracked relay’s past funding batches — the ones older than the 48h watch window, whose burners the live sweep will never look at. Runs only in the idle time between cycles, and not at all on a cycle that used its whole budget, so it cannot slow detection down. Reconstructed plays are labelled everywhere they are counted; they are never fed to the copy engine.

off on

Auto-track ceiling The most enabled relays auto-track may grow the fleet to. Every enabled relay is swept every cycle, so this is the ceiling on per-cycle cost. At the cap a discovered relay is recorded, not dropped — it is retried when the cap moves. Counts enabled relays only: a disabled one costs nothing, so it does not occupy a slot. Does not apply to relays you track by hand.

relays

Drip-hub minimum cluster How many graded winners one funder must be keeping alive before it counts as a hub worth tracking. Lower tracks more addresses on thinner evidence. Was settable only by SQL.

winners

Explorer exits

—