Token Airdrop Weekly Intelligence — October 5 – 11, 2026

The same five questions every week, so that patterns become visible across issues. This week the market was supply-heavy and measurement-light: three of the four largest unlocks were sized two ways by different trackers, and the week's biggest event was not an unlock at all but a security failure in the hardware wallets claimants use to hold what they receive. Answers below run from what actually moved to what to watch next.

How to read this issue

The five questions below are fixed week to week so that their answers can be compared across issues; only the content changes. A few conventions apply throughout. A "printed end date" is a date the project or exchange itself published, not a tracker's estimate; where a date or figure comes from a third party, the row says so. Where two sources give different sizes for the same event, both are printed and neither is averaged — this week that convention does more work than usual. Nothing is presented as fact unless the project has said it, and anything labelled a prediction is a scheduled date rather than a forecast of an outcome.

One scope note matters for reading the week correctly. This issue covers events that took place between October 5 and 11, 2026. Dates before that window appear only where they are part of the timeline of an event inside it — an attack's run-up, a window that closed this week — and dates after it appear only as scheduled events. That boundary is what makes the five answers comparable from one issue to the next: each covers the same seven days, against the same fixed questions.

1.1 What defined market activity this week?

An unlock-heavy week with a supply-side tilt and an unusually large measurement problem. Four discrete releases above $20 million landed between October 5 and 11: Ethena's ENA (Oct 5), Hyperliquid's HYPE (Oct 6), Stable's STABLE (Oct 8) and ADI (Oct 9); a fifth supply event, RAIN's recurring monthly emission (Oct 10), moved the week's largest token count. Two of them — ENA and ADI — carried two headline sizes each, and a third, HYPE, carried a committed figure and a whitepaper ceiling that some calendars still display instead. That is not a market event so much as a data event: the same dates were reported with incompatible magnitudes, and no primary source reconciled them.

Underneath the unlocks, the week's defining story was a security one. The Ledger CryptoBilis drain on October 9 moved an estimated $86 million to $93.2 million out of hundreds of hardware wallets whose devices had been tampered with before delivery. Its relevance to this market is direct: the wallets swept were the same ones used to hold claimed tokens, the loss fell mostly on TRON USDT balances, and it demonstrated that "self-custody" depends on a supply chain most holders never inspect. The pattern — compromised keys and access rather than clever contract bugs — has been the dominant failure mode for months, and this drain extends it one step further: from the holder's keys to the device that holds them.

Put the two halves together and the week's structure is clear. On the supply side, tokens were released on schedule and, in the one case with a clear buyer, routed off-book — an orderly, predictable process. On the custody side, the assumption everything else rests on — that a device in your hand holds keys only you control — was shown to be conditional on where the device came from. That asymmetry is the useful takeaway: the release calendar behaved exactly as published, while the security layer beneath it did not. A claimant who planned for the first and not the second had the wrong risk model for the week.

The security half deserves a second look, because its timing was not incidental to the week's structure. The drain executed on the same day that several scheduled items landed — an unlock, a threshold-driven claim round and a liquidation close — so the one event with no date attached to it had to compete for attention with several that did. Whether that alignment was chosen or coincidental cannot be established from the public record, and it does not change the outcome, but it does explain why the week's most consequential event for holders was not the one a calendar would have flagged.

It is worth separating the week's two halves by their half-life, because that is what makes one matter more than the other. The unlock figures will be superseded within days as the sizing disputes settle or are forgotten, and the threshold print will be superseded by the next round. The custody failure will not: a tampered supply chain is a standing condition until a root-cause report names the step that failed, and the devices involved are the ones holders are still using. A reader who tracked only the dated items would have ended the week focused on the half that fades, and missed the half that persists.

1.2 What is the state of live and upcoming claims?

The tracked board stayed stable in count and gained a dated row. Three rows now carry a printed end date: Sonic's unclaimed burn (October 15, roughly 32.69 million S), Pharos's portal close (October 25) and Grass Stage 2 (January 22, 2027). One printed-window row left the board: the Kraken Beldex and Humanity liquidation closed on October 9, its two-window ambiguity resolved in favour of the exchange's own notice.

The pattern worth naming: this week's claim-side attrition came from gates, not windows. Cambria's Opt-In deadline and Kraken's liquidation both ended on fixed dates, and neither offered a second chance. A live claim with an open window invites procrastination; an eligibility gate does not, and the two are frequently presented the same way in airdrop guides.

The practical rule that falls out of this is to treat gates and windows as different instruments. A window is a deadline you can plan around; a gate is a decision that must be made in advance, whose cost is not the reward you forgo but the eligibility you lose. Cambria's opt-in is the clean example: accepting the agreement cost a holder nothing at the time, while declining it — or simply not noticing — removed an allocation entirely. Two of the week's items were gates rather than windows, a higher proportion than a supply-heavy week would suggest, and it is the category most easily missed by anyone tracking only claim amounts.

There is a second pattern in the board's stability. The count of live claims barely moved, but the composition shifted: one row gained a date, one row closed, and two rows entered the dated tier's neighbourhood without yet qualifying for it. Stability in a headline number can therefore hide real movement underneath, which is why this tracker reports tiers rather than a single total. A holder scanning for "how many claims are live" would have seen almost no change; a holder scanning for "what do I need to do this week" would have seen four separate items.

Two further properties of the board are worth stating because they are easy to misread from a single week. The first is that the tiers are ordered by visibility, not by value: a row in the dated tier is not more valuable than one in the open-window tier, it is merely more legible. The second is that the counts move in single steps, which means a change of one is not noise to be smoothed away — it is the week's entire movement, and it should be read together with its cause. Pharos's addition and Kraken's removal both shifted the count by one in opposite directions, and only the reasons distinguish them.

1.3 What changed in eligibility mechanics?

Two shifts, in opposite directions. Binance Alpha's October 9 round replaced a fixed allocation with the "Alpha Box" — a multi-project pool split into Common (80%), Rare (15%) and Ultra Rare (5%) tiers, assigned at claim time. The threshold (245 points) and cost (15 points) stayed legible, but the reward behind them became a distribution rather than a number, which changes the decision from "is the allocation worth the points?" to "is the expected value of a box worth the points?"

Monad ran the disclosure order backwards. It published a claim-portal date (October 14) and an allocation-check date (October 28) while leaving eligibility rules, task list and weighting unpublished at the time of writing. It describes the model as task-based and time-bound, with tasks granting eligibility directly and no manual review — a transparency claim, but not yet a disclosure. The ethical wrinkle is that a claimant cannot verify the fairness of a task-based airdrop until the tasks are known, and by then the window may have opened.

Ethos, meanwhile, showed the third approach: it made the unlock a property rather than a permission. The WHUF contract upgrade replaced a multisig-controlled switch with a timestamp hardcoded on-chain, so the October 8 unlock required no eligibility decision at all — it simply happened at 15:00 UTC, with the 1,425 locked wallets becoming transferable automatically. Eligibility converged on "verifiable and final"; three projects this week split that into three different interpretations.

Set beside each other, the three readings describe a genuine design fork. Alpha Box puts discretion in the reward — the pool is fixed but the tier is assigned at random. Monad puts discretion in the gate — the portal is dated but the rules are unpublished. Ethos removes discretion entirely — the unlock is a timestamp, not a decision. The fork matters because a claimant's planning burden differs in each case: randomisation requires pricing an expected value, an unpublished gate requires watching for disclosure, and a hardcoded unlock requires nothing at all. Of the three, only the last is auditable by the claimant before it happens, and that is the direction eligibility mechanics appear to be moving.

There is a fourth reading, less comfortable than the other three, in how each project handled its moment of uncertainty. Alpha Box moved the uncertainty into the claim itself, where the randomness is at least described in advance. Monad moved it into the gate, where it stays invisible until the rules appear. Ethos removed it, which is why its model is the easiest to trust and the hardest to replicate — a hardcoded timestamp is only available to a project willing to commit to one, and most will not. The lesson is not that a single design is correct, but that a claimant should ask which of the three they are dealing with before allocating effort, because the diligence each requires differs by an order of magnitude.

1.4 What did post-airdrop behaviour show?

Two clean observations. First, on concentrated unlocks: Hyperliquid's 3.75 million HYPE went not to a scattered set of core contributors selling into the market, but to a single institutional buyer through an over-the-counter trade. HYPE traded near $92.60 on October 6, up 1.4%, having held above $91 through the session — an orderly response that tells us more about routing than about demand, because the supply never touched the public order book. The follow-up question, whether that batch moves on-chain toward exchanges, is still open.

Second, on gate expiries: Kraken's liquidation closed on October 9 after a three-week run-up during which the only actionable step was withdrawing before September 25. The episode ended with the exchange disposing of remaining balances at prices it explicitly declined to guarantee. That is post-airdrop behaviour in its least forgiving form — the reward was credited automatically, the exit was self-service, and the penalty for inaction was set by the exchange's order book rather than the project.

The two observations share a common thread worth stating plainly: in both cases the outcome was determined by a decision made before the event, not during it. HYPE's OTC routing was arranged in advance, so the unlock's on-the-day price said little about demand. Kraken's exit was available for three weeks, so the closing price reflected only those who had not acted. This is a recurring property of airdrop-adjacent events: the visible outcome is usually the residue of earlier choices, which is why the on-the-day numbers are the least informative part of the record and why this tracker leads with schedules rather than price moves.

A third observation belongs here, though it is about absence rather than action. The two events that generated the most speculation before the week — the HYPE unlock and the Monad portal — produced, respectively, no visible selling and no published rules. In both cases the informational vacuum was filled by estimates: a sizing figure for HYPE that turned out to describe a ceiling rather than a claim, and a recipient count for Monad that is a target rather than a verified distribution. The pattern repeats across the week and is worth naming, because it is the mechanism by which an unverified number becomes the number people quote.

1.5 Outlook for the week ahead

The next seven days carry four claim-side or deadline events and the month's densest TGE cluster. InterLink's 10M Linkers claim closes October 12 at 23:59 UTC. Monad's claim portal opens October 14 at 13:00 UTC. Sonic's burn executes October 15. Binance's USD1 Stage 2 terms are due on or before October 16, which is also the day Margex's ETH campaign ends. On the launch side, October 14 is the single busiest date: Monad, Enso and Yei Finance (CLO) all open claims or listings, plus Fleek's 10 million FLK community airdrop.

There is also an item on the board that is not a date at all, and it is the one most likely to be missed. Pharos's window closes October 25, but the row only became legible this week, when the project published the date; anyone who stopped scanning the board in early October would not know the row existed. That is the argument for treating the calendar as a recurring instrument rather than a one-off list — the set of dated rows changes even when no window opens, because visibility is itself a moving quantity, and it moves in both directions.

Two things to watch that are not dates. First, whether the Ledger supply-chain story produces a broader custody-hygiene response — a run of wallet-migration activity or a shift toward freshly generated seeds would be the first measurable behavioural effect. Second, whether the unlock-measurement disagreements (ENA, ADI, HYPE) recur next week or were a one-off cluster; if trackers keep publishing 8×-apart figures for the same event, this tracker will need a standing method note rather than per-week flags.

A third thread runs under both. The week's events all point at the same underlying question — how much of a claim's value is knowable in advance? Ethos answers "all of it," because the unlock is a timestamp. Monad answers "none of it yet," because the rules are unpublished. The unlock calendar answers "the date, not the size," because the size is disputed. Where that question gets answered earlier and more completely, a claimant can plan; where it does not, they can only react. That is the axis along which this market is most usefully read, and it is the one we will keep measuring next week.

Signals vs. noise

The table separates what changed the market from what changed only the commentary, and the split is not always intuitive. Two rows on the signal side — the Ledger drain and the HYPE routing — describe things that happened to supply or to custody, and therefore alter what a holder should do. Two others — the Alpha Box and the ENA/ADI sizing — describe things that happened to information, where the underlying event was ordinary but its reporting was not. The distinction matters because the noise column is where most of the week's traffic lived: a headline number that keeps moving as tracing continues, a price move that reflects off-book supply, the larger of two figures circulating because it alarms. Read top to bottom, the table is a quick way to sort the week into decisions and distractions.

Sources

FAQ

Related Reading

• Token Airdrop Weekly News Review — October 5 – 11, 2026
• Token Airdrop Weekly Data Report — October 5 – 11, 2026
• Airdrop Calendar & Tracker — October 5 – 11, 2026
• The CryptoBilis Drain: Anatomy of a Hardware-Wallet Supply-Chain Attack