Airdrop Calendar & Tracker — October 5 – 11, 2026

The tracked claim board by status, each row carrying a source link. This week two rows left the board (the Kraken liquidation closed; Cambria's opt-in deadline passed), one row gained a printed end date (Pharos, October 25), and the dated stack tightened to three: Sonic, Pharos and Grass. Confirmed-but-undated rows held at two — Jumper and AlloX — and the rumored tier stayed small. Where a date or figure comes from a third-party tracker rather than the project, the row says so.

Two structural changes are worth flagging before the tables. The first is that the dated tier held its count while changing its membership — Pharos entered and Kraken left, leaving the number where it started. The second is that the confirmed-but-undated tier stayed at two, which is its steady state: rows enter it when a project completes a sale or publishes an eligible list, and they leave only when a date is announced. Neither movement is dramatic, and both are the kind this board is built to record rather than to comment on.

How to read this board

The tracker sorts every claim it follows into one of five tiers, and the sort is by visibility rather than by size. The question each tier answers is not "how much is this worth?" but "can a claimant see, in advance, when it ends?" That distinction matters more than values, because the failure this board exists to prevent is a claim that expires while a third-party list still shows it as live. A reward can be large and still lost to a missed gate; a reward can be small and still safely collected. The tiers below run from the least visible (an open window with no published end) to the most final (a closed row), with the dated rows in between carrying the dates that actually do something.

One method note runs through the whole board. "Printed end date" means the project or exchange has published a specific closing date; an open-ended window, a countdown clock, or a tracker's estimate does not qualify. Where a date comes from a third-party tracker rather than the project, the source column names the tracker and the row is labelled accordingly. Closed rows leave the dated tier and appear under "Closed this week," so the dated count reflects only live obligations rather than everything the tracker has ever listed. This is why the count moves when a window ends rather than when it opens.

A consequence of sorting by visibility is that the board is not a ranking of value, and reading it as one is the most common mistake. A row in the confirmed-but-undated tier may be worth far more than a row in the dated tier; what differs is whether a claimant can see a clock. The board therefore answers two questions at once — what exists, and what is time-sensitive — and a reader who only wants the second should read the dated and closed tiers and skip the rest. Keeping the other tiers visible is a deliberate choice, because a project that has confirmed a token but not a date is a different kind of fact from a rumour, and collapsing the two would lose the distinction.

Live claims — open window, no printed end date

Grass is the only row here that is a claim in the ordinary sense: a live window with an amount a holder can already see. The detail most often misread is the payment asset — Stage 2 pays in USDC, not GRASS, and the project states explicitly that this creates no new GRASS tokens and leaves circulating supply unchanged. For anyone who counted the reward as a token allocation, that is a meaningful difference for valuation and for tax treatment alike.

Monad and AlloX sit in the same tier for different reasons. Monad's portal has not opened yet, so there is nothing to claim; its presence here records that the airdrop is real and dated, not that it is actionable. AlloX has an eligible list and live points but no confirmed token day, which makes it a farm-in-progress rather than a claim. Treating either as "live" in the sense Grass is live would be a category error the tier is meant to prevent.

The open-window tier is also where the board does the least for a reader, and that is by design. With no end date to sort on, the only ordering available is the project's own status, which is why these rows carry a short note instead of a clock. A reader looking for something to do this week should not find it here — these rows are context, not tasks — and the tier exists mainly so that the absence of a date is visible rather than simply unstated.

The three rows also illustrate why "live" needs a qualifier. Grass is live in the actionable sense: a holder can claim today and see the amount. Monad is live only in the scheduled sense, because the portal it points at has not opened. AlloX is live in the accrual sense, because points are being earned now but no token exists to claim. Three meanings of one word, held in a single tier only because none of them yet carries an end date; the moment Monad's portal opens it becomes actionable, and the moment AlloX dates its TGE it moves.

Live claims — with a printed end date

Three rows, three different consequences for a missed date — and the difference is worth reading before treating "the deadline" as a single kind of event. Sonic's burn destroys unclaimed supply outright, which is a supply-side change that affects everyone still holding S, not just the wallets that never claimed. Pharos returns unclaimed tokens to its foundation, which keeps them in circulation under the project's control. Grass simply retains what is not claimed, with no burn and no return of supply. The dated count stayed at three only because Kraken's liquidation left the tier on October 9; before that it was four.

There is a fourth distinction the three rows make, about what a claimant actually controls. Sonic's burn affects holders whether or not they ever looked at the claim; Pharos's close returns tokens to a foundation that already holds the rest of the supply; Grass's expiry simply leaves value unclaimed. Only the first changes the asset for everyone. That is a reminder that "deadline" describes a date, not a consequence, and the consequence is what determines whether missing it matters to anyone beyond the claimant — which is why the table's middle column exists.

Note also what the dates do not say. Sonic names a day but no time, which means the burn can be triggered at any moment after the date without further notice — a reminder that a "printed end date" is a floor on when a window closes, not a precise instant. Pharos's date is the last day of a stated 180-day claim window, which makes it one of the few rows where the end date is derivable from the project's own published duration rather than from a fresh announcement.

Upcoming — dated

October 14 is the single busiest date on the near-term board: Monad's portal opens, and three claim or listing events — Enso, Yei Finance and Fleek — land the same day, with the CLOUSDT perpetual arriving alongside Yei's Alpha listing. That clustering has a practical consequence for anyone running multiple campaigns at once: two of those four use Binance Alpha Points as the entry currency, so a single point balance has to cover two simultaneous claims, and the order in which a holder claims can change what remains available for the next one.

Two of the dated items are schedule updates rather than new events. Binance's USD1 Stage 2 terms are due "on or before October 16," which is a promise of disclosure rather than a claim window; the campaign runs continuously across the date. The tracker lists it because the terms determine the reward for the second half of October, and because the stablecoin tranche (up to 2.5 million USD1) exists only in Stage 2.

The October 14 cluster is worth reading for a second reason: it is the point where claim-side and launch-side events begin to compete for the same operational capacity. A wallet claiming an Alpha Points allocation at the same time it is pre-positioning for a TGE is deciding where to hold value and how much gas or energy to keep available, and those decisions interact. None of the individual items is unusual; the compression is, and compression is exactly what a calendar exists to surface. A reader who plans item by item rather than by date will find three of the week's events landing on one day.

Confirmed — undated

"Confirmed" here means the project has said the token is real and committed to a launch; "undated" means it has not said when. Jumper is the week's clearest example of that gap: a completed public sale that drew roughly $48.6 million in subscriptions, a teased TGE, and no day attached. The tracker holds the distinction rather than resolving it, because a teased TGE is not a claim window and should not be treated as one. AlloX is similar but slightly further along — its MiCA whitepaper has completed the required process and it has published an eligible-user count, but the public round and TGE still follow in sequence without a fixed date.

It is tempting to treat this tier as a watchlist for future claims, and worth resisting. A teased TGE that has not been dated can stay here for months, and the trigger that moves it — a project publishing a day — is not something a claimant can accelerate. The useful action, if any, is to note the row and set a reminder against the source rather than against a date, because the calendar will not warn you: this tier is defined by the absence of a date, so nothing in it will appear as an upcoming deadline until the project changes that absence itself.

Rumored — unverified

The rumored tier stays deliberately small, and that is a design choice rather than an accident. A tracker that lists every speculative launch dilutes its own signal; a tracker that lists only what a project has confirmed leaves genuine pre-announcement activity out of the picture. It sits in the middle by holding a row only when a project has named a window without a date, and by saying plainly why the row is unverified. Cambria qualifies because its $RSGP token is confirmed but its TGE window comes from an AMA rather than a project-published date — a schedule, not a deadline.

The tier's other function is defensive. Because it lists only projects that have named a window without a date, it doubles as a record of what has not been confirmed — useful when a claim appears to be missing from the board. If a project is absent from the dated and confirmed tiers, the honest answer to "why isn't this tracked?" is usually that the project has said nothing dateable, which is itself the finding. Keeping the rumoured tier small is what makes that inference possible; a tier bloated with speculation would make absence meaningless.

Closed this week

Three rows left the board on fixed dates, and two of them closed with value still on the table for anyone who missed the gate. The Kraken liquidation is the starkest: the replacement tokens were credited automatically months earlier, so no one had to claim anything to receive them — and yet the exit required a deliberate withdrawal before September 25, after which the exchange disposed of remaining balances at prices it explicitly declined to guarantee. Cambria's opt-in is the mirror image on the eligibility side: a hard gate that had to be accepted in advance, with no claims portal and no recourse for a missed deadline.

It is worth being precise about what "closed" means here. A closed row is not necessarily finished — holders of the replaced Kraken tokens received them months earlier and still hold them; what closed was the exchange's window for disposing of the remainder. Cambria's token has not launched at all, and what closed was a gate. The board records closures at the level of the actionable step, not the level of the project, which is why a single project can appear in more than one tier at the same time.

This tier exists so that a closed window is visible as closed. The most common failure in airdrop tracking is a claim that quietly expires while a third-party list still shows it as live; recording closures explicitly is what keeps the dated count honest. The Alpha Box round was a same-day event rather than a window, and it is listed here for completeness because it produced a threshold print the data report tracks.

The three closures also differ in whether anything could have been done about them, and that is the part worth carrying forward. Kraken's exit was open for weeks and its warning is a plain one: the replacement tokens were credited automatically, so the loss fell on holders who had no reason to act on a claim they never made. Cambria's gate required an affirmative choice, so the loss fell on those who ignored an instruction rather than those who missed a reward. Alpha Box was a same-day event with no carry-over at all. Three closures, three different failure modes, and only one of them was about missing a deadline.

Change Log

What moved this week, stated as before-and-after so the board can be audited against last week's edition.

• Kraken (BDX/BELDEX, H/HUMANITY): moved from "Live — printed end date" to "Closed this week." The two-window ambiguity (exchange notice Oct 2–9 vs third-party Sep 28–Oct 2) is resolved; the exchange's notice is treated as primary. Effect on the dated count: −1.
• Pharos (PROS): moved from "Live — no end date" to "Live — printed end date" (Oct 25). First week this row carries a visible close. Effect on the dated count: +1.
• Cambria (RSGP): moved from "Upcoming — dated" to "Closed this week" on the opt-in gate (Oct 8), while its TGE expectation (Oct 13–14) remains unverified and stays in the rumored tier.
• Monad (MON): added to "Upcoming — dated" with a confirmed Oct 14 portal; eligibility rules still unpublished.
• Jumper (JUMP): added to "Confirmed — undated" after its Legion sale closed with no fixed TGE date.
• Binance Alpha Box (Oct 9): added to "Closed this week"; the round's 245-point threshold enters the data report's series.

The log is short this week, and deliberately so: five of its six entries are single-row moves, and the sixth — the Alpha Box round — affects the data report's series rather than the board. A quiet log is not the same as a quiet week. It means the board's structure held while its contents changed, which is exactly the case a calendar is designed for; the weeks with long logs are the ones where the tier definitions themselves moved.

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 — September 28 – October 4, 2026
• Airdrop Market Report — September 2026