From 6ee3e7dab8b4399decf3212f5dea5cdc2098ef5d Mon Sep 17 00:00:00 2001 From: wakgill <76528604+wakgill@users.noreply.github.com> Date: Tue, 5 Jan 2021 00:48:54 -0600 Subject: [PATCH] Create 57.md --- docs/forum/bitcoin-forum/57.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 docs/forum/bitcoin-forum/57.md diff --git a/docs/forum/bitcoin-forum/57.md b/docs/forum/bitcoin-forum/57.md new file mode 100644 index 0000000..ab0c14b --- /dev/null +++ b/docs/forum/bitcoin-forum/57.md @@ -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 +--- + +
+Re: Proof-of-work difficulty increasing
+February 17, 2010, 05:58:03 PM
+ 
+Quote from: Sabunir on February 16, 2010, 08:51:51 AM
+-------------
+. 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%.
+
+Quote from: Sabunir on February 16, 2010, 08:51:51 AM
+-------------
+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.