ada小真真1688

$BTC Bitcoin surged to $87,000 before retreating. Even with trading heating up, don’t rush to call it a breakout.

CoinDesk reported early this morning that Bitcoin briefly approached this level before falling back below $86,000. At 16:16 Beijing time, Binance’s BTCUSDT perpetual contract was trading at around 86,400 USDT, still below the level reached in this rally. Keep spot-market reports and futures quotes separate—don’t mistake a screenshot from this morning for the current price.

This perpetual contract recorded about 9.95 billion USDT in trading volume over the past 24 hours. Trading is active, but repeated buying and selling also add to volume; it can’t be treated directly as new capital flowing in.

I’m not convinced by the claim that “huge volume means the breakout is secure.” If the pullback continues after the surge, chasing the rally with a story can make it easy to overlook selling pressure.

Tap $BTC to check this candlestick and its trading volume: after the surge and pullback, has the price stabilized? Decide for yourself.

$BTC #BitcoinHitsResistanceAt87000AndRetreats

An ETF on $ZEC saw a weekly outflow of $93.6 million—can it really retain buy-side demand after listing?

On October 3, BeInCrypto cited SoSoValue data, saying Grayscale’s ZCSH first recorded a weekly net outflow. Two weeks earlier, it was still a net inflow of $98.2 million.

On October 4 at 13:37, Binance ZEC perpetuals were trading at $1,319, roughly flat over 24 hours. Looking only at today’s small fluctuations would miss the pullback from the previous week.

I don’t buy the idea that “an ETF means institutions will provide long-term backing.” Once listing opens the gateway, the incoming money can also leave. The net outflow records the subscription/redemption direction; it can’t be directly equated to fund losses, nor can it be used to explain the entire decline as investors withdrawing. If the price rebounds in the next round, I’d rather verify whether ETF subscriptions and redemptions have improved as well.

Open $ZEC to check the daily chart and trading volume—whether this rebound has volume. Verify first, then make a judgment.

$ZEC #Zcash spot ETF first shows a weekly net outflow of $93.6 million

$BTC 回到原点，三倍产品却可能已经亏了。

SEC approved listing rules for triple-leveraged products tied to bitcoin, ethereum, and others on October 2. The filing says: aiming for three times the daily performance of the futures benchmark, and without deducting fees. This “daily” part cannot be missed.

Here’s a hypothetical example: if the futures benchmark first rises 10%, then falls by about 9.09%, it returns to the starting point. The ideal 3x product would first rise 30%, then fall by about 27.27%, and after two days it would be down roughly 5.45%. This only considers daily compounding; it excludes fees and tracking differences.

With the same end point, how you get there makes a big difference. The more volatile the market, the less you should interpret “3x” as simply holding long enough for gains to naturally triple. In one-way trends, the compounding outcome is also different.

These products primarily obtain exposure through futures, so you can’t use that to infer spot buying demand. How much real demand the approval news brings still needs to be seen in the product and trading data.

Open $BTC to view the daily chart and volume: after the approval news, did volatility expand and did trading activity continue? First verify the price action, then discuss the impact of this news.

$BTC

$NEAR This time the money was追回了—I've also been waiting for a vulnerability post-mortem.

NEAR Intents lead Alex Shevchenko announced that the $3.8 million in stolen funds has been fully returned, and the team will stop investigating. Previously, he gave the attackers a 48-hour deadline to return the money; now that it’s back, he has once again urged people to disclose the issue through the bug bounty program.

Getting the money back is definitely good news—fewer affected people will suffer losses. But seeing “stop investigating,” the question I most want answered is: how did the vulnerability get in, and how was it verified after the fix?

The “fully returned” result is what the responsible party has publicly stated. Relying on just this announcement, I won’t vouch for the security of the entire service, and I certainly won’t translate it directly into a promise that the coin price will rise.

Keep an eye on $NEAR for the follow-up public post-mortem: was the full vulnerability incident described clearly, including the patch and how the fix was validated? This one is worth waiting for more than a victory announcement.

$NEAR

$PEPE ’s ETF application has moved forward another step—why can’t it still be treated as institutional buying?

Canary submitted its first pre-effective amendment on October 2. The proposed listing venue is listed as Cboe BZX, custody is listed as BitGo, and the price benchmark is also filled in: CoinDesk’s 60-minute weighted price.

There’s one line in the prospectus you can’t skip: no offers may be made before the registration statement becomes effective. Creation and redemption are arranged in baskets of 10,000 shares—this is the planned operating method, and it still can’t be used to prove that money has already flowed in.

I don’t like framing every time a filing is supplemented as institutions rushing to accumulate. Even after the product launches, you still have to see whether actual subscriptions keep up. Counting this money in ahead of time can hurt you if expectations fall short.

Open up $PEPE to look at the daily chart and volume: after this news, did the higher volume continue? Check it yourself—don’t treat application progress as approval.

$PEPE #Canary submitted PEPE spot ETF amendment S-1 file

$BTC 碰上弱非农，就能放心当利好吗？

Tonight the U.S. Bureau of Labor Statistics will release the September jobs report: nonfarm payrolls only increased by 29,000, with a combined downward revision of 60,000 for July and August. Even the earlier figures are weaker as well.

But the unemployment rate is 4.2%, and the official line is that the change is not significant. In the trending headline that says “rose to,” don’t read it as the unemployment rate suddenly jumping up.

A cooling in employment could ease rate-hike pressure—or it could also make investors worry about the economy. For Bitcoin, easing rate pressure is one layer; if investors start cutting exposure to risk assets, another layer of pressure will follow.

I’m not comfortable declaring $BTC a “good thing” based only on the headline number for new jobs. Weak data can change rate expectations, but whether buy-side demand can hold up still depends on trading.

Open $BTC and compare the price and trading volume before and after the nonfarm release: if it spikes higher, can subsequent volume keep up?

$BTC #U.S. September nonfarm payrolls added only 29,000; unemployment rate rose to 4.2%

$WLFI This round of 150 million token airdrops—what’s easiest to miss isn’t the prize pool, but the snapshots.

Binance today at 08:00 starts the continuation of the USD1 airdrop. The campaign is split into two phases, each with 75 million WLFI tokens, plus up to 2.5 million USD1 tokens; rewards are distributed weekly.

But this isn’t ‘just hold and you automatically get everything based on your balance.’ The system looks at hourly snapshots taken multiple times per day and uses the day’s lowest balance for calculation. If a contract or leveraged account wants to get 1.2x, the USD1 contract’s daily minimum open positions must also reach 300 USD1. Borrowing other stablecoins, swapping into USD1, and then participating will also receive a 70% value discount based on the announcement rules.

So a big prize pool doesn’t mean everyone gets more, and it also doesn’t mean demand has already entered the market.

First, open $WLFI to check the real-time trading volume: if after the campaign starts the volume doesn’t increase in step, then 150 million tokens is just a pool figure—not what the market has already voted for.

$WLFI $USD1

$BTC has net inflows for 9 consecutive trading days of an ETF, yet the price has not broken through.

On September 29, U.S. spot Bitcoin ETFs saw net inflows of $66.19 million. BlackRock’s IBIT added $51.09 million, Ark Invest’s ARKB added $33.24 million, while Bitwise’s BITB recorded net outflows of $18.14 million. The total is positive, but the capital isn’t consistently standing on the same side.

At the same time, Binance’s BTCUSDT is around $83,828, down 0.64% over the past 24 hours, still below the day’s high of $84,555.

I don’t really believe the words “consecutive 9 days” by themselves. ETF inflows are only part of the picture—whether the market can absorb them depends on sell pressure and trading volume.

Open $BTC to check the daily chart and volume: if ETFs keep flowing in, but that $84,000 support still can’t hold, this divergence is more worth watching than “9 consecutive days.”

$BTC

What did Vald say

$BTC tiny upticks, yet Strategy bought another 1,665 shares.

On September 28, the company disclosed that this purchase cost $142.7 million at an average price of $85,681, bringing its holdings up to 847,666 shares. Tonight, Binance perpetuals are trading at 83,956.5 USDT, up 1.245% over the past 24 hours—still below the average price of this purchase.

Even more interesting: in the same week, it also repurchased $152 million worth of STRC, and the amount was actually higher than the buy-in for the coin. Money isn’t just being concentrated in BTC; the company is also managing its own financing structure.

The easy mistake is to equate “bought again” directly with an immediate pump. The corporate buy is real, but whether the price can hold depends on execution and subsequent disclosures.

First, open $BTC and take a look at this daily candle: whether it can hold around 83,900. Then see if Strategy continues adding next week.

$BTC

$ZEC daily line continues with three bearish candles.

On the 26th it surged to 1699, and the next three daily K-lines all closed bearish. Today the low was 1356, and it is currently 1443.21, down 8.122% in 24 hours.

Don’t mistake the rebound from 1356 as the daily line turning good. Open $ZEC and compare the daily line with this volume candle.

$ZEC

The hot ranking still says it dropped forty percent. Open the order book—over the past 24 hours, it’s actually up.

Binance perpetuals are currently at 252.55 USDT, up 5.683% over 24 hours, with a day low of 195.43 today. A news alert at 17:40 yesterday noted that it briefly fell below 200 and was more than 40% below the high from this morning—that was yesterday’s price.

At 13:31 today, BlockBeats said to Lookonchain: an address that’s been asleep for more than three years has started moving funds to exchanges. One of them deposited 8,250 QNT into Binance, about $1.88 million; two transactions combined totaled roughly $4 million sent in. The money has been transferred to the exchange—trading still needs to happen next.

Don’t take the sentence from the hot ranking as meaning it’s still in free fall right now. Measured from yesterday’s early-session high, yes, it’s pulled back deeply; the 24-hour low has already been passed, and the price is moving back above 195.

Over the next few hours, we’ll check again: whether it can hold around 252, and whether these two giant whales are still sending to exchanges.

$QNT #QNT has fallen more than 40% from its intraday high

Cross-chain transfers now have an extra checkpoint; the default 16 validator nodes haven’t been removed.

On September 28, Chainlink’s official changelog: CCIP 2.0 went live. Institutions can add their own cross-chain validators or connect to compliance checks; by default, it’s still the original committee validation, and full finality remains the default. BlockBeats reiterated the same day that ANZ, Fidelity International, SBI Digital Markets, AWS, and Google Cloud, among others, were listed as supporters.

The easiest mistake is to treat this as “cross-chain transfers no longer need to wait for confirmation,” or to attribute LINK’s roughly 11% rise that day directly to this upgrade. The price and the announcement can happen on the same day, but you can’t write them as cause and effect.

Next, there’s only one thing to look at: which issuers have connected their own validators to mainnet for transfers.

$LINK #Chainlink上线CCIP2支持企业验证

Hynix was falling, yet Binance’s two-times inverse ETF on it still rose 11.2%.

On September 28, Caixin cited sources as saying that SK Hynix’s U.S. subsidiary Solidigm is considering an IPO in the U.S. as early as next year, planning to raise about $15 billion; South Korean shares of Hynix fell by more than 4.5% at one point that day. The Korea Herald quoted the company’s official statement: Solidigm is evaluating several options and has not confirmed any specific plans yet.

SKDD is a short-term instrument designed by GraniteShares to deliver negative two times the daily rise and fall of Hynix’s ADR. It does not directly hold Hynix, nor is it a bullish bet on memory. This is an ETF perpetual contract, not direct ownership of the ETF.

The easiest mistake is to take SKDD’s rise as a reversal in the memory sector. It’s up because the underlying is down; the listing filings also have not confirmed anything yet.

Next, just watch two things: whether the official side confirms the listing arrangements, and whether the $7.323 USDT level can hold.

$SKDD

MongoDB took a 19.4% hit in Binance stock perpetuals, with its CEO poached by Meta the same day. Yet the guidance was reiterated using the original numbers.

On September 28, MongoDB officially announced that President and CEO Chirantan "CJ" Desai would step down immediately and move to Meta to take an executive role. The board asked former CEO Dev Ittycheria, who led the company from 2014 to 2025, to return as interim head and launched a search for a permanent successor. The company also reaffirmed the Q3 and fiscal year 2027 guidance that it issued on September 1.

Meta’s newsroom simultaneously announced the launch of the Meta Enterprise Platform. Zuckerberg called it the business’s “next major pillar.” Desai was appointed Chief Enterprise Platform Officer and would report directly to him.

The easiest mistake would be to treat this as MongoDB’s business collapsing. The guidance hasn’t changed—it’s about people. What’s moving the market is the sudden handover, along with the Investor Day on September 29.

This is for stock perpetual contracts, not direct stock ownership. Going forward, there are only two things to watch: what the old CEO says about the handover at Investor Day, and whether the 334.48 USDT level can hold.

$MDB

QNT once surged to 373 USDT, but as of 11:29 it has fallen back to 259.43 USDT. The partnership is real, but how the token captures value is still not explained clearly.

On September 24, The Clearing House announced it has selected Quant to provide interoperability, orchestration, and transaction management technology for its “on-chain money program,” and to connect existing payment systems such as RTP and CHIPS. The official plan is to open the program to participating institutions in the first half of 2027.

The easiest figure to misread is “$20 trillion per day.” This is the clearing and settlement volume of The Clearing House’s existing payment network, not the on-chain transaction flow already generated by the new project. Quant’s entry into U.S. banking payment infrastructure is progress; however, banks adopting Quant does not mean every transaction will create an equivalent QNT buy order. Real usage, fee structures, and how value is captured by the token still need to be disclosed.

For now, there are only two things to watch: whether the pullback from 373 USDT can be stopped, and whether, before the project goes live, it can disclose the real participating institutions, actual usage, and fee model.

$QNT

Connecting to any entry point that claims to be the “GIWA mainnet” right now could be a wallet-risk gamble: according to official sources, this mainnet hasn’t even launched yet.

On September 27, the GIWA official account clarified that the project is still in the testnet phase and has never gone live with a mainnet RPC, so there is no such thing as a “mainnet RPC leak.”

The official documentation currently only lists GIWA Sepolia, with chain ID 91342; the mainnet section still says “in development.” The website shows “GIWA Mainnet,” and the icon looks similar, but that can’t prove it’s official.

The easiest place to get tripped up is right here: many people only look at the project name and don’t check the network status. With unknown RPCs, cross-chain bridges, or deposit/充值 entry points—if they claim they are running on the GIWA mainnet, you should pause and verify first.

If you really want to validate, check the official domain first, then confirm the chain ID and contract address.

#GIWA

In the same security incident, Bitget’s latest accounting has added another $35.9 million.

Late on September 25, Bitget raised the amount of confirmed assets that were transferred from an initial estimate of $351.6 million to approximately $387.5 million. The newly added portion comes from Zcash and TRON on-chain assets that had not been included earlier, and it does not mean that a new unauthorized transfer has occurred.

The platform says the attack path has been identified, the root vulnerability has been fixed, and the incident remains under control; Mandiant and SlowMist are participating in the investigation. The first announcement also confirmed that cold wallets were not affected, and withdrawals have been temporarily suspended.

The easiest line to misread is “user fund safety.” It means the platform’s commitment to cover losses—not that withdrawals have already resumed, nor that a complete root-cause report has been publicly released. Independent reporting by Reuters confirms the suspension of withdrawals and the scale of losses, but the timeline for recovery still depends on official updates.

Look at the official follow-ups first: when withdrawals will resume, and what the full root-cause report will look like—these matter more than a single sentence saying “it has been fixed.”

#bitget遭黑客攻击损失3.52亿美元

$351.6 million outflow from Bitget wallet—what users are most concerned about now is just one question: when will withdrawals be available again?

Bitget CEO Chen Geller said that at 18:31 UTC on September 24, an unauthorized transfer occurred involving some hot wallets and warm wallets, with estimated losses of $351.6 million. The platform said cold wallets were not affected, withdrawals have been suspended, and the incident is still under investigation.

Two figures need to be viewed together: estimated losses of about $351.6 million, and the user protection fund exceeding $464 million. The fund size on paper is sufficient to cover this loss. When users can regain withdrawal privileges and how much of the funds can be recovered still depends on subsequent announcements and on-chain tracking.

The easiest thing to misread this situation is to treat “the protection fund is large enough” as “the issue is already resolved.” The announcement is only the first step. What truly answers the security question is the scope of affected wallets, the amount to be recovered, and the time when withdrawals are restored.

Next, closely follow the official disclosures regarding the scope of affected wallets, the recovery amount, and the timeline for restoring withdrawals. BGB’s short-term price fluctuations may be worth watching, but the price can’t replace the platform’s answers to security concerns.

$BGB