From db01e36e695e789a6f84a338eb41308a02906f59 Mon Sep 17 00:00:00 2001
From: wakgill <76528604+wakgill@users.noreply.github.com>
Date: Thu, 7 Jan 2021 23:43:03 -0600
Subject: [PATCH] Create 111.md

---
 docs/forum/bitcoin-forum/111.md | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)
 create mode 100644 docs/forum/bitcoin-forum/111.md

diff --git a/docs/forum/bitcoin-forum/111.md b/docs/forum/bitcoin-forum/111.md
new file mode 100644
index 0000000..e515b99
--- /dev/null
+++ b/docs/forum/bitcoin-forum/111.md
@@ -0,0 +1,24 @@
+---
+layout: forum
+title: 'Re: Proof-of-work difficulty increasing'
+grand_parent: Forum Posts
+parent: Bitcoin Forum
+nav_order: 111
+date: 2010-06-02 18:45:38 UTC
+original: https://bitcointalk.org/index.php?topic=43.msg1323#msg1323
+---
+
+# Re: Proof-of-work difficulty increasing
+
+---
+
+```
+Re: Proof-of-work difficulty increasing
+June 02, 2010, 06:45:38 PM
+
+That's a good idea.  I'm not sure where exactly to fit that in, but it could certainly calculate the expected average time between blocks generated, and then people would know what to expect.
+
+Every node and each processor has a different public key in its block, so they're guaranteed to be scanning different territory.
+
+Whenever the 32-bit nonce starts over at 1, bnExtraNonce gets incremented, which is an arbitrary precision integer.
+```