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

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

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.

marsbit16 ч. назад

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

marsbit16 ч. назад

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星球日报16 ч. назад

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

Odaily星球日报16 ч. назад

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

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

ambcrypto01/16 00:29

Bitcoin Core V30 Bug Risks Total Wallet Loss For Legacy Users

Bitcoin Core developers issued an urgent warning regarding a critical bug in versions 30.0 and 30.1 that, in rare cases, can delete all wallet files on a node during legacy (BDB) wallet migration, potentially leading to fund loss for users without backups. A fix is expected in version 30.2, and users are advised to avoid migrating legacy wallets until then. The disclosure sparked debate within the community, with some arguing the risk is understated since v30 forces migration for legacy wallet users, while others noted limited real-world impact with only one user reportedly affected. All agree on the precaution: back up wallets and delay migration until the patch is released.

bitcoinist01/07 23:06

Bitcoin Core V30 Bug Risks Total Wallet Loss For Legacy Users

bitcoinist01/07 23:06

Vitalik Buterin says Ethereum can handle temporary loss of finality

Vitalik Buterin, co-founder of Ethereum, stated that the network can tolerate temporary losses of finality without serious risk, even after a recent client bug nearly disrupted its confirmation mechanism. Buterin emphasized that while finalization indicates a block is irreversible, occasional delays of several hours due to bugs are acceptable. The critical issue to avoid is finalizing incorrect blocks. Experts, including Fabrizio Romano Genovese, supported this view, noting that during such events, Ethereum operates similarly to Bitcoin, which relies on probabilistic finality. In Ethereum, finality is achieved when a block receives over 66% of validator votes and remains unchallenged for over two epochs (64 blocks). While this mechanism ensures deterministic finality, its temporary loss reverts the network to probabilistic guarantees, as seen in a May 2023 incident. The loss of finality may impact infrastructure like bridges and layer-2 solutions, potentially delaying deposits or cross-chain transactions. However, users would not face transaction rollbacks or invalidations. Polygon confirmed that operations would continue normally, though transfers from Ethereum might be delayed until finality is restored. Genovese noted that developers choosing not to implement fallback mechanisms for finality loss bear responsibility for such delays.

cointelegraph12/10 11:55

Vitalik Buterin says Ethereum can handle temporary loss of finality