summaryrefslogtreecommitdiff
path: root/bip-0050.mediawiki
diff options
context:
space:
mode:
Diffstat (limited to 'bip-0050.mediawiki')
-rw-r--r--bip-0050.mediawiki2
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0050.mediawiki b/bip-0050.mediawiki
index 4f48fca..fbc1c0f 100644
--- a/bip-0050.mediawiki
+++ b/bip-0050.mediawiki
@@ -41,7 +41,7 @@ This would be an issue even if the entire network was running version 0.7.2. It
===Immediately===
'''Done''': Release a version 0.8.1, forked directly from 0.8.0, that, for the next two months has the following new rules:
-# Reject blocks that would probably could cause more than 10,000 locks to be taken.
+# Reject blocks that would probably cause more than 10,000 locks to be taken.
# Limit the maximum block-size created to 500,000 bytes
# Release a patch for older versions that implements the same rules, but also increases the maximum number of locks to 537,000
# Create a web page on bitcoin.org that will urge users to upgrade to 0.8.1, but will tell them how to set DB_CONFIG to 537,000 locks if they absolutely cannot.