-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
8 changed files
with
151 additions
and
51 deletions.
There are no files selected for viewing
20 changes: 20 additions & 0 deletions
20
static/delvingbitcoin/Aug_2024/2937_Zawy-s-Alternating-Timestamp-Attack.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,20 @@ | ||
| <?xml version='1.0' encoding='UTF-8'?> | ||
| <feed xmlns="http://www.w3.org/2005/Atom"> | ||
| <id>1</id> | ||
| <title>Zawy’s Alternating Timestamp Attack</title> | ||
| <updated>2024-08-12T02:11:13.291117+00:00</updated> | ||
| <author> | ||
| <name>AntoineP 2024-08-11 09:44:37.218000+00:00</name> | ||
| </author> | ||
| <generator uri="https://lkiesow.github.io/python-feedgen" version="0.9.0">python-feedgen</generator> | ||
| <entry> | ||
| <id>1</id> | ||
| <title>Zawy’s Alternating Timestamp Attack</title> | ||
| <updated>2024-08-12T02:11:13.291142+00:00</updated> | ||
| <link href="https://delvingbitcoin.org/t/zawy-s-alternating-timestamp-attack/1062/3" rel="alternate"/> | ||
| <summary>The proposed solution addresses significant vulnerabilities within the blockchain's consensus mechanism, specifically targeting the timewarp attack. The suggested fix, when integrated with the consensus cleanup's timewarp correction, aims to ensure that retarget periods become monotonic, thereby enhancing the system's resilience against specific types of attacks. The timewarp attack presents two major threats: firstly, it substantially increases the power of a 51% attacker, making the network more susceptible to malicious activities. Secondly, it encourages behavior that is detrimental to the long-term sustainability of the system by tempting miners and users to increase the block rate for short-term gains. | ||
|
|
||
| Moreover, the discussion highlights the Murch-Zawy attack, which, unlike the timewarp, necessitates the non-publication of blocks for an extended period (16 weeks) but similarly allows an adversary to benefit from continuously reduced difficulty levels. This aspect of the Murch-Zawy attack aligns with the timewarp in enabling attackers to significantly lower the difficulty, potentially down to the lowest possible level, within a comparable timeframe. The dialogue suggests incorporating the solution as part of broader efforts to revive and strengthen the consensus cleanup initiative, indicating a strategic approach to mitigating vulnerabilities and ensuring the robustness of the platform. For further information on the consensus cleanup and its implications, interested parties can visit [this link](https://delvingbitcoin.org/t/great-consensus-cleanup-revival/710should-we-really-fix-it-3).</summary> | ||
| <published>2024-08-11T09:44:37.218000+00:00</published> | ||
| </entry> | ||
| </feed> |
18 changes: 18 additions & 0 deletions
18
...elvingbitcoin/Aug_2024/2938_Stable-Channels-peer-to-peer-dollar-balances-on-Lightning.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| <?xml version='1.0' encoding='UTF-8'?> | ||
| <feed xmlns="http://www.w3.org/2005/Atom"> | ||
| <id>1</id> | ||
| <title>Stable Channels - peer-to-peer dollar balances on Lightning</title> | ||
| <updated>2024-08-12T02:09:31.677160+00:00</updated> | ||
| <author> | ||
| <name>Christian Decker 2024-08-11 10:26:23.542000+00:00</name> | ||
| </author> | ||
| <generator uri="https://lkiesow.github.io/python-feedgen" version="0.9.0">python-feedgen</generator> | ||
| <entry> | ||
| <id>1</id> | ||
| <title>Stable Channels - peer-to-peer dollar balances on Lightning</title> | ||
| <updated>2024-08-12T02:09:31.677197+00:00</updated> | ||
| <link href="https://delvingbitcoin.org/t/stable-channels-peer-to-peer-dollar-balances-on-lightning/875/11" rel="alternate"/> | ||
| <summary>The discussion centers on the differentiation between classical Lightning Network (LN) channels and hosted channels, emphasizing that while both exist within Tony's channels framework, they should not be conflated. Hosted channels are distinguished from traditional LN channels primarily by their inability to settle disputes on-chain. Unlike classical LN channels which have an inbuilt dispute resolution mechanism leveraging the blockchain, hosted channels only offer a proof of misbehavior without any automatic on-chain dispute resolution capabilities. This distinction underlines the unique operational mechanisms and limitations inherent to each type of channel, arguing against the oversimplification or misunderstanding of equating one with the other merely because they share some functionalities or are part of the same network architecture.</summary> | ||
| <published>2024-08-11T10:26:23.542000+00:00</published> | ||
| </entry> | ||
| </feed> |
18 changes: 18 additions & 0 deletions
18
static/delvingbitcoin/Aug_2024/2940_Zawy-s-Alternating-Timestamp-Attack.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| <?xml version='1.0' encoding='UTF-8'?> | ||
| <feed xmlns="http://www.w3.org/2005/Atom"> | ||
| <id>1</id> | ||
| <title>Zawy’s Alternating Timestamp Attack</title> | ||
| <updated>2024-08-12T02:11:01.982019+00:00</updated> | ||
| <author> | ||
| <name>MentalNomad 2024-08-11 15:43:44.982000+00:00</name> | ||
| </author> | ||
| <generator uri="https://lkiesow.github.io/python-feedgen" version="0.9.0">python-feedgen</generator> | ||
| <entry> | ||
| <id>1</id> | ||
| <title>Zawy’s Alternating Timestamp Attack</title> | ||
| <updated>2024-08-12T02:11:01.982043+00:00</updated> | ||
| <link href="https://delvingbitcoin.org/t/zawy-s-alternating-timestamp-attack/1062/4" rel="alternate"/> | ||
| <summary>The theoretical soundness of an attack on a blockchain system, which involves selfish mining over a 16-week period, is acknowledged. However, the practicality of this attack is questioned due to the high requirements, such as the need for an attacker to control at least 50% of the network's hash rate. Despite these constraints, the attack presents a significant risk as it allows for the faster production of blocks and consequently, an increased rate of rewards. This creates a financial incentive for miners, or a coalition of miners whose combined hash rate exceeds 50%, to exploit this vulnerability. It is thus recommended that measures be taken to prevent the possibility of this exploit being used.</summary> | ||
| <published>2024-08-11T15:43:44.982000+00:00</published> | ||
| </entry> | ||
| </feed> |
24 changes: 24 additions & 0 deletions
24
static/delvingbitcoin/Aug_2024/2941_Zawy-s-Alternating-Timestamp-Attack.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,24 @@ | ||
| <?xml version='1.0' encoding='UTF-8'?> | ||
| <feed xmlns="http://www.w3.org/2005/Atom"> | ||
| <id>1</id> | ||
| <title>Zawy’s Alternating Timestamp Attack</title> | ||
| <updated>2024-08-12T02:10:54.870210+00:00</updated> | ||
| <author> | ||
| <name>zawy 2024-08-11 17:44:12.799000+00:00</name> | ||
| </author> | ||
| <generator uri="https://lkiesow.github.io/python-feedgen" version="0.9.0">python-feedgen</generator> | ||
| <entry> | ||
| <id>1</id> | ||
| <title>Zawy’s Alternating Timestamp Attack</title> | ||
| <updated>2024-08-12T02:10:54.870242+00:00</updated> | ||
| <link href="https://delvingbitcoin.org/t/zawy-s-alternating-timestamp-attack/1062/5" rel="alternate"/> | ||
| <summary>In the intricate ecosystem of cryptocurrency mining, the potential for a >50% attack raises significant concerns regarding the security and integrity of blockchain networks. Such an attack involves a single entity or collusion among entities controlling more than half of the network's mining power, enabling them to manipulate the Median Time Past (MTP) by selectively ignoring blocks from other miners. This capability would theoretically allow these entities to maximize their profits at the expense of the network's credibility and the coin's value. However, the economic disincentive linked to the depreciation of mining equipment and the overall devaluation of the coin serves as a deterrent against such actions. In contrast, testnets, which lack a profit motive, may be more vulnerable to attacks carried out for experimental or disruptive purposes. | ||
|
|
||
| The discussion transitions into exploring theoretical solutions aimed at mitigating these risks without precipitating adverse outcomes within the digital currency ecosystem. Among the proposed measures, a range of modifications to time-related rules within the mining algorithm are considered, each varying in terms of perfection and feasibility. These include implementing a monotonic, approximately 10-second "arrival" rule alongside the elimination of the MTP, Future Time Limit (FTL), and existing constraints on block time adjustments (referred to as 4x and 1/4 limits). A less ideal but still effective approach suggests maintaining monotonicity while reducing the FTL and removing the MTP and aforementioned limits. As safer alternatives, setting a two-hour past time limit for every block or every 2016 blocks with enforced actual time adjustments emerges as practical options that balance security with operational simplicity. | ||
|
|
||
| Further complexity is added by the consideration of soft versus hard forks as mechanisms for introducing these changes. Hard forks, requiring widespread consensus among network participants, present a higher barrier to implementation compared to soft forks, which can be activated with support from a smaller segment of the network. The proposition of a one-day past time limit via a soft fork, advocated by Johnson Lau, illustrates a strategic compromise that aims to safeguard against prolonged >50% attacks with minimal disruption. This approach notably includes additional safeguards during the transition between mining difficulty adjustments, ensuring continuity and stability within the blockchain infrastructure. | ||
|
|
||
| By carefully weighing these theoretical interventions against their potential impacts on the cryptocurrency landscape, the conversation underscores the delicate balance between innovation, security, and the preservation of trust within digital economies.</summary> | ||
| <published>2024-08-11T17:44:12.799000+00:00</published> | ||
| </entry> | ||
| </feed> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.