7*24

Hot topic

Market

Activities

On August 26, the resentencing date for Tornado Cash developer Roman Storm has been postponed to April 26, 2027, due to the pending ruling on his motion for acquittal. Previously, U.S. prosecutors had pushed for the resentencing to be scheduled for October 2026.

[Tornado Cash Co-Founder Roman Storm's Resentencing Delayed to April 26, 2027]On August 26, the resentencing date for Tornado Cash developer Roman Storm has been postponed to April 26, 2027, due to the pending ruling on his motion for acquittal. Previously, U.S. prosecutors had pushed for the resentencing to be scheduled for October 2026.

Tornado Cash Co-Founder Roman Storm's Resentencing Delayed to April 26, 2027

On August 26, the retrial date for Tornado Cash developer Roman Storm has been postponed to April 26, 2027, as his motion for acquittal is still awaiting a ruling. Previously, U.S. prosecutors had pushed for the retrial to be scheduled for October 2026.

[Tornado Cash Co-Founder Roman Storm's Retrial Postponed to April 26, 2027]On August 26, the retrial date for Tornado Cash developer Roman Storm has been postponed to April 26, 2027, as his motion for acquittal is still awaiting a ruling. Previously, U.S. prosecutors had pushed for the retrial to be scheduled for October 2026.

Tornado Cash Co-Founder Roman Storm's Retrial Postponed to April 26, 2027

According to Beating AI news, Shopify CEO Tobi Lütke is considering banning Claude Code within the company. It's not that Claude is ineffective, but rather that it insists on using its own CLAUDE.md. Shopify utilizes multiple agents, including Claude Code and Codex, while other tools can share AGENTS.md. However, Claude Code only reads CLAUDE.md. The two sets of documents will recursively layer in large code repositories, and if one layer fails to sync, someone will end up with incorrect rules. Shopify has already implemented automated checks to cover this issue, but Tobi feels this is unnecessary trouble. His request is quite simple: Claude Code should also read AGENTS.md, and maintaining a single version would suffice. Claude Code team member Thariq responded that they would make AGENTS.md easier to use. However, he then explained why Claude needs its own prompts, skills, and CLAUDE.md: the models differ, and specialized optimization yields better results. The short-term solution remains to reference AGENTS.md within CLAUDE.md, which does not address Tobi's concern. While it's acceptable to continue optimizing for Claude, why must project rules maintain a separate entry for Claude? Grok reviewed the previously leaked Claude Code source code and concluded more directly: the filename CLAUDE.md is hardcoded in the loading logic, and simply switching it to AGENTS.md would allow the original recursive discovery, loading, and referencing mechanisms to function without significant architectural changes. In short, AGENTS.md is usable; Claude Code just insists on keeping its own CLAUDE.md. Comments largely support Tobi, with DHH stating the distinction is unnecessary, Jesse Pollak expressing frustration, and Chamath Palihapitiya believing that maintaining two systems will inevitably lead to 'brain splitting.' Kun Chen suggested that the correct approach should be to default to reading AGENTS.md, and if Claude-specific optimization is truly needed, then CLAUDE.md should remain an optional choice, rather than the other way around.

[Should Agents Differentiate Between Apple MD and Android MD? Claude Insists on Its Own System]According to Beating AI news, Shopify CEO Tobi Lütke is considering banning Claude Code within the company. It's not that Claude is ineffective, but rather that it insists on using its own CLAUDE.md. Shopify utilizes multiple agents, including Claude Code and Codex, while other tools can share AGENTS.md. However, Claude Code only reads CLAUDE.md. The two sets of documents will recursively layer in large code repositories, and if one layer fails to sync, someone will end up with incorrect rules. Shopify has already implemented automated checks to cover this issue, but Tobi feels this is unnecessary trouble. His request is quite simple: Claude Code should also read AGENTS.md, and maintaining a single version would suffice. Claude Code team member Thariq responded that they would make AGENTS.md easier to use. However, he then explained why Claude needs its own prompts, skills, and CLAUDE.md: the models differ, and specialized optimization yields better results. The short-term solution remains to reference AGENTS.md within CLAUDE.md, which does not address Tobi's concern. While it's acceptable to continue optimizing for Claude, why must project rules maintain a separate entry for Claude? Grok reviewed the previously leaked Claude Code source code and concluded more directly: the filename CLAUDE.md is hardcoded in the loading logic, and simply switching it to AGENTS.md would allow the original recursive discovery, loading, and referencing mechanisms to function without significant architectural changes. In short, AGENTS.md is usable; Claude Code just insists on keeping its own CLAUDE.md. Comments largely support Tobi, with DHH stating the distinction is unnecessary, Jesse Pollak expressing frustration, and Chamath Palihapitiya believing that maintaining two systems will inevitably lead to 'brain splitting.' Kun Chen suggested that the correct approach should be to default to reading AGENTS.md, and if Claude-specific optimization is truly needed, then CLAUDE.md should remain an optional choice, rather than the other way around.

Should Agents Differentiate Between Apple MD and Android MD? Claude Insists on Its Own System

According to Beating AI news, Shopify CEO Tobi Lütke is considering banning Claude Code within the company. It's not that Claude is ineffective, but it insists on using its own CLAUDE.md. Shopify employs various agents, including Claude Code and Codex. Other tools can share AGENTS.md, but Claude Code only reads CLAUDE.md. The two sets of documents will recursively layer in large code repositories. If one layer fails to sync, someone ends up with incorrect rules. Shopify has already implemented automated checks to address this issue, but Tobi feels this is unnecessary trouble. His request is quite simple: Claude Code should also read AGENTS.md, and maintaining a single version would suffice. Thariq, a member of the Claude Code team, responded that they would make AGENTS.md easier to use. However, he then explained why Claude needs its own prompts, skills, and CLAUDE.md: the models are different, and specialized optimization yields better results. The short-term solution remains to reference AGENTS.md within CLAUDE.md, which does not resolve Tobi's issue. You can continue to optimize for Claude, but why must project rules maintain a separate entry for Claude? Grok reviewed the previously leaked Claude Code source code and concluded that the filename CLAUDE.md is hard-coded in the loading logic. Simply changing it to AGENTS.md would allow the original recursive discovery, loading, and referencing mechanisms to function without major architectural changes. In short, AGENTS.md is usable; Claude Code just insists on keeping its own CLAUDE.md. The comments largely support Tobi. DHH stated that the distinction is entirely unnecessary, Jesse Pollak expressed frustration, and Chamath Palihapitiya believes that continuing with two systems will inevitably lead to 'brain splitting.' Kun Chen suggested that the correct approach should be to default to reading AGENTS.md, and if specific Claude optimizations are needed, then keep CLAUDE.md as an optional choice, rather than the other way around.

[Should Agents Differentiate Between Apple MD and Android MD? Claude Insists on Its Own System]According to Beating AI news, Shopify CEO Tobi Lütke is considering banning Claude Code within the company. It's not that Claude is ineffective, but it insists on using its own CLAUDE.md. Shopify employs various agents, including Claude Code and Codex. Other tools can share AGENTS.md, but Claude Code only reads CLAUDE.md. The two sets of documents will recursively layer in large code repositories. If one layer fails to sync, someone ends up with incorrect rules. Shopify has already implemented automated checks to address this issue, but Tobi feels this is unnecessary trouble. His request is quite simple: Claude Code should also read AGENTS.md, and maintaining a single version would suffice. Thariq, a member of the Claude Code team, responded that they would make AGENTS.md easier to use. However, he then explained why Claude needs its own prompts, skills, and CLAUDE.md: the models are different, and specialized optimization yields better results. The short-term solution remains to reference AGENTS.md within CLAUDE.md, which does not resolve Tobi's issue. You can continue to optimize for Claude, but why must project rules maintain a separate entry for Claude? Grok reviewed the previously leaked Claude Code source code and concluded that the filename CLAUDE.md is hard-coded in the loading logic. Simply changing it to AGENTS.md would allow the original recursive discovery, loading, and referencing mechanisms to function without major architectural changes. In short, AGENTS.md is usable; Claude Code just insists on keeping its own CLAUDE.md. The comments largely support Tobi. DHH stated that the distinction is entirely unnecessary, Jesse Pollak expressed frustration, and Chamath Palihapitiya believes that continuing with two systems will inevitably lead to 'brain splitting.' Kun Chen suggested that the correct approach should be to default to reading AGENTS.md, and if specific Claude optimizations are needed, then keep CLAUDE.md as an optional choice, rather than the other way around.

On August 26, according to Whale Alert monitoring, at 06:41 and 13:12 Beijing time today, USDC Treasury minted a total of 250 million USDC on the Solana chain in two transactions, amounting to a total of $500 million.

[USDC Treasury Mints $500 Million USDC on Solana Chain in Last 6 Hours]On August 26, according to Whale Alert monitoring, at 06:41 and 13:12 Beijing time today, USDC Treasury minted a total of 250 million USDC on the Solana chain in two transactions, amounting to a total of $500 million.

USDC Treasury Mints $500 Million USDC on Solana Chain in Last 6 Hours

On August 26, according to GMGN market data, the market cap of the Robinhood Chain ecosystem token PONS has risen above $120 million, currently reported at approximately $121 million, with a 24-hour increase of 36.25%, now priced at $0.120.

[PONS Market Cap Surpasses $120 Million with 24-Hour Increase of Over 36%]On August 26, according to GMGN market data, the market cap of the Robinhood Chain ecosystem token PONS has risen above $120 million, currently reported at approximately $121 million, with a 24-hour increase of 36.25%, now priced at $0.120.

PONS Market Cap Surpasses $120 Million with 24-Hour Increase of Over 36%

On August 26, according to GMGN market data, the market cap of the Robinhood Chain ecosystem token PONS has risen above $120 million, currently reported at approximately $121 million, with a 24-hour increase of 36.25%, currently priced at $0.120.

[PONS Market Cap Surpasses $120 Million with 24-Hour Increase of Over 36%]On August 26, according to GMGN market data, the market cap of the Robinhood Chain ecosystem token PONS has risen above $120 million, currently reported at approximately $121 million, with a 24-hour increase of 36.25%, currently priced at $0.120.

On August 26, Uniswap founder Hayden Adams stated that with the advancement of the tokenization wave of real-world assets (RWA), automated market makers (AMM) are on a clear path to dominate global financial markets. Adams pointed out that traditional market makers monopolize high profits through vertical integration and pursue high-cost delta-neutral hedging, while blockchain decouples execution, custody, and settlement, significantly lowering the barriers to market making. In the on-chain ecosystem, liquidity naturally tends to 'correlated pairs,' requiring only a few high-liquidity 'bridge pairs' (such as SPY/USD, ETH/USDC) to connect to the dollar channel. Since market makers holding correlated assets bear lower inventory risks, passive AMMs can replace traditional high-cost market-making strategies at a very low capital cost.

[Uniswap Founder Hayden Adams: AMMs Are on a Clear Path to Dominate Global Financial Markets]On August 26, Uniswap founder Hayden Adams stated that with the advancement of the tokenization wave of real-world assets (RWA), automated market makers (AMM) are on a clear path to dominate global financial markets. Adams pointed out that traditional market makers monopolize high profits through vertical integration and pursue high-cost delta-neutral hedging, while blockchain decouples execution, custody, and settlement, significantly lowering the barriers to market making. In the on-chain ecosystem, liquidity naturally tends to 'correlated pairs,' requiring only a few high-liquidity 'bridge pairs' (such as SPY/USD, ETH/USDC) to connect to the dollar channel. Since market makers holding correlated assets bear lower inventory risks, passive AMMs can replace traditional high-cost market-making strategies at a very low capital cost.

Uniswap Founder Hayden Adams: AMMs Are on a Clear Path to Dominate Global Financial Markets

火币HTX报道，8月10日，Meta推出轻量级Glimmer AI模型，用户可在本地运行。

【Meta推出轻量级Glimmer AI模型】火币HTX报道，8月10日，Meta推出轻量级Glimmer AI模型，用户可在本地运行。

Meta推出轻量级Glimmer AI模型

Застереження：Наведені вище матеріали не представляють позицію компанії HTX.，HTX не дає жодних торгових рекомендацій.。

Схожі статті

Усі коментарі0НовіПопулярно

Популярні теми

Схожі статті