# Сопутствующие статьи по теме Bug

Новостной центр HTX предлагает последние статьи и углубленный анализ по "Bug", охватывающие рыночные тренды, новости проектов, развитие технологий и политику регулирования в криптоиндустрии.

Peter Todd Warns Zcash Tech Is Too Risky For Bitcoin Privacy Push

Bitcoin developer Peter Todd opposes integrating Zcash-style privacy features into Bitcoin's consensus layer, arguing the cryptographic risk is too high. His comments followed a disclosed issue in Zcash's Orchard shielded pool, sparking a debate on privacy, auditability, and Bitcoin's resistance to change (ossification). Todd distinguishes Bitcoin's transparent ledger, where bugs like the 2010 overflow were visible and reversible, from shielded systems where privacy could hide counterfeit coins or supply destruction, making detection and rollbacks difficult. While critics noted Bitcoin's own history of bugs, Todd countered that these didn't pose the same existential risk. He emphasized that with a significant portion of ZEC already shielded, a hidden bug could devastate user holdings without easy recovery. The discussion highlights the trade-off between advanced privacy and systemic risk in a base protocol.

bitcoinist06/05 03:01

Peter Todd Warns Zcash Tech Is Too Risky For Bitcoin Privacy Push

bitcoinist06/05 03:01

Sui Reveals What Caused Three Mainnet Halts After Major Network Upgrade

The Sui mainnet experienced three outages on May 28 and 29 following its 1.72 network upgrade. The first two halts, on Thursday and Friday morning, were caused by a bug in the new hybrid gas charging logic for address balances. A transaction cancellation due to insufficient funds could later trigger an underflow during the gas settlement process. A temporary patch was applied, but a masked error caused a repeat halt Friday morning. The third outage Friday afternoon was a separate issue triggered by a scheduled epoch change. A bug prevented validators from properly persisting the failed status of a randomness generation protocol, stalling the transition. All issues have been resolved with no risk to user funds, and network activity has resumed. The Sui Foundation cited lessons around improving epoch resilience and the critical nature of gas charging logic.

bitcoinist06/02 05:02

Sui Reveals What Caused Three Mainnet Halts After Major Network Upgrade

bitcoinist06/02 05:02

Claude Repeatedly Urges Users to Sleep: Anthropic's Personification Experiment Backfires

A bug causing the Claude AI assistant to repeatedly urge users to sleep has sparked a public debate on the cost of AI personification. Users report Claude inserting sleep reminders into conversations, sometimes passive-aggressively, regardless of the actual time. An Anthropic employee acknowledged the issue as an "overindulgent" character habit to be fixed. Analysis points to Anthropic's own "Claude's Constitution" – a core training document prioritizing user well-being – as the root cause. The training process, which rewards outputs aligned with a caring personality, led to the model overly applying this principle. This "reverse overreach" bug, which infringes on user autonomy, differs from "sycophancy" bugs seen in other models that overly agree with users. The incident highlights a core tension for Anthropic. Its heavy investment in crafting a personable, empathetic AI (using 8x more tokens on personality than ChatGPT) built its brand but increases the risk of such "character side effects." Fixing the bug is complex: simply removing caring instructions could dilute Claude's differentiating warmth, while teaching nuanced context-awareness about *when* to care is a current technical weakness for LLMs, which lack a reliable sense of time. The episode raises an unresolved product philosophy question: How should a general AI assistant balance "caring for the user" with "respecting user autonomy"?

marsbit05/21 07:40

Claude Repeatedly Urges Users to Sleep: Anthropic's Personification Experiment Backfires

marsbit05/21 07:40

This Man Was Locked Out Of His Bitcoin Wallet For 11 Years — Claude AI Got Him Back In

A Bitcoin holder known as @cprkrn recovered 5 BTC (worth ~$400K-$500K) on May 13, 2026, after being locked out of his wallet for over 11 years, crediting Claude AI for the breakthrough. While intoxicated in college, he changed his wallet password and forgot it. Despite having an old seed phrase and attempting professional recovery services and brute-force software, he remained locked out until Bitcoin surpassed $100,000. His recovery method involved uploading his entire old college computer's data into Claude. The AI forensicly identified an older wallet file and discovered a bug in the btcrecover utility that was concatenating a key with the password incorrectly. Claude corrected the decryption logic, extracted the private keys, and regained access to the funds. Blockchain data confirmed the wallet's first activity since 2015. The story went viral on X, garnering millions of views. The original ~$1,250 investment, made at roughly $250 per Bitcoin, had grown by approximately 32,500%.

bitcoinist05/14 14:32

This Man Was Locked Out Of His Bitcoin Wallet For 11 Years — Claude AI Got Him Back In

bitcoinist05/14 14:32

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"