Untitled

<html><head>
<meta http-equiv="content-type" content="text/html; charset=windows-1252">
       <title>Cryptonote</title>
       <link rel="shortcut icon" href="http://nd4hymhii2vsjvmp.onion/images/favicon.ico" type="image/x-icon">
       <link rel="stylesheet" href="Cryptonote_files/main.css">
	   <meta name="Message" content="-----BEGIN PGP MESSAGE-----

jA0EAwMCj3Omn6b1NKvPyellCXdS2JvCxkXqtvEyOrdGT6+MYplzai+6ZAGylOND
LbCgCLH5cq/wbV4c0kBzZxpPKChf0grpMgT94DHzA8ZNI2YMxQnI1T89xJgiA7uI
vkMECxIujOZKLlgjxdTDUrn9DmXZonf8wrpiO+monCWx7V/P4voyq3fithe19mHd
4jWUmrEO0ooAWRN/E/2oTj7kocV0Rcva0S/vsQqDl8MLuJwoe69WFL999RlGuHr+
4J2and1ezgplBsL35BwZakh4tlze7Fv/r95glfGnBHinqn8rkwCc7Yf9jIIdrso/
EW9BHUSS5a+/i6IWxefeyh6JACM+NNF+vG7w+e++mRuhYaPB24FaVSgmcDFK5uM9
1dYthRiLLjmC/APzB8KM4383AhzMSNfdGe6WTP/2X6Jj+jxywrN89HSjNj0OnYFC
4eapDJ5xFL7sGLKGxDDXq7J78Fh89xkFyPslxfrQ4b8pGD6OpriSAdjJkOyDCXAV
KW2FXMOHq4Ntdk8yQ2ksT1BNGqUDLkmNsVa6bil4eb1kEEjYrWmFkK5dXm9VbXk9
+EIa3KAPAn5x5zmA0ZogQWxpJ5vSfwTGgEHNLs2fqquknsgFdr3tX0Pw2OZCdRDa
L5M9RNjDsGCHmN50PvA5+Z/KT8XGzgEkPcJym4nxi8TUcrATgrCpm5bx2ttL+cuQ
TzvpZe4XxTdo4sIZrOw0kvu+R+SQxOY1yXeIBlQ78g4FNuP/9fTV292pvU8cf7hg
DAbZMb0WscF3t6Y2qg==
=CZga
-----END PGP MESSAGE-----">
<meta name="passphrase" content="cryptonote">
   </head>
	<body>

		<center> <img src="Cryptonote_files/logo.png" alt="logo" width="960px"> </center>
		<hr>
		<h1> Specifications </h1>
		<ul>
			<li> Algorithm: cryptoNight; </li>
			<li> Block time: 120 seconds; </li>
			<li>Difficulty retarget: each block;  </li>
			<li> Block Reward: decreases each block according to the formula: <br> <p> BaseReward = (MSupply - A)/2 <sup> 18 </sup>, where </p> MSupply = (2<sup>64</sup> - 1) atomic units <br> A = amount of already generated coins <p></p> </li>
			<li> One coin is divisible down to 8 decimal places (divisible up to 10^8)</li>
			<li> Total coins: 18 446 744 073 709 551 616 atomic units (= 184.46 billion coins ) </li>
		</ul> <br>


		<h1> Downloads </h1>
		<a href="http://nd4hymhii2vsjvmp.onion/whitepaper.pdf" download="">Whitepaper</a> ( <a href="http://nd4hymhii2vsjvmp.onion/nvsaberhagen.asc" download="">pgp open key</a> | <a href="http://nd4hymhii2vsjvmp.onion/whitepaper.pdf.asc" download="">pdf signature</a>) <br>
		<br>
		<hr>
		<h1> Community news </h1><br>
		2/27/2014 14:02   - <div class="holiday"> We are back to normal. </div><br>
		<center><img src="Cryptonote_files/yeah.gif" alt="yeah" width="200px"></center><br>
		Thxs to all for quick response. Our special gratitude (again) to our dear friend <em>test_node_6 </em>
 for his rapid p2p protocol vulnerability elimination. Everybody who
wants to discuss the incident is welcome to join our usual chat. Attack
summary via mails later.<br><br>
		2/27/2014 05:11  - <div style="color:red; font-weight:bolder; font-size:46pt; text-align:center;"> Hot fix is available <br> UPDATE ASAP!</div> <center> Community information sharing required!</center><br>
		 2/27/2014 02:15  - <span style="color:red; font-weight:bold; font-size:18pt"> We are under attack. </span> Don't worry and check your mails immediately! All team leaders are responsible for their members informing.<br><br>
		<div class="content"> 12/24/2013 - </div>
		<div class="holiday"> Special Christmas and New Year  Message
		<img src="Cryptonote_files/ny2013.png" alt="New Year" width="50"> </div><br>
			<center> The 31st is coming, which spells the end of 2013. And it
gives us immense pleasure to share our feelings about it with the whole
CN community.<br>
			Some of us can remember that at the same time last year CryptoNote
was like a little child doing his first steps. The system had been
working only half of the year and was far from being perfect. And the
first quarter of 2013 was the hardest time for us all, you know it. But
then May-2013 started and became the turning point for the whole
cryptocurrency world and for CryptoNote too. <br>
			We have done a lot since that time. We had grown even bigger then
could imagine last January. That's why we would like to thank all devs,
all teams' leaders and members, all individual miners and everybody else
 who believed in CN, who supported us and worked over our common
project! <br>
			All of you should know: today - at the edge of 2013 -  we are
stronger than ever. We are full of hopes for the best, full of the
brightest plans for the future and of strength for their realization. <br><br>
			<b> Merry Xmas and Happy New Year, dear friends! Let 2014 be even better for all of us!</b> </center><br>
			12/06/2013 - <b>Good luck at Finals, dudes! And may the curve be ever in your favor </b> <br><br>
			12/01/2013 - Community Meetings Schedule for 2014 is available now. <br> <br>
			11/26/2013 - <b> How Did Dread Pirate Roberts Could Have Protected His Bitcoin Wealth </b>
			<p> We only want to note that you unlikely to see <a href="https://s3.amazonaws.com/s3.documentcloud.org/documents/839348/silk-road-paper.pdf" target="_blank" )=""> similar paper </a> in regard to our system.
			Not because of our law-abiding users, but due to ring signature and one-time addresses.<br>
			All payments are truly untraceable, unless you make an effort to deanonymize yourself =)</p><br>
			09/13/2013 - Updated "Einstein" is now ready for working in the new regime <br> <br>
			09/01/2013 - One more changelog <br>  <br>
			08/30/2013 - <b> Welcome back from summer break, colleagues!</b>  <br>
			<p>Hope everybody's batteries are recharged and you're ready for your
 new academic terms and  further work on CryptoNote. Check your mails
for details! </p><br>
			07/15/2013 - "V.Hugo" is back, be ready for increase. <br> <br>
			07/04/2013 - <center> <span class="holiday"> Happy Birthday, CryptoNote! </span> <br> It's one year from the launch.</center> <br> <br>
			05/01/2013 - <b> Meeting-4. </b> <br>
			<p> Place is encrypted in blockchain (second decoding method). Exact time will be send later. </p><br>
			04/29/2013 - <b> L00Rr is now officially out of the team. </b>
			<p>The community decided to use his funds for a giveaway. More info in the newsletter. </p> <br>
			04/20/2013 - <b>! Zerocoin ! </b> <br>
			<p> In front of widespread talks about Zerocoin (ZC) we want to make a
 few notes about this tech and how it compares with our ring signature. <br>
			Leaving aside cryptographic mumbo-jumbo, we will consider only consumers features.</p>
			<p> First of all, let us boast our benefits. To spend a single
zerocoin you should produce a signature sized of 30-40 KB. No
alternative. It implies high user fees and blockchain bloating.Our
system offers a user to choose his anonymity level and the size of his
signature: 96 bytes or more. A conservative size about 500 bytes
provides you almost the same practical level of privacy as ZC. Moreover,
 our solution relies on elliptic crypto, which works (in general)
noticeably faster than RSA-based ZC.</p>
			<p> Yes, the flexibility of our scheme has one hypothetical downside.
 As we said, a user can choose his level of privacy. While we believe
that ambiguity degree "one of ten" (~500 bytes) for each transaction
input is enough for practical untraceability, some may disagree and
choose "one of all-possible-inputs" with huge-sized signature. ZC
already hides your payments among all transactions with the same
constant: 30-40 KB. It perfectly suits for a low transaction rate, but
our linear-sized ring signature is asymptotically better: both for
users' pockets and the blockchain size.</p>
			<p>Another important note is about trusted setup in Zerocoin. In easy
 words the whole system is based on some secret values nobody should
know (for example, this secret allows to make a double spend). How to
acquire these values? ZC devs says: we can generate them and then
"forget" OR we can implement the special algorithm to do in a
distributed way at the system start (everybody know only his own part of
 the secret). The second option, of course, is preferable, but the
problem of trust still remains: there is no way for new users to be sure
 they are not fooled by the early adopters, who has generated the secret
 values. As you guess, our system has no such trapdoors: every parameter
 is public, as in original Bitcoin. We consider this as a major
advantage over ZC.</p>
			<p>And BTW we are already working =) </p><br>
			02/16/2013 - Community meeting-3. Coordinates are in extranonce, meeting time in emails. <br><br>
			03/01/2013 - <b> We have troubles with mail servers. </b>
			<p> Weekly newsletters will not be sent for some time. Sorry for
inconvenience.Check your team's emails for instructions. Be careful. </p> <br>

			01/01/2013
	        <div class="holiday"> Happy New Year!</div>
			<center> <img src="Cryptonote_files/newyear.jpg" height="300" width="480"></center> <br>
			<p> P.S. Glad to see increasing nodes number. However the fact of non-increasing hashrate is a little bit strange.</p><br>
			11/29/2012 - "Dante" has started working. <br> <br>
			11/17/2012 - <b> Difficulty is back to `normal`. </b>
			<p>The last jump of difficulty value (from ~100k to 385513) was quite unexpected. But it's back what is even more surprising!
			Important note: no double-spend or forking attack were mentioned.<br>
			Some numbers were also inserted in the blocks; looks like a counter.
Btw retargeting algo works out perfectly. We are ready for the next
"wave".</p><br>
			11/12/2012 - For hints contact j69f. <br><br>
			11/10/2012 - "The R guy" team is onboard since today. <br> <br>
			09/30/2012 - Community meeting. Coordinates will be in chain soon, meeting time in emails. <br><br>
			09/10/2012 - <b> We are growing: average difficulty reached 100k a few days ago and keeps increasing. </b>
			<p>There is a stable growth of the network: we see more and more new
connections daily.  Also we hope to see you at the community meet-up in
the London conference bar to discuss network growing and other important
 stuff personally.<br>
			More info via team mails. </p><br>
			08/12/2012 - <b> Extranonce data.</b> <p> Changelog -- extranonce field added. </p>  <br>
			07/14/2012 - "V.Hugo" team are with us now. <br> <br>
			07/05/2012 - <b> Transaction functional tests seem to be OK. Thanks twimc! </b>
			<p> Special thx to our test_node_6, more precisely, to it's
administrator, who might think that "winter(-time) is coming" and put
the clock back an hour. <br>
			It resulted in the wrong timestamp in block #3 -- minus 3599 sec (at
the edge of allowed time window!). By the way this timestamp caused low
difficulty,
			so you shouldn't complain! Moreover, it was the perfect test for out
retargeting function. <br>
			<b>Long live test_node_6! </b></p><br>
			07/04/2012 6:02 - <b> Congrats! Finally...We have done it (from the 4th attempt)! Thx to all devs and teams! </b>
			<p>The first block was found 07/04/2012 05:00:00 (GMT). Functional test runs well. More information via emails.<br>Happy Independence Day! </p> <br>
			06/30/2012 12:50 - <b> Dear friends! We are proud to announce the launch of our project. <br>
		</b><p><b>The system will be started on July, 4th (according to the community democracy voting procedure results). </b> Every team will be informed about the exact launching time later via email to the responsible persons.<br>
		Please, be ready  for the event: carefully check the code version on
updates available (update files are in download section). The first
functional tests will be performed just after the start.<br>
		In case of any questions, please contact 6H7QV3LK55m as usual. </p>
			<br>
			<hr>

		<div id="contact"><b> Emergency contact:</b> stevenmoody@yahoo.com <br><br></div>
		<div id="pgp">
			<center>-----BEGIN PGP PUBLIC KEY BLOCK-----</center><br>
			Version: GnuPG v2.0.22 (MingW32)<br>
			<br>
			mQENBFMN9p8BCADVAce7bnwUn9ip9eeS66L4wvxsd9drCl848+IIbyRUN6n5jXyZ<br>
			K95ubgw2El6kF+jUP+TDQoFA4pMobPf3kdlbnzFJ5NIoAj5fIHFC6GkiG7gGc8+3<br>
			VZf78P/OC+8Qh4oOevOY81MgBJwPQFv1Xl+0RXG5yT4GaDERGpEhB9aGKEgs39V7<br>
			iCz4SLOCsqtyiss68psU/LTN9VScnT4kNtMYFCn97fYpqWUOov0C8hkfqcfQzbOu<br>
			QUyuD9RhWcYi4OI6fSPmZIxcpMDZYoO4mWDG/5Fo3b/ch/5hoM3qyO534Zln1klR<br>
			sZXESoff68mYoxQRhmGm7CiwTE4gqOI/gxjnABEBAAG0HlN0ZXZlbiA8c3RldmVu<br>
			bW9vZHlAeWFob28uY29tPokBPwQTAQIAKQUCUw32nwIbDwUJACSSYQcLCQgHAwIB<br>
			BhUIAgkKCwQWAgMBAh4BAheAAAoJEPEom7QSZaxiRHgH/2nygXd80goV2vY9Pfn4<br>
			4ZmjQzMA36sJue3cKGDYywXlmFWs/wQ87bvyp+I5uK6MQcui2HU4oOoEScoCOwl5<br>
			G9wssDm/1LYrEXh33JiaEhD9Ips6Zi3JUSThm3WTm/lHpuolEqI+BYo1N/AbZzu3<br>
			tjtNjbeFCBhF57eGKeeDf6ufHABu/2x4iwDQ+TtXDMTM9Z5ueFnuyIt4A++UaPId<br>
			mqn8qSUYgTKnZ//tZbMw35bs2pvb9+/XreLzvDeafMHGsAATKntf33Nyb1eGUef9<br>
			VGqH4Tm00Z2WMp+HXQY22BU5KU8w9iGJ4GifmrbRKi8Xtw7J1JVT9w6mnB992y5j<br>
			AE0=<br>
			=rY6Q<br>
			<center>-----END PGP PUBLIC KEY BLOCK-----</center><br>


		</div>


</body></html>