<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Le 16/07/2017 à 18:10, Ron Garret a
écrit :<br>
</div>
<blockquote
cite="mid:D7BFBF75-5F2E-4953-B885-276AB9A4CDC7@flownet.com"
type="cite">
<pre wrap="">The attack model is not that someone counterfeits a coin ab initio. The attack model is that someone <b class="moz-txt-star"><span class="moz-txt-tag">*</span>copies<span class="moz-txt-tag">*</span></b> a <b class="moz-txt-star"><span class="moz-txt-tag">*</span>legitimate<span class="moz-txt-tag">*</span></b> already-issued coin and circulates the copy <b class="moz-txt-star"><span class="moz-txt-tag">*</span>instead<span class="moz-txt-tag">*</span></b> of the original legitimate coin.
</pre>
</blockquote>
<br>
Hi Ron, thanks for your reply. If the coin is not counterfeited ab
initio, then it contains wallet's the private key, and not "SUCKER".
The only way to get a coin with "SUCKER" instead of the wallet's
private key is to get a counterfeited coin, but all the purpose of
the technology is about detecting these counterfeited coins, so it
can't happen, unless there are bugs in the protocol, that's why I
ask for help for reviewing it. There are some weaknesses, with
proposed fixes and workarounds, I'd like to find better fixes, or
other bugs to fix.<br>
<br>
Thanks again,<br>
<br>
Camille.<br>
<br>
<blockquote
cite="mid:D7BFBF75-5F2E-4953-B885-276AB9A4CDC7@flownet.com"
type="cite">
<pre wrap="">
rg</pre>
</blockquote>
<p><br>
</p>
</body>
</html>