mirror of
https://github.com/monero-project/monero-site.git
synced 2025-01-18 23:53:42 +02:00
Moneropedia relocalized
+ 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
This commit is contained in:
parent
20512711d7
commit
4c1e8dd858
93
README.md
93
README.md
@ -136,14 +136,14 @@ And you will increment the version number in the following way:
|
||||
## 4.0 How to make a blog post
|
||||
|
||||
### 4.1 Quick Start
|
||||
* Make new .md file in _posts (named whatever, no spaces)
|
||||
* Make new .md file in \_posts (named whatever, no spaces)
|
||||
* Front Matter (below)
|
||||
* Write Blog Post
|
||||
* Test/Build
|
||||
* Submit PR
|
||||
|
||||
### 4.2 Make a file
|
||||
Navigate to the _posts folder of the website and make a new file. Be sure the file name has no spaces and the ending is .md
|
||||
Navigate to the \_posts folder of the website and make a new file. Be sure the file name has no spaces and the ending is .md
|
||||
|
||||
### 4.3 Front Matter
|
||||
```
|
||||
@ -171,12 +171,12 @@ You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure
|
||||
|
||||
* Create file in /resources/user-guides with an .md ending and no spaces in filename.
|
||||
* File content as in 5.3
|
||||
* Create file in /_i18n/en/resources/user-guides with the exact same filename as above ending in .md
|
||||
* Create file in /\_i18n/en/resources/user-guides with the exact same filename as above ending in .md
|
||||
* Write User Guide
|
||||
* Add versioning snippet
|
||||
* Copy User Guide file to ALL LANGUAGES in /_i18n/[ALL LANGUAGES]/resources/user-guides
|
||||
* Copy User Guide file to ALL LANGUAGES in /\_i18n/[ALL LANGUAGES]/resources/user-guides
|
||||
* set translation to false in the snippet the top of each language version of your User Guide, except the original language
|
||||
* Add guide using markdown in the correct category, and in alphabetic order, in ALL LANGUAGES to /_i18n/[ALL LANGUAGES]/resources/user-guides/index.md being careful not to mess with any indentation
|
||||
* Add guide using markdown in the correct category, and in alphabetic order, in ALL LANGUAGES to /\_i18n/[ALL LANGUAGES]/resources/user-guides/index.md being careful not to mess with any indentation
|
||||
* Test/Build
|
||||
* Submit PR
|
||||
|
||||
@ -222,7 +222,7 @@ As you paste into each folder, open up the file and edit the snippet at the top
|
||||
`{% include disclaimer.html translated="false" version=page.version %}`. This does not need to be done in the original language that the User Guide was written in.
|
||||
|
||||
### 5.7 Add Guide to the 'User Guide' landing page of EACH LANGUAGE
|
||||
In the /_i18n/[ORIGINAL LANGUAGE OF USER GUIDE]/resources/user-guides folder, find the file labeled index.md and open it.
|
||||
In the /\_i18n/[ORIGINAL LANGUAGE OF USER GUIDE]/resources/user-guides folder, find the file labeled index.md and open it.
|
||||
|
||||
DO NOT CHANGE ANYTHING IN THIS DOCUMENT BESIDES WHAT YOU ARE INSTRUCTED TO.
|
||||
|
||||
@ -242,28 +242,57 @@ You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure
|
||||
|
||||
## 6.0 How to make a Moneropedia Entry
|
||||
|
||||
### 6.1 Make a file
|
||||
### 6.1 Make a Global file
|
||||
Navigate to the /resources/moneropedia folder and make a new file. Be sure the file name has no spaces and the ending is .md
|
||||
|
||||
### 6.2 Front Matter
|
||||
Fil this file with this exact content:
|
||||
```
|
||||
---
|
||||
layout: moneropedia
|
||||
---
|
||||
|
||||
@moneropedia_article
|
||||
|
||||
{% t global.lang_tag %}
|
||||
{% tf resources/moneropedia/account.md %}
|
||||
|
||||
```
|
||||
|
||||
### 6.2 Make the localized File
|
||||
Navigate to the /\_i18n/en/resources/moneropedia folder and make a new file. give it the same <name>.md than in previous step.
|
||||
Start the file with the front Matter:
|
||||
```
|
||||
---
|
||||
entry: "PUT THE NAME OF THE TERM HERE IN QUOTE, THIS IS HOW IT WILL SHOW UP ON THE LANDING PAGE"
|
||||
terms: ["PUT", "TERMS", "HERE", "EXPLAINED", "BELOW"]
|
||||
summary: "PUT SUMMARY OF YOUR ENTRY HERE IN QUOTES"
|
||||
---
|
||||
```
|
||||
|
||||
There is one thing to highlight. The `terms:` section of the front matter can be filled with as many terms as you would like. This is how other Moneropedia entries will link to this page. You can link to other Moneropedia entries as well in your page by putting an ampersand before the term used, i.e. `@THE-TERM-USED`. This will make an automatic link in the Moneropedia entry to the referred term, replace the @term with the word used in that terms `entry:` area of the front matter, and on hover it will show the summary. How cool is that?
|
||||
There is two thing to highlight:
|
||||
The `terms:` section of the front matter can be filled with as many terms as you would like. This is how other Moneropedia entries will link to this page. You can link to other Moneropedia entries as well in your page by putting an ampersand before the term used, i.e. `@THE-TERM-USED`. This will make an automatic link in the Moneropedia entry to the referred term, replace the @term with the word used in that terms `entry:` area of the front matter, and on hover it will show the summary. How cool is that?
|
||||
The lines must not contains trailing whitespace, and it must be no blank lines added, otherwise the site with not build correctly.
|
||||
|
||||
### 6.3 Write
|
||||
Write your Moneropedia entry. Remember that you can link to other Moneropedia entries using `@term-used-in-entry` as described above. Just go to the .md file of the Moneropedia entry you want to link to and use any of the terms in the `terms:` field of the front matter. Be sure to write whichever one you choose EXACTLY as shown and preceded by an ampersand.
|
||||
|
||||
### 6.4 Build/Test
|
||||
### 6.4 Copy to other languages
|
||||
Copy the file from the /\_i18n/en/resources/moneropedia folder to the other /\_i18n/<language>/resources/moneropedia folders and add the untranslated snippet at the same time just after the front matter, so it looks like:
|
||||
```
|
||||
---
|
||||
entry: "PUT THE NAME OF THE TERM HERE IN QUOTE, THIS IS HOW IT WILL SHOW UP ON THE LANDING PAGE"
|
||||
terms: ["PUT", "TERMS", "HERE", "EXPLAINED", "BELOW"]
|
||||
summary: "PUT SUMMARY OF YOUR ENTRY HERE IN QUOTES"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
```
|
||||
|
||||
If you want to translate in your native language, go to the 14.3.2 section below to read about specificities.
|
||||
|
||||
### 6.5 Build/Test
|
||||
Build your website using `jekyll serve` if it's not rebuilding automatically and test check the link to your entry is appearing on the alphabetical list of Moneropedia entries and that it leads to your entry when clicked. Test your Moneropedia entry in the browser and contact rehrar if there are any bugs.
|
||||
|
||||
### 6.5 Submit Pull Request
|
||||
### 6.6 Submit Pull Request
|
||||
You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
|
||||
|
||||
## 7.0 How to make a FFS Proposal
|
||||
@ -302,7 +331,7 @@ The layout will depend on if you are simply presenting an idea that you do not p
|
||||
|
||||
### 7.4 Editing the .yml file
|
||||
|
||||
Navigate to the /_data folder and open the file titled `ffs.yml`. In this file you will find a long list of FFS proposals.
|
||||
Navigate to the /\_data folder and open the file titled `ffs.yml`. In this file you will find a long list of FFS proposals.
|
||||
|
||||
**DO NOT MESS WITH THE FORMATTING OR INDENTATION OF ANYTHING OR JEKYLL WILL NOT BUILD PROPERLY!**
|
||||
|
||||
@ -497,7 +526,7 @@ Now inside the label tag you're going to find where it says 'CHANGE QUESTION' an
|
||||
|
||||
Lastly, find the words 'CHANGE ANSWER' and change it to the answer of your question.
|
||||
|
||||
**DO NOT MESS WITH THE INDENTATION HERE. The div that has `markdown=1` MUST be flush with the left side, the answer to the question must start flush with the left side, and the `</div>` MUST be flush with the left side. **
|
||||
**DO NOT MESS WITH THE INDENTATION HERE. The div that has `markdown=1` MUST be flush with the left side, the answer to the question must start flush with the left side, and the `</div>` MUST be flush with the left side.**
|
||||
|
||||
### 12.2 Build/Test
|
||||
Build your website using `jekyll serve` if it's not rebuilding automatically. If the build is successful, go to the FAQ page `/get-started/faq/` and check to see that your question is showing up and, when clicked, the answer drops down. If not, check to make sure that the `id="tab-CHANGETHIS"` in the input and the `for="CHANGETHIS"` in the label are identical to each other. Test the page and let rehrar know if there are any bugs.
|
||||
@ -566,6 +595,34 @@ Go to the /i18n folder and find the two letter code for the language you wish to
|
||||
### 14.3 Translate the file
|
||||
Here you can do your translation. Depending on the page, you may have to maneuver around some HTML or markdown. In general, anything between two tags (such as `<p>TRANSLATE THIS</p>`) should be fine. Testing is VERY important, so do NOT skip step 13.4. If during testing, the page appears different from the original English page (besides the translated text of course), you did something wrong and may have to start again.
|
||||
|
||||
#### 14.3.2 Notes for Moneropedia Entries
|
||||
Moneropedia entries have two specificities:
|
||||
|
||||
* The Front Matter:
|
||||
Moneropedia Fron should be translated for both *entry:* and *summary:* elements. However, *terms:* should be extanded with their translation, leaving the English words **untouched**.
|
||||
This is really important for compatibility purposes. With this, if a new guide is added to the site, an English term on the untranslated version of the guide in another language could be linked to the moneropedia article (of the same language).
|
||||
|
||||
* The old *unstranslated* snippet must be removed, therefor the next section 14.4 is irrelevant here.
|
||||
|
||||
Finally, your entry should go from:
|
||||
```
|
||||
---
|
||||
entry: "Entry name in English"
|
||||
terms: ["English", "terms"]
|
||||
summary: "English summary."
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
```
|
||||
To:
|
||||
```
|
||||
---
|
||||
entry: "Translated entry name"
|
||||
terms: ["English", "terms", "translated", "terms"]
|
||||
summary: "Translated summary."
|
||||
---
|
||||
```
|
||||
|
||||
### 14.4 set the 'translated' snippet to true
|
||||
Somewhere on the page (usually the top) should be a snippet that says `{% include disclaimer.html translated="false" version=page.version %}`. Simply change this to `{% include disclaimer.html translated="true" version=page.version %}`. This will remove the orange bar from the bottom saying the page is untranslated.
|
||||
|
||||
@ -580,7 +637,7 @@ You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure
|
||||
## 15.0 How to add a new language
|
||||
Whoo boy, this is the big one. Please follow all directions exactly.
|
||||
|
||||
### 15.1 _config.yml file
|
||||
### 15.1 \_config.yml file
|
||||
Navigate to the root folder of the whole website and find the file labeled `_config.yml`. Open it and find the line that says `languages:`. Add your two letter language code (Google it if you don't know it) in between the brackets after the others already present. You will need to put a comma after the previous last one.
|
||||
|
||||
Example:
|
||||
@ -589,14 +646,14 @@ languages: ["en", "es", "NEW LANG HERE"]
|
||||
```
|
||||
Save and exit the file.
|
||||
|
||||
### 15.2 _data folder
|
||||
### 15.2 \_data folder
|
||||
Navigate to the `_data/lang` folder and copy the `template` folder. Paste it into the same folder and the copy renamed to the two letter language code of the language you will be translated to.
|
||||
**The template folder itself should still be there. It should not be renamed. There should be a new folder in addition to the ones that were already there.**
|
||||
|
||||
Translate the content of the files. Do not touch anything labeled `url`, and in the roadmap.yml ONLY translate the `name:` content.
|
||||
|
||||
### 15.3 _i18n folder
|
||||
Navigate to the _i18n folder and duplicate the en.yml file. Rename the duplicate to the two letter language code of your language with a `.yml` at the end and change all sections marked 'translated: "yes"' to 'translated: "no"'. Change back to 'yes' once you have translated that section. Now duplicate the `en` folder and rename it with the correct language code.
|
||||
### 15.3 \_i18n folder
|
||||
Navigate to the \_i18n folder and duplicate the en.yml file. Rename the duplicate to the two letter language code of your language with a `.yml` at the end and change all sections marked 'translated: "yes"' to 'translated: "no"'. Change back to 'yes' once you have translated that section. Now duplicate the `en` folder and rename it with the correct language code.
|
||||
**The original folder and yml file themselves should still be there. They should not be renamed. There should be a new folder and yml file in addition to the ones that were already there.**
|
||||
|
||||
Enter the .yml file and translate everything there.
|
||||
|
@ -11,6 +11,6 @@ The process of cryptographically computing a mathematical proof for a block, con
|
||||
|
||||
Mining is the distributed process of confirming transactions on the public ledger of all transactions, aka @blockchain. Monero nodes use the blockchain to distinguish legitimate transactions from attempts to re-spend coins that have already been spent elsewhere.
|
||||
|
||||
Monero is powered strictly by Proof of Work. It employs a mining algorithm that has the potential to be efficiently tasked to billions of existing devices (any modern x86 CPU and many GPUs). Monero uses the CryptoNight Proof of Work (PoW) algorithm, which is designed for use in ordinary CPUs and GPUs.
|
||||
Monero is powered strictly by Proof of Work. It employs a mining algorithm that has the potential to be efficiently tasked to billions of existing devices (any modern x86 CPU and many GPUs). Monero uses a variant of CryptoNight Proof of Work (PoW) algorithm, which is designed for use in ordinary CPUs and GPUs.
|
||||
|
||||
The smart mining feature allows transparent CPU mining on the user's computer, far from the de facto centralization of mining farms and pool mining, pursuing Satoshi Nakamoto's original vision of a true P2P currency.
|
||||
|
@ -25,6 +25,7 @@ global:
|
||||
outdatedMax: This page is outdated. We do not recommend using it. Instead, please see the
|
||||
outdatedVersion: english version
|
||||
outdatedMin: This page has been updated since the translation. You can use this version, but it may be incomplete.
|
||||
lang_tag: "@lang_tag_en"
|
||||
|
||||
titles:
|
||||
index: Home
|
||||
@ -529,6 +530,13 @@ library:
|
||||
Quarterly Monero magazine, Q3 2017 edition.<br>
|
||||
In this issue, updates about: development, Monero Research Lab, Kovri, community, Hardware, and Monerujo.
|
||||
|
||||
moneropedia:
|
||||
translated: "yes"
|
||||
add_new_button: Add New Entry
|
||||
add_new_text1: If there is an entry you'd like to modify or be added, please
|
||||
add_new_link: open an issue on this website's Github repository
|
||||
add_new_text2: or submit changes via pull request
|
||||
|
||||
blog:
|
||||
title_1: All
|
||||
title_2: Blog
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: ""
|
||||
terms: ["", ""]
|
||||
summary: ""
|
||||
@ -7,4 +6,4 @@ summary: ""
|
||||
|
||||
### The Basics
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
<Re-write summary here>
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Account"
|
||||
terms: ["account", "accounts", "wallet", "wallets"]
|
||||
summary: "similar in function to a bank account, contains all of your sent and received transactions"
|
||||
@ -23,7 +22,7 @@ This means that individuals can easily create a Monero account for themselves as
|
||||
|
||||
Monero relies heavily on a cryptography principle known as *public/private key cryptography* or *asymmetric cryptography*, which is thoroughly detailed in [this Wikipedia article](https://en.wikipedia.org/wiki/Public-key_cryptography).
|
||||
|
||||
Your account is based on two keys, a @spend-key and a @view-key. The @spend-key is special in that it is the single key required to spend your Monero funds, whereas the @view-key allows you to reveal your @transactions to a third party, for example for auditing or accounting purposes. These keys in your account also play an important role in Monero's @transaction-privacy.
|
||||
Your account is based on two keys, a @spend-key and a @view-key. The @spend-key is special in that it is the single key required to spend your Monero funds, whereas the @view-key allows you to reveal your @transactions to a third party, for example for auditing or accounting purposes. These keys in your account also play an important role in Monero's @transaction's privacy.
|
||||
|
||||
The private keys for both of these must be protected by you in order to retain your account privacy. On the other hand, the public keys are obviously public (they are part of your Monero account address). For normal public/private key cryptography someone could send you a private message by encrypting it with either of your public keys, and you would then be the only one able to decrypt it with your private keys.
|
||||
|
||||
@ -52,7 +51,7 @@ Your wallet has been generated.
|
||||
To start synchronizing with the daemon, use "refresh" command.
|
||||
Use "help" command to see the list of available commands.
|
||||
Always use "exit" command when closing monero-wallet-cli to save your
|
||||
current session's state. Otherwise, you might need to synchronize
|
||||
current session's state. Otherwise, you might need to synchronize
|
||||
your wallet again (your wallet keys are NOT at risk in any case).
|
||||
|
||||
PLEASE NOTE: the following 25 words can be used to recover access to your wallet. Please write them down and store them somewhere safe and secure. Please do not store them in your email or on file storage services outside of your immediate control.
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Address Book"
|
||||
tags: ["kovri"]
|
||||
terms: ["Address-Book"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Address"
|
||||
terms: ["address", "addresses"]
|
||||
summary: "either an alias, such as donate.getmonero.org, or a set of 95 characters starting with a 4"
|
||||
@ -9,9 +8,9 @@ summary: "either an alias, such as donate.getmonero.org, or a set of 95 characte
|
||||
|
||||
When you send Monero to someone you only need one piece of information, and that is their Monero address. A *raw* Monero address is a set of 95 characters starting with a '4'. The Monero donation address, for instance, is <span class="long-term">44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A</span>.
|
||||
|
||||
Because those addresses are long and complex you will often encounter an @OpenAlias address instead. For example, Monero donations can be sent to <span class="long-term">donate@getmonero.org</span> or <span class="long-term">donate.getmonero.org</span>.
|
||||
Because those addresses are long and complex, you will often encounter an @OpenAlias address instead. For example, Monero donations can be sent to <span class="long-term">donate@getmonero.org</span> or <span class="long-term">donate.getmonero.org</span>.
|
||||
|
||||
If you would like to get an @OpenAlias address of your own then there is some information on the [OpenAlias page](/knowledge-base/openalias).
|
||||
If you would like to get an @OpenAlias address of your own then there is some information on the [OpenAlias page](/resources/openalias).
|
||||
|
||||
### Integrated address
|
||||
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Airgap"
|
||||
terms: ["airgap"]
|
||||
summary: "An airgap is a security measure to physically separate a computer or device from all other networks, such as the Internet."
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Atomic Units"
|
||||
terms: ["atomic-units", "atomic-unit"]
|
||||
summary: "Atomic Units refer to the smallest fraction of 1 XMR."
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Base32 address"
|
||||
tags: ["kovri"]
|
||||
terms: ["Base32-address", "Base32-addresses"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Base64 address"
|
||||
tags: ["kovri"]
|
||||
terms: ["Base64-address", "Base64-addresses"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Block"
|
||||
terms: ["block", "blocks"]
|
||||
summary: "a container of transactions, a sequence of which forms a blockchain"
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Blockchain"
|
||||
terms: ["blockchain", "blockchains"]
|
||||
summary: "a distributed ledger of all transactions both past and present, without revealing who the funds came from or went to"
|
||||
@ -7,7 +6,7 @@ summary: "a distributed ledger of all transactions both past and present, withou
|
||||
---
|
||||
|
||||
### The Basics
|
||||
A @blockchain is a distributed database that continuously grows with a record of all of the transactions that have occurred with a given cryptocurrency. This database is often referred to as a ledger because the data contains a large list of transactions that have taken place. In Monero, these transactions are packaged together into 'blocks' every 2 minutes (on average) and all miners and nodes on the network have copies of these blocks.
|
||||
A @blockchain is a distributed database that continuously grows with a record of all of the transactions that have occurred with a given cryptocurrency. This database is often referred to as a ledger because the data contains a large list of transactions that have taken place. In Monero, these transactions are packaged together into 'blocks' every 2 minutes (on average), and all miners and nodes on the network have copies of these blocks.
|
||||
|
||||
### Monero's @Blockchain
|
||||
Unlike Bitcoin and other cryptocurrencies, transactions in the Monero @blockchain do not reveal where funds came from or went to, providing anonymity and making the currency completely @fungible. Additionally, the amounts of all transactions are hidden by @RingCT, a feature of Monero. For auditing or other transparency purposes a user can share a @view-key to prove they control certain amounts of @Moneroj.
|
||||
Unlike Bitcoin and other cryptocurrencies, transactions in the Monero @blockchain do not reveal where funds came from or went to, providing anonymity and making the currency completely @fungible. Additionally, the amounts of all transactions are hidden by @RingCT, a feature of Monero. For auditing or other transparency purposes a user can share a @view-key to prove they control certain amounts of Moneroj.
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Bootstrap-node"
|
||||
terms: ["bootstrap-node", "bootstrap-nodes"]
|
||||
summary: "A node to which a daemon connects to give immediate usability to wallets while syncing"
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Canonically-unique host"
|
||||
tags: ["kovri"]
|
||||
terms: ["Canonically-unique-host"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Change"
|
||||
terms: ["change"]
|
||||
summary: "Monero sent as part of a transaction, that returns to your account instead of going to another recipient"
|
||||
@ -7,10 +6,10 @@ summary: "Monero sent as part of a transaction, that returns to your account ins
|
||||
|
||||
### The Basics
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
Monero sent as part of a transaction, that returns to your account instead of going to another recipient.
|
||||
|
||||
### More Information
|
||||
|
||||
The @wallet in the the Monero software makes change automatically, but when you send a transaction, you are taking an @input that you control and telling the Monero network what to do with it. The @input is a "deposit" to your account that you are able to spend. @Outputs are the part of the transaction that tells the Monero network where to send the funds.
|
||||
The @wallet in the Monero software makes change automatically, but when you send a transaction, you are taking an input that you control and telling the Monero network what to do with it. The input is a "deposit" to your account that you are able to spend. Outputs are the part of the transaction that tells the Monero network where to send the funds.
|
||||
|
||||
You might have multiple inputs in your account, in many different denominations (For example: you deposited 0.5 XMR on Friday, and 0.75 XMR on Saturday). So, when have a transaction with an input of 0.5 XMR, but you only want to send 0.1 XMR, your transaction will include a @fee to pay the @miner, an output for 0.1 XMR to send to the recipient, and the rest that you want to send back to yourself will be an output back to you (this is called "change"). Once the transaction is completed, the change becomes available to you as an input that you can again split and send with a new transaction.
|
||||
You might have multiple inputs in your account, in many different denominations (For example: you deposited 0.5 XMR on Friday, and 0.75 XMR on Saturday). So, when have a transaction with an input of 0.5 XMR, but you only want to send 0.1 XMR, your transaction will include a fee to pay the @miner, an output for 0.1 XMR to send to the recipient, and the rest that you want to send back to yourself will be an output back to you (this is called "change"). Once the transaction is completed, the change becomes available to you as an input that you can again split and send with a new transaction.
|
||||
|
@ -1,14 +1,13 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Clearnet"
|
||||
tags: ["kovri"]
|
||||
terms: ["Clearnet"]
|
||||
summary: "The internet in which anonymous overlay networks are built upon"
|
||||
summary: "The Internet in which anonymous overlay networks are built upon"
|
||||
---
|
||||
|
||||
### The Basics
|
||||
|
||||
When you use the internet for things like news, email, social media, and even Monero, you are most likely using a clearnet connection. This means that *all* of your connections can be tracked, traced, and monitored by:
|
||||
When you use the Internet for things like news, email, social media, and even Monero, you are most likely using a clearnet connection. This means that *all* of your connections can be tracked, traced, and monitored by:
|
||||
|
||||
- your [ISP](https://en.wikipedia.org/wiki/ISP)
|
||||
- the website/service/person you're communicating with
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Coinbase Transaction"
|
||||
terms: ["coinbase-transaction"]
|
||||
summary: "a special type of transaction included in each block, which contains a small amount of Monero sent to the miner as a reward for their mining work"
|
||||
@ -7,4 +6,4 @@ summary: "a special type of transaction included in each block, which contains a
|
||||
|
||||
### The Basics
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
A special type of transaction included in each block, which contains a small amount of Monero sent to the miner as a reward for their mining work.
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Consensus"
|
||||
terms: ["consensus", "consensus-network"]
|
||||
summary: "consensus describes a property of distributed networks like Monero where most of the participants follow the rules, and thus reject bad participants"
|
||||
@ -7,4 +6,4 @@ summary: "consensus describes a property of distributed networks like Monero whe
|
||||
|
||||
### The Basics
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
Consensus describes a property of distributed networks like Monero where most of the participants follow the rules, and thus reject bad participants.
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Cryptocurrency"
|
||||
terms: ["cryptocurrency", "cryptocurrencies", "altcoin", "altcoins"]
|
||||
summary: "a digital currency in which encryption techniques are used to regulate the generation of units of currency and verify the transfer of funds, usually operating independently of a central bank"
|
||||
@ -7,16 +6,16 @@ summary: "a digital currency in which encryption techniques are used to regulate
|
||||
|
||||
### The Basics
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
A digital currency in which encryption techniques are used to regulate the generation of units of currency and verify the transfer of funds, usually operating independently of a central bank.
|
||||
|
||||
### More Information
|
||||
|
||||
Cryptocurrency is the generic term for a large set of digital assets that use encryption techniques to generate units of currency, verify the transactions, and transfer value. Generally, cryptocurrencies are considered to be decentralized. Cryptocurrency should not be confused with virtual currency which is a type of digital money that is usually controlled by it's creators or developers. (Some examples of virtual currency are gametime in World of Warcraft, ROBUX in Roblox, reward points programs, or Ripple, all of which can be exchanged for currency or cash value, but are not considered cryptocurrency because they are centalized and controlled/issued by a single entity).
|
||||
Cryptocurrency is the generic term for a large set of digital assets that use encryption techniques to generate units of currency, verify the transactions, and transfer value. Generally, cryptocurrencies are considered to be decentralized. Cryptocurrency should not be confused with virtual currency which is a type of digital money that is usually controlled by its creators or developers. Some examples of virtual currency are gametime in World of Warcraft, ROBUX in Roblox, reward points programs, or Ripple, all of which can be exchanged for currency or cash value, but are not considered cryptocurrency because they are centalized and controlled/issued by a single entity.
|
||||
|
||||
Monero is one of many cryptocurrencies currently available. Other examples are Bitcoin, Litecoin, Dogecoin, Dash, Zcash, etc, but nearly all other cryptocurrencies lack features that make them a true money (most importantly @fungability which is a requirement for it to be a @store-of-value).
|
||||
Monero is one of many cryptocurrencies currently available. Other examples are Bitcoin, Litecoin, Dogecoin, Dash, Zcash, etc, but nearly all other cryptocurrencies lack features that make them a true money (most importantly @fungibility which is a requirement for it to be a store-of-value).
|
||||
|
||||
Not all cryptocurrencies operate the same, but they usually share the properties of @decentralization, encryption, and the ability to send and receive transactions. Most are irreversible, pseudonymous, global, and permissionless. Most aim to be a @store-of-value or be digital cash that allows you to transact.
|
||||
Not all cryptocurrencies operate the same, but they usually share the properties of decentralization, encryption, and the ability to send and receive transactions. Most are irreversible, pseudonymous, global, and permissionless. Most aim to be a store-of-value or be digital cash that allows you to transact.
|
||||
|
||||
Most cryptocurrencies (including Monero) use a distributed ledger (called a @blockchain) to keep track of previous transactions . The blockchain serves to tell other users on the network that transactions have happened. There are many different ways for cryptocurrencies to create their blockchain, and not all are the same. Monero uses @proof-of-work to craft blocks, where other cryptocurrencies may use proof-of-stake or other consolidated methods.
|
||||
Most cryptocurrencies (including Monero) use a distributed ledger (called a @blockchain) to keep track of previous transactions. The blockchain serves to tell other users on the network that transactions have happened. There are many different ways for cryptocurrencies to create their blockchain, and not all are the same. Monero uses proof-of-work to craft blocks, where other cryptocurrencies may use proof-of-stake or other consolidated methods.
|
||||
|
||||
Ultimately, cryptocurrency is an attempt to create @trustless value; that is free from borders, governments, and banks. Whether that be to transact or to be digital gold is up to the users of each.
|
||||
Ultimately, cryptocurrency is an attempt to create trustless value; that is free from borders, governments, and banks. Whether that be to transact or to be digital gold is up to the users of each.
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Data Directory"
|
||||
tags: ["kovri"]
|
||||
terms: ["Data-Directory"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Denominations"
|
||||
terms: ["denominations", "subunits", "tacoshi", "piconero", "nanonero", "micronero", "millinero", "centinero", "decinero","decanero","hectonero","kilonero","meganero","giganero"]
|
||||
summary: "A denomination is a proper description of a currency amount. It is oftentimes a sub-unit of the currency. For example, traditionally a cent is 1/100th of a particular unit of currency.)"
|
||||
@ -7,7 +6,7 @@ summary: "A denomination is a proper description of a currency amount. It is oft
|
||||
|
||||
### The Basics
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
A denomination is a proper description of a currency amount. It is oftentimes a sub-unit of the currency. For example, traditionally a cent is 1/100th of a particular unit of currency.).
|
||||
|
||||
Monero denomination names add SI prefixes after dropping the initial "mo" for ease of use. Actually, the smallest unit of Monero is 1 piconero (0.000000000001 XMR).
|
||||
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Destination"
|
||||
tags: ["kovri"]
|
||||
terms: ["Destination", "Destinations"]
|
||||
@ -12,7 +11,7 @@ A @destination is the @I2P @in-net address of the final endpoint you are trying
|
||||
|
||||
### In-depth Information
|
||||
|
||||
An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-address or a `.i2p` hostname while, internally, @Kovri / @I2P @address-book uses @base64-addresses. Ultimately, all @destinations in @I2P are 516-byte (or longer) keys:
|
||||
An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-addresses or a `.i2p` hostname while, internally, @Kovri / @I2P @address-book uses @base64-addresses. Ultimately, all @destinations in @I2P are 516-byte (or longer) keys:
|
||||
|
||||
`256-byte public key + 128-byte signing key + a null certificate = 516 bytes in Base64 representation`
|
||||
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Eepsite"
|
||||
tags: ["kovri"]
|
||||
terms: ["Eepsite", "Hidden-Service", "Garlic-Site", "Garlic-Service"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Encryption"
|
||||
tags: ["kovri"]
|
||||
terms: ["encryption", "encrypted", "encrypting", "decryption", "decrypted", "decrypting"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Floodfill"
|
||||
tags: ["kovri"]
|
||||
terms: ["Floodfill"]
|
||||
|
18
_i18n/en/resources/moneropedia/fluffyblocks.md
Normal file
18
_i18n/en/resources/moneropedia/fluffyblocks.md
Normal file
@ -0,0 +1,18 @@
|
||||
---
|
||||
entry: "Fluffy Blocks"
|
||||
terms: ["fluffy blocks", "fluffyblocks"]
|
||||
summary: "a way of saving bandwidth when sending new blocks around the network"
|
||||
---
|
||||
|
||||
### The Basics
|
||||
|
||||
A @block is made up of a header and @transactions. Fluffy Blocks only contain
|
||||
a header, a list of transaction indices, and any transactions that the node
|
||||
recieving the block may be missing. This saves bandwidth because nodes might
|
||||
already know about most or all of the transactions in the block and they don't
|
||||
need to be sent them again.
|
||||
|
||||
### See Also
|
||||
|
||||
* [BIP152 "Compact Block Relay"](https://github.com/bitcoin/bips/blob/master/bip-0152.mediawiki)
|
||||
* [Xthin](https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/release/doc/bu-xthin-protocol.md)
|
@ -1,16 +1,16 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Fungibility"
|
||||
terms: ["fungibility"]
|
||||
terms: ["fungibility", "fungible"]
|
||||
summary: "property of a currency whereby two units can be substituted in place of one another"
|
||||
---
|
||||
|
||||
### The Basics
|
||||
|
||||
Fungibility means that two units of a currency can be mutually substituted and the substituted currency is equal to another unit of the same size. For example, two $10 bills can be exchanged and they are functionally identical to any other $10 bills in circulation (although $10 bills have unique ID numbers and are therefore not completely fungible). Gold is probably a closer example of true fungibility, where any 1 oz. of gold of the same grade is worth the same as another 1 oz of gold. Monero is fungible due to the nature of the currency which provides no way to link transactions together nor trace the history of any particular XMR. 1 XMR is functionally identical to any other 1 XMR.
|
||||
Property of a currency whereby two units can be substituted in place of one another.
|
||||
|
||||
Fungibility is an advantage Monero has over Bitcoin and almost every other cryptocurrency, due to the privacy inherent in the Monero @blockchain and the permanently traceable nature of the Bitcoin blockchain. With Bitcoin, any BTC can be tracked by anyone back to it's creation @coinbase-transaction. Therefore, if a coin has been used for an illegal purpose in the past, this history will be contained in the @blockchain in perpetuity. This lack of fungibility means that certain businesses will be obligated to avoid accepting BTC that have been previously used for purposes which are illegal, or simply run afoul of their Terms of Service. Currently some large Bitcoin companies are blocking, suspending, or closing accounts that have received Bitcoin used in online gambling or other purposes deemed unsavory by said companies.
|
||||
Fungibility means that two units of a currency can be mutually substituted and the substituted currency is equal to another unit of the same size. For example, two $10 bills can be exchanged and they are functionally identical to any other $10 bill in circulation (although $10 bills have unique ID numbers and are therefore not completely fungible). Gold is probably a closer example of true fungibility, where any 1 oz. of gold of the same grade is worth the same as another 1 oz. of gold. Monero is fungible due to the nature of the currency which provides no way to link transactions together nor trace the history of any particular XMR. 1 XMR is functionally identical to any other 1 XMR.
|
||||
|
||||
Monero has been built specifically to address the problem of traceability and non-fungability inherent in other cryptocurrencies. By having completely private transactions Monero is truly fungible and there can be no blacklisting of certain XMR, while at the same time providing all the benefits of a secure, decentralized, permanent blockchain.
|
||||
Fungibility is an advantage Monero has over Bitcoin and almost every other cryptocurrency, due to the privacy inherent in the Monero @blockchain and the permanently traceable nature of the Bitcoin blockchain. With Bitcoin, any BTC can be tracked by anyone back to its creation @coinbase-transaction. Therefore, if a coin has been used for an illegal purpose in the past, this history will be contained in the @blockchain in perpetuity. This lack of fungibility means that certain businesses will be obligated to avoid accepting BTC that have been previously used for purposes which are illegal, or simply run afoul of their Terms of Service. Currently some large Bitcoin companies are blocking, suspending, or closing accounts that have received Bitcoin used in online gambling or other purposes deemed unsavory by said companies.
|
||||
|
||||
Monero has been built specifically to address the problem of traceability and non-fungibility inherent in other cryptocurrencies. By having completely private transactions Monero is truly fungible and there can be no blacklisting of certain XMR, while at the same time providing all the benefits of a secure, decentralized, permanent blockchain.
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Garlic-Encryption"
|
||||
tags: ["kovri"]
|
||||
terms: ["Garlic-Encryption", "Layered-Encryption"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Garlic Routing"
|
||||
tags: ["kovri"]
|
||||
terms: ["Garlic-Routing"]
|
||||
@ -8,7 +7,7 @@ summary: "Routing technology as implemented in Kovri"
|
||||
|
||||
### The Basics
|
||||
|
||||
The term *@garlic-routing* has a diverse history of varying interpretations. As it currently stands, Monero defines *@garlic-routing* as the method in which @Kovri and @I2P create a @message-based anonymous overlay network of internet peers.
|
||||
The term *@garlic-routing* has a diverse history of varying interpretations. As it currently stands, Monero defines *@garlic-routing* as the method in which @Kovri and @I2P create a @message-based anonymous overlay network of Internet peers.
|
||||
|
||||
The @Garlic-Encryption of @Garlic-Routing is similar to the @Layered-Encryption of [Onion Routing](https://en.wikipedia.org/wiki/Onion_routing) and effectively conceals the IP address of the sender and secures information sent from the sender to its @destination (and vice-versa).
|
||||
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "I2NP"
|
||||
tags: ["kovri"]
|
||||
terms: ["I2NP"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "I2P"
|
||||
tags: ["kovri"]
|
||||
terms: ["I2P"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "I2PControl"
|
||||
tags: ["kovri"]
|
||||
terms: ["I2PControl"]
|
||||
@ -8,7 +7,7 @@ summary: "An API inteface for Kovri and Java-I2P that allows simple remote contr
|
||||
|
||||
### The Basics
|
||||
|
||||
@I2Pcontrol is [JSONRPC2](https://en.wikipedia.org/wiki/JSON-RPC) [API](https://en.wikipedia.org/wiki/Application_programming_interface) for @Kovri and @Java-I2P which allows an @I2PControl client to remote control/monitor a running instance.
|
||||
@I2Pcontrol is a [JSONRPC2](https://en.wikipedia.org/wiki/JSON-RPC) [API](https://en.wikipedia.org/wiki/Application_programming_interface) for @Kovri and @Java-I2P which allows an @I2PControl client to remote control/monitor a running instance.
|
||||
|
||||
Two available @I2PControl clients are: [qtoopie](https://github.com/EinMByte/qtoopie) (C++ client) and [itoopie](https://github.com/i2p/i2p.itoopie) (Java client). Read `kovri.conf` to configure @I2PControl for @Kovri.
|
||||
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "In-net"
|
||||
tags: ["kovri"]
|
||||
terms: ["In-net"]
|
||||
|
@ -1,21 +0,0 @@
|
||||
---
|
||||
layout: full
|
||||
title: "Moneropedia"
|
||||
title-pre-kick: "Moneropedia - The "
|
||||
title-kick: "Monero Wiki"
|
||||
title-post-kick: ""
|
||||
kick-class: "softyellow-kicks"
|
||||
icon: "icon_wiki"
|
||||
attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
|
||||
---
|
||||
|
||||
|
||||
<div class="row">
|
||||
|
||||
@moneropedia
|
||||
|
||||
</div>
|
||||
|
||||
<p><a href="https://github.com/monero-project/monero-site/new/master/knowledge-base/moneropedia" class="btn-link btn-auto btn-primary">Add New Entry</a></p>
|
||||
|
||||
If there is an entry you'd like to modify or be added, please [open an issue on this website's Github repository](https://github.com/monero-project/monero-site/issues) or submit changes via pull request.
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Java I2P"
|
||||
tags: ["kovri"]
|
||||
terms: ["Java-I2P"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Jump Service"
|
||||
tags: ["kovri"]
|
||||
terms: ["Jump-Service"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Kovri"
|
||||
tags: ["kovri"]
|
||||
terms: ["Kovri"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Lease-Set"
|
||||
tags: ["kovri"]
|
||||
terms: ["LeaseSet", "LeaseSets"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Lease"
|
||||
tags: ["kovri"]
|
||||
terms: ["Lease", "Leases"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Locally-unique host"
|
||||
tags: ["kovri"]
|
||||
terms: ["Locally-unique-host"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Message"
|
||||
tags: ["kovri"]
|
||||
terms: ["Message", "Messages"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Mining"
|
||||
terms: ["mining", "miner", "miners"]
|
||||
summary: "the process of cryptographically computing a mathematical proof for a block, containing a number of transactions, which is then added to the blockchain"
|
||||
@ -7,14 +6,10 @@ summary: "the process of cryptographically computing a mathematical proof for a
|
||||
|
||||
### The Basics
|
||||
|
||||
Mining is the distributed process of confirming transactions on the public ledger of all transactions, aka @blockchain. Monero nodes use the block chain to distinguish legitimate transactions from attempts to re-spend coins that have already been spent elsewhere.
|
||||
The process of cryptographically computing a mathematical proof for a block, containing a number of transactions, which is then added to the blockchain.
|
||||
|
||||
Monero is powered strictly by Proof of Work. It employs a mining algorithm that has the potential to be efficiently tasked to billions of existing devices (any modern x86 CPU and many GPU's). Monero uses the @CryptoNight Proof of Work (@PoW) algorithm, which is designed for use in ordinary CPUs and GPUs.
|
||||
Mining is the distributed process of confirming transactions on the public ledger of all transactions, aka @blockchain. Monero nodes use the blockchain to distinguish legitimate transactions from attempts to re-spend coins that have already been spent elsewhere.
|
||||
|
||||
The smart mining feature allows transparent CPU mining on the user's computer, far from the de facto centralization of mining farms and pool mining, pursuing Satoshi Nakamoto's original vision of a true P2P currency.
|
||||
Monero is powered strictly by Proof of Work. It employs a mining algorithm that has the potential to be efficiently tasked to billions of existing devices (any modern x86 CPU and many GPUs). Monero uses a variant of CryptoNight Proof of Work (PoW) algorithm, which is designed for use in ordinary CPUs and GPUs.
|
||||
|
||||
As of June 2017, botnets made of hacked computers account for a not-insignificant portion of the miners on the Monero network. This is due to the profitability of mining on CPUs via the @CryptoNight algorithm.
|
||||
|
||||
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
The smart mining feature allows transparent CPU mining on the user's computer, far from the de facto centralization of mining farms and pool mining, pursuing Satoshi Nakamoto's original vision of a true P2P currency.
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Mnemonic Seed"
|
||||
terms: ["mnemonic-seed", "mnemonic"]
|
||||
summary: "a 13 or 25 word phrase used to backup a Monero account, available in a number of languages"
|
||||
@ -7,7 +6,7 @@ summary: "a 13 or 25 word phrase used to backup a Monero account, available in a
|
||||
|
||||
### The Basics
|
||||
|
||||
{{ page.summary | capitalize }}. This 25-word phrase (13 words in the case of MyMonero) has all the information needed to view and spend funds from a Monero @account.
|
||||
A 13 or 25 word phrase used to backup a Monero account, available in a number of languages. This 25-word phrase (13 words in the case of MyMonero) has all the information needed to view and spend funds from a Monero @account.
|
||||
|
||||
### In-depth Information
|
||||
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Network Database"
|
||||
tags: ["kovri"]
|
||||
terms: ["Network-Database"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Node"
|
||||
terms: ["node", "nodes", "full-node", "full-nodes"]
|
||||
summary: "a device on the Internet running the Monero software, with a full copy of the Monero blockchain, actively assisting the Monero network"
|
||||
@ -7,17 +6,17 @@ summary: "a device on the Internet running the Monero software, with a full copy
|
||||
|
||||
### The Basics
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
A device on the Internet running the Monero software, with a full copy of the Monero blockchain, actively assisting the Monero network.
|
||||
|
||||
### More Information
|
||||
|
||||
Nodes participate in the Monero network and secure @transactions by enforcing the rules of the network. Nodes download the entire @blockchain to know what transactions have taken place. Nodes assist the network by relaying transactions to other nodes on the network. Nodes may also choose contribute to the Monero network by participating in crafting @blocks (this is called @mining).
|
||||
Nodes participate in the Monero network and secure @transactions by enforcing the rules of the network. Nodes download the entire @blockchain to know what transactions have taken place. Nodes assist the network by relaying transactions to other nodes on the network. Nodes may also choose to contribute to the Monero network by participating in crafting @blocks (this is called @mining).
|
||||
|
||||
Mining is the process by which nodes create a block from the previously accepted block, transactions that are waiting to be processed in the @tx-pool, and the @coinbase. When a node believes it has crafted a valid block it will transmit the completed block to other nodes on the network and those nodes signal agreement by working on the next block in the chain.
|
||||
Mining is the process by which nodes create a block from the previously accepted block, transactions that are waiting to be processed in the transaction pool, and the @coinbase-transaction. When a node believes it has crafted a valid block it will transmit the completed block to other nodes on the network and those nodes signal agreement by working on the next block in the chain.
|
||||
|
||||
The rules that nodes follow are built into the Monero software; When all nodes agree about the rules to follow this is called @consensus). Consensus is necessary for a cryptocurrency because it is how the blockchain is built; If nodes don't agree about which blocks are valid, for example people who have not updated their Monero software, those nodes that don't agree will no longer be able to participate in the Monero network.
|
||||
The rules that nodes follow are built into the Monero software; When all nodes agree about the rules to follow this is called @consensus. Consensus is necessary for a cryptocurrency because it is how the blockchain is built; If nodes don't agree about which blocks are valid, for example people who have not updated their Monero software, those nodes that don't agree will no longer be able to participate in the Monero network.
|
||||
|
||||
The Monero Core Team plans for a @hardforks every 6 months, to occur in September and March of each year. At that time, if you are running a node it must be updated to the most recent version of the Monero software or it will no longer be able to participate in the network.
|
||||
The Monero Core Team plans for a hardfork every 6 months, to occur in September and March of each year. At that time, if you are running a node it must be updated to the most recent version of the Monero software or it will no longer be able to participate in the network.
|
||||
|
||||
---
|
||||
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "NTCP"
|
||||
tags: ["kovri"]
|
||||
terms: ["NTCP"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "OpenAlias"
|
||||
terms: ["OpenAlias"]
|
||||
summary: "a standard that allows you to use an email or domain syntax to pay someone instead of an address, eg. donate@getmonero.org or donate.getmonero.org"
|
||||
@ -15,6 +14,6 @@ As part of the ongoing development of the Monero cryptocurrency project, we aske
|
||||
|
||||
At its most basic, OpenAlias is a TXT DNS record on a FQDN (fully qualified domain name). By combining this with DNS-related technologies we have created an aliasing standard that is extensible for developers, intuitive and familiar for users, and can interoperate with both centralized and decentralized domain systems.
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
A standard that allows you to use an email or domain syntax to pay someone instead of an address, eg. donate@getmonero.org or donate.getmonero.org.
|
||||
|
||||
More information can be found on the [OpenAlias page](/knowledge-base/openalias) or on the [OpenAlias website](https://openalias.org)
|
||||
More information can be found on the [OpenAlias page](/resources/openalias) or on the [OpenAlias website](https://openalias.org)
|
||||
|
@ -1,7 +1,9 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Paper Wallet"
|
||||
terms: ["paperwallet", "paperwallets", "paper-wallet", "paper-wallets"]
|
||||
summary: "A paper wallet stores the information necessary to send and receive Monero"
|
||||
---
|
||||
|
||||
### The Basics
|
||||
|
||||
A paper wallet stores the information necessary to send and receive Monero.
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Payment ID"
|
||||
terms: ["payment-ID", "payment-IDs"]
|
||||
summary: "an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters"
|
||||
@ -11,15 +10,17 @@ Payment ID is an **arbitrary** and **optional** transaction attachment that cons
|
||||
|
||||
The Payment ID is usually used to identify transactions to merchants and exchanges: Given the intrinsic privacy features built into Monero, where a single public address is usually used for incoming transactions, the Payment ID is especially useful to tie incoming payments with user accounts.
|
||||
|
||||
### Compact Payment ID's and Integrated Addresses
|
||||
### Compact Payment IDs and Integrated Addresses
|
||||
|
||||
Since the 0.9 Hydrogen Helix version, the Payment IDs can be encrypted and embedded in a payment address. The payment ID's of this type should be 64-bits and are encrypted with a random one-time key known only to the sender and receiver.
|
||||
Since the 0.9 Hydrogen Helix version, Payment IDs can be encrypted and embedded in a payment address. The Payment IDs of this type should be 64-bits and are encrypted with a random one-time key known only to the sender and receiver.
|
||||
|
||||
### Creating a Payment ID
|
||||
It is recommended to use the official wallet's `integrated_address` command to automatically generate Integrated Addresses that contain Compact Payment ID's. If you want to use the command line, you can generate Payment ID's as follows:
|
||||
It is recommended to use the official wallet's `integrated_address` command to automatically generate Integrated Addresses that contain Compact Payment IDs. If you want to use the command line, you can generate Payment IDs as follows:
|
||||
|
||||
Creating a compact Payment ID for an Integrated Address:
|
||||
|
||||
```# openssl rand -hex 8```
|
||||
|
||||
Creating an old-style Payment ID:
|
||||
|
||||
```# openssl rand -hex 32```
|
||||
|
@ -1,12 +1,13 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Pedersen Commitment"
|
||||
terms: ["commitments", "commitment", "pedersen"]
|
||||
summary: "Pedersen commitments are cryptographic algorythms that allow a prover to commit to a certain value without revealing it or being able to change it."
|
||||
summary: "Pedersen commitments are cryptographic algorythms that allow a prover to commit to a certain value without revealing it or being able to change it"
|
||||
---
|
||||
|
||||
### The Basics
|
||||
|
||||
Pedersen commitments are cryptographic algorythms that allow a prover to commit to a certain value without revealing it or being able to change it.
|
||||
|
||||
When you spend Monero, the value of the inputs that you are spending and the value of the outputs you are sending are encrypted and opaque to everyone except the recipient of each of those outputs. Pedersen commitments allow you to send Monero without revealing the value of the transactions. Pedersen commitments also make it possible for people to verify that transactions on the blockchain are valid and not creating Monero out of thin air.
|
||||
|
||||
### What It Means
|
||||
@ -15,10 +16,8 @@ As long as the encrypted output amounts created, which include an output for the
|
||||
|
||||
Pedersen commitments mean that the sums can be verified as being equal, but the Monero value of each of the sums and the Monero value of the inputs and outputs individually are undeterminable. Pedersen commitments also mean that even the ratio of one input to another, or one output to another is undeterminable.
|
||||
|
||||
Even though it's unclear which inputs are really being spent (the ring signature lists both the real inputs being spent and decoy inputs therefore you don't actually know which input Pedersen commitments you need to sum) that's okay, because the RingCT ring signature only has to prove is that for one combination of the inputs the outputs are equal to the sum of the inputs. For mathematical reasons, this is impossible to forge.
|
||||
It is unclear which inputs are really being spent as the ring signature lists both the real inputs being spent and decoy inputs, therefore you don't actually know which input Pedersen commitments need to be summed. That's okay, because the @RingCT ring signature only has to prove that for one combination of the inputs the outputs are equal to the sum of the inputs. For mathematical reasons, this is impossible to forge.
|
||||
|
||||
### In-depth Information
|
||||
|
||||
See information in [Ring Confidential Transactions paper](https://eprint.iacr.org/2015/1098.pdf) by Shen Noether of the Monero Research Lab.
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Reseed"
|
||||
tags: ["kovri"]
|
||||
terms: ["Reseed"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Ring Size"
|
||||
terms: ["ring-size"]
|
||||
summary: "total number of possible signers in a ring signature"
|
||||
|
@ -1,24 +1,14 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Ring CT"
|
||||
terms: ["ringCT", "ring-CT"]
|
||||
summary: "a way to hide the amount sent in a Monero transaction"
|
||||
---
|
||||
|
||||
### The Basics
|
||||
RingCT, short for Ring Confidential Transactions, is how transaction amounts are hidden in Monero.
|
||||
RingCT, short for Ring Confidential Transactions, is how transaction amounts are hidden in Monero.
|
||||
|
||||
Ring CT was implemented in block #1220516 in January 2017. After September 2017, this feature became mandatory for all transactions on the network.
|
||||
|
||||
RingCT introduces an improved version of @ring-signatures called A Multi-layered Linkable Spontaneous Anonymous Group signature, which allows for hidden amounts, origins and destinations of transactions with reasonable efficiency and verifiable, trustless coin generation.
|
||||
RingCT introduces an improved version of @ring-signatures called "A Multi-layered Linkable Spontaneous Anonymous Group signature", which allows for hidden amounts, origins and destinations of transactions with reasonable efficiency and verifiable, trustless coin generation.
|
||||
|
||||
For more information, please read the creator Shen Noether's paper [here](https://eprint.iacr.org/2015/1098).
|
||||
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Ring Signature"
|
||||
terms: ["ring-signature", "ring-signatures"]
|
||||
summary: "a group of cryptographic signatures with at least one real participant, but no way to tell which in the group is the real one as they all appear valid"
|
||||
@ -13,6 +12,6 @@ For instance, a ring signature could be used to provide an anonymous signature f
|
||||
|
||||
### Application to Monero
|
||||
|
||||
A ring signature makes use of your @account keys and a number of public keys (also known as outputs) pulled from the @blockchain using a triangular distribution method. Over the course of time, past outputs could be used multiple times to form possible signer participants. In a "ring" of possible signers, all ring members are equal and valid. There is no way an outside observer can tell which of the possible signers in a signature group belongs to your @account. So, ring signatures ensure that transaction outputs are untraceable. Moreover, there are no fungibility issues with Monero given that every transaction output has plausible deniability (e.g. the network can not tell which outputs are spent or unspent).
|
||||
A ring signature makes use of your @account keys and a number of public keys (also known as outputs) pulled from the @blockchain using a triangular distribution method. Over the course of time, past outputs could be used multiple times to form possible signer participants. In a "ring" of possible signers, all ring members are equal and valid. There is no way an outside observer can tell which of the possible signers in a signature group belongs to your @account. So, ring signatures ensure that transaction outputs are untraceable. Moreover, there are no @fungibility issues with Monero given that every transaction output has plausible deniability (e.g. the network can not tell which outputs are spent or unspent).
|
||||
|
||||
To read how Monero gives you privacy by default (unlinkability), see @stealth-addresses.
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Router-Info"
|
||||
tags: ["kovri"]
|
||||
terms: ["Router-Info", "Router-infos"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Scalability"
|
||||
terms: ["scalability"]
|
||||
summary: "Growth potential of Monero, resources required, and methods of increasing efficiency"
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Cryptographic Signature"
|
||||
terms: ["signature", "signatures"]
|
||||
summary: "a cryptographic method for proving ownership of a piece of information, as well as proving that the information has not been modified after being signed"
|
||||
@ -7,4 +6,4 @@ summary: "a cryptographic method for proving ownership of a piece of information
|
||||
|
||||
### The Basics
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
A cryptographic method for proving ownership of a piece of information, as well as proving that the information has not been modified after being signed.
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Smart Mining"
|
||||
terms: ["smart-mining"]
|
||||
summary: "a process of having a throttled miner mine when it otherwise does not cause drawbacks"
|
||||
@ -7,11 +6,9 @@ summary: "a process of having a throttled miner mine when it otherwise does not
|
||||
|
||||
### The Basics
|
||||
|
||||
Smart mining is the process of having a throttled miner mine when it otherwise does not cause drawbacks.
|
||||
Smart mining is the process of having a throttled @miner mine when it otherwise does not cause drawbacks.
|
||||
Drawbacks include increases heat, slower machine, depleting battery, etc. The intent of smart mining is to increase network security by allowing as many people as possible to let the smart miner on all the time. For this to work, the miner must prove unobtrusive, or it will be turned off, depriving the Monero network from a little bit of security. As such, it is likely that a smart miner will mine slower than a normal miner on the same hardware.
|
||||
|
||||
Smart mining is available in the official CLI and GUI wallet, which are available in the [downloads page](https://getmonero.org/downloads/).
|
||||
|
||||
It is hoped that the relative slowness of a smart miner (especially on low-power machines) will be offset by the large amount of people running a miner for a possible "lottery win", and thus increase the Monero network security by a non trivial amount. The increased hash rate from many different sources helps keep the Monero network decentralized.
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Spend Key"
|
||||
terms: ["spend-key", "spend-keys"]
|
||||
summary: "one of the two pairs of private and public cryptographic keys that each account has, with the *private* spend key used to spend any funds in the account"
|
||||
@ -7,7 +6,7 @@ summary: "one of the two pairs of private and public cryptographic keys that eac
|
||||
|
||||
### The Basics
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
One of the two pairs of private and public cryptographic keys that each account has, with the *private* spend key used to spend any funds in the account.
|
||||
|
||||
### In-depth Information
|
||||
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "SSU"
|
||||
tags: ["kovri"]
|
||||
terms: ["SSU"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Stealth Address"
|
||||
terms: ["stealth-address", "stealth-addresses"]
|
||||
summary: "automatic one-time addresses for every transaction"
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Subscription"
|
||||
tags: ["kovri"]
|
||||
terms: ["Subscription"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Tail Emission"
|
||||
terms: ["Tail-Emission"]
|
||||
summary: "the block reward at the end of the emission curve"
|
||||
@ -11,6 +10,6 @@ Monero block rewards will never drop to zero. Block rewards will gradually drop
|
||||
|
||||
### Why
|
||||
|
||||
Miners need an incentive to mine. Because of the dynamic blocksize, competition between miners will cause fees to decrease. If mining is not profitable due to a high cost and low reward, miners lose their incentive and will stop mining, reducing the security of the network.
|
||||
Miners need an incentive to mine. Because of the dynamic blocksize, competition between @miners will cause fees to decrease. If mining is not profitable due to a high cost and low reward, miners lose their incentive and will stop mining, reducing the security of the network.
|
||||
|
||||
Tail emission ensures that a dynamic block size and fee market can develop.
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Transactions"
|
||||
terms: ["transaction", "transactions"]
|
||||
summary: "a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)"
|
||||
@ -7,7 +6,7 @@ summary: "a cryptographically signed container that details the transfer of Mone
|
||||
|
||||
### The Basics
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
A cryptographically signed container that details the transfer of Monero to a recipient (or recipients).
|
||||
|
||||
The parameters of a transaction contain one or more recipient addresses with corresponding amounts of funds and a @ring-size parameter that specifies the number outputs bound to the transaction. The more outputs that are used, a higher degree of obfuscation is possible, but that comes with a cost. Since a transaction gets larger with more outputs, the transaction fee will be higher.
|
||||
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Transports"
|
||||
tags: ["kovri"]
|
||||
terms: ["Transports", "Transport"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Tunnel"
|
||||
tags: ["kovri"]
|
||||
terms: ["Tunnel", "Tunnels"]
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Transaction Unlock Time"
|
||||
terms: ["unlock-time"]
|
||||
summary: "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
|
||||
@ -7,7 +6,7 @@ summary: "a special transaction where the recipient can only spend the funds aft
|
||||
|
||||
### The Basics
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
A special transaction where the recipient can only spend the funds after a future date, as set by the sender.
|
||||
|
||||
Unlock time allows you to send a transaction to someone, such that they can not spend it until after a certain number of blocks, or until a certain time.
|
||||
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "View Key"
|
||||
terms: ["view-key", "view-keys"]
|
||||
summary: "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"
|
||||
@ -7,10 +6,8 @@ summary: "one of two sets of private and public cryptographic keys that each acc
|
||||
|
||||
### The Basics
|
||||
|
||||
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".
|
||||
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.
|
||||
|
||||
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.
|
||||
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".
|
||||
|
||||
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
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.
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Wallet"
|
||||
terms: ["wallet", "wallets"]
|
||||
summary: "A wallet stores the information necessary to send and receive Monero"
|
||||
@ -11,7 +10,7 @@ A Monero account, or wallet, stores the information necessary to send and receiv
|
||||
|
||||
The term "hot wallet" describes a Monero @account which is connected to the Internet. You can send funds easily but security is much lower than a cold wallet. Never store large amounts of cryptocurrency in a hot wallet!
|
||||
|
||||
A cold wallet is generated on a trusted device or computer via an @airgap. If the device is to be reused, the data storage should be securely overwritten. As soon as a cold wallet is connected to the internet or its mnemonic phrase or @spend-key is entered on an internet-connected device, it's no longer "cold" and should be considered "hot".
|
||||
A cold wallet is generated on a trusted device or computer via an @airgap. If the device is to be reused, the data storage should be securely overwritten. As soon as a cold wallet is connected to the Internet or its mnemonic phrase or @spend-key is entered on an Internet-connected device, it's no longer "cold" and should be considered "hot".
|
||||
|
||||
A Monero @paper-wallet can be generated by downloading the source code of https://moneroaddress.org/. Verify the signature of the code on a trusted airgapped device. Create the wallet and print or store it on the media of your choice.
|
||||
|
||||
|
@ -25,6 +25,7 @@ global:
|
||||
outdatedMax: Esta página no está actualizada. No recomendamos utilizarla. En su lugar, favor de ver la
|
||||
outdatedVersion: versión en inglés
|
||||
outdatedMin: Esta página ha sido actualizada desde la traducción. Puedes utilizar esta versión, pero puede estar incompleta.
|
||||
lang_tag: "@lang_tag_es"
|
||||
|
||||
titles:
|
||||
index: Inicio
|
||||
@ -528,6 +529,13 @@ library:
|
||||
Quarterly Monero magazine, Q3 2017 edition.<br>
|
||||
In this issue, updates about: development, Monero Research Lab, Kovri, community, Hardware, and Monerujo.
|
||||
|
||||
moneropedia:
|
||||
translated: "no"
|
||||
add_new_button: Add New Entry
|
||||
add_new_text1: If there is an entry you'd like to modify or be added, please
|
||||
add_new_link: open an issue on this website's Github repository
|
||||
add_new_text2: or submit changes via pull request
|
||||
|
||||
blog:
|
||||
title_1: All
|
||||
title_2: Blog
|
||||
|
@ -1,10 +1,10 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: ""
|
||||
terms: ["", ""]
|
||||
summary: ""
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
<Re-write summary here>
|
@ -1,10 +1,10 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Account"
|
||||
terms: ["account", "accounts", "wallet", "wallets"]
|
||||
summary: "similar in function to a bank account, contains all of your sent and received transactions"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
Those familiar with Monero's predecessors will be more familiar with the term *wallet* to describe this. In Monero we call this an account, and it is a private account owned and operated by a Monero user.
|
||||
@ -23,7 +23,7 @@ This means that individuals can easily create a Monero account for themselves as
|
||||
|
||||
Monero relies heavily on a cryptography principle known as *public/private key cryptography* or *asymmetric cryptography*, which is thoroughly detailed in [this Wikipedia article](https://en.wikipedia.org/wiki/Public-key_cryptography).
|
||||
|
||||
Your account is based on two keys, a @spend-key and a @view-key. The @spend-key is special in that it is the single key required to spend your Monero funds, whereas the @view-key allows you to reveal your @transactions to a third party, for example for auditing or accounting purposes. These keys in your account also play an important role in Monero's @transaction-privacy.
|
||||
Your account is based on two keys, a @spend-key and a @view-key. The @spend-key is special in that it is the single key required to spend your Monero funds, whereas the @view-key allows you to reveal your @transactions to a third party, for example for auditing or accounting purposes. These keys in your account also play an important role in Monero's @transaction's privacy.
|
||||
|
||||
The private keys for both of these must be protected by you in order to retain your account privacy. On the other hand, the public keys are obviously public (they are part of your Monero account address). For normal public/private key cryptography someone could send you a private message by encrypting it with either of your public keys, and you would then be the only one able to decrypt it with your private keys.
|
||||
|
||||
@ -52,7 +52,7 @@ Your wallet has been generated.
|
||||
To start synchronizing with the daemon, use "refresh" command.
|
||||
Use "help" command to see the list of available commands.
|
||||
Always use "exit" command when closing monero-wallet-cli to save your
|
||||
current session's state. Otherwise, you might need to synchronize
|
||||
current session's state. Otherwise, you might need to synchronize
|
||||
your wallet again (your wallet keys are NOT at risk in any case).
|
||||
|
||||
PLEASE NOTE: the following 25 words can be used to recover access to your wallet. Please write them down and store them somewhere safe and secure. Please do not store them in your email or on file storage services outside of your immediate control.
|
||||
|
@ -1,11 +1,11 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Address Book"
|
||||
tags: ["kovri"]
|
||||
terms: ["Address-Book"]
|
||||
summary: "Allows you to visit I2P websites/services that have the .i2p domain"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
In order to browse @I2P sites or services with @Kovri, you'll need an address book. An address book will allow you to translate @I2P websites/services that use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain) into an address that @I2P network will understand.
|
||||
|
@ -1,17 +1,17 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Address"
|
||||
terms: ["address", "addresses"]
|
||||
summary: "either an alias, such as donate.getmonero.org, or a set of 95 characters starting with a 4"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
When you send Monero to someone you only need one piece of information, and that is their Monero address. A *raw* Monero address is a set of 95 characters starting with a '4'. The Monero donation address, for instance, is <span class="long-term">44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A</span>.
|
||||
|
||||
Because those addresses are long and complex you will often encounter an @OpenAlias address instead. For example, Monero donations can be sent to <span class="long-term">donate@getmonero.org</span> or <span class="long-term">donate.getmonero.org</span>.
|
||||
Because those addresses are long and complex, you will often encounter an @OpenAlias address instead. For example, Monero donations can be sent to <span class="long-term">donate@getmonero.org</span> or <span class="long-term">donate.getmonero.org</span>.
|
||||
|
||||
If you would like to get an @OpenAlias address of your own then there is some information on the [OpenAlias page](/knowledge-base/openalias).
|
||||
If you would like to get an @OpenAlias address of your own then there is some information on the [OpenAlias page](/resources/openalias).
|
||||
|
||||
### Integrated address
|
||||
|
||||
|
@ -1,10 +1,10 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Airgap"
|
||||
terms: ["airgap"]
|
||||
summary: "An airgap is a security measure to physically separate a computer or device from all other networks, such as the Internet."
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
"An air gap, air wall or air gapping is a network security measure employed on one or more computers to ensure that a secure computer network is physically isolated from unsecured networks, such as the public Internet or an unsecured local area network.[2] The name arises from the technique of creating a network that is physically separated (with a conceptual air gap) from all other networks. The air gap may not be completely literal, as networks employing the use of dedicated cryptographic devices that can tunnel packets over untrusted networks while avoiding packet rate or size variation can be considered air gapped, as there is no ability for computers on opposite sides of the gap to communicate."
|
||||
|
@ -1,10 +1,10 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Atomic Units"
|
||||
terms: ["atomic-units", "atomic-unit"]
|
||||
summary: "Atomic Units refer to the smallest fraction of 1 XMR."
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
Atomic Units refer to the smallest fraction of 1 XMR.
|
||||
|
@ -1,11 +1,11 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Base32 address"
|
||||
tags: ["kovri"]
|
||||
terms: ["Base32-address", "Base32-addresses"]
|
||||
summary: "Base32 encoded hash of a Base64 address"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
A Base32 address is a shortened, encoded version of an @I2P address. The Base32 address is the first part in a `.b32.i2p` hostname.
|
||||
|
@ -1,11 +1,11 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Base64 address"
|
||||
tags: ["kovri"]
|
||||
terms: ["Base64-address", "Base64-addresses"]
|
||||
summary: "Base64 encoded I2P destination"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
A @base64-address is a 516-character [Base64 encoded](https://en.wikipedia.org/wiki/Base64) @I2P @destination. @base64-addresses are primarily used for @address-book, @jump-service, and also internally.
|
||||
|
@ -1,10 +1,10 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Block"
|
||||
terms: ["block", "blocks"]
|
||||
summary: "a container of transactions, a sequence of which forms a blockchain"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
A block is a container of @transactions, with a new block being added to the @blockchain once every 2 minutes (see constant `DIFFICULTY_TARGET_V2` defined as 120 seconds), on average.
|
||||
|
@ -1,13 +1,13 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Blockchain"
|
||||
terms: ["blockchain", "blockchains"]
|
||||
summary: "a distributed ledger of all transactions both past and present, without revealing who the funds came from or went to"
|
||||
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
A @blockchain is a distributed database that continuously grows with a record of all of the transactions that have occurred with a given cryptocurrency. This database is often referred to as a ledger because the data contains a large list of transactions that have taken place. In Monero, these transactions are packaged together into 'blocks' every 2 minutes (on average) and all miners and nodes on the network have copies of these blocks.
|
||||
A @blockchain is a distributed database that continuously grows with a record of all of the transactions that have occurred with a given cryptocurrency. This database is often referred to as a ledger because the data contains a large list of transactions that have taken place. In Monero, these transactions are packaged together into 'blocks' every 2 minutes (on average), and all miners and nodes on the network have copies of these blocks.
|
||||
|
||||
### Monero's @Blockchain
|
||||
Unlike Bitcoin and other cryptocurrencies, transactions in the Monero @blockchain do not reveal where funds came from or went to, providing anonymity and making the currency completely @fungible. Additionally, the amounts of all transactions are hidden by @RingCT, a feature of Monero. For auditing or other transparency purposes a user can share a @view-key to prove they control certain amounts of @Moneroj.
|
||||
Unlike Bitcoin and other cryptocurrencies, transactions in the Monero @blockchain do not reveal where funds came from or went to, providing anonymity and making the currency completely @fungible. Additionally, the amounts of all transactions are hidden by @RingCT, a feature of Monero. For auditing or other transparency purposes a user can share a @view-key to prove they control certain amounts of Moneroj.
|
||||
|
@ -1,10 +1,10 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Bootstrap-node"
|
||||
terms: ["bootstrap-node", "bootstrap-nodes"]
|
||||
summary: "A node to which a daemon connects to give immediate usability to wallets while syncing"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
The daemon running on a local @node has to sync with other (remote) @nodes. While it is not fully synced, @wallet may still be connected to the local node. Therefore, the @wallet cannot access the @blocks that are bot yet synced on the local @node.
|
||||
|
@ -1,11 +1,11 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Canonically-unique host"
|
||||
tags: ["kovri"]
|
||||
terms: ["Canonically-unique-host"]
|
||||
summary: "A host that is canonically resolved to an address or set of addresses"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
A Canonically-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) that will canonically resolve to a designated address or set of addresses. Not to be confused with a @locally-unique-host.
|
||||
|
@ -1,16 +1,16 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Change"
|
||||
terms: ["change"]
|
||||
summary: "Monero sent as part of a transaction, that returns to your account instead of going to another recipient"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
Monero sent as part of a transaction, that returns to your account instead of going to another recipient.
|
||||
|
||||
### More Information
|
||||
|
||||
The @wallet in the the Monero software makes change automatically, but when you send a transaction, you are taking an @input that you control and telling the Monero network what to do with it. The @input is a "deposit" to your account that you are able to spend. @Outputs are the part of the transaction that tells the Monero network where to send the funds.
|
||||
The @wallet in the Monero software makes change automatically, but when you send a transaction, you are taking an input that you control and telling the Monero network what to do with it. The input is a "deposit" to your account that you are able to spend. Outputs are the part of the transaction that tells the Monero network where to send the funds.
|
||||
|
||||
You might have multiple inputs in your account, in many different denominations (For example: you deposited 0.5 XMR on Friday, and 0.75 XMR on Saturday). So, when have a transaction with an input of 0.5 XMR, but you only want to send 0.1 XMR, your transaction will include a @fee to pay the @miner, an output for 0.1 XMR to send to the recipient, and the rest that you want to send back to yourself will be an output back to you (this is called "change"). Once the transaction is completed, the change becomes available to you as an input that you can again split and send with a new transaction.
|
||||
You might have multiple inputs in your account, in many different denominations (For example: you deposited 0.5 XMR on Friday, and 0.75 XMR on Saturday). So, when have a transaction with an input of 0.5 XMR, but you only want to send 0.1 XMR, your transaction will include a fee to pay the @miner, an output for 0.1 XMR to send to the recipient, and the rest that you want to send back to yourself will be an output back to you (this is called "change"). Once the transaction is completed, the change becomes available to you as an input that you can again split and send with a new transaction.
|
||||
|
@ -1,14 +1,14 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Clearnet"
|
||||
tags: ["kovri"]
|
||||
terms: ["Clearnet"]
|
||||
summary: "The internet in which anonymous overlay networks are built upon"
|
||||
summary: "The Internet in which anonymous overlay networks are built upon"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
When you use the internet for things like news, email, social media, and even Monero, you are most likely using a clearnet connection. This means that *all* of your connections can be tracked, traced, and monitored by:
|
||||
When you use the Internet for things like news, email, social media, and even Monero, you are most likely using a clearnet connection. This means that *all* of your connections can be tracked, traced, and monitored by:
|
||||
|
||||
- your [ISP](https://en.wikipedia.org/wiki/ISP)
|
||||
- the website/service/person you're communicating with
|
||||
|
@ -1,10 +1,10 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Coinbase Transaction"
|
||||
terms: ["coinbase-transaction"]
|
||||
summary: "a special type of transaction included in each block, which contains a small amount of Monero sent to the miner as a reward for their mining work"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
A special type of transaction included in each block, which contains a small amount of Monero sent to the miner as a reward for their mining work.
|
@ -1,10 +1,10 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Consensus"
|
||||
terms: ["consensus", "consensus-network"]
|
||||
summary: "consensus describes a property of distributed networks like Monero where most of the participants follow the rules, and thus reject bad participants"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
Consensus describes a property of distributed networks like Monero where most of the participants follow the rules, and thus reject bad participants.
|
@ -1,22 +1,22 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Cryptocurrency"
|
||||
terms: ["cryptocurrency", "cryptocurrencies", "altcoin", "altcoins"]
|
||||
summary: "a digital currency in which encryption techniques are used to regulate the generation of units of currency and verify the transfer of funds, usually operating independently of a central bank"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
A digital currency in which encryption techniques are used to regulate the generation of units of currency and verify the transfer of funds, usually operating independently of a central bank.
|
||||
|
||||
### More Information
|
||||
|
||||
Cryptocurrency is the generic term for a large set of digital assets that use encryption techniques to generate units of currency, verify the transactions, and transfer value. Generally, cryptocurrencies are considered to be decentralized. Cryptocurrency should not be confused with virtual currency which is a type of digital money that is usually controlled by it's creators or developers. (Some examples of virtual currency are gametime in World of Warcraft, ROBUX in Roblox, reward points programs, or Ripple, all of which can be exchanged for currency or cash value, but are not considered cryptocurrency because they are centalized and controlled/issued by a single entity).
|
||||
Cryptocurrency is the generic term for a large set of digital assets that use encryption techniques to generate units of currency, verify the transactions, and transfer value. Generally, cryptocurrencies are considered to be decentralized. Cryptocurrency should not be confused with virtual currency which is a type of digital money that is usually controlled by its creators or developers. Some examples of virtual currency are gametime in World of Warcraft, ROBUX in Roblox, reward points programs, or Ripple, all of which can be exchanged for currency or cash value, but are not considered cryptocurrency because they are centalized and controlled/issued by a single entity.
|
||||
|
||||
Monero is one of many cryptocurrencies currently available. Other examples are Bitcoin, Litecoin, Dogecoin, Dash, Zcash, etc, but nearly all other cryptocurrencies lack features that make them a true money (most importantly @fungability which is a requirement for it to be a @store-of-value).
|
||||
Monero is one of many cryptocurrencies currently available. Other examples are Bitcoin, Litecoin, Dogecoin, Dash, Zcash, etc, but nearly all other cryptocurrencies lack features that make them a true money (most importantly @fungibility which is a requirement for it to be a store-of-value).
|
||||
|
||||
Not all cryptocurrencies operate the same, but they usually share the properties of @decentralization, encryption, and the ability to send and receive transactions. Most are irreversible, pseudonymous, global, and permissionless. Most aim to be a @store-of-value or be digital cash that allows you to transact.
|
||||
Not all cryptocurrencies operate the same, but they usually share the properties of decentralization, encryption, and the ability to send and receive transactions. Most are irreversible, pseudonymous, global, and permissionless. Most aim to be a store-of-value or be digital cash that allows you to transact.
|
||||
|
||||
Most cryptocurrencies (including Monero) use a distributed ledger (called a @blockchain) to keep track of previous transactions . The blockchain serves to tell other users on the network that transactions have happened. There are many different ways for cryptocurrencies to create their blockchain, and not all are the same. Monero uses @proof-of-work to craft blocks, where other cryptocurrencies may use proof-of-stake or other consolidated methods.
|
||||
Most cryptocurrencies (including Monero) use a distributed ledger (called a @blockchain) to keep track of previous transactions. The blockchain serves to tell other users on the network that transactions have happened. There are many different ways for cryptocurrencies to create their blockchain, and not all are the same. Monero uses proof-of-work to craft blocks, where other cryptocurrencies may use proof-of-stake or other consolidated methods.
|
||||
|
||||
Ultimately, cryptocurrency is an attempt to create @trustless value; that is free from borders, governments, and banks. Whether that be to transact or to be digital gold is up to the users of each.
|
||||
Ultimately, cryptocurrency is an attempt to create trustless value; that is free from borders, governments, and banks. Whether that be to transact or to be digital gold is up to the users of each.
|
||||
|
@ -1,11 +1,11 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Data Directory"
|
||||
tags: ["kovri"]
|
||||
terms: ["Data-Directory"]
|
||||
summary: "Where essential kovri data for runtime is stored"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
Depending on your OS, @Kovri currently stores all run-time data in the following directory:
|
||||
|
@ -1,13 +1,13 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Denominations"
|
||||
terms: ["denominations", "subunits", "tacoshi", "piconero", "nanonero", "micronero", "millinero", "centinero", "decinero","decanero","hectonero","kilonero","meganero","giganero"]
|
||||
summary: "A denomination is a proper description of a currency amount. It is oftentimes a sub-unit of the currency. For example, traditionally a cent is 1/100th of a particular unit of currency.)"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
A denomination is a proper description of a currency amount. It is oftentimes a sub-unit of the currency. For example, traditionally a cent is 1/100th of a particular unit of currency.).
|
||||
|
||||
Monero denomination names add SI prefixes after dropping the initial "mo" for ease of use. Actually, the smallest unit of Monero is 1 piconero (0.000000000001 XMR).
|
||||
|
||||
|
@ -1,18 +1,18 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Destination"
|
||||
tags: ["kovri"]
|
||||
terms: ["Destination", "Destinations"]
|
||||
summary: "A in-net address that serves as a final endpoint (either local or remote)"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
A @destination is the @I2P @in-net address of the final endpoint you are trying to connect to (example: an @I2P website, service, or Monero node). This can also include a *local destination* of which *other* peers need to connect to in order to make contact for communication (similar to how, in @clearnet, your IP address is given to a website when you connect so it knows *where* to send the information back to).
|
||||
|
||||
### In-depth Information
|
||||
|
||||
An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-address or a `.i2p` hostname while, internally, @Kovri / @I2P @address-book uses @base64-addresses. Ultimately, all @destinations in @I2P are 516-byte (or longer) keys:
|
||||
An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-addresses or a `.i2p` hostname while, internally, @Kovri / @I2P @address-book uses @base64-addresses. Ultimately, all @destinations in @I2P are 516-byte (or longer) keys:
|
||||
|
||||
`256-byte public key + 128-byte signing key + a null certificate = 516 bytes in Base64 representation`
|
||||
|
||||
|
@ -1,11 +1,11 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Eepsite"
|
||||
tags: ["kovri"]
|
||||
terms: ["Eepsite", "Hidden-Service", "Garlic-Site", "Garlic-Service"]
|
||||
summary: "A website or service hosted within the I2P network"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
Is it [**EEP!** *(in response to the site's content)*](https://en.wikipedia.org/wiki/Onomatopoeia), or **end-to-end protocol**, or something else entirely different?
|
||||
|
@ -1,11 +1,11 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Encryption"
|
||||
tags: ["kovri"]
|
||||
terms: ["encryption", "encrypted", "encrypting", "decryption", "decrypted", "decrypting"]
|
||||
summary: "The process of encoding messages or information in a way that only authorized parties can decode and read"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
From [Encryption](https://en.wikipedia.org/wiki/Encryption):
|
||||
|
@ -1,11 +1,11 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Floodfill"
|
||||
tags: ["kovri"]
|
||||
terms: ["Floodfill"]
|
||||
summary: "An I2P router which maintains a distributed network-database"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
By actively managing a distributed network-database, a router with *floodfill* capability has the ability to help maintain network stability and resiliancy while also being decentralized and trust-less.
|
||||
|
19
_i18n/es/resources/moneropedia/fluffyblocks.md
Normal file
19
_i18n/es/resources/moneropedia/fluffyblocks.md
Normal file
@ -0,0 +1,19 @@
|
||||
---
|
||||
entry: "Fluffy Blocks"
|
||||
terms: ["fluffy blocks", "fluffyblocks"]
|
||||
summary: "a way of saving bandwidth when sending new blocks around the network"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
A @block is made up of a header and @transactions. Fluffy Blocks only contain
|
||||
a header, a list of transaction indices, and any transactions that the node
|
||||
recieving the block may be missing. This saves bandwidth because nodes might
|
||||
already know about most or all of the transactions in the block and they don't
|
||||
need to be sent them again.
|
||||
|
||||
### See Also
|
||||
|
||||
* [BIP152 "Compact Block Relay"](https://github.com/bitcoin/bips/blob/master/bip-0152.mediawiki)
|
||||
* [Xthin](https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/release/doc/bu-xthin-protocol.md)
|
@ -1,16 +1,17 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Fungibility"
|
||||
terms: ["fungibility"]
|
||||
terms: ["fungibility", "fungible"]
|
||||
summary: "property of a currency whereby two units can be substituted in place of one another"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
Fungibility means that two units of a currency can be mutually substituted and the substituted currency is equal to another unit of the same size. For example, two $10 bills can be exchanged and they are functionally identical to any other $10 bills in circulation (although $10 bills have unique ID numbers and are therefore not completely fungible). Gold is probably a closer example of true fungibility, where any 1 oz. of gold of the same grade is worth the same as another 1 oz of gold. Monero is fungible due to the nature of the currency which provides no way to link transactions together nor trace the history of any particular XMR. 1 XMR is functionally identical to any other 1 XMR.
|
||||
Property of a currency whereby two units can be substituted in place of one another.
|
||||
|
||||
Fungibility is an advantage Monero has over Bitcoin and almost every other cryptocurrency, due to the privacy inherent in the Monero @blockchain and the permanently traceable nature of the Bitcoin blockchain. With Bitcoin, any BTC can be tracked by anyone back to it's creation @coinbase-transaction. Therefore, if a coin has been used for an illegal purpose in the past, this history will be contained in the @blockchain in perpetuity. This lack of fungibility means that certain businesses will be obligated to avoid accepting BTC that have been previously used for purposes which are illegal, or simply run afoul of their Terms of Service. Currently some large Bitcoin companies are blocking, suspending, or closing accounts that have received Bitcoin used in online gambling or other purposes deemed unsavory by said companies.
|
||||
Fungibility means that two units of a currency can be mutually substituted and the substituted currency is equal to another unit of the same size. For example, two $10 bills can be exchanged and they are functionally identical to any other $10 bill in circulation (although $10 bills have unique ID numbers and are therefore not completely fungible). Gold is probably a closer example of true fungibility, where any 1 oz. of gold of the same grade is worth the same as another 1 oz. of gold. Monero is fungible due to the nature of the currency which provides no way to link transactions together nor trace the history of any particular XMR. 1 XMR is functionally identical to any other 1 XMR.
|
||||
|
||||
Monero has been built specifically to address the problem of traceability and non-fungability inherent in other cryptocurrencies. By having completely private transactions Monero is truly fungible and there can be no blacklisting of certain XMR, while at the same time providing all the benefits of a secure, decentralized, permanent blockchain.
|
||||
Fungibility is an advantage Monero has over Bitcoin and almost every other cryptocurrency, due to the privacy inherent in the Monero @blockchain and the permanently traceable nature of the Bitcoin blockchain. With Bitcoin, any BTC can be tracked by anyone back to its creation @coinbase-transaction. Therefore, if a coin has been used for an illegal purpose in the past, this history will be contained in the @blockchain in perpetuity. This lack of fungibility means that certain businesses will be obligated to avoid accepting BTC that have been previously used for purposes which are illegal, or simply run afoul of their Terms of Service. Currently some large Bitcoin companies are blocking, suspending, or closing accounts that have received Bitcoin used in online gambling or other purposes deemed unsavory by said companies.
|
||||
|
||||
Monero has been built specifically to address the problem of traceability and non-fungibility inherent in other cryptocurrencies. By having completely private transactions Monero is truly fungible and there can be no blacklisting of certain XMR, while at the same time providing all the benefits of a secure, decentralized, permanent blockchain.
|
||||
|
||||
{{ page.summary | capitalize }}.
|
||||
|
@ -1,11 +1,11 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Garlic-Encryption"
|
||||
tags: ["kovri"]
|
||||
terms: ["Garlic-Encryption", "Layered-Encryption"]
|
||||
summary: "Layered encryption as implemented in Kovri / I2P"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
@garlic-encryption is @I2P's implementation of @message based @layered-encryption (similar to flow-based [Onion-Routing](https://en.wikipedia.org/wiki/Onion_routing)).
|
||||
|
@ -1,14 +1,14 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "Garlic Routing"
|
||||
tags: ["kovri"]
|
||||
terms: ["Garlic-Routing"]
|
||||
summary: "Routing technology as implemented in Kovri"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
The term *@garlic-routing* has a diverse history of varying interpretations. As it currently stands, Monero defines *@garlic-routing* as the method in which @Kovri and @I2P create a @message-based anonymous overlay network of internet peers.
|
||||
The term *@garlic-routing* has a diverse history of varying interpretations. As it currently stands, Monero defines *@garlic-routing* as the method in which @Kovri and @I2P create a @message-based anonymous overlay network of Internet peers.
|
||||
|
||||
The @Garlic-Encryption of @Garlic-Routing is similar to the @Layered-Encryption of [Onion Routing](https://en.wikipedia.org/wiki/Onion_routing) and effectively conceals the IP address of the sender and secures information sent from the sender to its @destination (and vice-versa).
|
||||
|
||||
|
@ -1,11 +1,11 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "I2NP"
|
||||
tags: ["kovri"]
|
||||
terms: ["I2NP"]
|
||||
summary: "The I2P Network Protocol: the mechanism in which I2NP messages are sent over the I2P network"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### The Basics
|
||||
|
||||
From @Java-I2P:
|
||||
|
@ -1,11 +1,11 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "I2P"
|
||||
tags: ["kovri"]
|
||||
terms: ["I2P"]
|
||||
summary: "The Invisible Internet Project: an anonymizing overlay network"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
### Monero
|
||||
|
||||
For Monero's implementation of @I2P, see @Kovri. For a comparison of @I2P to [Tor](https://torproject.org/), read the [Comparison](https://geti2p.net/en/comparison/tor) page.
|
||||
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user