Cosmetics

This commit is contained in:
Piotr Włodarek 2018-01-18 13:00:19 +01:00
parent bafcd591a0
commit e848e0ff24
5 changed files with 7 additions and 9 deletions

View file

@ -1,6 +1,6 @@
# Ed25519 curve # Ed25519 curve
!!! danger !!! note
Author is nowhere close to being a cryptographer. Be sceptical on accuracy. Author is nowhere close to being a cryptographer. Be sceptical on accuracy.
!!! note !!! note

View file

@ -1,6 +1,6 @@
# Asymmetric cryptography in Monero # Asymmetric cryptography in Monero
!!! danger !!! note
Author is nowhere close to being a cryptographer. Be sceptical on accuracy. Author is nowhere close to being a cryptographer. Be sceptical on accuracy.
Before we get to Monero specific stuff, a little bit of context. We are talking asymmetric cryptography here. Before we get to Monero specific stuff, a little bit of context. We are talking asymmetric cryptography here.

View file

@ -1,6 +1,6 @@
# Monero private key image # Monero private key image
!!! danger !!! note
Author is nowhere close to being a cryptographer. Be sceptical on accuracy. Author is nowhere close to being a cryptographer. Be sceptical on accuracy.
Private key image serves to detect double spending attempts. Private key image serves to detect double spending attempts.
@ -8,7 +8,7 @@ Private key image serves to detect double spending attempts.
In Monero funds are always sent to a one-time public key `P`. In Monero funds are always sent to a one-time public key `P`.
Related one-time private key `x` is specific to unspent output. Related one-time private key `x` is specific to unspent output.
As output can be spent only once (in whole), the related private key can be used only once. As output can be spent only once (in whole), the related private key can be used only once as well.
Thus, specific private key image `I` being present on the blockchain means Thus, specific private key image `I` being present on the blockchain means
that related output was already spent, and subsequent attempts must not be allowed. that related output was already spent, and subsequent attempts must not be allowed.
@ -44,3 +44,4 @@ The key image `I` is a one-way function of the private key `x`.
* [StackExchange answer](https://monero.stackexchange.com/questions/2883/what-is-a-key-image) * [StackExchange answer](https://monero.stackexchange.com/questions/2883/what-is-a-key-image)
* [Another SE answer](https://monero.stackexchange.com/questions/2158/what-is-moneros-mechanism-for-defending-against-a-double-spend-attack) * [Another SE answer](https://monero.stackexchange.com/questions/2158/what-is-moneros-mechanism-for-defending-against-a-double-spend-attack)
* [Critical bug](https://getmonero.org/2017/05/17/disclosure-of-a-major-bug-in-cryptonote-based-currencies.html) regarding key image verification that was once present in Monero

View file

@ -1,6 +1,6 @@
# Private keys in Monero # Private keys in Monero
!!! danger !!! note
Author is nowhere close to being a cryptographer. Be sceptical on accuracy. Author is nowhere close to being a cryptographer. Be sceptical on accuracy.
In Monero, the root private key is generated [randomly](/cryptography/prng). Other private keys are derived deterministically from the root private key. In Monero, the root private key is generated [randomly](/cryptography/prng). Other private keys are derived deterministically from the root private key.

View file

@ -1,11 +1,8 @@
# Public keys in Monero # Public keys in Monero
!!! danger !!! note
Author is nowhere close to being a cryptographer. Be sceptical on accuracy. Author is nowhere close to being a cryptographer. Be sceptical on accuracy.
!!! warning
Article is a work in progress.
Public key is deterministically derived from private key based on [Ed25519 curve](/cryptography/asymmetric/ed25519) with a little Monero-specific twist. Public key is deterministically derived from private key based on [Ed25519 curve](/cryptography/asymmetric/ed25519) with a little Monero-specific twist.
Public key is meant to be shared. Assuming correct implementation, it is not practically possible to recover private key from public key. Public key is meant to be shared. Assuming correct implementation, it is not practically possible to recover private key from public key.