7*24

Hot topic

Market

Activities

On March 31, Google Research revealed that a quantum computer can crack Bitcoin private keys in just 9 minutes, which is 1 minute faster than the average Bitcoin block time. The threat of memory pool attacks has now become a real concern, prompting us to urgently transition to post-quantum cryptographic solutions.

[Google: Quantum Computer Can Crack Bitcoin Private Keys in Just 9 Minutes]On March 31, Google Research revealed that a quantum computer can crack Bitcoin private keys in just 9 minutes, which is 1 minute faster than the average Bitcoin block time. The threat of memory pool attacks has now become a real concern, prompting us to urgently transition to post-quantum cryptographic solutions.

Google: Quantum Computer Can Crack Bitcoin Private Keys in Just 9 Minutes

On March 31, the market structure experienced a subtle yet crucial shift as the Federal Reserve signaled a pause on interest rate hikes, leading the market to retract its rate increase expectations, indicating that policy pressure is no longer rising. Simultaneously, the Middle East conflict has been postponed to an April negotiation window, shifting risks from acute shocks to prolonged consumption. The combination of these factors has transitioned the market from 'rapid contraction' to 'dull oscillation under low liquidity.' This week, attention should still be paid to Wednesday's ISM and ADP reports, as well as Friday's non-farm payrolls; however, in an environment of decreased trading depth, data is more likely to trigger short-term volatility rather than provide a directional trend. Current market liquidity signals are clear: the bid-ask spread for U.S. Treasuries has widened by about 27%, and some market depths have dropped to around 10%, indicating that market makers are continuously contracting risk. Returning to BTC, the short-term structure has converged to a range of $66,100 to $68,500. The lower boundary of $66,100 serves as a repeatedly validated support zone, while the upper boundary of $68,500 represents the current main liquidation pressure. Movements within this range are fundamentally liquidity scans rather than trend-driven; only if it effectively surpasses $68,500 will there be an opportunity to unlock a higher liquidity space; otherwise, it will continue to experience repeated compression within the range.

[Bitunix Analyst: Policy Shift to Caution and Delayed War Push BTC into Low Liquidity Compression Between $66,100 and $68,500]On March 31, the market structure experienced a subtle yet crucial shift as the Federal Reserve signaled a pause on interest rate hikes, leading the market to retract its rate increase expectations, indicating that policy pressure is no longer rising. Simultaneously, the Middle East conflict has been postponed to an April negotiation window, shifting risks from acute shocks to prolonged consumption. The combination of these factors has transitioned the market from 'rapid contraction' to 'dull oscillation under low liquidity.' This week, attention should still be paid to Wednesday's ISM and ADP reports, as well as Friday's non-farm payrolls; however, in an environment of decreased trading depth, data is more likely to trigger short-term volatility rather than provide a directional trend. Current market liquidity signals are clear: the bid-ask spread for U.S. Treasuries has widened by about 27%, and some market depths have dropped to around 10%, indicating that market makers are continuously contracting risk. Returning to BTC, the short-term structure has converged to a range of $66,100 to $68,500. The lower boundary of $66,100 serves as a repeatedly validated support zone, while the upper boundary of $68,500 represents the current main liquidation pressure. Movements within this range are fundamentally liquidity scans rather than trend-driven; only if it effectively surpasses $68,500 will there be an opportunity to unlock a higher liquidity space; otherwise, it will continue to experience repeated compression within the range.

Bitunix Analyst: Policy Shift to Caution and Delayed War Push BTC into Low Liquidity Compression Between $66,100 and $68,500

On March 31, VIX index futures plummeted, at one point dropping over 4% to report at 27 points. According to the Wall Street Journal, Trump told aides he is willing to end the war without reopening the Strait of Hormuz. (Dongxin News Agency)

[VIX Index Futures Plunge Over 4%]On March 31, VIX index futures plummeted, at one point dropping over 4% to report at 27 points. According to the Wall Street Journal, Trump told aides he is willing to end the war without reopening the Strait of Hormuz. (Dongxin News Agency)

VIX Index Futures Plunge Over 4%

According to monitoring by 1M AI News, a developer reverse-engineered the 228MB binary of the standalone version of Claude Code using Ghidra, MITM proxy, and radare2, discovering two independent cache bugs that can increase API costs by 10-20 times without the user's knowledge. Related analysis has been submitted to GitHub (issue #40524) and marked by Anthropic as a regression bug for resolution. The first bug exists in the custom Bun runtime used by the standalone version. Each time an API request is made, the runtime looks for a billing identifier in the request body and replaces it, but the replacement logic hits the first matching item in the request body. If the conversation history happens to contain that string (for example, discussing Claude Code's internal billing mechanism), the replacement will hit the message content instead of the system prompt, causing a full cache rebuild for every request. A temporary workaround is to run it using npx @anthropic-ai/claude-code, as the npm package version does not include this replacement logic. The second bug affects all users who use --resume or --continue to restore sessions, introduced since v2.1.69. When restoring a session, the injection point for system supplementary information is different from that of a new session, leading to a complete mismatch of cache prefixes, resulting in the entire conversation history being rewritten from scratch instead of being read from the cache. Subsequent rounds return to normal, but the restore operation itself incurs significant additional overhead, and there is currently no external workaround. The developer estimates that for a long conversation of about 500,000 tokens, Bug 1 incurs an additional cost of approximately $0.04 per request, while Bug 2 incurs an additional cost of approximately $0.15 per restore, with the combined cost of a single request potentially exceeding $0.20. Previously, Anthropic engineer Lydia Hallie confirmed that users are reaching usage limits 'far faster than expected,' and several users in the Reddit comments believe that these two cache bugs may be one of the fundamental reasons for the abnormal consumption of usage.

[Reverse Engineering of Claude Code Reveals Two Cache Bugs, Potentially Increasing API Costs by 10-20 Times]According to monitoring by 1M AI News, a developer reverse-engineered the 228MB binary of the standalone version of Claude Code using Ghidra, MITM proxy, and radare2, discovering two independent cache bugs that can increase API costs by 10-20 times without the user's knowledge. Related analysis has been submitted to GitHub (issue #40524) and marked by Anthropic as a regression bug for resolution. The first bug exists in the custom Bun runtime used by the standalone version. Each time an API request is made, the runtime looks for a billing identifier in the request body and replaces it, but the replacement logic hits the first matching item in the request body. If the conversation history happens to contain that string (for example, discussing Claude Code's internal billing mechanism), the replacement will hit the message content instead of the system prompt, causing a full cache rebuild for every request. A temporary workaround is to run it using npx @anthropic-ai/claude-code, as the npm package version does not include this replacement logic. The second bug affects all users who use --resume or --continue to restore sessions, introduced since v2.1.69. When restoring a session, the injection point for system supplementary information is different from that of a new session, leading to a complete mismatch of cache prefixes, resulting in the entire conversation history being rewritten from scratch instead of being read from the cache. Subsequent rounds return to normal, but the restore operation itself incurs significant additional overhead, and there is currently no external workaround. The developer estimates that for a long conversation of about 500,000 tokens, Bug 1 incurs an additional cost of approximately $0.04 per request, while Bug 2 incurs an additional cost of approximately $0.15 per restore, with the combined cost of a single request potentially exceeding $0.20. Previously, Anthropic engineer Lydia Hallie confirmed that users are reaching usage limits 'far faster than expected,' and several users in the Reddit comments believe that these two cache bugs may be one of the fundamental reasons for the abnormal consumption of usage.

Reverse Engineering of Claude Code Reveals Two Cache Bugs, Potentially Increasing API Costs by 10-20 Times

Musk stated on X that the future of AI primarily lies in video understanding and generation, "because photons are the highest bandwidth communication form to date, these are key tools on the path to AGI," and noted that xAI's image generation tool Grok Imagine is "profitable, not a loss-making project." This statement comes in the context of OpenAI's announcement last week to shut down its AI video platform Sora. According to reports from WSJ and several media outlets, Sora has generated approximately $2.1 million in revenue since its launch in September last year, with an average daily operating loss reported at around $1 million. OpenAI also terminated its $1 billion partnership with Disney. Musk did not disclose specific revenue figures for Grok Imagine. He previously stated on March 25 that "the next version of Grok Imagine will be outstanding, and we are doubling our investment," and described it as "a tool more important than people realize."

[Musk Claims Grok Imagine is Profitable for xAI, Video is Key Tool for AGI]Musk stated on X that the future of AI primarily lies in video understanding and generation, "because photons are the highest bandwidth communication form to date, these are key tools on the path to AGI," and noted that xAI's image generation tool Grok Imagine is "profitable, not a loss-making project." This statement comes in the context of OpenAI's announcement last week to shut down its AI video platform Sora. According to reports from WSJ and several media outlets, Sora has generated approximately $2.1 million in revenue since its launch in September last year, with an average daily operating loss reported at around $1 million. OpenAI also terminated its $1 billion partnership with Disney. Musk did not disclose specific revenue figures for Grok Imagine. He previously stated on March 25 that "the next version of Grok Imagine will be outstanding, and we are doubling our investment," and described it as "a tool more important than people realize."

Musk Claims Grok Imagine is Profitable for xAI, Video is Key Tool for AGI

According to monitoring by 1M AI News, Xiaomi's MiClaw team has launched a system input method that contains serious security oversights. Users discovered that by repeatedly clicking on the version number of the input method, a debugging page could be accessed, which directly exposed the API call addresses, API Key, model provider, and model name of the AI service in plain text. The leaked API address points to ByteDance's cloud service platform, Volcano Engine's Ark interface, using the doubao-seed-1-6-lite-251015 model from the Doubao series. Based on the prompts, this AI feature is used for post-processing voice input, responsible for correcting typos, grammatical errors, and adding punctuation in the transcribed text. Users confirmed that the key is real and valid, allowing direct calls from external platforms; Xiaomi has reportedly changed the key since then. Decompiling the code also revealed engineering quality issues: developers used an if ("fixed string".length() > 0) method to check whether a hardcoded string that is always true is non-empty, a practice that would not appear in any normal code review process. Additionally, Xiaomi was found to have hardcoded the API key of the AI company Moonshot in the code submissions of its open-source project mone on GitHub, with the submission date being January 2025, and no changes recorded since.

[Xiaomi's New Input Method Exposes AI Model Keys Due to Security Flaw]According to monitoring by 1M AI News, Xiaomi's MiClaw team has launched a system input method that contains serious security oversights. Users discovered that by repeatedly clicking on the version number of the input method, a debugging page could be accessed, which directly exposed the API call addresses, API Key, model provider, and model name of the AI service in plain text. The leaked API address points to ByteDance's cloud service platform, Volcano Engine's Ark interface, using the doubao-seed-1-6-lite-251015 model from the Doubao series. Based on the prompts, this AI feature is used for post-processing voice input, responsible for correcting typos, grammatical errors, and adding punctuation in the transcribed text. Users confirmed that the key is real and valid, allowing direct calls from external platforms; Xiaomi has reportedly changed the key since then. Decompiling the code also revealed engineering quality issues: developers used an if ("fixed string".length() > 0) method to check whether a hardcoded string that is always true is non-empty, a practice that would not appear in any normal code review process. Additionally, Xiaomi was found to have hardcoded the API key of the AI company Moonshot in the code submissions of its open-source project mone on GitHub, with the submission date being January 2025, and no changes recorded since.

Xiaomi's New Input Method Exposes AI Model Keys Due to Security Flaw

On March 31, Hong Kong-listed company Xinhui Technology Holdings Limited (Stock Code: 1611.HK) announced the official completion of its brand renaming. Starting from 9:00 AM on March 31, 2026, the company's stock abbreviation on the Hong Kong Stock Exchange will officially change from 'Xinhui Technology Holdings (SINOHOPE TECH)' to 'Xinhui Group (BITFIRE GROUP)'. The new official website www.bitfire.com has also been launched. This renaming marks the company's transition from a regional fintech enterprise to a new phase of development as a global, comprehensive digital financial group.

[Xinhui Technology Officially Renamed to 'Xinhui Group' and Launches International Domain]On March 31, Hong Kong-listed company Xinhui Technology Holdings Limited (Stock Code: 1611.HK) announced the official completion of its brand renaming. Starting from 9:00 AM on March 31, 2026, the company's stock abbreviation on the Hong Kong Stock Exchange will officially change from 'Xinhui Technology Holdings (SINOHOPE TECH)' to 'Xinhui Group (BITFIRE GROUP)'. The new official website www.bitfire.com has also been launched. This renaming marks the company's transition from a regional fintech enterprise to a new phase of development as a global, comprehensive digital financial group.

Xinhui Technology Officially Renamed to 'Xinhui Group' and Launches International Domain

According to Cointelegraph, Nasdaq announced that starting May 1, 2026, it will officially eliminate the 10% minimum public float requirement and introduce a 'Fast Track' rule, allowing large-cap IPOs to join the Nasdaq-100 Index within approximately 15 trading days.

[Nasdaq to Eliminate 10% Minimum Public Float Requirement and Introduce 'Fast Track' Rule from May 1]According to Cointelegraph, Nasdaq announced that starting May 1, 2026, it will officially eliminate the 10% minimum public float requirement and introduce a 'Fast Track' rule, allowing large-cap IPOs to join the Nasdaq-100 Index within approximately 15 trading days.

Nasdaq to Eliminate 10% Minimum Public Float Requirement and Introduce 'Fast Track' Rule from May 1

The identity of the bail sureties for FTX founder Sam Bankman-Fried has been disclosed, including former Stanford Law School Dean Larry Kramer and research scientist Andreas Paepcke, who provided guarantees of $500,000 and $200,000, respectively. Reports indicate that the total bail amount of $250 million is primarily secured by properties owned by his parents in California. Previously, his lawyers attempted to keep the identities of the sureties confidential, but the court ordered their disclosure in response to a media request. The related case is still under review, and SBF is facing multiple fraud charges.

[FTX Founder SBF's Bail Sureties Revealed, Including Former Stanford Law School Dean]The identity of the bail sureties for FTX founder Sam Bankman-Fried has been disclosed, including former Stanford Law School Dean Larry Kramer and research scientist Andreas Paepcke, who provided guarantees of $500,000 and $200,000, respectively. Reports indicate that the total bail amount of $250 million is primarily secured by properties owned by his parents in California. Previously, his lawyers attempted to keep the identities of the sureties confidential, but the court ordered their disclosure in response to a media request. The related case is still under review, and SBF is facing multiple fraud charges.

FTX Founder SBF's Bail Sureties Revealed, Including Former Stanford Law School Dean

According to official website news, Nordic encryption trading platform Safello announced the integration of Apple Pay and Google Pay to expand its payment options. With the new integration, customers can now directly purchase cryptocurrencies using Apple Pay or Google Pay through the Safello platform.

[Crypto trading platform Safelo allows users to purchase cryptocurrencies using Apple Pay or Google Pay]According to official website news, Nordic encryption trading platform Safello announced the integration of Apple Pay and Google Pay to expand its payment options. With the new integration, customers can now directly purchase cryptocurrencies using Apple Pay or Google Pay through the Safello platform.

Crypto trading platform Safelo allows users to purchase cryptocurrencies using Apple Pay or Google Pay

Article

Grok on X Begins Automatic Translation and Recommendation of Foreign Language Posts

Strategy Accumulates 45,000 BTC in Last 30 Days, Fastest Growth in a Year

Reuters Opinion: Iran May Cause Widespread Damage to Gulf Energy Infrastructure if US Launches Ground Offensive

Predicted Market Transactions Reach 191 Million in March

Trump's Influence Fades: Market Immune to Verbal Assurances as U.S. Stocks Drop for Five Consecutive Weeks

Dollar Strengthens Again Amid Concerns Over Escalating War

Crypto trading platform Safelo allows users to purchase cryptocurrencies using Apple Pay or Google Pay

Isenção de responsabilidade：O conteúdo acima não representa as posições da HTX.，A HTX não faz quaisquer recomendações de negociação.。

Artigos relacionados

Todos os comentários0Mais recentePopular

Tópicos em destaque

Artigos relacionados