summaryrefslogtreecommitdiff
path: root/bip-0115.mediawiki
diff options
context:
space:
mode:
Diffstat (limited to 'bip-0115.mediawiki')
-rw-r--r--bip-0115.mediawiki4
1 files changed, 2 insertions, 2 deletions
diff --git a/bip-0115.mediawiki b/bip-0115.mediawiki
index 52366ab..8bc90f6 100644
--- a/bip-0115.mediawiki
+++ b/bip-0115.mediawiki
@@ -5,7 +5,7 @@
Author: Luke Dashjr <luke+bip@dashjr.org>
Comments-Summary: No comments yet.
Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0115
- Status: Draft
+ Status: Rejected
Type: Standards Track
Created: 2016-09-23
License: BSD-2-Clause
@@ -83,7 +83,7 @@ Why are block heights required to be absolute, rather than relative?
Why are blocks older than 52596 deep in the chain not verified?
* This is to avoid creating an infinite storage requirement from all full nodes which would be necessary to maintain all the block headers indefinitely. 52596 block headers requires a fixed size of approximately 4 MB.
-* In any case where you might want to specify a deeper block, you can also just as well specify a more recent one that decends from it.
+* In any case where you might want to specify a deeper block, you can also just as well specify a more recent one that descends from it.
* It is assumed that 1 year is sufficient time to double-spend any common UTXOs on all blockchains of interest.
* If a deeper check is needed, it can be softforked in. Making the check more shallow, on the other hand, is a hardfork.