summaryrefslogtreecommitdiff
path: root/bip-0115.mediawiki
diff options
context:
space:
mode:
authorflack <flack@contentcontrol-berlin.de>2017-10-05 23:43:18 +0200
committerGitHub <noreply@github.com>2017-10-05 23:43:18 +0200
commitfba4c80b9f36f5648f2156265a10cff017f5fc2f (patch)
treef1c4ab994e7969f52fec527b8a31f9204140a5bf /bip-0115.mediawiki
parent583c92809a9230bfbe2061ebb428476ecaa115fc (diff)
Typo fix
Diffstat (limited to 'bip-0115.mediawiki')
-rw-r--r--bip-0115.mediawiki2
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0115.mediawiki b/bip-0115.mediawiki
index 52366ab..9432f5c 100644
--- a/bip-0115.mediawiki
+++ b/bip-0115.mediawiki
@@ -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.