CryptoNight - Revision history

Luke-jr: corrections

2014-06-19T18:43:32Z

corrections

← Older revision		Revision as of 18:43, 19 June 2014
Line 2:		Line 2:
	It is designed to be suitable for ordinary PC CPUs, but currently no special purpose devices for mining are available.		It is designed to be suitable for ordinary PC CPUs, but currently no special purpose devices for mining are available.
	Therefore, CryptoNight can only be CPU-mined for the time being.		Therefore, CryptoNight can only be CPU-mined for the time being.
	CryptoNight is the ~~main~~ CryptoNote~~'s hash function~~.		CryptoNight was originally implemented in the [[CryptoNote]] codebase.

	== Principles ==		== Principles ==

Name at 16:10, 19 June 2014

2014-06-19T16:10:47Z

← Older revision		Revision as of 16:10, 19 June 2014
Line 2:		Line 2:
	It is designed to be suitable for ordinary PC CPUs, but currently no special purpose devices for mining are available.		It is designed to be suitable for ordinary PC CPUs, but currently no special purpose devices for mining are available.
	Therefore, CryptoNight can only be CPU-mined for the time being.		Therefore, CryptoNight can only be CPU-mined for the time being.
	CryptoNight is the main CryptoNote's hash-function.		CryptoNight is the main CryptoNote's hash function.

	== Principles ==		== Principles ==

Name at 16:08, 19 June 2014

2014-06-19T16:08:27Z

← Older revision		Revision as of 16:08, 19 June 2014
Line 2:		Line 2:
	It is designed to be suitable for ordinary PC CPUs, but currently no special purpose devices for mining are available.		It is designed to be suitable for ordinary PC CPUs, but currently no special purpose devices for mining are available.
	Therefore, CryptoNight can only be CPU-mined for the time being.		Therefore, CryptoNight can only be CPU-mined for the time being.
			CryptoNight is the main CryptoNote's hash-function.

	== Principles ==		== Principles ==

Luke-jr: Altcoins are off-topic

2014-06-12T05:34:15Z

Altcoins are off-topic

← Older revision		Revision as of 05:34, 12 June 2014
Line 1:		Line 1:
	CryptoNight is ~~the~~ proof-of-work algorithm ~~used in [[CryptoNote]] and [[Bytecoin\|Bytecoin (BCN)]]~~. It is designed to be ~~egalitarian, being~~ suitable for ordinary PC CPUs, ~~and~~ currently no special purpose devices for mining are available. Therefore, ~~the currencies based on~~ CryptoNight ~~are~~ CPU-mined for the time being.		CryptoNight is a proof-of-work algorithm.
			It is designed to be suitable for ordinary PC CPUs, but currently no special purpose devices for mining are available.
			Therefore, CryptoNight can only be CPU-mined for the time being.

	== Principles ==		== Principles ==
Line 9:		Line 11:
	# GPUs may run hundreds of concurrent instances, but they are limited in other ways. GDDR5 memory is slower than the CPU L3 cache and remarkable for its bandwidth, not random access speed.		# GPUs may run hundreds of concurrent instances, but they are limited in other ways. GDDR5 memory is slower than the CPU L3 cache and remarkable for its bandwidth, not random access speed.
	# Significant expansion of the scratchpad would require an increase in iterations, which in turn implies an overall time increase. "Heavy" calls in a trustless p2p network may lead to serious vulnerabilities, because nodes are obliged to check every new block's proof-of-work. If a node spends a considerable amount of time on each hash evaluation, it can be easily DDoSed by a flood of fake objects with arbitrary work data (nonce values).		# Significant expansion of the scratchpad would require an increase in iterations, which in turn implies an overall time increase. "Heavy" calls in a trustless p2p network may lead to serious vulnerabilities, because nodes are obliged to check every new block's proof-of-work. If a node spends a considerable amount of time on each hash evaluation, it can be easily DDoSed by a flood of fake objects with arbitrary work data (nonce values).


	~~== See Also ==~~

	* [[Bytecoin]]
	* [[CryptoNote]]

	== External Links ==		== External Links ==
Line 20:		Line 16:
	* [https://cryptonote.org/inside.php#equal-proof-of-work CryptoNight on CryptoNote's website]		* [https://cryptonote.org/inside.php#equal-proof-of-work CryptoNight on CryptoNote's website]



	~~[[Category:Alternative cryptocurrencies]]~~
	[[Category:Digital currencies]]		[[Category:Digital currencies]]
	[[Category:Technical]]		[[Category:Technical]]

Lapp0 at 18:29, 11 June 2014

2014-06-11T18:29:00Z

← Older revision		Revision as of 18:29, 11 June 2014
Line 1:		Line 1:
	CryptoNight is the proof-of-work algorithm used in [[CryptoNote]] and [[Bytecoin\|Bytecoin (BCN)]]. It is designed to be egalitarian, being suitable for ordinary PC CPUs, ~~but not the~~ special purpose devices for mining. Therefore, the currencies based on CryptoNight are CPU-mined ~~only~~.		CryptoNight is the proof-of-work algorithm used in [[CryptoNote]] and [[Bytecoin\|Bytecoin (BCN)]]. It is designed to be egalitarian, being suitable for ordinary PC CPUs, and currently no special purpose devices for mining are available. Therefore, the currencies based on CryptoNight are CPU-mined for the time being.

	== Principles ==		== Principles ==

Volka at 12:24, 18 April 2014

2014-04-18T12:24:23Z

← Older revision		Revision as of 12:24, 18 April 2014
Line 19:		Line 19:

	* [https://cryptonote.org/inside.php#equal-proof-of-work CryptoNight on CryptoNote's website]		* [https://cryptonote.org/inside.php#equal-proof-of-work CryptoNight on CryptoNote's website]
	* [https://en.bitcoin.it/wiki/CryptoNight]

Volka at 12:23, 18 April 2014

2014-04-18T12:23:00Z

← Older revision		Revision as of 12:23, 18 April 2014
Line 19:		Line 19:

	* [https://cryptonote.org/inside.php#equal-proof-of-work CryptoNight on CryptoNote's website]		* [https://cryptonote.org/inside.php#equal-proof-of-work CryptoNight on CryptoNote's website]
			* [https://en.bitcoin.it/wiki/CryptoNight]

Name at 16:07, 17 April 2014

2014-04-17T16:07:55Z

← Older revision		Revision as of 16:07, 17 April 2014
Line 10:		Line 10:
	# Significant expansion of the scratchpad would require an increase in iterations, which in turn implies an overall time increase. "Heavy" calls in a trustless p2p network may lead to serious vulnerabilities, because nodes are obliged to check every new block's proof-of-work. If a node spends a considerable amount of time on each hash evaluation, it can be easily DDoSed by a flood of fake objects with arbitrary work data (nonce values).		# Significant expansion of the scratchpad would require an increase in iterations, which in turn implies an overall time increase. "Heavy" calls in a trustless p2p network may lead to serious vulnerabilities, because nodes are obliged to check every new block's proof-of-work. If a node spends a considerable amount of time on each hash evaluation, it can be easily DDoSed by a flood of fake objects with arbitrary work data (nonce values).

	CryptoNote was created with the state-of-the-art cryptography with sufficient security level for the next decades. Schnorr signatures and 256-bit ECC keys (the basis for EdDSA) are very strong cryptos, which have passed the test of times. It has been implemented in various systems (not only ours). There have been tons of papers with analysis and researches on that top. I can't say the same applies to pairing-based cryptography or NTRU.
	== See Also ==		== See Also ==

Name at 16:07, 17 April 2014

2014-04-17T16:07:39Z

← Older revision		Revision as of 16:07, 17 April 2014
Line 10:		Line 10:
	# Significant expansion of the scratchpad would require an increase in iterations, which in turn implies an overall time increase. "Heavy" calls in a trustless p2p network may lead to serious vulnerabilities, because nodes are obliged to check every new block's proof-of-work. If a node spends a considerable amount of time on each hash evaluation, it can be easily DDoSed by a flood of fake objects with arbitrary work data (nonce values).		# Significant expansion of the scratchpad would require an increase in iterations, which in turn implies an overall time increase. "Heavy" calls in a trustless p2p network may lead to serious vulnerabilities, because nodes are obliged to check every new block's proof-of-work. If a node spends a considerable amount of time on each hash evaluation, it can be easily DDoSed by a flood of fake objects with arbitrary work data (nonce values).

			CryptoNote was created with the state-of-the-art cryptography with sufficient security level for the next decades. Schnorr signatures and 256-bit ECC keys (the basis for EdDSA) are very strong cryptos, which have passed the test of times. It has been implemented in various systems (not only ours). There have been tons of papers with analysis and researches on that top. I can't say the same applies to pairing-based cryptography or NTRU.
	== See Also ==		== See Also ==

Godwin at 09:19, 15 April 2014

2014-04-15T09:19:51Z

← Older revision		Revision as of 09:19, 15 April 2014
Line 22:		Line 22:
	[[Category:Alternative cryptocurrencies]]		[[Category:Alternative cryptocurrencies]]
	[[Category:Digital currencies]]		[[Category:Digital currencies]]
			[[Category:Technical]]