From 70f7edb1fedabd6563c90e55be4f954ae31ddb7c Mon Sep 17 00:00:00 2001 From: nadams Date: Wed, 17 May 2017 09:17:16 -0700 Subject: [PATCH] Edited ch04.asciidoc with Atlas code editor --- ch04.asciidoc | 1 - 1 file changed, 1 deletion(-) diff --git a/ch04.asciidoc b/ch04.asciidoc index 108d2fbc..68eb4594 100644 --- a/ch04.asciidoc +++ b/ch04.asciidoc @@ -766,7 +766,6 @@ Eugenia could advertise a randomly generated address (e.g., +1J7mdg5rbQyUHENYdx3 In both cases, one of the risks of using a single fixed address (rather than a separate dynamic address per donor) is that a thief might be able to infiltrate your website and replace it with his own address, thereby diverting donations to himself. If you have advertised your donation address in a number of different places, your users may visually inspect the address before making a payment to ensure it is the same one they saw on your website, on your email, and on your flyer. In the case of a random address like +1J7mdg5rbQyUHENYdx39WVWK7fsLpEoXZy+, the average user will perhaps inspect the first few characters "1J7mdg" and be satisfied that the address matches. Using a vanity address generator, someone with the intent to steal by substituting a similar-looking address can quickly generate addresses that match the first few characters, as shown in <>. [[table_4-13]] -[role="pagebreak-before"] .Generating vanity addresses to match a random address |======= | *Original Random Address* | 1J7mdg5rbQyUHENYdx39WVWK7fsLpEoXZy