Token Airdrop Weekly News Review — September 28 – October 4, 2026

Eleven source-verified items this week. The through-lines: Binance renewed its USD1 airdrop for a fifth consecutive round and — for the first time — attached a stablecoin reward; a Concrete (CT) token generation event collided with a same-ticker City Protocol in the trackers; and the NEAR ecosystem, two days after getting its first US spot ETF, absorbed a $3.8 million exploit that ended in a full recovery. As always: who said it, where it was said, and nothing presented as fact unless the project itself has said it.

1. Binance renews the USD1 airdrop a fifth time — and adds its first stablecoin rewards

Binance announced on October 1–2 that the USD1 holder airdrop continues from October 2, 2026 at 08:00 (UTC+8), with a total pool of 150 million WLFI plus — a first for the program — up to 2.5 million USD1. The campaign runs in two stages: Stage 1 (October 2–16) distributes 75 million WLFI; Stage 2 (October 16–30) distributes another 75 million WLFI plus the USD1 pool, with Stage 2 terms to be updated on or before October 16. Weekly payouts arrive by 02:00 UTC+8 each Saturday (18:00 UTC Friday), calculated from hourly snapshots of net USD1 balances across Spot, Funding, Margin and USDⓈ-M Futures accounts. USD1 held in Futures or Margin earns a 1.2× multiplier only while daily open interest on USD1 pairs stays at or above 300 USD1. Sources: Binance News (Oct 2); Binance announcement (Oct 2).

Our take: the design detail that matters is not the pool size — 150 million WLFI matches the previous round — but the composition change. A stablecoin reward tranche, however small at 2.5 million USD1, moves the campaign from "yield paid in the issuer's own token" toward "yield paid in the asset itself." It is also a quiet acknowledgment of the measurement gap we have tracked all month: WLFI payouts have never arrived with a published per-distribution value.

2. The previous campaign closed its fourth distribution — still without a published value

The Sep 4 – Oct 2 round of the USD1 campaign scheduled its fourth and final weekly distribution for October 2. As with the September 11, 18 and 25 distributions, no WLFI token value for the October 2 payout was published in sources accessible to us at publication. That makes it four distributions from four without a published value — the longest-running measurement gap this tracker follows. Sources: Binance campaign terms (Sep 4); prior weekly checks in our Sep 21–27 Data Report.

For context on how the round was built: the terms published September 4 set a 150 million WLFI pool over four weekly Saturday payouts, calculated from hourly snapshots of net USD1 balances across Spot, Funding, Margin and USDⓈ-M Futures accounts, with a 1.2× multiplier on Futures and Margin balances that only applies while daily open interest on USD1 pairs stays at or above 300 USD1. None of those mechanics changed across the round. What never arrived was the number that would let a holder verify what any single payout was actually worth.

Our take: four rounds and four blanks is no longer a measurement gap — it is the program's de facto reporting standard. When a distribution's token value is never printed, the reward is unverifiable at distribution time, and the only figure a farmer can underwrite is the one Binance just added: a stablecoin tranche, denominated in the asset itself. Whether Stage 2's USD1 payouts arrive with published values will tell us if that was the point.

3. Concrete (CT) held its TGE — Binance Alpha first, OKX and HTX the same day

Concrete Network, Ltd. executed the CT token generation event on September 30, 2026. Binance Alpha was the first venue to open trading at 08:00 UTC, with an airdrop claim for users holding at least 223 Alpha Points (200 CT per claim, the threshold decreasing by 5 points every 5 minutes while unclaimed, and each claim consuming 15 points). OKX and HTX listed CT/USDT spot the same day, with OKX running a structured call auction. CT is a fixed-supply (1 billion) governance and configuration token for Concrete's vault and yield platform: 35% ecosystem, 28% investors, 22% team, 15% foundation — meaning 50% sits with team and investors under long-term vesting. Contracts are live on Ethereum and BNB Chain. Coinbase added CT to its listing roadmap on September 9, which Crypto Briefing noted does not guarantee active trading. Trackers including CoinCarp had no CT price data at the time of writing. Sources: Binance Square (Sep 30); CoinMarketCap research summary; BSCN.

The allocation split deserves the farmer's attention more than the claim mechanics do. A 200 CT claim from a 1 billion fixed supply is 0.00002% of max supply per eligible account — the claim is a rounding error by design, and the 223-point threshold (falling 5 points every 5 minutes while unclaimed) is the campaign's real price discovery: it reveals how many point-holders wanted out of their points at all. That 50% of supply sits with team and investors under long-term vesting is standard for the category, but it means circulating float at TGE is a fraction of the headline number — trackers showing no CT price data in the first days is consistent with a thin, slowly-unfolding market rather than an anomaly.

Our take: this TGE's most useful output was not the token — it was the disambiguation. Two unrelated projects shared a tracker ticker this month, and only one of them (Concrete) demonstrably traded. When ticker strings and official documentation disagree, the docs win; the Data Snapshot in this issue now carries "Concrete (CT)" and "City Protocol ($CIT)" as separate rows, and we would advise every farmer to treat a ticker as a search query, not an identity.

4. Binance opened a two-batch Concrete trading competition

Alongside the listing, Binance Wallet launched a Concrete (CT) trading competition in two batches: October 1–8 and October 8–15 (21:00 UTC+8 boundaries). In each batch, the top 2,000 users by CT buy volume split 258,000 CT — 129 CT per eligible user — with early-bird and new-trader multipliers applied to effective volume. Source: Binance announcement (Oct 1).

The two-batch structure means the second window (October 8–15) overlaps two other dated events this tracker follows: the WHUF unlock on October 8 and Sonic's burn on October 15. Farmers running multi-campaign Octobers now have three clocks to reconcile in a single week, and only one of them (the competition) is a volume race where missing the window costs the entry rather than the asset.

Our take: 258,000 CT split 2,000 ways is a volume competition wearing an airdrop's clothes. The 129 CT per headline user is fixed regardless of how much volume it takes to place in the top 2,000, so the rational play is to know your point-and-fee budget before the batch opens — and to remember that "effective volume" with multipliers means the leaderboard, not raw buys, is what pays.

5. NEAR Intents lost $3.8 million in an Omni-infrastructure exploit

On October 1, 2026, NEAR Intents — the cross-chain swap service — disclosed a security breach: a bug in how its Omni deposit and withdrawal infrastructure interacted with its smart contract let an attacker drain more than $3.8 million from the platform's BSC hot wallet. On-chain analyst ZachXBT flagged the irregular outflows first; the stolen funds were routed to KuCoin and bridged into Bitcoin. The team said its SHIELD monitoring layer triggered an automatic pause, the contract-side flaw was patched within roughly an hour, and deposits and withdrawals across 11 networks (BNB Smart Chain, Polygon, TON, Optimism, Avalanche, Stellar, Monad, X Layer, ADI, Scroll and Plasma) stayed suspended for roughly 12 hours. NEAR Intents pledged full reimbursement and reported the incident to law enforcement. The core NEAR Protocol blockchain, the NEAR token and other applications were unaffected. Sources: The Cryptonomist (Oct 1); Protos (Oct 1); ThreatCluster.

6. The twist: the exploiter returned the full $3.8 million

On October 2, NEAR Intents general manager Alex Shevchenko said the team had identified a suspected exploiter and published return addresses across Bitcoin, EVM chains and Solana, giving the attacker 48 hours to send the money back. Reporting citing the team's statements says the exploiter complied — the full $3.8 million was returned within the window, with a message from the attacker embedded in the return transaction — and the team closed its investigation on October 4. That is a rare full recovery within days. Sources: Blockchain Breaches (citing AMBCrypto, Cryptobriefing).

Our take: a full recovery is the best-case ending, but the sequence matters more than the outcome. The same protocol that froze $503,000 of Bitget hacker funds on September 28 could not keep its own hot wallet safe four days later. Infrastructure that sits in the middle of every cross-chain flow is a single point of failure in both directions — and airdrop farmers routing claims through NEAR Intents had 12 hours of frozen deposits to think about it.

7. Bitwise launched the first US spot NEAR ETF — two days before the exploit

Bitwise's NEAR ETF (ticker NRR) began trading on NYSE Arca on September 29, 2026 — the first US spot exchange-traded fund dedicated to NEAR. The fund holds spot tokens directly, carries a 0.75% management fee, and stakes assets through an institutional desk targeting an estimated 5% annual reward rate. Bitwise's fund materials cited NEAR Intents' total swap volume of over $32 billion as part of the investment case. The exploit arrived two days later; NEAR fell roughly 7.5–8.6% intraday on October 1 (source accounts differ: $5.1 → $4.79 per Protos; a fall to $4.92 per BeInCrypto via ThreatCluster; the daily close was $4.8090, −9.96%, per Binance data on Investing.com). Sources: CoinDCX; TheCryptoDesk; Investing.com (Binance NEAR/USD).

Two details make this relevant to airdrop watchers specifically. First, the product design: a spot ETF that stakes means passive US brokerage exposure now competes with self-custody farming for the same token's yield — 0.75% of fees against a targeted ~5% staking reward is a net ~4.25% before token price moves. Second, the marketing dependency: the fund's investment case leaned on NEAR Intents' $32 billion cumulative swap volume, and that same infrastructure was the thing that broke 48 hours later. The weekly close still printed $5.0010 on October 2 (per Binance data on Investing.com) — above the $3.33 trigger from the airdrop design we profiled two weeks ago — so the price-gated cycle remains in its untested-below-trigger state.

Our take: an ETF debut and an exploit in the same week is the NEAR story in miniature — institutional packaging arriving on top of retail-grade operational risk. The full recovery (item 6) rescues the week's outcome, but the sequence is the lesson: the same swap rails cited in an ETF prospectus are also the attack surface, and no fee schedule prices that.

8. Ethos hardened the WHUF unlock before it happens

Ethos Network shipped a contract upgrade on September 28 — audited by Guardian — that replaces the WHUF token's original multisig-controlled global unlock switch with a timestamp hard-coded on-chain: October 8, 2026 at 15:00 UTC. A frozen lock list of 1,425 sale and bonus wallets (publicly verifiable on Basescan) stays locked until that moment, while the Foundation treasury is separated so market makers can receive inventory before transferability begins. The 85% price guarantee for vouched tokens is unchanged, and the guarantee eligibility window closes when tokens become transferable. Context from the sale: the auction raised $8.4 million from 1,560 participants at a $4.20 clearing price (2 million WHUF, 20% of the fixed 10 million supply; implied FDV ≈ $42 million), and only 31% of the referral pool was used, so 60,530.73 WHUF were burned — a 0.6% supply reduction. No exchange listing has been officially confirmed for October 8. Sources: Bitrue; CoinGabbar.

Our take: hard-coding the unlock timestamp on-chain converts a promise into a property. A multisig-controlled switch asks 1,425 locked wallets to trust a committee's future behavior; a timestamp hard-coded at October 8, 15:00 UTC lets every one of them verify their own lock expiry on Basescan without trusting anyone. The 31%-used referral pool — and the 60,530.73 WHUF burn that followed — is the same discipline applied to distribution: underspend gets retired, not recycled. Eligibility design is converging on "verifiable and final," and projects that keep discretionary switches after this will look increasingly dated.

9. City Protocol's token is $CIT, not CT — and its TGE execution is unconfirmed

A ticker collision worth untangling. September trackers (Bitrue, citing ICO Analytics) listed "City Protocol (CT)" with a September 28 TGE. City Protocol's own documentation, however, names the native token $CIT: a fixed 10,000,000,000 supply minted on Ethereum before TGE, 17.9% (1,793,365,000 CIT) unlocked at TGE including the full 1% airdrop allocation (100,000,000 CIT), and team/advisor and investor allocations with no TGE unlock. We found no accessible confirmation that the September 28 TGE actually executed. The other CT — Concrete's — is the token in item 3. Treat the two as unrelated projects that happened to share a tracker ticker. Sources: City Protocol docs; Bitrue; Bittime.

The tokenomics detail that matters for the hypothetical claimant: the 1% airdrop allocation (100,000,000 CIT) is listed as fully unlocked at TGE — no vesting tail — while the team/advisor and investor buckets carry no TGE unlock at all. That is the inverse of Concrete's structure (where 50% of supply is team-and-investor under long-term vesting) and of most TGEs this tracker has tabulated this year. It is also all unverified until a TGE is confirmed to have happened, which is why this row sits in "unconfirmed execution" rather than "completed" in the calendar.

Our take: when trackers and official documentation disagree, the docs win — and the correction has a cost. Every September row that printed "City Protocol (CT), TGE September 28" now needs a footnote; we corrected ours. The deeper point is that "TGE happened" and "TGE was scheduled" are different facts, and this cycle produced a full week where trackers printed the second as if it were the first.

10. Kraken's Beldex/Humanity liquidation: two windows in circulation

The payout for Kraken's delisted Beldex and Humanity tickers closed on September 25, 2026 at 14:00 UTC, and whatever remained went to automatic liquidation. Two windows are now in circulation: Crypto World Headline's Week 40 write-up described a September 28 – October 2 liquidation that "has now ended," while Kraken's own support notice for the Beldex migration states remaining balances are liquidated between October 2 and October 9, 2026 — a window that was still running at publication. We print both values and treat the exchange notice as primary. The exchange's own language remains unusually blunt: liquidation prices may fall well below recent reference prices, and proceeds could be minimal or zero. Sources: CryptoTicker Week 40; Kraken support notice — Beldex migration.

What is not in dispute is the sequence and the stakes. Withdrawals closed September 25 at 14:00 UTC — that date is consistent across both reports — and everything still sitting in affected accounts after that moment became subject to automatic disposal at market prices the exchange explicitly refuses to guarantee. For a holder who missed the window, the difference between the two printed windows (Sep 28 – Oct 2 vs Oct 2–9) is not academic: it is whether any disposal of their balance happened this week or is happening now.

Our take: two windows in circulation for the same liquidation is a small episode with a large lesson — third-party deadline lists are snapshots, exchange notices are the ledger. When they disagree, print both and weight the exchange; and note that "the deadline has passed" is itself a claim that can be wrong. The blunt zero-proceeds language is Kraken being honest about slippage on illiquid delisted assets — every delisting airdrop carries that risk, and almost none of them print it.

11. The week ahead: an October deadline stack and a $1.11B (or $1.9B) unlock wave

Dated items now on the calendar: InterLink's First 10M Linkers claim closes October 12, 2026 at 23:59 UTC (1 ITL plus a commemorative NFT per eligible user; holders must have at least 10,000 ITLG at distribution time). Sonic's unclaimed-token burn executes October 15. Margex's $2.7M ETH campaign ends October 16. And the early-October unlock wave is large — with a familiar tracker disagreement: BeInCrypto's snapshot puts October 5–11 unlocks at roughly $1.11 billion (3.75 million HYPE ≈ $340 million on October 6 — which the team says goes to a single institutional buyer — plus 171.88 million ENA ≈ $41.52 million on October 5 and 11.31 million APT ≈ $9.06 million on October 11), while a Tokenomist snapshot cited by Bittime recorded over $1.9 billion across 32 October releases, and separately lists ENA's October 5 release as roughly 1.41 billion tokens. We print both without averaging. DoubleZero's 1.66 billion 2Z unlock (≈ $113 million) already landed on October 2, inside this week. Sources: CoinMarketCap (InterLink); CryptoTicker Week 40; The Cryptonomist (BeInCrypto data); Bittime (Tokenomist data).

Reading the stack as a farmer's calendar rather than a news list: October 8 (WHUF transferable) and October 12 (InterLink close) are claim-side events — value that expires if ignored. October 15 (Sonic burn) is a supply-side event — unclaimed tokens leave circulation, which changes the arithmetic for everyone who claimed and everyone who did not. October 16 carries two deadlines at once (Margex's campaign and Binance's Stage 2 terms). The unlock events (October 5, 6 and 11) are context for sell pressure rather than action items, with the HYPE concentration — 3.75 million tokens to a single institutional buyer — the one to watch for how a concentrated unlock behaves versus a scattered one. Every date here is a published schedule, not a forecast; we will verify execution in next week's issue.

Our take: a $1.11B week against a $1.9B month is not a contradiction — it is two scopes, and the fact that trackers now routinely disagree by hundreds of millions on the same events is itself a data point about the maturity of unlock reporting. The number with real airdrop relevance is the single-buyer HYPE release: concentrated unlocks land differently than scattered ones, and next week's price action around it will be the first clean read this tracker gets on that question in October.

Data Snapshot

Every figure above is attributed in the linked sources; the threshold series and its caveats are tabulated in the weekly data report.

What we did not find

• No published per-distribution value for the fourth USD1/WLFI payout (October 2) — four rounds, four gaps.
• No accessible confirmation that City Protocol's September 28 TGE executed; its official docs call the token $CIT.
• No confirmed exchange listing for WHUF on October 8 — transferability and listing are different events.
• No official Drop 2 date or trigger for NEAR's milestone airdrop; a third-party report of a $6.66 next tranche remains unconfirmed by the team.

Sources

FAQ

Related Reading

• Token Airdrop Weekly Data Report — September 28 – October 4, 2026
• NEAR's $3.8M Week: An ETF Debut, an Exploit, and a Full Recovery
• NEAR@3.33: Anatomy of a Price-Triggered Airdrop
• Airdrop Market Report — September 2026