BitcoinCash/nakamoto-archive
1
Fork 0
Code Issues Pull Requests Releases Activity

Create 57.md

Browse Source
This commit is contained in:
wakgill
2021-01-05 00:48:54 -06:00
committed by GitHub
parent a7ca8540ab
commit 6ee3e7dab8
1 changed files with 28 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/forum/bitcoin-forum/57.md
+28
View File
@@ -0,0 +1,28 @@
---
layout: forum
title: 'Re: Proof-of-work difficulty increasing'
grand_parent: Forum Posts
parent: Bitcoin Forum
nav_order: 57
date: 2010-02-17 17:58:03 UTC
original: https://bitcointalk.org/index.php?topic=43.msg388#msg388
---
# Re: Proof-of-work difficulty increasing
---
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight">
<code>Re: Proof-of-work difficulty increasing
February 17, 2010, 05:58:03 PM
<a href="https://bitcointalk.org/index.php?topic=43.msg372#msg372">Quote from: Sabunir on February 16, 2010, 08:51:51 AM</a>
-------------
. Perhaps it has to do with my connection's very high latency (2000ms or more on average)
-------------
2 seconds of latency in both directions should reduce your generation success by less than 1%.
<a href="https://bitcointalk.org/index.php?topic=43.msg372#msg372">Quote from: Sabunir on February 16, 2010, 08:51:51 AM</a>
-------------
and/or my high packet loss (sometimes up to 10% loss)?
-------------
Probably OK, but I'm not sure. The protocol is designed to resync to the next message, and messages get re-requested from all the other nodes you're connected to until received. If you miss a block, it'll also keep requesting it every time another blocks comes in and it sees there's a gap. Before the original release I did a test dropping 1 out of 4 random messages under heavy load until I could run it overnight without any nodes getting stuck.</code></pre></div></div>