Crypto Sisyphus

Spot market, rolling 24 hours: $BTC +0.89%. The move is not particularly large. Looking only at this price movement, I’d rather first clarify how ETF flows are measured than rush to explain the price change.

According to a report by Jinse Finance on October 23, U.S. Bitcoin ETFs recorded net outflows of 6,998 BTC that day and net inflows of 4,312 BTC over seven days. Both figures are measured in BTC: the first is the net flow for a single day, while the second is the cumulative net flow over seven days. The time windows differ, so their opposite directions are not contradictory. These figures are not dollar amounts or total ETF holdings, and they cannot be equated directly with 6,998 BTC being sold on the spot market.

Net outflows indicate that redemptions exceeded subscriptions during the relevant period, but the report does not say which investors the funds came from, where they went afterward, or establish that all those coins entered the market and were traded. Likewise, seven-day net inflows do not guarantee that demand will continue. Looking at the daily figure alongside the weekly cumulative figure shows that the directions differ over the short and longer windows. But these numbers alone cannot tell us whether the market as a whole is buying or withdrawing.

I’ll keep checking whether daily flows remain negative, whether the seven-day cumulative figure changes direction, and whether changes in holdings corroborate the net flows. If daily outflows quickly reverse, they look more like short-term volatility; if they persist and weigh on the longer window, then it would be worth discussing whether ETF demand is weakening. For now, the simultaneous rise in prices and ETF net outflows does not mean that one caused the other.

The security rules have changed; the real test is just beginning: Can fixes come faster without making testing less thorough? Bitcoin Core has merged a change to its vulnerability disclosure policy. Vulnerabilities that AI tools can easily discover or rediscover will no longer be subject to the previous confidential handling, which could last for months. This is a policy change; it does not mean any vulnerabilities have already been fixed and released under the new rules.

BlockBeats reported at 23:00 Beijing time on October 23 that maintainers hope to speed up fixes and disclosure for this kind of vulnerability. Under the old process, a patch would be released while details were kept confidential for a while, giving node operators time to upgrade. But if a simple hint is enough for AI to rediscover a vulnerability, keeping it secret for a long time may no longer keep others from finding it. The new rules target issues that are “easy to discover”; they do not require immediate disclosure of every vulnerability.

There are costs on both sides of this trade-off. Fixing issues sooner could shorten the window of exposure to risk, benefiting node operators and participants who rely on nodes to validate and relay transactions. But BlockBeats also notes that relevant updates may not receive the same level of testing before they are released to users. Moving quickly does not guarantee a reliable patch, and insufficient testing could shift the burden to maintainers and those upgrading. Key questions include how vulnerabilities will be classified, which still-supported versions a patch will cover, and whether users can upgrade promptly.

The report notes that the change comes amid a rise in AI-assisted security vulnerability reports. An earlier review of 390 Bitcoin projects found 4,962 potential vulnerabilities, 85 of which were rated critical. These were potential issues identified in the review; it would be inaccurate to say that Bitcoin Core itself has 4,962 vulnerabilities. Jinse Finance reported at 23:00 Beijing time on October 23 that no vulnerability has yet been formally classified as “easy to discover” under the new rules. The policy has been merged, but its practical effects remain to be seen.

This news directly concerns Bitcoin’s core software; it is not a change to Ethereum’s security policy, and $ETH should not be drawn into the conclusion just because it is also a crypto asset. What to watch next is whether a real-world case falls under the new rules, how the patch is released and tested, and how quickly users of still-supported versions upgrade. Whether the faster pace is worthwhile will ultimately depend on whether faster fixes deliver real security improvements.

奖励退去之后，玩家为什么还愿意回来？这比“道具能不能转手”难回答得多。奖励能给人一个开始参与的理由，却不能替玩法本身提供吸引力。要是每次打开游戏，最先惦记的是今天能拿什么、能换多少钱，那更像是在打卡，不一定是在享受游戏。没有可核实的留存数据，我不替任何项目宣布玩家留下了。

本轮现货滚动24小时，$IMX +1.09%。本轮现货滚动24小时，$GALA +0.81%。本轮现货滚动24小时，$AXS +0.59%。这些数字只描述各自的价格变化，不能证明玩家人数、游戏收入或产品质量同步变化，也不能拿一枚的涨幅替另外两枚解释。

资产流通可能让玩家更方便地转让暂时用不上的物品，解决“东西在我这儿闲着、别人正好用得上”的小麻烦。但能交易和好玩是两回事：道具在玩法里有没有用、转让流程和成本是否清楚，才决定这种便利落在谁身上。交易方便本身不会自动带来留存，更不能替游戏回答“为什么值得再玩一局”。

眼下没有与这三种代币直接相关、可核实的应用消息，也没有活跃、留存或收入数据。比起从涨跌猜哪款游戏更能留人，我更想看到具体用途，以及激励减少后玩家是否仍愿意回来。币价记下的是市场变化；玩家为什么留下，还是得靠实际使用来回答。

Three spot assets moved in two different directions: over this rolling 24-hour period, $BEB -10.88%; over this rolling 24-hour period, $PEPE +10.91%; over this rolling 24-hour period, $ARK +23.98%. One fell and two rose—the contrast is clear. But prices only tell me how things moved during this period; they don’t show whether a project has improved or deteriorated, much less establish a single reason for the gains and losses.

What I most want to verify is whether this rally is backed by sustained trading and actual usage, or whether a short-term price move has made the story seem convincing before the evidence is in. The reported 24-hour trading volumes are approximately $6.6 million, $99.53 million, and $5.3 million. The figures vary considerably, but trading volume is not order-book depth. It can’t tell us how much impact large orders entering or exiting would have, nor does it prove that demand is established.

A sharp decline doesn’t prove something is wrong with a project; a rapid rise doesn’t prove that someone is pumping the price or preparing to sell. These are possibilities to check, not established facts. There’s currently no evidence on order books, concentration of holdings, capital flows, or project usage, so I can’t say these indicators are worsening or improving.

I’m concerned that impressive gains might make me fear missing out, while also causing me to give too much weight to short-term volatility. If we later see sustained trading, clear usage data, and verifiable changes in holdings, I’ll revise my assessment. If all we see is more price movement, the contrast will remain just that—a contrast.

In the Solana ecosystem, on-ramps, aggregators, and liquidity are often discussed together, but they don’t solve the same problem: on-ramps let people start interacting, aggregators may help find routes, and liquidity affects execution conditions. The harder question is why users come back. Trading volume and address counts alone can’t be taken as proof of unique users or retention.

BlockBeats reported at 10:23 a.m. Beijing time on October 23 that SlowMist had warned of a GitHub repository disguised as a Solidity interview practice project that concealed a data-stealing backdoor. SlowMist advised developers to carefully inspect files and terminal startup parameters before using untrusted projects. This is a security risk in the development environment, not a vulnerability in the Solana network, and it doesn’t mean the entire ecosystem is affected. Even when a product’s user journey is smooth, whether users and developers can feel safe using it is also worth considering.

For the rolling 24-hour spot period in this round, $SOL +0.12%. For the rolling 24-hour spot period in this round, $JUP -0.35%. For the rolling 24-hour spot period in this round, $RAY -1.04%. These three figures describe only the price movements of their respective assets. They don’t prove that the security warning affected market prices, nor do they show that ecosystem usage rose or fell in tandem.

What I’d rather know is: after completing an interaction, what exactly did the user save or gain? There’s currently no data on retention or sustained use, so we can’t mistake activity for habit; but a temporary lack of evidence doesn’t mean an application has no value. On-ramps, aggregation, and liquidity are conditions—the actual utility and repeated use are what deserve further scrutiny.

Bitcoin weathered volatility in risk assets this week, but can we say it has broken free from macroeconomic forces? I think it’s too soon. BlockBeats reported on October 23, Beijing time, that CoinShares said Bitcoin held up relatively well this week amid renewed volatility in risk-asset markets, thanks mainly to a recovery in spot buying, stronger equity-market performance, and some short covering. This is the report’s explanation of market performance, not a transaction-by-transaction record of fund flows, and it does not prove that any one factor alone drove prices higher.

Interest-rate expectations are more worth watching. The report said markets broadly expect the Federal Reserve to leave rates unchanged on October 28, but expectations of another rate hike in December remain elevated, with the probability close to 83%. Weakness in the housing market could leave room to pause rate hikes; however, last week’s higher-than-expected CPI and PPI data suggest inflationary pressure has not disappeared. With both signals in play, a recovery in spot buying alone is not enough to conclude that liquidity will ease.

The report discusses $BTC , and its resilience should not be directly extrapolated to $ETH . To judge whether this support can continue, we also need to see whether spot demand persists, how interest-rate expectations evolve, and whether Bitcoin can continue to hold up amid future market volatility. The report did not provide direct fund-flow data sufficient to confirm the magnitude of these factors’ effects; the simultaneous appearance of prices and news does not, by itself, establish causation.

Access, aggregation, and liquidity are often discussed together as indicators of ecosystem activity, but they address different things: access gets people started, aggregation may help find trading routes, and liquidity affects execution conditions. Whether users come back depends on actual utility and continued use; trading volume and address counts alone cannot be taken as proof of unique users or retention.

According to a report by BlockBeats on October 23, Marinade released its Q3 2026 report. As of September 30, it had 7.94 million SOL staked, up 21.2% quarter over quarter. This is data from a single staking protocol and does not mean the entire Solana ecosystem grew at the same pace; the report also provided no data on unique users or retention. The scale of staking shows capital participation, but it cannot answer whether applications have become more useful.

Spot market, rolling 24-hour period: $SOL +0.05%. Spot market, rolling 24-hour period: $JUP -0.35%. Spot market, rolling 24-hour period: $RAY -1.47%. These are just the respective price movements; they do not prove that the report affected the market, nor do they show that ecosystem usage rose or fell in tandem.

What I’d really like to know is: after completing an operation, what exactly did users save or gain? The assessment would be more solid if we could later see evidence of specific product utility and continued use; staking growth could also simply reflect a shift in capital allocation. For now, this report offers a clue about capital participation, not an answer about user retention.

Looking at how these three spot assets have performed, I’d rather get to the bottom of one question: In DeFi, who ultimately gets the money users pay? Over the rolling 24-hour period, $ETH +0.11%. Over the rolling 24-hour period, $AAVE +0.51%. Over the rolling 24-hour period, $UNI +1.26%. These figures show only individual price movements. They cannot directly tell us about protocol revenue, borrowing demand, or holders’ rights, nor can they explain one another.

First, let’s distinguish between different kinds of money. Interest paid by borrowers is the cost of using funds; fees paid by traders are another source of revenue; token incentives may be an expense incurred to attract liquidity. Issuing more rewards doesn’t mean a protocol is earning more. And even if a protocol collects fees, that doesn’t automatically mean token holders get a share. Treating coupons as sales revenue can make the books look lively, but the actual income and expenses haven’t yet been tallied.

We also need to distinguish between stocks and flows: assets held in a protocol at a given point in time are a stock, while fees collected and rewards issued over a period of time are flows. A large stock doesn’t mean high revenue, and an increase in flows doesn’t necessarily mean higher net returns. A governance proposal is just a proposal; approval and implementation are separate matters. Without clear rules and a record of implementation, we can’t describe a proposed benefit as something holders already have.

For ordinary users, in addition to borrowing interest, changes in collateral prices can bring liquidation risk; those supplying funds also need to check the rules of the specific market. You can’t infer from a token’s price who receives the fees or who pays for the rewards. This describes general mechanisms, not any features Aave or Uniswap have recently adopted. Nor is there reliable information here to assess their current fee rates, returns, or risk parameters.

So rather than fixating on which coin has risen more, I’d rather ask: Who pays, who bears the risk, what does the protocol collect, and where does the money ultimately go? There’s currently no evidence linking this round of price movements to those accounts. A price chart isn’t a protocol ledger. Until the specific rules and their implementation have been verified, the conclusion should remain unconfirmed.

Spot prices are up $BTC +0.05% over the rolling 24-hour period. That’s barely a move, so I’d rather first clarify what “transferred in” means in the funding report than use a headline-grabbing amount to explain the price.

According to a report by BlockBeats on October 23, Onchain Lens monitored a transfer of 3,215 BTC, worth about $262.41 million, from a BlackRock ETF wallet to Coinbase Prime over the past two hours. The report also mentioned that the same wallet transferred 38,882 ETH, worth about $93.22 million. The BTC and ETH amounts and their dollar valuations are different units of measurement and should not be conflated. A transfer to an exchange does not mean the assets have been sold, nor can it be directly counted as a net outflow from the market or a reduction in ETF holdings.

I’d treat this as an on-chain movement that needs follow-up verification. To determine whether it has created actual selling pressure, we’d also need to see whether trades followed, whether the relevant wallets’ holdings changed, and whether ETF holdings or net-flow data provide supporting evidence. A single transfer does not represent BlackRock’s overall activity, much less the direction of fund flows across the entire market.

The fact that prices barely moved at the same time as a large transfer does not mean the two are causally related. For now, all we can confirm is that the gain over the rolling 24-hour period was small and that the report recorded this transfer. The available information does not tell us whether it was part of a trading arrangement, a custody transfer, or preparation for a sale. Rather than guessing based on the dollar valuation, I’d prefer to wait for trading and holdings data to fill in the picture.

How low does $BTC volatility have to fall before “calm” is worth treating as a risk signal? Rhythm reported on October 23 that, according to a Bitwise report, Bitcoin’s 30-day and 60-day trading ranges had narrowed to 1.8% and 3.0%, respectively, while 3-month and 6-month implied volatility stood at the 0.8th and 0.2nd percentiles of their distributions over the past three years. Implied volatility reflects how the market prices future volatility; it is not a guarantee of future price movements. Such low pricing suggests the market expects relatively calm conditions. If unexpected news emerges later, volatility picking up again would not be surprising—but that is only a conditional assessment.

The report also noted that U.S. spot Bitcoin ETFs had recorded net inflows of $1.074 billion so far this week, providing support for the price. On the other hand, the net position change indicator for long-term holders was negative, leading Bitwise to suggest that they may be in a distribution phase. These two signals point in different directions: ETF net inflows are flow data, while the long-term holder indicator signals changes in holdings. They cannot simply be offset against each other, nor can they confirm the scale of any selling. The report listed distribution by long-term holders as one reason for the current consolidation, but the available information is not enough to prove it is the sole cause.

More key evidence is still missing: how long low-volatility pricing will persist, whether the change in long-term holders’ net positions will continue, and whether ETF inflows can be sustained. The short-term holder cost basis of about $74,800 and the realized market mean of about $77,600 cited in the report are reference points for monitoring the range, not guaranteed support levels or directional signals. $ETH is outside the scope of this Bitcoin report, so these observations about flows and volatility should not be applied to it. For now, I would consider “the market is very calm” alongside “coins may be changing hands,” and wait for subsequent data to confirm the picture rather than mistake low volatility for the disappearance of risk.

Is Bitcoin still following risk sentiment, or has it found a rhythm of its own? Rhythm reported on October 23 that QCP Capital said credit risks in the AI infrastructure sector are spreading faster, with growing concerns about financing costs, debt-servicing capacity, and returns on capital expenditure weighing on U.S. stocks and crypto markets. The report also noted that CoreWeave bond yields rose to around 15%, while its share price fell about 10% on October 22. These are QCP’s analysis of market conditions and figures cited in the report; they do not prove that any single factor directly caused Bitcoin’s price movements.

QCP noted that BTC has recently weakened in tandem with U.S. stocks and has yet to show price action independent of traditional markets. One possible transmission mechanism is that, after reassessing high financing costs and debt risks, investors become less willing to hold risk assets, affecting Bitcoin as well. I would interpret this as the market temporarily pricing Bitcoin according to overall risk sentiment, rather than as confirmation that funds are flowing out of Bitcoin in every instance.

There is a real-world basis for this explanation: the report mentioned not only credit in AI infrastructure, but also a trend of market funds shifting toward relatively safe assets such as longer-term U.S. Treasuries. If investors broadly reduce their risk exposure, BTC may be affected by portfolio reallocations even if it has no direct connection to the financing of the companies involved. But a “trend of shifting” does not specify the amount of capital involved, and certainly cannot be directly converted into the volume of Bitcoin sold.

Who might benefit? If defensive positioning continues, longer-term U.S. Treasuries may attract more attention. Those under pressure include AI infrastructure companies that rely on financing, as well as assets that are sold off along with others when risk appetite contracts. These are possible channels through which benefits and costs may be transmitted—not proof that the report established how much any investor group gained or that any party incurred a specific loss.

There are also counterexamples: rising credit risks do not mean everyone will sell Bitcoin, and market correlations can change over time. The report provides no ETF net flows, changes in Bitcoin holdings, or records showing that AI credit risks directly triggered trades. If BTC continues to weaken alongside U.S. stocks after credit pressures ease, risk sentiment alone would not fully explain the move. If BTC behaves differently while risk assets are under pressure, the view that it “still struggles to escape its risk-asset status” would also need to be reassessed.

The same report also noted that French 10-year government bond yields rose above 5.1%, with the spread over German government bonds widening to around 170 basis points; meanwhile, tensions in the Middle East pushed Brent and WTI crude oil to five-month highs. These are separate macro risk signals and should not all be attributed to AI financing. The fact that news and price movements occur at the same time does not, by itself, prove causation.

Spot, rolling 24 hours, $BTC -0.37%. Spot, rolling 24 hours, $ETH -0.28%. These two figures describe only the respective price movements; QCP’s analysis discussed Bitcoin weakening alongside U.S. stocks and did not provide a corresponding assessment of Ethereum. A report about one coin should not be applied to another.

What is worth checking next is whether financing pressures in AI infrastructure continue to spread, and whether BTC keeps weakening in tandem with U.S. stocks during volatility in credit markets. If the relationship breaks down, macro risk sentiment may have been only a temporary explanation; if the pressure persists and the correlation holds, subsequent observations would lend more support to QCP’s view.

What an AI compute network most needs to answer may not be “Can it connect to a model?” but rather: who keeps paying for it? A product’s demand starts to be validated when people try it, some pay for it, and the demand recurs. Having computing resources on a network, or giving a token an AI label, cannot substitute for any of that. As a retail investor interested in AI, I’d rather see the bills than fill in the ending of the story first.

In this rolling 24-hour spot period, $TAO is up 0.23%. In this rolling 24-hour spot period, $RENDER is down 4.08%. In this rolling 24-hour spot period, $FET is up 0.16%. Their different price movements describe only their respective prices. They don’t tell us who has customers, whose computing power is being used, or whether product progress caused the market moves.

According to a report by Jinse Finance on October 23, TAO briefly fell below $260 and was trading at $259.9 at the time of the report, up 0.66% over 24 hours. That reflects the market at the time of the report; it is not data for this rolling 24-hour period, nor can it be used to explain demand or future prices. The fact that a price move and a news item occur in sequence does not mean the latter caused the former.

To assess supply and demand for computing power, you need to look at both sides: providers bear the costs of equipment, energy, and idle capacity, while users weigh price, speed, and reliability. Network incentives can attract resources, but distributing rewards doesn’t mean customers are already paying. If demand is mainly sustained by subsidies, whether resources remain after incentives are reduced is the test worth watching. This describes a general mechanism; it does not mean these three networks already have specific customers or particular utilization rates.

Even if a network really has users, the value of its token still needs to be assessed separately: What function does the token serve? How are fees generated and distributed? Do holders have clearly defined rights? Growth in a company’s AI business also does not automatically mean these tokens will benefit. There isn’t enough information right now to say who is consistently paying for these three networks or which forms of demand have been validated. Getting clear on those questions is far more grounded than treating the AI label as an answer.

Does placing sell orders mean the market is already facing additional selling pressure? I don’t think the two are equivalent. According to an October 23 report by BlockBeats, data monitored by TradingBeats showed that seven key addresses on Hyperliquid had placed 90 limit sell orders between $83,400 and $85,112, totaling about 510.22 BTC, with a notional value of approximately $42.896 million. That figure is eye-catching, but it describes orders placed—not sell volume that has already been executed.

What’s more important to unpack is that these orders served different purposes. The report said that about $30.846 million in “reduce-only” sell orders came from five long-position addresses and were intended to trim existing long positions after the price rose. Another account planned to sell 64 BTC at $83,583, against a long position of 124 BTC. The former was an arrangement to reduce existing exposure; even if the latter filled as planned, it would simply reduce the corresponding long position and cannot be casually described as opening a new short.

Two other sell orders, near $83,700 and $83,820, were intended to open short positions. They totaled about $6.701 million and came from an account that currently had no BTC position and planned to establish an 80 BTC short after a rebound. This portion is indeed closer to an intention to add new short exposure, but “plans to open” does not mean the orders have already been filled. Limit orders can sit and wait, or they can be canceled. Without subsequent execution records, plans on the order book should not be described as selling that has already taken place.

Mechanically, a limit sell order tells us that its owner is willing to sell or adjust a position at a certain price. It does not mean the market will necessarily encounter an equivalent amount of actual sell supply at that price. If the price reaches the order zone and the orders fill, reduce-only orders will realize part of existing long positions, while short-opening orders may increase short exposure. If the price never reaches them, the orders are canceled, or positions change beforehand, the outcome will be different. Notional value can help indicate scale, but it cannot replace execution and position-change data.

Who might benefit from these arrangements? If the reduce-only orders fill, their owners can realize part of their long positions and lower their exposure. The account planning to open a short may get an opportunity to establish one. The potential costs also fall on the order placers: the market may not move as expected, and if orders remain unfilled, their plans will not be realized. If they do fill and the price continues to rise, short sellers may face adverse price movements. Other traders might adjust their expectations after seeing these sell orders, but the report does not show that the orders have already changed market prices or other traders’ decisions.

Conversely, the clustering of orders is not entirely without information. If the price later approaches this range, the orders remain in place and begin to fill—and especially if the short-opening orders actually increase short positions—then these orders are more likely to turn into observable supply or short-side pressure. But if the orders are canceled, the price never reaches them, or only reduce-only orders fill, we should not exaggerate “someone is preparing to sell” into “the market has already been hit by heavy selling.” I would rather treat this as a set of intentions that still need to be verified than as evidence of market manipulation by a major player.

This news concerns only Bitcoin addresses and their orders; it cannot be used to explain Ethereum’s order flow. $BTC is the subject of the reported activity; $ETH does not appear among these orders. The fact that the two are often discussed together does not mean activity in one can be attributed to the other.

I’ll check three specific things going forward: whether orders in the $83,400–$85,112 range remain in place, whether the orders that actually fill are for reducing positions or opening shorts, and whether the relevant accounts’ positions change accordingly. The size of the orders offers a clue to watch, but execution and position records are what can truly show whether supply has increased.

In DeFi, the costs users pay and the benefits token holders receive are often lumped together under the phrase “the protocol generates revenue.” This round’s rolling 24-hour spot figures: $ETH -0.15%; this round’s rolling 24-hour spot figures: $AAVE +0.21%; this round’s rolling 24-hour spot figures: $UNI +1.69%. These are just price movements. They do not prove protocol revenue, borrowing demand, or that holders can receive a share of the money—and the three price movements cannot explain one another.

First, let’s break down where the money comes from: interest paid by borrowers is the cost of borrowing; fees paid by traders are a separate charge; and token incentives offered to attract liquidity may be a protocol expense. Paying out rewards does not mean the protocol has earned revenue; collecting fees does not automatically mean token holders get a share. Treating coupons as turnover may make the books look good, but net income and expenses have yet to be calculated.

We also need to distinguish between stocks and flows. Assets held in a protocol at a given point in time are a stock; the fees collected and rewards distributed over a period are flows. A large stock does not mean high revenue, and an increase in flows does not mean net returns have increased. A governance proposal is only a proposal; approval and implementation are separate matters. Without clear rules and a record of implementation, a possible arrangement cannot be presented as a benefit holders have already received.

For ordinary users, beyond borrowing interest, there is also the liquidation risk that may arise from changes in collateral prices; people supplying funds also need to check the rules of the specific market. You cannot infer from token prices how fees are handled or who bears the cost of rewards. These are general mechanisms and do not mean that Aave or Uniswap has recently adopted any new feature; there is also no reliable information on which to base an assessment of their fee rates, returns, or risk parameters.

What I really want to ask is: Who pays, who bears the risk, what does the protocol collect, and where does the money ultimately go? The information available is insufficient to connect these separate sets of accounts to the price movements this round. A token price is a market quote, not a protocol ledger; until the specific rules and evidence of implementation have been verified, the conclusion should remain that the matter is still unverified.

The easier a vulnerability is to discover, the more important it is to keep it secret—or should it be fixed and disclosed as soon as possible? Bitcoin Core is revising its security vulnerability disclosure policy. The debate is not really about whether “AI can find vulnerabilities,” but whether the old approach to keeping them secret can still protect users. In an October 23 report, BlockBeats quoted developer Antoine Poinsot as arguing that delaying disclosure offers too little protection for vulnerabilities that can be easily found with a simple LLM prompt, and instead delays the release of fixes.

According to the report, the new policy aims to release fixes as soon as possible for major versions that are still maintained, alongside security advisories. Note that this is a policy plan; it does not mean that all vulnerabilities have been fixed, nor is there evidence that any specific vulnerability is being exploited. The goal is to narrow the gap between discovering a problem and users getting a fix: if a problem is not particularly difficult to find, continuing to keep it secret may not deter potential discoverers, but could leave users waiting longer for a patch.

Who might benefit? Node operators still using supported versions may get fixes sooner, and ordinary users may consequently spend less time exposed. Who bears the cost? Developers will need to investigate, patch, and ship releases more quickly, while maintenance resources may also be taken up by a larger number of reports. Advisories also need to clearly explain which versions are affected and how to upgrade; otherwise, even if they are published sooner, users may not know what to do, undermining their protective effect.

This does not mean that “all vulnerabilities will be disclosed immediately.” BlockBeats reports that low-severity vulnerabilities will be disclosed two weeks after the release of a major version containing the fix. Medium- and high-severity vulnerabilities will generally be disclosed two weeks after the last affected version reaches end of support, while critical vulnerabilities that seriously affect Bitcoin’s foundational security will follow a separate process. This tiered disclosure approach shows that developers are still weighing the need to notify users quickly against the risk of exposing details too early.

The strongest concern raised by opponents is also valid: if details are disclosed before a fix is ready, the disclosure itself could give potential attackers a lead. On the other hand, if a vulnerability is already easy to find, simply delaying an announcement may not keep it secret. Which side poses the greater risk cannot be decided by slogans like “act fast” or “keep it secret”; it also depends on whether patches can promptly cover versions that are still maintained and whether advisories enable users to take action.

The report also notes that AI-assisted security research is putting new pressure on the ecosystem, and cites a previous surge in AI-generated vulnerability reports. The number of reports is not the same as the number of real vulnerabilities, and certainly does not show that an attack has occurred. False positives consume maintenance resources, a cost the policy will have to contend with. But the available information does not provide a false-positive rate, details of specific vulnerabilities, or evidence of how effective the fixes have been, so it is not yet possible to tell whether the new approach has actually shortened the risk window.

This policy applies to Bitcoin Core and concerns the maintenance of $BTC software; $ETH is not covered by this policy change, and it should not be assumed to have undergone the same change simply because it is also a crypto asset. Going forward, it will be worth checking whether easy-to-find vulnerabilities are fixed promptly, whether patches cover major versions that are still maintained, and whether security advisories are clear and actionable. If those records do not improve, “fixing vulnerabilities as soon as possible” remains a goal—not protection users have already received.

With three price movements side by side, what I most want to verify is not which one looks more like an opportunity, but whether the rises are supported by sustained buying and the declines accompanied by sustained selling. Over the past rolling 24 hours in the spot market, $REZ +14.07%. Over the past rolling 24 hours in the spot market, $OSMO +12.61%. Over the past rolling 24 hours in the spot market, $MRNAB -18.24%. What we can confirm is the contrast in prices; we cannot infer directly from the gains and losses that there is a problem with demand, supply, or the projects.

I would pay particular attention to whether sustained selling is behind the sharp drop, but that is only a concern, and I may be giving too much weight to short-term volatility. The available information includes no order book, unlock schedule, or holder concentration data, so we cannot say that supply pressure has intensified. Trading volume at quoted prices is also not the same as order-book depth, and cannot tell us how much market impact can be absorbed.

Conversely, there is likewise no existing evidence that buying will persist in either of the two rising assets. Impressive gains make me fear missing out, while steep declines can easily lead me to mistake speculation for an explanation. If verifiable evidence of sustained selling, unlocks, or changes in holdings emerges, I will take supply risks more seriously; if no such evidence appears and the price movements gradually converge, I will revise my view as well. For now, the only thing we can confirm is the price movement; the reasons remain to be verified.

Over the rolling 24 hours, $BTC -0.33%. This is only a price change and cannot, by itself, tell us where the funds went. Rather than speculate about the reason for this small pullback, I’d rather verify a specific on-chain transfer: BlockBeats reported on October 23 that, according to monitoring by Onchain Lens, a Bitcoin whale recently transferred more than 5,099 BTC, worth approximately $415 million.

The report said that 949.7 BTC (about $77.55 million) was transferred to Binance and Deribit, possibly for sale or other trading activity, while approximately 4,150 BTC (about $337.7 million) was transferred to the whale’s own wallets. The two portions went to different destinations, so it would be wrong to say the entire transfer was made in preparation for a sale—or to describe a transfer to an exchange as a completed trade.

I’d treat this as a single transaction worth watching, not as a snapshot of market-wide fund flows. The report provides no information about subsequent trades, changes in holdings, or the whale’s purpose. The dollar valuation also doesn’t tell us how many coins were actually sold. The simultaneous appearance of price and transfer news doesn’t mean the transfer caused this price movement. If verifiable trading records emerge later, we can check whether the coins sent to exchanges actually resulted in sell orders. Until then, “possibly for sale” remains only a possibility; we shouldn’t turn it into a conclusion.

What matters most to get straight in DeFi isn’t which coin looks better today, but who pays the protocol and where the money ultimately goes. Over the rolling 24-hour period for spot trading this round: $ETH -0.91%; over the rolling 24-hour period for spot trading this round: $AAVE +0.70%; over the rolling 24-hour period for spot trading this round: $UNI +2.75%. These are price movements, not proof of protocol revenue, borrowing demand, or token-holder entitlements. Nor can three different price trends tell us who actually made money.

According to a report by Jinse Finance on October 23, Ethereum has postponed the planned activation of the Glamsterdam upgrade on the Hoodi testnet, which was originally scheduled for October 26. A new activation date has not yet been set. The report also noted that ChainSecurity identified compatibility risks in EIP-8037’s gas repricing mechanism. This is a delay to a testnet schedule, not evidence of a mainnet failure or a change in DeFi protocol revenue. It’s a reminder that on-chain applications depend on the underlying network, but this Ethereum news doesn’t let us infer that anything specific has gone wrong with Aave or Uniswap.

Keep the accounts separate: interest paid by borrowers may make up returns for capital providers; protocol fees are a separate source of revenue, and how they’re used depends on the specific rules. Token incentives, meanwhile, may be a cost the protocol incurs to attract liquidity and shouldn’t be conflated with fee revenue. It’s like the difference between money a shop takes in for goods and coupons it gives out: issuing more rewards doesn’t mean net revenue is higher.

It’s also important to distinguish stock from flow. Assets locked in a protocol at a given point in time are a stock; fees collected and incentives paid over a period are flows. A large stock doesn’t mean high revenue, and rising revenue doesn’t automatically mean token holders receive a share. A governance proposal is just a proposed arrangement awaiting a decision; even approval doesn’t mean it has been implemented. To say token holders have clear entitlements, we need specific rules and evidence of implementation—we can’t infer that from the token price.

For ordinary users, I care more about borrowing costs, the risks borne by capital providers, and where the fees ultimately go. Without reliable, specific parameters and allocation rules, the answer should stop at “not yet verified.” A protocol may solve the problem of matching capital, but that doesn’t mean every participant benefits from the same pool of money. And the price movements of these three tokens this round are no substitute for keeping these accounts.

With these gains and losses side by side, what I most want to verify is whether there is sustained selling pressure behind the sharp drop, rather than rushing to invent a story to explain the price moves. Rolling 24-hour spot: $MRNAB -17.58%; rolling 24-hour spot: $REZ +12.39%; rolling 24-hour spot: $BMT +30.26%. These figures only show each asset’s price change: a big rally doesn’t mean demand has been proven, and a sharp drop doesn’t prove that something is wrong with the project.

So far, all we can confirm is the price movement and quoted trading volume; trading volume is not order-book depth and can’t show how much buying or selling the market can absorb. I’m concerned about whether $MRNAB ’s decline is accompanied by sustained selling, but that’s only a possibility to verify—and I may also be giving short-term volatility too much weight. At this point, there’s no evidence such as order-book data, unlock schedules, or holding concentration, so I can’t say that selling pressure has increased.

Conversely, there’s no concrete evidence that buying pressure behind $REZ and $BMT will persist either. Impressive gains can make me afraid of missing out, while a sharp drop can easily lead me to mistake speculation for a conclusion. If verifiable evidence of sustained selling, unlock schedules, or changes in holdings emerges, I’ll take supply risk more seriously; if no such evidence appears and the price action gradually stabilizes, I’ll revise my assessment as well. For now, all we can confirm is the contrast in price movements; the reasons still need to be verified.

Bitcoin Core is changing the timing of vulnerability disclosures. The key issue is not “AI finding vulnerabilities,” but how quickly they should be fixed after discovery and when they should be made public. According to a report by Rhythm on October 23, developer Antoine Poinsot believes that delaying disclosure of vulnerabilities discoverable with a simple prompt no longer provides enough protection and may instead delay the release of patched versions. According to the report, the new policy will release fixes as soon as possible for major versions that are still maintained, along with security advisories. Other vulnerabilities will continue to be disclosed in stages according to their severity, while critical vulnerabilities that seriously affect Bitcoin’s fundamental security will follow a separate process.

The change targets the window of exposure: if an issue is easy to find, keeping it secret may not stop others from discovering it, but could slow down remediation. The aim of releasing patches promptly is to give affected users the chance to upgrade sooner. But this does not mean that all vulnerabilities have been fixed, nor does it mean that any particular vulnerability is being exploited. Whether advisories clearly identify affected versions and explain how to upgrade also determines whether users can act in time.

I’m more interested in seeing a track record of implementation than policy statements alone. The report does not list specific vulnerabilities, affected versions, or completed fixes, so it is not yet possible to determine whether the exposure window has actually been shortened. Evidence that fixes cover major versions still under maintenance, together with clear security advisories, would better demonstrate whether this change is effective. $BTC is directly relevant to this policy; $ETH is outside the scope of Bitcoin Core’s policy, so this news should not be applied to Ethereum.