4c1e8dd858
+ correction on Italian Account + Removed leftover miners.md (replaced by mining.md) + Removed Dust and update Copyright + Code improvement to avoid reading the config file and to use the builtin jekyll config variable passed in the content + Ammount.md:25/26 glitch "\@transaction-privacy" corrected. PL to be checked twice. + Italian ammount.md moneropedia links corrected (terms added to destination entries, unnecessary markdown links removed) + Polish corrections + extend ruby \word-boundary in regex to match `-based` `-like` `-form` + Updated readme according to the new way to add or translate a moneropedia entry + fix mining with CryptoNight variant + rebased to include AR + chery picked #820 to avoid conflicts
1.0 KiB
| entry | terms | summary | ||
|---|---|---|---|---|
| View Key |
|
one of two sets of private and public cryptographic keys that each account has, with the private view key required to view all transactions related to the account |
{% include untranslated.html %}
The Basics
One of two sets of private and public cryptographic keys that each account has, with the private view key required to view all transactions related to the account.
Monero features an opaque blockchain (with an explicit allowance system called the @view-key), in sharp contrast with transparent blockchains used by any other cryptocurrency not based on CryptoNote. Thus, Monero is said to be "private, optionally transparent".
Every Monero address has a private viewkey which can be shared. By sharing a viewkey, a person is allowing access to view every incoming transaction for that address. However, outgoing transactions cannot be reliably viewed as of June 2017. Therefore, the balance of a Monero address as shown via a viewkey should not be relied upon.