# Bài viết Liên quan Response

Trung tâm Tin tức HTX cung cấp những bài viết mới nhất và phân tích chuyên sâu về "Response", bao gồm xu hướng thị trường, cập nhật dự án, phát triển công nghệ và chính sách quản lý trong ngành tiền kỹ thuật số.

‘Beyond code errors’ – How Drift Protocol’s $285mln drain shifts DeFi security bar

The Drift Protocol exploit, resulting in a $285 million loss, marks a significant shift in DeFi security threats, moving beyond simple code errors to sophisticated attacks on governance and operational control layers. The attacker used pre-signed transactions and manipulated a multi-signature mechanism to gain admin access rapidly. This incident underscores that security now depends more on protecting protocol operations and user assets than solely fixing smart contract bugs. Drift’s response demonstrated the critical role of fast crisis management—halting deposits and withdrawals quickly, coordinating with security partners, and providing transparency—which helped contain cross-protocol risks and maintain market confidence. The event reflects a broader trend in DeFi, where attackers increasingly target access and control mechanisms. This has elevated the importance of operational security, prompting protocols to compete not only on yield but also on their ability to manage risk, protect capital, and respond effectively during crises. Industry data shows a growing focus on security investments, such as signer rotation and emergency controls, as key factors in building resilience and trust.

ambcrypto04/06 05:03

‘Beyond code errors’ – How Drift Protocol’s $285mln drain shifts DeFi security bar

ambcrypto04/06 05:03

3 'Hello's and You're Out of Quota: Where Did Your Claude Code Allowance Go? A 28-Day Cache Bug and an Official Response Telling You to 'Use It Sparingly'

Over the past month, Claude Code experienced a critical caching bug that caused prompt cache read rates to drop to 4–17%, far below the typical 97–99%. This meant users were charged 10–20 times more than normal when resuming conversations, as the system reprocessed entire contexts instead of reusing cached content. The bug persisted across 20 versions from March 4 to April 1. User complaints surged after a promotional period ended, revealing the severity of the issue. Anthropic responded by tightening usage limits and offering user advice—such as downgrading models or reducing context windows—but did not issue refunds or reset quotas. Despite confirming and fixing a caching regression bug, the company maintained that no overcharging occurred. The response contrasts with OpenAI’s approach of compensating users during similar incidents. Subscribers reported extreme consumption rates, with some exhausting their monthly quotas in minutes.

marsbit04/03 09:34