summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoss Nicoll <jrn@jrn.me.uk>2014-04-26 16:25:22 +0100
committerRoss Nicoll <jrn@jrn.me.uk>2014-04-26 16:25:22 +0100
commit22646636dd79518691a5ba5ed51bc35a84d11d49 (patch)
treea20146ba523bc9c816e33754f6ff6a6d34b69cdf
parente196a4a7d0171d499fa496078526b7479db22d18 (diff)
downloadbips-22646636dd79518691a5ba5ed51bc35a84d11d49.tar.xz
Replaced example domain name with example.com.
-rw-r--r--bip-0070.mediawiki2
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0070.mediawiki b/bip-0070.mediawiki
index 3e861db..1ee56bd 100644
--- a/bip-0070.mediawiki
+++ b/bip-0070.mediawiki
@@ -25,7 +25,7 @@ The current, minimal Bitcoin payment protocol operates as follows:
This BIP extends the above protocol to support several new features:
-# Human-readable, secure payment destinations-- customers will be asked to authorize payment to "website.com" instead of an inscrutable, 34-character bitcoin address.
+# Human-readable, secure payment destinations-- customers will be asked to authorize payment to "example.com" instead of an inscrutable, 34-character bitcoin address.
# Secure proof of payment, which the customer can use in case of a dispute with the merchant.
# Resistance from man-in-the-middle attacks that replace a merchant's bitcoin address with an attacker's address before a transaction is authorized with a hardware wallet.
# Payment received messages, so the customer knows immediately that the merchant has received, and has processed (or is processing) their payment.