summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGregory Maxwell <greg@xiph.org>2014-04-01 17:04:24 -0700
committerGregory Maxwell <greg@xiph.org>2014-04-01 17:04:24 -0700
commitad078df048726604cccc1cff70ce952815913605 (patch)
treecd8fd0ce74d297ec41b6b1b4242604c12c314b7c
parent21d9261d3ef1aae6932def07263b5387b12e7f4c (diff)
parente04e99c315dd4067e267b62f84c9eeffeeccf94e (diff)
downloadbips-ad078df048726604cccc1cff70ce952815913605.tar.xz
Merge pull request #44 from sipa/bip42
Include image and index entry for BIP42
-rw-r--r--bip-0042.mediawiki2
-rw-r--r--bip-0042/inflation.pngbin0 -> 4628 bytes
2 files changed, 1 insertions, 1 deletions
diff --git a/bip-0042.mediawiki b/bip-0042.mediawiki
index a3fcdb2..d48bcf7 100644
--- a/bip-0042.mediawiki
+++ b/bip-0042.mediawiki
@@ -30,7 +30,7 @@ The block number is divided by 210000 (the "apparent" subsidy halving interval i
Despite the nice showoff of underhanded programming skills - we want Bitcoin to be well-specified. Otherwise, we're clearly in for a bumpy ride:
-<img src="http://bitcoin.sipa.be/inflation-small.png"></img>
+<img src="bip-0042/inflation.png"></img>
Note that several other programming languages do not exhibit this behaviour, making new implementations likely to be slower and generally more bogus than Bitcoin Core. For example, Python unexpectedly returns 0 when shifting an integer beyond its size.
diff --git a/bip-0042/inflation.png b/bip-0042/inflation.png
new file mode 100644
index 0000000..3ebc254
--- /dev/null
+++ b/bip-0042/inflation.png
Binary files differ