HANA: A 13% Rebound After 13.96M Tokens Reach a Gate-Labelled Wallet
HANA’s rebound is visible in spot markets, but it follows a large transfer into exchange custody and a sell-off that left more contracts open. Our reading: demand has returned; whether it can absorb further supply matters more than the headline gain.
HANA gained 12.78% over October 31’s first 17 hours, with Gate and KuCoin spot moving alongside it. Yet the previous sell-off did not reduce aggregate contract quantity, and 13.96M tokens had reached a Gate-labelled wallet two days earlier.
For a prospective long, the useful confirmation is spot holding through renewed exchange-bound supply without another sharp build in derivatives exposure. For an existing short, resilient spot demand and shrinking positions would weaken the continuation case.
The rebound added contracts
Binance priceOpen-contract quantity
16.5%
8.3%
0.0%
10-31 00:0010-31 17:00 UTC
Change from October 31 00:00 UTC. Quantity removes the price-valuation effect in notional OI.
The sell-off reduced the dollar value of positions, not their quantity
The starting clue was not simply that HANA bounced. During the October 29 sell-off, price fell 15.63% and OI notional fell 13.87%, which could look like a reduction in open positions on a dollar-denominated chart. Looking at the underlying contract quantity changed that reading: it increased 2.03%.
Our interpretation is that aggregate exposure survived the decline. Individual positions may have closed while others opened; the market did not reset through a net reduction in contracts. October 31 added another 5.18% in quantity while price rose 12.78%.
The later hours were less aggressive. From 10:00 to 17:00 UTC, quantity fell 2.51% and price eased 3.23%. That is an initial reduction in exposure after the morning peak. The next distinction is whether spot can hold while that reduction continues, or whether declining demand takes price down with it.
Price and exposure through the sell-off
PriceContract quantity
30.2%
15.1%
-0.1%
10-27 00:0010-31 17:00 UTC
Change from October 27 00:00 UTC; final point October 31 17:00 UTC. Price uses the preceding hourly close.
13.96M HANA moved from a contract into exchange custody
The chain investigation led to a four-transfer sequence on October 29. A contract, 0xf287…be26, sent 13.9587M HANA to a 2-of-3 Safe; the same amount then passed through two EOAs to 0x0d0707…b492fe, labelled “Gate 1” by Blockscan. Every hop has a matching successful transaction receipt.
The economic change is location: a large token balance moved from a contract-controlled route into a wallet attributed to an exchange. That makes exchange-side inventory and subsequent selling relevant to the rebound. It does not establish that the depositor sold, that the exchange credited a particular account, or that the same tokens remained there.
Timing narrows the causal claim. HANA was already at 0.01435 USDT by 08:00 UTC, before the first transfer at 08:50:57; the Gate-labelled wallet received the tokens at 18:07:32. This route is therefore a supply lead to monitor, not evidence that this deposit initiated the earlier decline.
Same amount at every hop: 13,958,706.796796796796796797 HANA
The rebound reaches spot markets; futures activity still dominates the observed CEX turnover
Because rising OI cannot identify a cash buyer, the next check was spot. Gate and KuCoin rose 13.25% and 12.97% over the same October 31 interval, close to Binance perpetuals’ 12.78%. This is broader price participation than an isolated perpetual premium.
Activity also returned to the selected on-chain pool: 2.82M USD changed hands in the first 17 hours, versus 1.39M over the previous full day. Gate recorded 521k USDT in spot turnover, against 11.18M USDT in Binance perpetuals. These observations support active spot trading, but gross turnover does not identify retained buying or the origin of demand.
Our working view is a rebound with spot participation carrying renewed derivatives exposure. A pure net short-covering explanation fits poorly with the full-window increase in contract quantity, although covering can occur within it. The four 04:00–16:00 funding settlements were positive: longs were paying to maintain exposure. If spot stalls while contracts expand again, the cost and reversal risk sit with a more exposed long side.
Spot venues joined the recovery
Binance perpetualGate spotKuCoin spot
16.5%
8.3%
0.0%
10-31 00:0010-31 17:00 UTC
Each series is rebased to its October 31 00:00 boundary close. Matched hourly bars through 17:00 UTC.
Conditional paths from the report cutoff; not subsequent outcomes or probability-ranked forecasts.
01Spot holds through supply → reassess the bearish case
Watch for
Further transfers reach identified exchange wallets, but spot holds its pullbacks; contract quantity stays flat or declines.
Market reading
Demand would be absorbing available supply without relying on a growing derivatives book.
Reader response
An existing short has a reason to reassess exposure. A prospective long should look for repeated spot resilience before treating the bounce as durable.
Reconsider if
Spot breaks down or apparent resilience becomes confined to perpetuals.
02Contracts outrun spot → avoid chasing the bounce
Watch for
Contract quantity and positive funding increase again while spot turnover and price follow-through fade.
Market reading
A more expensive long position book would be supporting less convincing cash-market progress.
Reader response
For a prospective long, defer a momentum entry. For an existing long, review exposure against the original risk plan rather than rely on the earlier percentage gain.
Reconsider if
Spot demand broadens and keeps price firm while derivatives exposure stops expanding.
Repeated exchange-bound transfers coincide with weaker spot prices and aggressive selling; exposure does not clear.
Market reading
The supply route would be becoming economically consequential, rather than merely a custody movement.
Reader response
An existing long should reassess downside exposure; a rebound thesis needs fresh absorption evidence. A transfer alone is insufficient reason for a new short.
Reconsider if
Exchange inventory declines through withdrawals, or spot absorbs the flows with stable prices.
Renewed cash demand plus additional derivatives exposure
Spot prices participated and contract quantity expanded. This is the best fit to the combined window, but turnover cannot identify sustained accumulation.
Watch for spot holding as quantity falls; weak spot alongside renewed quantity growth would weaken the reading.
Custody or inventory repositioning, rather than an immediate sale
The four-hop transfer may represent custody, market-making inventory, collateral or preparation for sale. Its destination label does not distinguish those purposes.
Exchange account records or identifiable execution would separate sale from custody. Follow deposits, withdrawals and spot response together.
Some shorts may have covered during the rally; late-window quantity declined. Net quantity nevertheless rose over the complete October 31 window.
A further rise in price with falling quantity and resilient spot would make covering more relevant. Position-level records would be needed to identify the closing side.
The rebound has spot participation; it still needs a supply-absorption test
The positive reading is that spot venues joined the recovery. The unresolved risk is a larger contract book alongside a documented route into exchange custody. This combination favors watching how spot handles the next supply event over treating either a deposit or a double-digit gain as a complete trading thesis.
If spot holds while contracts shrink, the rebound becomes less dependent on expanding derivatives exposure and the bearish case weakens. If contracts expand while spot loses momentum—or new deposits accompany spot weakness—the case for chasing the rebound deteriorates.
Market observations use completed hourly bars through October 31 17:00 UTC. Exact Binance closes end one millisecond before the labelled boundary; charts use nominal hourly boundaries. No incomplete 17:00–18:00 bar is included. BNB Chain balances and total supply are fixed to block 130896080, October 31 17:21:12 UTC. Transfer discovery used the existing Kyara bounded explorer; final claims use fresh indexed movements, fixed-block calls and transaction receipts. Receipts were collected October 31; Argus supplied no observations. USD pool volume is kept separate from USDT exchange turnover. Scenarios are qualitative, not probability-ranked or backtested execution rules.
Source notes / Market records, limits & open questions
HANA’s rebound is visible in spot markets, but it follows a large transfer into exchange custody and a sell-off that left more contracts open. Our reading: demand has returned; whether it can absorb further supply matters more than the headline gain.
Observedread directly from chain or exchangeDerivedcomputed or inferred from what was readReportedthird-party claimUnknownnot yet confirmed
01
Market
Open interest, funding and price
Longer market history & event chart
Findings
DerivedF02Binance HANAUSDT hourly closes rose from 0.0140900 to 0.0158900 USDT (+12.7750%) between the October 30 23:59:59.999 close and October 31 16:59:59.999 UTC close. October 29’s full UTC day fell 15.6331%, from 0.0154800 to 0.0130600. By October 29 07:59:59.999, price was already 0.0143500, before the first transfer in F06.#Binance hourly candlesCaptured source filesCaptured source files
DerivedF03Binance open-contract quantity rose from 419,612,935 to 428,130,328 (+2.0298%) during October 29, while notional fell 13.8746%. On October 31 00:00–17:00 UTC quantity rose from 418,846,299 to 440,554,643 (+5.1829%); notional rose 18.5862% to 6,993,452.51 USDT. From 10:00 to 17:00, quantity eased 2.5121% from 451,906,939. Quantity retains the provider’s HANA-contract units.#Binance open interestCaptured source filesCaptured source files
DerivedF04October 31 funding settled at +0.043778%, +0.026031%, +0.033554% and +0.026042% at 04:00, 08:00, 12:00 and 16:00 UTC. These four rates sum to 0.129405% of constant notional; longs paid shorts. Actual account cash payments depend on position notional at each settlement.#Binance settled fundingCaptured source filesCaptured source files
DerivedF05Across October 31 00:00–17:00 UTC hourly boundaries, Gate spot rose 13.2507% and KuCoin spot 12.9722%, alongside Binance perpetuals’ 12.7750%. The October 27–31 comparison contains 114 paired hourly closes; median absolute Binance-perpetual/Gate-spot spread was 0.1924%.#Gate spot candlesKuCoin spot candlesCaptured source filesCaptured source files
DerivedF09For October 31 00:00–17:00 UTC, Binance perpetual turnover was 11.1836M USDT, Gate spot 521,218.46 USDT and KuCoin spot 49,985.09 USDT. GeckoTerminal reports 2.8156M USD turnover in the selected HANA/USDT pool, 0xd21b…d759. The previous full day recorded 3.2205M USDT at Binance and 1.3854M USD in that pool. The periods have different lengths; USD and USDT totals are kept separate.#GeckoTerminal selected poolGate spot candlesBinance turnoverCaptured source filesCaptured source files
Event chronology
02
Limits and unknowns
Out of scope, other explanations, open questions
Out of scope
The depositing account, beneficial owner and any internal exchange sale are unknown. The Gate attribution comes from Blockscan’s search index; direct page retrieval failed.F06F07
Public spot turnover does not reveal net retained demand. No customer-level positions, realized liquidation ledger or same-account spot/perpetual hedge is available.F03F09
The circulating-supply providers disagree; total supply is used only for transfer scale. Selected addresses are not a complete entity-adjusted ownership distribution.F08F10
Selected BNB Chain records accompany this case. Transaction records establish movements; actor intent and exchange execution require separate evidence.
A1
Flows
Transfer paths
Findings
ObservedF06Exactly 13,958,706.796796796796796797 HANA moved on October 29 from 0xf287a07e5c5fcfd924752233ab03f1397d4ebe26 to 0x797855c44c76b3673c1d429d48aa6c002e3b3064 at 08:50:57 UTC; to 0xa9b52d94c767024783b6a8880f8fb16da2cd4e00 at 14:50:32; to 0x330e9591725d8730534862410ab8ee78142f840b at 17:22:03; and to 0x0d0707963952f2fba59dd06f2b425ace40b492fe at 18:07:32. The amount is 1.395871% of the fixed-block 1bn token supply. Indexed transfers agree with successful transaction receipts. Fixed-block calls report a signing threshold of 2 and 3 owners for the Safe. The intermediate Safe and two EOAs had zero HANA at block 130896080.#Transfer 1Transfer 2Transfer 3Transfer 4Captured source filesCaptured source files
ReportedF07Blockscan’s search-indexed address page labels 0x0d0707963952f2fba59dd06f2b425ace40b492fe as “Gate 1” and shows BSC activity. The label was retrieved October 31. Direct access returned HTTP 403; this is attributed provider labelling, not a verified identification of the depositing customer or proof of trading.#Blockscan: Gate 1Captured source filesCaptured source files
ObservedF08At BNB Chain block 130896080 (October 31 17:21:12 UTC), totalSupply was exactly 1,000,000,000 HANA. Selected balances were 260,441,598.3612 at 0x73d8…46db, 157,614,580.6242 at 0xc882…f071, 84,242,770.3358 at 0xf287…be26 and 80,140,068.0868 at the Gate-labelled address. These are address balances, not beneficial-owner holdings or tradable float.#BNB Chain block 130896080Captured source filesCaptured source files
ReportedF10CoinGecko’s October 31 snapshot reports 240,000,000 circulating HANA. Binance’s latest retained OI record carries a CMCCirculatingSupply field of 851,864,778.416679. Fixed-block totalSupply is 1bn. The report uses the verified total-supply denominator and does not select either circulating estimate as free float.#CoinGecko supplyBinance CMC supply fieldCaptured source filesCaptured source files
Sources & reproducibility
The data captured for this case
Market bars end October 31 17:00 UTC; chain balances are fixed to 17:21:12 UTC. Source retrieval timestamps are retained separately in the receipts.
Saved API responses and RPC receipts include an offline recomputation script. Hashes establish file integrity. The Gate wallet label is attributed to a search-indexed Blockscan result; direct page access failed.