Yo-yo-coy

Ripple 和 Arf 在 10 月 22 日宣布合作，把 RLUSD 的结算流动性引入 XRP Ledger。

数据显示：

1. 合作规模：Arf 是瑞士监管的结算流动性机构，年结算量约 100 亿美元（10-22 官方公告）。首阶段直接在 XRP Ledger 上为持牌支付公司提供 RLUSD 短期资金，周转周期 1 到 5 天。

2. RLUSD 的链上分布：总供应量约 25.1 亿美元（10-3 数据），其中约 12.4 亿美元、49% 发行在 XRP Ledger 上，另约 12.7 亿美元在以太坊。账本账户数 825 万，代币化现实资产的可转让部分约 2.78 亿美元（tradingnews，10-22）。

3. 上游已经铺好：10 月 12 日渣打上线了 XRP Ledger 上的 RLUSD 机构托管（tradingnews，10-22）。本轮合作把托管往下游推进了一步，从"存得住"走到"用得上"。

结算场景里用到的 XRP Ledger 都绕不开 XRP：交易手续费和账户储备需要 XRP 支付。这类需求不制造短期价格波动，但它是真实的链上使用。

XRP 守在 1.30 美元一线（10-23，FXStreet）。结算场景的每一次扩张，都是对 XRP 长期需求的一次加固。$XRP

仅个人看法，不构成任何投资建议。

DASH’s gains on October 23 were driven by futures, not spot demand.

Here’s what the data shows:

DASH briefly rose more than 10% in the morning session on 10-23, with a 24-hour trading range of $50.76–$55.81. Its market cap was about $690 million, ranking it 92nd (InsideBitcoins, 10-23 data).

The drivers are worth breaking down: perpetual futures trading volume rose 77% from the previous period to about $218 million; open interest (OI) also increased 16%; and the funding rate turned positive at 0.0056%, indicating that longs were paying to add positions (CryptoPulseDaily, 10-24 data).

But the leverage came and went quickly: OI fell to about $81.21 million on 10-23, after briefly exceeding $140 million; net exchange inflows were only about $1.24 million (CoinEdition, 10-23 data). Spot-market demand clearly failed to keep pace with futures activity.

The price action reflects this too: on 10-24, DASH fell back to around $51.84 (live Binance spot price via Finnhub), versus a previous close of $55.48, down about 6.6% on the day. Technically, $53.54 is immediate support and $55.88 is resistance (CoinEdition, 10-23).

Assessment: This is a classic case of an older coin being “pulled up by futures while spot fails to follow.” The rally’s staying power will depend on whether spot-market volume picks up to support it. Until then, crowded long positions in a positive-funding environment are a factor that needs to be worked off. This is just my personal opinion and does not constitute investment advice.

$DASH

#DASH #Dash

TON was the biggest loser among the top 30 coins on October 23, closing down about 7.1% at $1.22.

Data shows:

1. Price action: TON has fallen about 8.4% over the past 48 hours and is currently trading around $1.23 (Kraken hourly chart, Oct. 24 data). The drop far outpaced every other coin in the top 30; no other major coin fell more than 5% that day.

2. Market comparison: BTC closed at $81,071 (-0.3%) and ETH at $2,384 (-0.1%) that day. The total crypto market cap was $2.69 trillion (+0.2%), and BTC's market dominance was 60.2% (Basis Desk, Oct. 24 data). TON's decline was about 24 times greater than BTC's, suggesting weakness specific to the coin rather than a systemic downturn.

3. Market breadth: Among the top 50 coins, 13 rose and 32 fell, with a median change of -0.8% (Basis Desk, Oct. 24 data). TON's -7.1% was far below the median, indicating that the decline was mainly driven by factors specific to TON.

4. Fund flows: There were 1,207 large whale transfers that day, with about $3 billion flowing into exchanges and about $2.4 billion flowing out (Basis Desk, Oct. 24 data). In a net-inflow environment, selling pressure on weaker coins can intensify.

Outlook: It is worth watching whether TON can stabilize around $1.20–$1.23 in the short term. So far, there are no clear signs of a reversal. This is just my personal opinion and does not constitute investment advice.

$TON

#TON #Toncoin

$AVAX sees an unlock worth approximately $15.4M today.

Notably, given its size, this unlock is likely to have a limited market impact: AVAX is currently around $9.07 (Finnhub Binance spot data, 10-24), with a market cap of approximately $4.13 billion. The unlock represents only about 0.37% of its supply.

Data shows:

1. Unlock schedule (compiled from DeFiLlama / In-Crypto / Messari data, UTC): AVAX on 10-24, approximately $15.4M; GRAM (TON ecosystem) on 10-23, approximately $49.0M, or about 1.3% of supply; ALT on 10-26, approximately $2.1M, or about 3.3%; KNTQ on 10-27, approximately $5.0M, or about 4.1%; FF on 10-29, approximately $21.1M, or about 6.1%.

2. AVAX price position: The current price is around $9.07, down approximately 2.2% over the past 5 days and 48.2% over the past year (Finnhub, 10-24). The unlock is happening while the price is weak, but its absolute size is small.

3. Context for this week’s total unlocks: Cliff and linear unlocks this week total over $278 million (Blockonomi figures as of 10-24). The largest linear unlocks are RAIN (approximately $86.65M) and SOL (approximately $41.52M). Linear releases are gradual, while cliff unlocks are the events to watch.

My view: This AVAX unlock, at 0.37% of supply, is more of a calendar event than a supply shock. The ones really worth watching are FF on 10-29 (approximately 6.1% of supply) and KNTQ on 10-27 (approximately 4.1%); percentage-based unlocks are more likely to amplify volatility in a weak market.

#AVAX #TokenUnlocks
These are solely my personal views and do not constitute investment advice.

Swell hot-key incident: ~2,500 ETH at risk under malicious upgrade contracts; official pauses deposits and withdrawals on October 23 as a precaution. $SWELL

◆ Timeline: At 14:25 UTC on October 21, attackers gained control of a Swell DAO operational hot key, including the oracle bot that sets the swETH/rswETH exchange rates. At 03:03 UTC on October 22, Swell confirmed on X that it had detected suspicious activity and was investigating with security partners and Seal911.
◆ Method: The attackers increased the exchange rates by 1% per hour—the maximum rate allowed by the system—with no new ETH backing. As of October 22, the on-chain swETH exchange rate was about 3.0% above its correct value (approximately 1.133254 ETH), while rswETH was about 2.0% higher.
◆ Sword of Damocles: Four malicious upgrade contracts have been deployed and could withdraw approximately 2,513 ETH if executed through the timelock. None have been executed so far, so the loss remains “unconfirmed.”
◆ Response: On October 23, the official team paused deposits and withdrawals for swETH and rswETH, saying they would resume once NAV had returned to the correct value. It emphasized that all user funds were safe. Each product line had a TVL of approximately $29 million (as of October 23). A connection to the Railway key leak has not been confirmed.

Notably, an inflated exchange rate without backing can propagate through lending markets: lending pools that price swETH/rswETH using on-chain rates may count the inflated figures as collateral. The rsETH incident involving KelpDAO is a precedent.

Pausing deposits and withdrawals is the right move to limit losses, but how long it takes to correct NAV—and whether the withdrawal path for those 2,513 ETH has been cut off—will determine whether this remains an “incident” or becomes a “loss.”

#Swell #再质押 #SecurityIncident
Personal opinion only; this is not investment advice.

One figure in SlowMist’s October 23 report deserves attention first: its threat intelligence system MistEye scanned 1,488 crypto-related domains, 793 of which had direct PHP fingerprints—about 53.3%. The issue isn’t PHP itself, but that the two high-severity vulnerabilities disclosed this round target the “off-chain components” of Web3.

◆ Vulnerabilities CVE-2026-109618 and CVE-2026-109619 both received a CVSS v4.0 score of 9.2, placing them in the critical severity category. No account password or API key is needed: sending a crafted request to a PHP service exposed to the public internet could allow arbitrary code execution with the privileges of the web service process.

◆ All versions from PHP 5.4 through 8.5.11 are affected. The official patched versions are 8.5.12, 8.4.27, 8.3.36, and 8.2.35. PHP 8.1 and earlier no longer receive regular upstream support and should be upgraded as soon as possible (PHP official release, October 21).

◆ The patch timeline underscores the severity: vulnerability details leaked on October 20, before the official disclosure, so the PHP security team moved up the emergency release from October 22 to October 21 at 14:00 UTC. Amazon’s threat intelligence team had observed attempts to exploit php2shell in its MadPot honeypot network as early as October 17—four full days before public disclosure.

◆ The off-chain attack chain is straightforward: compromise a project’s web server → tamper with the frontend → trick users into signing malicious transactions → steal assets directly. The fact that an on-chain contract has no vulnerabilities doesn’t mean the off-chain components that support it are secure. Frontend pages, APIs, airdrop claim pages, operations dashboards, and custodial wallet services are all within the scope of potential impact.

◆ Responses from different countries reflect the severity: the Netherlands’ National Cyber Security Centre temporarily shut down websites as a precaution, while South Korea’s presidential office convened an emergency cybersecurity meeting and raised the cybersecurity alert level. W3Techs reports that PHP is used by 69.3% of websites whose server-side language can be identified.

It’s worth noting that SlowMist also emphasized that having a PHP fingerprint does not mean a system has been compromised—the 53.3% figure measures exposure, not a list of victims. But for project teams, the remediation window is tight: temporary mitigations can only reduce the risk of specific attack paths; applying the patch is the complete solution. $BTC

#网络安全 #Web3安全 #SlowMist
Personal opinion only; this is not investment advice.

TL;DR: Aave founder Stani Kulechov unveiled Aavenomics 3.0 during the Q3 community livestream on October 22: buybacks, staking, and token burns. The core idea is to connect protocol revenue to the value support of $AAVE . Six months later, a leading DeFi protocol is finally tackling the old problem of “governance tokens being worthless.”

1. First, what was paused: Buybacks have been on hold since April 19, the day after the rsETH incident. The DAO set aside 25,000 ETH to compensate DeFi United. Buybacks can resume only after the shortfall is made up.

2. The budget has actually shrunk: A forum proposal before the pause cut the annual buyback budget from about $50 million to about $30 million. It’s not a huge amount, but the direction has shifted from “we’re done” back to “let’s do it.”

3. The real new addition this time is token burns: Previously, repurchased tokens went into the treasury’s ecosystem reserve and sat there unused. Under the 3.0 plan, a portion of repurchased tokens will go to the staking incentives pool, while the rest will be sent directly to a burn address. Genuine deflation and a balance-sheet buyback are two different things.

4. The fundamentals aren’t bad: In Q3, DAO revenue was about $18.9 million and net profit about $4 million; total deposits were about $33.6 billion (+41%), and active loans about $13.2 billion (+32%). The protocol is still making money, which is a prerequisite for the buyback story to hold up.

5. A bonus: The V4 Equities Hub has been deployed on Base. Seven tokenized US stocks (Apple, Amazon, Alphabet, Meta, Microsoft, Nvidia, and Tesla) can be used as collateral to borrow stablecoins. Deposits were about $9.6 million at launch, and the service is available only to compliant users outside the US.

It’s clear that connecting protocol revenue to token value has become a collective move among DeFi protocols, and Aave is the first major player to put the mechanism on the table. Two things will determine whether the story holds up: whether the burn ratio can pass a governance vote, and whether buybacks will have enough purchasing power once they resume.

#Aave #DeFi #RWA
These are my personal views only and do not constitute investment advice.

Cardano’s treasury has received an unusual spending proposal—buying copper. $ADA

Here’s the bottom line: Toto Finance is requesting 22 million ADA (about $5 million) from the Cardano treasury to establish a “Cardano Strategic Copper Reserve.” Voting closes on November 15. If all the funds are spent and the price of ADA stays unchanged, copper would need to rise by about 49.4% for the treasury to recoup its original investment.

The details fall into four areas (according to a CoinDesk report on October 23):

1. Use of funds: About two-thirds would go toward physical copper in a COMEX-approved warehouse in New Orleans. Each pound of copper would correspond to one CuTT token, and the copper would be sold in installments over 12 months after being held for 18–24 months. The remaining third would cover custody, insurance, auditing, and execution fees. The treasury’s returns would consist only of copper sale proceeds and any leftover funds; the platform equity and commercial revenue from CuTT would belong to Toto. Toto itself could receive up to about 3.36 million ADA (around 15% of the requested amount).

2. Hurdle: The proposal assumes copper is purchased at $6.73 per pound and sold at about $10.06 per pound (+49.4%). Founder Metzger’s optimistic scenario is that copper rises by about 30% annually, or 69% over 24 months, just enough to cover the costs—but that’s a projection, not a promise.

3. Allocation: The treasury withdrawal cap is 500 million ADA (through around July 2027). As of October 16, about 457.4 million ADA had already been used. This 22 million ADA request would consume more than half of the remaining allocation, and returned funds would not replenish the cap.

4. Comparison: In May this year, the Cardano Foundation requested 7.8 million ADA to host a summit and received only 65.21% support—below the two-thirds threshold—so the proposal was rejected outright. Toto is asking for about three times as much.

For context, ADA was trading at about $0.22 on October 23 (Binance spot data at 07:00 UTC). It has fallen about 40% so far in 2026, and its market cap has dropped out of the top ten. Governance is debating a copper reserve worth several million dollars, while the market is still trying to hold the $0.22 support level. The two stories are playing out on different timelines.

#Cardano #CopperReserve
These are personal views only and do not constitute investment advice.

DFINITY founder Dominic Williams publicly accused NEAR Intents on October 22 of using DFINITY’s proprietary cryptographic technology without authorization. He also said that if the matter went to court, the chances of winning would be 70%–85%. $ICP

This isn’t a debate over technical approaches, but a direct accusation of “misappropriation” targeting the core signing mechanism of NEAR Intents.

The allegations focus on three points (according to BlockBeats’ October 22 report). First, technology: NEAR Intents’ Confidential Key Derivation is suspected of being based on DFINITY’s vetKeys system. Williams also claimed that a former DFINITY employee who was fired leaked related research, accelerating NEAR’s implementation of threshold ECDSA. Second, architecture: Williams said NEAR’s signing process actually runs on only about eight servers, contrary to its claims of decentralization, while ICP’s equivalent algorithm runs on distributed subnets. Third, legal issues: Williams went so far as to say that this “could lead to legal issues.”

Notably, the market reaction was quite muted. On October 23, ICP was trading at around $2.78 (Finnhub, Binance spot), with a 24-hour change within ±1%; it was down about 9.6% over the past seven days, with a market cap of about $1.55 billion (CoinPaprika, October 23). The community was quicker to react—a PA News report on October 22 said someone had created a meme coin mocking Williams.

My take: Take posts from founders trading accusations with a grain of salt. There’s only one real variable: whether Williams can produce evidence. If he can’t, this is just a war of words; if he can, the technical foundations of NEAR Intents will be reassessed. This is just my personal opinion and does not constitute investment advice.

#ICP #DFINITY

On October 28, the BSC testnet will undergo the Jenner hard fork. $BNB

Bottom line: This is a clear upgrade focused on “payments” and “compliant assets.” BSC is starting to catch up on the infrastructure needed for institutional use.

Three changes, each more practical than the last (sources: official BNB Chain Developers announcement on 10-22; reports by CryptoBriefing and CryptoTimes on 10-22, and CoinGabbar on 10-23):

First, BEP-703, Payment Lane. By default, 5% of each block’s gas capacity is reserved for qualifying payments. Governance can raise this to 10% for traffic such as regular BNB transfers (sent to non-contract accounts). The idea is straightforward: even when the network is congested, simple transfers should still have a path through.

Second, BEP-702, CAS20. This is a standard for compliant assets that brings governance controls such as allowlists and blocklists to the protocol layer. Issuers can directly decide who can hold and transfer assets—laying the groundwork for stablecoins and tokenized RWAs. Note that the full functionality still needs to be activated through a future governance decision; at the testnet stage, only the standard itself is being introduced.

Third, BEP-706. A millisecond-precision block timestamp precompile (at address 0x70) lets contracts read timestamps to the nearest thousandth of a second, while the existing block.timestamp remains at second-level precision. This is a tangible improvement in timing precision for DeFi oracles and auction bids.

On the price front, BNB is trading around $740 today (Binance market data, 10-23; its 24-hour decline has narrowed to around 0.29%). It is moving with the broader market, and the hard-fork news has yet to make a visible impact on the price.

Worth noting: Jenner is only being deployed on the testnet for now. The mainnet launch date will be announced separately through governance. Node operators need to complete their client upgrades by 10-28.

My take: Jenner’s significance for $BNB isn’t about being “faster”; it’s about paving the way for payments and compliant assets ahead of time. Stablecoins and RWAs will be the main battleground for the next wave of institutional adoption—the chain comes first, and the capital follows.

Personal opinion only; not investment advice.
#BNB #BNBChain #HardFork

NEAR is voting to cut its annual inflation cap again, from 2.5% to 1.6%. $NEAR

The bottom line: This is NEAR’s second inflation-reduction proposal in a year. The cut is half the size of the last one, but the path to implementation is more complicated—the governance vote is only the first hurdle; validators will also need to upgrade separately.

The numbers:
- Proposal HSP-029 was initiated by Sal Ternullo of SVRN. House of Stake voting opened on 10-19 and closes on 11-2 (a 14-day window; sources: TokenPost/cryptonews, 10-21)
- A linear reduction over 24 months, at about 3.75 basis points per month; if approved, it will have a 90-day grace period before taking effect
- Under the proposal’s model, annualized staking rewards fall from 5.268% to 3.372% (based on the 9-22 snapshot and a 42.71% staking rate); the allocation of new tokens remains unchanged: 90% to stakers and 10% to the treasury
- About 11.8 million fewer tokens issued over two years, and about 66.1 million fewer cumulatively over six years—equivalent to 4.36% of the total supply
- Price: NEAR was about $4.97 on 10-23, down about 0.6% over 24 hours (real-time Binance spot data from Finnhub)

My take: The real variable isn’t the vote result, but how quickly the 406 validators follow through. The previous reduction from 5% to 2.5% passed with 68.41% support, and Solana’s SGP-0002 also passed a similar inflation cut in 2026-08 with 67.001% of staked voting power. Both ecosystems have been through this playbook. Staking rewards are very likely to shrink, while non-staking holders benefit from a tangible reduction in dilution. This is just my personal opinion and not investment advice.

#NEAR #代币经济学 $NEAR

Starknet’s “going solo” proposal has received community authorization: 93.52% of voting power supported researching a breakaway from Ethereum to build an independent post-quantum L1. $STRK

The bottom line: This is the first “independent L1 research” proposal in the L2 camp to receive formal backing through a governance vote, with 93.52% support in the most highly attended vote in Starknet governance history.

1. Voting details (ended October 22, with a 7-day voting period; reported by Cointelegraph, KuCoin, and COINOTAG on October 23): About 3,200 votes, representing more than 2,800 unique wallets; 93.52% of voting power voted in favor, while about 6.5% opposed or abstained. StarkWare abstained throughout, leaving the decision to the community.

2. The scope of authorization is clear: This was a non-binding consultative vote that authorized “research,” not a migration. STRK will remain the native token, with no new token issued; the bridge to Ethereum will remain open.

3. Timeline: StarkWare first proposed the idea on the community forum on October 8. CEO Eli Ben-Sasson told Cointelegraph that work on the white paper would begin before the end of this week, with a draft to be released for public comment in November and a goal of achieving quantum resistance by 2027. The proposal was prompted by the fact that Starknet’s bridge and DA infrastructure still depend on Ethereum’s upgrade schedule. StarkWare believes Ethereum’s own 2029 timeline for quantum resistance is too slow.

4. Price data (Binance page, October 23): STRK was around $0.053, down about 4.89% over 24 hours, with a 24-hour high/low of $0.05649/$0.05256 and a market cap of about $402 million.

My take: 93.52% is a genuine signal of community sentiment, but the real hurdle to “going solo” has never been the vote—it’s whether the bridge, DA, and security assumptions can be cleanly separated. Until the white paper draft comes out in November, this remains only at the research stage, and the price suggests the market isn’t yet assigning a premium to this authorization.

#Starknet #STRK
Personal opinion only; this does not constitute investment advice.

Over the past 24 hours, approximately $524 million in futures positions across the market were liquidated. Meanwhile, the price of $BTC is now caught between two liquidation maps: around $692 million in long positions are stacked below $80,000, and around $1.025 billion in short positions are stacked above $83,000.

The data suggests that leveraged liquidations, rather than spot selling, were the primary driver of this pullback:

1. MyToken data (October 23, Beijing time): Around $524 million in positions were liquidated across the market over the past 24 hours, including $BTC : 179 million, ETH: 107 million, SOL: around 15.36 million, and XRP: around 10.68 million. Liquidations were concentrated in BTC and ETH, with altcoins accounting for only a small fraction.
2. Coinglass liquidation intensity data (cited by LookOnChain on October 23): If $BTC falls below $80,000, the liquidation intensity for longs on major CEXs would be around $692 million; if it breaks above $83,000, the liquidation intensity for shorts would be around $1.025 billion. Both sides are waiting for the price to move first.
3. CoinDesk, as relayed by tradersunion (October 23): During the overnight drop that took BTC below $81,000, around $435 million in positions were liquidated, including $385 million in longs. During the Asian session, the price rebounded to around $82,000. The Fear and Greed Index fell from 68 to 50, going from Greed back to Neutral in a single day.

We can see that $80,000 has become the last line of consensus defense for longs: a break below it could trigger $692 million in cascading liquidations, pushing prices lower; a move above $83,000 would put shorts on the hook. Both sides are exposed, so in the short term, the key question is which liquidation level the price gets pushed toward first.

The next key thing to watch is clear: whether the $80,000 level holds will determine whether this round of deleveraging is a one-off release or develops into a chain reaction.

#爆仓数据 #Bitcoin
These are my personal views only and do not constitute investment advice.

Grayscale’s token holder yield rankings are out: 8.0% at the top, -5.5% at the bottom—protocols making money doesn’t mean token holders are making money $HYPE $CAKE $LIT

On October 22, Grayscale published two crypto asset valuation rankings, putting one thing on the table: measure the same set of tokens by “profitability” and “token holder returns,” and the results don’t line up at all.

1. Token holder yield rankings (data as of October 22). HYPE came first at 8.0%, followed by LIT at 7.9% and CAKE in third at 2.6%, then AERO, UNI, RAY, PENDLE, AAVE, JUP, and CRV. But half the tokens on the list had negative yields: CRV came last at -5.5%, and JUP was at -2.6%. The calculation adds staking rewards and buybacks, then subtracts new issuance—when issuance exceeds returns, token holders are being diluted.

2. Adjusted earnings yield rankings. CAKE came first at 14.4%, LIT second at 14.1%, and HYPE third at 9.8%. JUP is the clearest example: its earnings yield is 3.5%, while its token holder yield is -2.6%.

3. The methodology is worth noting. Zach Pandl, Grayscale’s head of research, says Bitcoin is like digital gold, while many other crypto assets can be valued using cash flows—“valuation doesn’t have to rely solely on narratives.”

For holders of these tokens, the pace of new issuance is another curve worth comparing alongside the revenue curve.

#DeFi收益 #TokenHolderYield

These are solely my personal views and do not constitute investment advice.

WAX cross-chain bridge attacked: 5 transactions transferred about $75,000, and the vulnerability was still unpatched when disclosed $WAXP

The conclusion up front: this is a classic cross-chain bridge attack in which “the source chain lies, and the destination chain executes without question.” The loss was modest, but the vulnerability’s structure is worth noting.

1. Timeline. At 09:06 (UTC), the attacker created a new account, fasdfas.al, on WAX. At 09:46, they withdrew 52,986.50 bridged USDC. At 09:47, they withdrew bridged USDT, DAI, WETH, and WBTC in the same way. At 10:00 (UTC), the Solana side released 52,986.50 USDC as instructed; at 10:05 (UTC), the Ethereum side released the corresponding assets.

2. Amounts. The 5 transactions totaled 52,986 USDC, 21,558 USDT, 840 DAI, 2.55 WETH, and 0.11 WBTC. Blockaid initially estimated the loss at about $75,000; an October 23 update from TokenPost put it at approximately $90,000.

3. Root cause. The problem was not on the receiving end. Blockaid’s analysis found that the contracts on Solana and Ethereum had “correctly” executed based on the information they received. The error was in the WAX-side ledger reporting: the attacker had not paid for the corresponding assets on WAX, but the bridge nevertheless deemed the withdrawals valid. The discrepancy between the WAX-side ledger and actual reserves was about $1,522.

4. Current status. At the time of disclosure, Blockaid classified the incident as an ongoing exploit. Reports tracking the situation on the morning of October 23 said the vulnerability was still unpatched, and the losses could continue to grow.

My take: The attack surface of a cross-chain bridge is often not the destination chain’s verification logic, but the reliability of claims made on the source chain. Users holding assets in the bridge can only wait passively until a patch is announced.

#WAX #Cross-Chain Bridge Security
Personal opinion only; not investment advice

The on-chain ledger and the exchange’s account no longer add up $TRX

At 23:35 on October 21 (Beijing time), Salus security researcher Darcy reported that a batch of TRON wallets flagged by Arkham as being associated with CoinDCX transferred out approximately 15.99 million USDT and 5,783.81 TRX, worth about $16 million. The largest single transfer, 15,819,002 USDT, first went to an intermediary address, then was split up and routed to deposit addresses at multiple exchanges.

The exchange’s response: Co-founder Sumit Gupta denied that there had been a new security breach, saying the addresses were created in January 2025, compromised in the hack that July, and deactivated afterward.

The questions being raised: On-chain investigator ZachXBT pointed out that one deposit address beginning with "TQKJQ" was still receiving user deposits in April and May 2026 and interacting with a hot wallet. In a clarification posted on October 22, CoinDCX acknowledged that its deposit-scanning and fund-sweeping process for old addresses had indeed failed for a period of time.

Notably, this isn’t the first time CoinDCX has been embroiled in controversy over address management. In July 2025, the exchange was robbed of around $44 million and subsequently offered a 25% bounty for recovering the funds.

Here’s the bottom line: this isn’t a simple choice between “hacked” and “not hacked.” There’s a clear gap between the exchange’s off-chain explanation and the on-chain records—and that gap itself is the most concerning signal.

#CoinDCX #On-chain security
Not investment advice

Circle shareholder sues Trump and his family’s crypto company: Complaint alleges UAE-linked deals worth over $2 billion violate the U.S. Constitution $WLFI

Bottom line first: This is not a regulatory enforcement action; it is a shareholder derivative lawsuit. Whether the complaint can succeed will take a long legal process to determine, but for the first time, the question of whether the “Foreign Emoluments Clause applies to crypto transactions” has been put before a federal court.

The facts:

1. The lawsuit. On October 22, 2026 (Thursday), Circle shareholder J. Benjamin Greenberg (a former Circle engineer) filed a lawsuit in federal court in Washington, D.C. The defendants include Trump, Middle East envoy Steve Witkoff, and World Liberty Financial (Cointelegraph, Bloomberg, 10-22/23).

2. The amounts alleged. The complaint points to two UAE-linked deals: first, the sale of a 49% stake in World Liberty for $500 million to an investment vehicle linked to Sheikh Tahnoon, a member of the UAE royal family; second, a $2 billion transaction by Abu Dhabi fund MGX using World Liberty’s USD1 stablecoin (funding Binance, Cointelegraph, 10-22).

3. Revenue figures. The complaint cites Trump’s 2025 financial disclosure: his crypto-related income exceeded $1.4 billion, of which nearly $800 million was associated with World Liberty. The $WLFI token’s price fell from about $0.45 in August 2025 to about $0.05 by the end of June 2026 (figures cited in the complaint).

4. The substance of the lawsuit. The plaintiff is a Circle shareholder. The argument is that World Liberty’s USD1 directly competes with USDC, and that Trump’s arrangements “make it impossible for Circle to compete”—a battle for stablecoin market share wrapped in constitutional language.

My take: The lawsuit won’t change any regulatory framework in the short term, but for the first time, it has put details of World Liberty’s funding flows and the Trump family’s crypto earnings into the public judicial record. For WLFI, the risk isn’t in the letter of the law, but in public opinion—with each new round of trial coverage, USD1 and WLFI are put under the microscope again.

Just my personal opinion; not investment advice.

#特朗普 #WorldLiberty #Stablecoin

Ethereum’s next hard fork has been put on hold: the Hoodi testnet activation scheduled for October 26 has been canceled, leaving the mainnet timeline up in the air too $ETH

The bottom line: this is not a security incident, but a routine course correction in Ethereum’s development process. The cost, however, is that Glamsterdam’s mainnet schedule will be pushed back by at least several weeks.

1. Official action. On October 22, the Ethereum Foundation published a blog post titled "Glamsterdam on Hoodi Postponed": the Hoodi activation scheduled for October 26 at 17:42:48 UTC (epoch 132,352) was canceled, with no replacement date set. The plans to activate Amsterdam on the execution layer and Gloas on the consensus layer, as well as to raise Hoodi’s gas limit to 200 million, were also withdrawn. The decision was made at the ACDE #248 meeting, just four days before activation.

2. The immediate trigger. An October 13 analysis by security firm ChainSecurity found that EIP-8037 and EIP-8038 change how gas is charged for state creation and state access. This causes code handling failed calls to behave differently after the upgrade: a failure path that would previously have reverted could instead run to completion, turning a “retryable operation” into a “permanent failure”—without any changes to the contract code itself. Researchers said they identified 13 at-risk cases in real-world contracts.

3. Scope of impact. Hoodi is the last public testnet before mainnet, while Glamsterdam was already activated on Sepolia on October 6. The three proposed mainnet dates—December 1, 8, and 9—were to be selected at the next consensus meeting after a successful Hoodi activation. That prerequisite is now gone, so there is no basis for setting a mainnet date. The Foundation’s announcement emphasized that mainnet users and ETH holders do not need to take any action.

4. Market price reference. ETH was around $2,396 on October 23 (Finnhub Binance data), down about 3.3% over 24 hours. The move has limited direct connection to the upgrade news and is mostly following the broader market downturn.

Notably, EIP-8037 changes the core logic of gas accounting—the bedrock of Ethereum’s economic model. A problem there could become a network-wide incident. The development team chose to halt the rollout at the testnet stage rather than push ahead on mainnet with a known risk. That decision deserves more praise than the upgrade itself.

Two things to watch next: first, when a replacement Hoodi activation date will be announced; and second, whether EIP-8037 will be revised and retained or removed from Glamsterdam altogether. The latter will determine whether this delay lasts weeks or months.

#以太坊升级 #Glamsterdam $ETH
These are solely my personal views and do not constitute investment advice.

a16z has removed “crypto” from the name of its flagship blockchain fund.

Bottom line: a name change doesn’t mean they’re reducing their holdings. a16z’s official line is that the fund still serves crypto founders 100%; what’s changing is the way it presents itself publicly, broadening its investment scope to encompass a wider range of frontier technologies.

TL;DR
◆ Timing: The Information reported on October 22 that the firm plans to drop “crypto” from the name of its main blockchain fund, renaming it a16z Frontier. Crypto Fund 5, which closed on May 5 this year, will retain its name for now.
◆ Personnel: A member of the founding team has left. Several aggregator sites point to longtime GP Ali Yahya. Chris Dixon is staying, while Eddy Lazzarin had already been promoted from CTO to GP.
◆ Size: Fund 5 raised $2.2 billion, less than half of Fund 4’s $4.5 billion in December 2022. The five funds total approximately $9.8 billion.
◆ Focus: Stablecoins, tokenized assets, and on-chain lending, with AI agents strengthening financial infrastructure. In June, the firm participated in Digital Asset’s $355 million funding round.

My take: A top-tier VC removing “crypto” from its signboard is precisely a sign that crypto has become a weaker fundraising label with traditional LPs. But the money is still there, with a sharper focus—stablecoins and tokenized assets are its answer. The fund name has changed; the $9.8 billion on its books hasn’t.

#a16z #crypto #风险投资 $BTC

This is solely my personal opinion and does not constitute investment advice.

If you still have open PTBUSDT or MITOUSDT contract positions ($PTB, $MITO ), you need to close them by 17:00 tomorrow (Beijing time).

On October 21, Binance Futures announced that the two USDⓈ-M perpetual contracts will be automatically settled and delisted at 09:00 UTC on October 23, which is 17:00 on October 23 Beijing time.

• Starting at 09:30 UTC on October 21, new positions that do not reduce exposure have been disabled; only closing positions is allowed. Some market makers are exempt to maintain liquidity.
• At 09:00 UTC on October 23, all remaining positions will be automatically settled at the prevailing market price, with P&L credited to the corresponding wallet.
• Once settlement is complete, both contracts will be officially delisted.

Note that the automatic settlement price is based on the market price at the time of settlement, which may differ from your expected position value during periods of volatility. Binance had just adjusted leverage and margin tiers for 14 contracts, including PTBUSDT, on October 13 (as reported by TokenPost). Delisting them just 10 days later suggests they no longer meet the required standards in terms of liquidity or project fundamentals.

It is worth noting that the delisting applies to these contract trading products, not the tokens themselves. If you hold a position, closing it yourself before settlement is the only way to control your exit.

This is not investment advice.

#Binance #ContractDelisting