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

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ề "Bug", 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ố.

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

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'

marsbit04/03 09:34

Anthropic Issues DMCA Takedown Notices, Massively Removes 8,100 Source Code Repositories

AI giant Anthropic has issued multiple DMCA takedown notices to GitHub in response to a major source code leak. The company is targeting illegally hosted repositories containing the code for Claude Code. As a result, GitHub has removed the main repository along with over 8,100 forked repositories, marking one of the largest code copyright clean-up operations in the AI industry. Contrary to initial reports of employee error, an internal investigation revealed the leak was caused by a bug in an internal packaging tool. This bug mistakenly included sensitive files and full TypeScript source code, which should have remained private, into a production build. While this finding shifts blame from employee misconduct, it highlights a critical security flaw in Anthropic's automated workflow. Despite the takedown, the code had already been downloaded by thousands of developers within 48 hours and widely shared on platforms like Telegram, cloud storage, and private Git servers, making complete eradication nearly impossible. The leaked code, which includes implementation logic and internal model fine-tuning instructions, continues to be actively analyzed by developers.

marsbit04/01 07:17

Anthropic Issues DMCA Takedown Notices, Massively Removes 8,100 Source Code Repositories

marsbit04/01 07:17

Hardcore Breakdown of Polymarket's Fee Formula: How Did the Extreme Rate of 90+% Pop Up?

Polymarket, a prediction market platform, recently faced backlash due to unexpectedly high transaction fees, with some users reporting fees as extreme as 94.8%. The issue stemmed from a temporary change in the fee calculation formula. The platform initially used an "old formula": fee = C × p × feeRate × (p × (1 - p))^exponent. However, a brief update to an "abnormal formula" removed a critical "× p" term, becoming: fee = C × feeRate × (p × (1 - p))^exponent. Since share prices (p) are always less than $1, this omission drastically increased fees, especially for very low-priced shares (near $0.001), as the fee was no longer scaled by the price. An exponent value of 0.5 in certain markets ("Weather" and "Economy") further exacerbated the curve, leading to the extreme rates. Polymarket quickly responded by implementing a "new formula": fee = C × feeRate × p × (1 - p), effectively setting the exponent to 1. This change significantly reduced fees, particularly for extreme price points, bringing maximum fees down to around 5%. The article advises users to avoid high fees by using limit orders (which are free and even offer a 20-25% maker rebate) or the platform's "Split" function to indirectly establish positions instead of market orders.

Odaily星球日报04/01 03:57

Hardcore Breakdown of Polymarket's Fee Formula: How Did the Extreme Rate of 90+% Pop Up?

Odaily星球日报04/01 03:57

A Quick Fix: Ripple Patches Major Issue That Could Threaten XRP Users On The Ledger

Ripple has released Rippled version 3.1.2 to patch a critical vulnerability in the XRP Ledger's Batch amendment feature. The flaw, discovered shortly after the feature's introduction, could have allowed attackers to execute unauthorized transactions and caused servers to crash or restart under certain conditions. Developers from RippleX collaborated on the urgent fix. This is the third rapid update addressing issues originating from Rippled 3.1.0. Separately, Ripple CTO David Schwartz responded to criticism about the company's practice of selling XRP to fund operations, arguing that such sales do not necessarily harm retail investors.

bitcoinist03/18 03:32

A Quick Fix: Ripple Patches Major Issue That Could Threaten XRP Users On The Ledger

bitcoinist03/18 03:32

Screwed by Polymarket, This Time the Bug Was a 'Time Warp'

Polymarket, a prediction market platform, encountered a technical issue related to the transition from Eastern Standard Time (EST) to Eastern Daylight Time (EDT) on March 8. The switch, which involves moving the clock forward by one hour, caused a disruption in the platform’s hourly cryptocurrency price prediction markets for assets like BTC, ETH, SOL, and XRP. Due to the time change, the 2:00 AM hour effectively did not exist, leading Polymarket’s system to display an illogical time range of "March 8, 1-1 AM ET" for these events, instead of the expected one-hour duration. This anomaly affected both the front-end display and API data, causing confusion among users. One automated trading user reported significant losses exceeding $100,000, as their system relied on accurate end-time data to execute trades. The incident highlights a design flaw in using local time (ET) without accounting for daylight saving transitions, unlike mainstream financial systems that typically use UTC time to avoid such inconsistencies. Users have called for Polymarket to switch to UTC and compensate affected traders. The platform has not yet issued an official response.

marsbit03/09 08:15

Screwed by Polymarket, This Time the Bug Was a 'Time Warp'

marsbit03/09 08:15

Got Ripped Off by Polymarket, This Time the Bug is a "Time Warp"

Title: Polymarket's "Time Warp" Bug During Daylight Saving Transition Causes User Losses On March 8, 2024, Polymarket, a prediction market platform, encountered a significant timing error due to the transition from Eastern Standard Time (EST) to Eastern Daylight Time (EDT) in the US. This annual clock adjustment, which skips the hour from 2:00 AM to 3:00 AM, disrupted the platform's automated event creation and settlement system. The issue affected Polymarket's "Crypto Up or Down" hourly prediction markets for assets like BTC, ETH, SOL, and XRP. Events scheduled to run from 1:00 AM to 2:00 AM ET were impacted. Due to the time change, the platform's front-end and API incorrectly displayed the event duration as "March 8, 1-1 AM ET"—a logically impossible interval—instead of the correct "1:00 AM to 3:00 AM ET" (which still represents one actual hour). This bug caused substantial problems for automated trading systems that rely on precise timing data from the API. One user, "@richrichardoz," reported losses exceeding $100,000 because their trading bot malfunctioned upon receiving identical start and end times. The user and others have called for Polymarket to switch its time standard to UTC (Coordinated Universal Time) to avoid such issues and to compensate affected users. The incident highlights a critical design flaw in using local time (which is subject to bi-annual changes) instead of UTC, the global standard for financial systems. This ensures time remains consistent, monotonic, and unambiguous for automated processes. While the impact was limited, it underscores the need for prediction markets to adopt the rigorous engineering standards of traditional financial infrastructure as they scale. Polymarket had not issued an official response at the time of writing.

Odaily星球日报03/09 08:10

Got Ripped Off by Polymarket, This Time the Bug is a "Time Warp"

Odaily星球日报03/09 08:10

Ripple Outlines Next Steps After Critical XRP Ledger Batch Amendment Bug

Ripple is implementing stricter security measures for the XRP Ledger amendment process after a critical bug was discovered in the proposed Batch amendment (XLS-56). The flaw, identified by Cantina AI, was caught before activation, preventing any mainnet impact. RippleX Head of Engineering J. Ayo Akinyele acknowledged the amendment "progressed further than it should have" and emphasized the need for higher review standards. While the network's safeguards worked as a final defense, Ripple is taking steps to make them a primary one. Proposed changes include mandatory multiple independent audits for high-risk features, an expanded bug bounty program, and formal adversarial testing. The company is also incorporating AI-assisted code review and aims to make formal verification standard for critical ledger components.

bitcoinist03/04 17:32

Ripple Outlines Next Steps After Critical XRP Ledger Batch Amendment Bug

bitcoinist03/04 17:32

XRP Ledger Security Debate Intensifies After BatchGate Scare

Following the near-miss incident known as BatchGate, a significant security concern has sparked a broader debate around governance and safety protocols on the XRP Ledger. Validator operator Daniel Keller criticized the existing review process as a "systemic failure" and withdrew support for all pending amendments. He emphasized that validators are governance participants, not unpaid auditors, and called for amendment proposers—particularly Ripple—to provide comprehensive documentation, testing, and security proofs. Keller also urged Ripple to increase investment in core protocol engineering and security. Other community members, like validator Vet, advocated for slower amendment rollouts, paid audits, and larger bug bounty programs. Keller disagreed with simply slowing down development, instead pushing for better incentives and resources to maintain progress without compromising security. The incident has raised fundamental questions about whether the XRPL’s amendment process has sufficient safeguards for the scale of changes being proposed. At the time of reporting, XRP was trading at $1.3566.

bitcoinist03/03 18:31

XRP Ledger Security Debate Intensifies After BatchGate Scare

bitcoinist03/03 18:31

XRPL Foundation Fixes Major Bug Just Ahead of Mainnet Release

A critical vulnerability in the XRP Ledger, potentially exposing up to $80 billion, was discovered by a security engineer using an AI-assisted tool. The flaw involved malformed transactions that could cause consensus failure under specific edge cases. The issue was responsibly disclosed, verified, and patched by the development team. Validator operators were urged to update their software immediately. No exploitation occurred prior to the fix. The incident highlights the effectiveness of combining AI tools with human expertise in blockchain security, enabling early detection of complex vulnerabilities and reinforcing trust in decentralized systems.

TheNewsCrypto02/27 13:16

XRPL Foundation Fixes Major Bug Just Ahead of Mainnet Release

TheNewsCrypto02/27 13:16

Sui publishes post-mortem after mainnet stall halted transactions for six hours

Sui Foundation published a post-mortem detailing a six-hour mainnet stall on January 15, caused by an edge-case bug in consensus commit logic. This led to validators processing conflicting transactions differently under specific garbage-collection conditions, resulting in divergent checkpoint digests. The network automatically halted to prevent inconsistent state finalization, prioritizing safety over availability. No forks, rollbacks, or fund losses occurred, and read operations remained functional. Sui is implementing improvements for faster recovery and enhanced testing to prevent similar issues, confirming the safety mechanisms worked as intended.

ambcrypto01/16 00:29