How leader replacement actually works (and why it matters)

Selection is treated as permanent. It is not.

Almost every copy trading product on the market is built around a single decision: which trader do you follow. The interface is a leaderboard, the action is a subscribe button, and after that the product has essentially nothing left to say. There is no mechanism that ends the relationship. If the trader you selected stops being good, the system keeps mirroring them faithfully until you personally notice and intervene.

That is a strange way to build a system whose entire value proposition rests on the quality of one input. A trader's public record is evidence about how they behaved over a past window. It is a reasonable basis for allocating capital. It is not a property of the trader that persists indefinitely, and treating the selection decision as permanent quietly assumes that it is.

Replacement is the part of a copy trading system that decides what happens when the original assumption stops holding. It deserves more attention than the selection step, because selection happens once and replacement is the process that has to run forever.

Why edge decay is inevitable

Edge decay is not a moral judgement about a trader and it is not usually a sign of carelessness. It is the ordinary outcome of a strategy interacting with a changing market and a growing account. On Hyperliquid perpetual futures there are four mechanisms that do most of the work.

• Regime change. A trader whose approach depends on directional persistence performs differently once volatility compresses and moves stop extending. Nothing about their execution changed; the conditions the strategy monetises are no longer present. Regimes shift on their own timeline and no scoring window can anticipate the shift.
• Crowding. Profitable behaviour on a transparent venue is observable. Hyperliquid positions and fills are on-chain, so a working pattern attracts imitation, and imitation compresses the dislocation the pattern exploited. The more legible the edge, the faster this happens.
• Size growth. A strategy that worked at one account size may not survive at five times that size. Larger orders consume more book depth, entries and exits move price against the trader, and the market selection that was viable narrows to the deepest perps. Success itself degrades the conditions the record was built under.
• Strategy drift. Traders change. Holding periods shorten, leverage creeps up after a losing stretch, market selection widens into thinner perps, a directional trader starts fading moves instead. When behaviour changes, the historical record stops describing the strategy currently being run — the score is measuring something that no longer exists.

How the system detects deterioration

Membership in the Elite basket is sticky. A leader is not dropped because someone else out-scored them this week; they are dropped when a rule fires. The score ranks candidates and weights capital across the basket, but a higher composite score elsewhere never by itself forces a replacement. That is deliberate anti-overrotation: rank-chasing on a transparent venue produces churn, and churn costs exit slippage, taker fees and a builder fee on every rebuilt position.

Detection instead runs on explicit thresholds evaluated per wallet. Activity is checked as a floor: fewer than 5 trades in the last 7 days, 7-day volume under $25,000, or 48 hours or more since the last fill each count as a soft issue. Risk is checked as a 30-day trading maximum drawdown above 35%. Return is checked as a 30-day PnL-based ROI below -15%. Any of these on a given evaluation day marks that day as a soft-issue day.

Two measurement details matter more than they sound. Drawdown is computed on jump-adjusted equity, not raw account value: a wallet that withdraws half its balance has not lost anything through trading, and treating that step-change as a trading drawdown would evict perfectly healthy leaders while masking real losses in accounts that keep topping up. ROI is likewise derived from PnL rather than balance change, for the same reason. Any system that gates on raw equity curves is measuring deposits as skill.

What the thresholds can see is realized, closed outcomes and observable activity. What they cannot see is intent — whether a leader is deliberately switching approach, sitting out a regime they distrust, or has simply stopped paying attention. Behaviour is the only honest input available, so behaviour is what gets measured.

Emergency removal and soft strikes are different mechanisms

Deterioration arrives at two very different speeds, and treating both the same way would produce the wrong response to at least one of them. So there are two paths.

Emergency removal handles conditions where waiting for more evidence is irrational. There are two: account value falling below roughly $1,000, and no fill for 96 hours or more combined with zero trades in the last 7 days. The first means the account no longer has the capital to run the strategy it qualified on. The second means the leader has effectively stopped trading, so the allocation is dormant and the record is describing a trader who is no longer present. Neither improves with more data. Removal happens on detection.

Soft strikes handle everything slower. A day on which one or more soft issues are present produces at most one strike per wallet per UTC calendar day — the cap exists so that a single bad stretch cannot be counted five times over by five overlapping metrics. Three strike-days trigger replacement. A clean evaluation day resets the counter to zero, so a leader who dips below an activity floor for a day and then trades normally does not accumulate a permanent record against themselves.

The structure buys a specific thing: time. Three strike-days means ordinary deterioration takes days, not minutes, to remove a leader, which is long enough for a statistically ordinary losing sequence to resolve itself and short enough that a genuinely broken leader is not carried for a month. It also means the process is honest about its own lag — during the strike window your account keeps mirroring that leader.

The distinction separates two questions that get conflated constantly: is this leader performing worse than expected, and is this leader still capable of running the strategy we allocated to. The first deserves patience. The second does not.

What happens to open positions

This is where sub-account isolation stops being an architectural detail and becomes the thing that makes replacement clean. Each mirrored leader trades in its own Hyperliquid sub-account, with its own balance, its own margin and its own liquidation price.

When a leader is removed, the mirrored positions in that leader's sub-account are closed at market, and the freed capital is reallocated to the incoming leader's sub-account under the current score weights. Every other sub-account is unaffected: no other leader's positions are touched, no other leader's margin changes, and no other leader's liquidation price moves. Attribution stays intact, so the outgoing leader's realized contribution is a closed, separable number rather than something entangled with the rest of the basket.

Compare that with a system that mirrors several leaders inside one netted account. Hyperliquid holds one net position per market per account, so unwinding one leader's contribution there means adjusting a net position that other leaders are also contributing to — and any margin released or consumed changes the risk profile of positions that had nothing to do with the replacement. Isolation is what allows a leader to be removed as a discrete operation instead of a portfolio-wide disturbance.

The honest part: replacement is not free. Closing at market pays taker cost, the 0.1% builder fee applies to the closing notional as it does to any mirrored volume, and the exit price is whatever the book offers at that moment rather than a price of our choosing. Sometimes a position closed on replacement would have recovered, and the removal will have cost you that recovery. There is no version of a rules-based process that avoids this — a rule that only ever fires when it turns out to have been right is not a rule. What the process can do is keep those costs bounded and infrequent, which is exactly why the default path requires three strike-days rather than firing on the first bad day.

Why rules-based beats manual, including your own judgement

The realistic alternative to automated replacement is not a better automated process. It is you, watching, and deciding. That comparison is worth making explicitly, because manual replacement fails in patterns that are well documented and not really about intelligence.

Manual removal is late by construction. A drawdown becomes emotionally obvious well after it becomes statistically meaningful, so the decision to stop following a trader tends to arrive near the bottom of their bad stretch — which is also, for a strategy that has not actually broken, the point where expected forward returns are least bad. Threshold-based evaluation fires on the same drawdown and activity numbers regardless of how the loss feels, and it counts strike-days rather than waiting for the pain to become undeniable.

Manual selection of the replacement is also biased. Under the discomfort of a loss, the natural move is toward whoever has performed best most recently, which systematically selects for traders whose recent numbers are inflated by a favourable regime — the most fragile moment to allocate to them. A scored candidate pool applies the same floors and the same five factors to the incoming leader as to the outgoing one, with no weight given to how recent or how salient their good period was.

And manual processes are inconsistent across leaders and across time. The threshold you apply to a leader you chose yourself is not the threshold you apply to one the system chose. The threshold you apply while up is not the one you apply while down. Rules do not have that variance, and they do not require you to be awake. Perpetuals trade continuously; a leader can breach position discipline at any hour, and a process that depends on you noticing is a process with gaps in it.

None of this makes the rules correct in every instance. It makes them consistent, and consistent application of a defensible rule is the only thing that compounds. A discretionary process that is right more often but applied unevenly does not.

Adaptive following versus static following

The practical difference between a static and an adaptive system shows up over a long enough window that most users never see it in a demo. A static system's composition is a snapshot of who looked good at signup. An adaptive system's composition is a sticky basket that is continuously re-checked against explicit criteria, with removal available as an ordinary outcome — through strikes when deterioration is gradual, immediately when the account is broken or dormant — rather than as an emergency you have to spot yourself.

That is the whole reason replacement logic belongs in the same design as score-weighted allocation and sub-account isolation. Weighting decides how much each leader gets. Isolation makes each leader independently accountable and independently removable. Replacement decides when the allocation should stop. Any one of the three without the other two is incomplete: weighting without replacement allocates carefully to a set that never changes, and replacement without isolation cannot be executed without disturbing everything else.

If you want the mechanics underneath this — how the five factors are computed, how score translates into an allocation weight, and how isolation is structured per leader — the scoring note and the documentation set them out, and the risk disclosure covers what replacement does not fix, including replacement lag itself.