diff --git a/docs/cryptography/asymmetric/ed25519.md b/docs/cryptography/asymmetric/ed25519.md index 4f86dfe..6e856ed 100644 --- a/docs/cryptography/asymmetric/ed25519.md +++ b/docs/cryptography/asymmetric/ed25519.md @@ -1,6 +1,6 @@ # Ed25519 curve -!!! danger +!!! note Author is nowhere close to being a cryptographer. Be sceptical on accuracy. !!! note diff --git a/docs/cryptography/asymmetric/introduction.md b/docs/cryptography/asymmetric/introduction.md index 010e53a..f48c4d2 100644 --- a/docs/cryptography/asymmetric/introduction.md +++ b/docs/cryptography/asymmetric/introduction.md @@ -1,6 +1,6 @@ # Asymmetric cryptography in Monero -!!! danger +!!! note 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. diff --git a/docs/cryptography/asymmetric/key-image.md b/docs/cryptography/asymmetric/key-image.md index 3cd4524..825594f 100644 --- a/docs/cryptography/asymmetric/key-image.md +++ b/docs/cryptography/asymmetric/key-image.md @@ -1,6 +1,6 @@ # Monero private key image -!!! danger +!!! note Author is nowhere close to being a cryptographer. Be sceptical on accuracy. 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`. 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 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) * [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 diff --git a/docs/cryptography/asymmetric/private-key.md b/docs/cryptography/asymmetric/private-key.md index 5e6c71e..39cc734 100644 --- a/docs/cryptography/asymmetric/private-key.md +++ b/docs/cryptography/asymmetric/private-key.md @@ -1,6 +1,6 @@ # Private keys in Monero -!!! danger +!!! note 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. diff --git a/docs/cryptography/asymmetric/public-key.md b/docs/cryptography/asymmetric/public-key.md index be8dd60..7065b3e 100644 --- a/docs/cryptography/asymmetric/public-key.md +++ b/docs/cryptography/asymmetric/public-key.md @@ -1,11 +1,8 @@ # Public keys in Monero -!!! danger +!!! note 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 meant to be shared. Assuming correct implementation, it is not practically possible to recover private key from public key.