mirror of
https://github.com/monero-project/monero-site.git
synced 2024-12-23 12:09:49 +00:00
Merge pull request #1136
Adopt versioning system used in the User Guides to keep track of the translation status of the Moneropedia entries
This commit is contained in:
luigi1111
GitHub
commit
fb21299aae
582 changed files with 626 additions and 287 deletions
|
|
@ -69,7 +69,7 @@ We are trying to move most of the localization work on Weblate, but some parts o
|
|||
* Navigate to the correct language in the /i18n folder and find the page you wish to translate
|
||||
* Do not translate any of the `*.yml` files in the /_18n folder
|
||||
* Click the file and translate the page, not touching any HTML or markdown
|
||||
* Remove `{% include untranslated.html %}` from the page
|
||||
* Adapt the snippet keeping track of the status of the translation in the document `{% include disclaimer.html translated="no" translationOutdated="no" %}`, changing to `yes` where appropriate
|
||||
* Test/Build
|
||||
* Submit PR
|
||||
|
||||
|
|
@ -86,7 +86,7 @@ Moneropedia entries have two specificities:
|
|||
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 *untranslated* snippet must be removed, therefore the next section is irrelevant here.
|
||||
* The snippet keeping track of the status of the translation must be updated (`{% include disclaimer.html translated="no" translationOutdated="no" %}`). If the document is translated, change `translated="no"` to `translated="yes"`. If the document is translated, but the original file (in English) was updated, change `translationOutdated="no"` to `translationOutdated="yes`.
|
||||
|
||||
Finally, your entry should go from:
|
||||
```
|
||||
|
|
@ -96,7 +96,7 @@ terms: ["English", "terms"]
|
|||
summary: "English summary."
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
```
|
||||
To:
|
||||
```
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["account", "accounts", "wallet", "wallets"]
|
|||
summary: "similar in function to a bank account, contains all of your sent and received transactions"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ terms: ["Address-Book"]
|
|||
summary: "Allows you to visit I2P websites/services that have the .i2p domain"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ 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 %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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">888tNkZrPN6JsEgekjMnABU4TBzc2Dt29EPAvkRxbANsAnjyPbb3iQ1YBRk1UXcdRsiKc9dhwMVgN5S9cQUiyoogDavup3H</span>.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ 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 %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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."
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["atomic-units", "atomic-unit"]
|
|||
summary: "Atomic Units refer to the smallest fraction of 1 XMR."
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
Atomic Units refer to the smallest fraction of 1 XMR.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["block", "blocks"]
|
|||
summary: "a container of transactions, a sequence of which forms a blockchain"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ summary: "a distributed ledger of all transactions both past and present, withou
|
|||
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["bootstrap-node", "bootstrap-nodes"]
|
|||
summary: "A node to which a daemon connects to give immediate usability to wallets while syncing"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["bulletproofs", "bulletproof"]
|
|||
summary: "a new kind of range proofs replacing RingCT in transactions to obfuscate the amounts sent"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
@RingCT was introduced to obfuscate transaction amounts. One goal of @RingCT was to prove the sum of inputs - outputs in the @transaction was equal to 0, and all outputs were positive numbers.
|
||||
To accomplish this, two kind of ring signatures were constructed: One ring signature for the whole transaction (to prove the sum is 0), and a set of ring signatures for the subsets of transaction bits (to prove the outputs are positive numbers), then combined together using originally Schnorr signatures (and later replaced by Borromean ring signature).
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ terms: ["Canonically-unique-host"]
|
|||
summary: "A host that is canonically resolved to an address or set of addresses"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["change"]
|
|||
summary: "Monero sent as part of a transaction, that returns to your account instead of going to another recipient"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
Monero sent as part of a transaction, that returns to your account instead of going to another recipient.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ terms: ["Clearnet"]
|
|||
summary: "The Internet in which anonymous overlay networks are built upon"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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:
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ 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 %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
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.
|
||||
|
|
@ -3,7 +3,7 @@ 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 %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
Consensus describes a property of distributed networks like Monero where most of the participants follow the rules, and thus reject bad participants.
|
||||
|
|
@ -3,7 +3,7 @@ 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 %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ terms: ["daemon"]
|
|||
summary: "Background process which runs and controls a Monero node"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
'Daemon' is the general term for a piece of software running in the background. In Monero, the Daemon is started through the 'monerod' program. If you run the Daemon locally, you are running a local @node. If the Daemon is running on another device it's a @remote-node. A @wallet, like the CLI or the GUI, needs to connect to a Daemon (local or remote) to relay @transactions to the network.
|
||||
|
||||
It's possible to send commands to the Daemon directly or through the RPC interface. See the [Daemon RPC guide]({{ site.baseurl_root }}/resources/developer-guides/daemon-rpc.html), which contains a detailed explanation (with examples) of the available RPC calls. For more detailed and technical information about the Daemon, see the Monerodocs reference at the bottom of this page.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["denominations", "subunits", "tacoshi", "piconero", "nanonero", "microne
|
|||
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 %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
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.).
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ terms: ["Destination", "Destinations"]
|
|||
summary: "A in-net address that serves as a final endpoint (either local or remote)"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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).
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ terms: ["encryption", "encrypted", "encrypting", "decryption", "decrypted", "dec
|
|||
summary: "The process of encoding messages or information in a way that only authorized parties can decode and read"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
From [Encryption](https://en.wikipedia.org/wiki/Encryption):
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["fluffy blocks", "fluffyblocks"]
|
|||
summary: "a way of saving bandwidth when sending new blocks around the network"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
A @block is made up of a header and @transactions. Fluffy Blocks only contain
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["fungibility", "fungible"]
|
|||
summary: "property of a currency whereby two units can be substituted in place of one another"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
Property of a currency whereby two units can be substituted in place of one another.
|
||||
|
|
|
|||
|
|
@ -4,6 +4,7 @@ terms: ["Kovri"]
|
|||
summary: "C++ router implementation of the I2P network"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
[Kovri](https://gitlab.com/kovri-project/kovri/) is a C++ implementation of the I2P network which was proposed to be integrated in Monero. At the moment the future of this I2P router is unclear and an integration with Monero is not planned.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ terms: ["Locally-unique-host"]
|
|||
summary: "A host defined by you and resolved only by you"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by **you** and resolved only by you; similar to how a [hosts file](https://en.wikipedia.org/wiki/Hosts_(file)) is implemented. Not to be confused with @canonically-unique-host.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ 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"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
The process of cryptographically computing a mathematical proof for a block, containing a number of transactions, which is then added to the blockchain.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["mnemonic-seed", "mnemonic"]
|
|||
summary: "a 13 or 25 word phrase used to backup a Monero account, available in a number of languages"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ 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"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
A device on the Internet running the Monero software, with a full copy of the Monero blockchain, actively assisting the Monero network.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ 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"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
The Monero Core Team released a standard called OpenAlias which permits much more human-readable addresses and "squares" the Zooko's triangle. OpenAlias can be used for any cryptocurrency and is already implemented in Monero, Bitcoin (in latest Electrum versions) and HyperStake.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["paperwallet", "paperwallets", "paper-wallet", "paper-wallets"]
|
|||
summary: "A paper wallet stores the information necessary to send and receive Monero"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
A paper wallet stores the information necessary to send and receive Monero.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["payment-ID", "payment-IDs"]
|
|||
summary: "an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
*Note:* Long Payment IDs have been removed since release 0.15; it's not possible to use them anymore. More info in the [blog post](https://getmonero.org/2019/06/04/Long-Payment-ID-Deprecation.html) that announced their deprecation.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["commitments", "commitment", "pedersen", "pedersen-commitment", "pederse
|
|||
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"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["pruning"]
|
|||
summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node.
|
||||
|
||||
There are three ways to prune:
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ terms: ["randomx", "random-x"]
|
|||
summary: "ASIC-resistant POW algoritm currenctly used by Monero"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
RandomX is a Proof Of Work algorithm developed by Monero contributors and adopted by Monero from release 0.15.
|
||||
|
||||
This innovative POW is optimized for CPUs and it's based on execution of random code and other memory-heavy techniques. The goal is to discourage the use of specialized hardware (like ASICs) for mining Monero. RandomX was created with the intent of keeping mining decentralized and to create a more egalitarian distribution of the block rewards.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ terms: ["remote-node", "remote-nodes"]
|
|||
summary: "Nodes wich are not running in the same machine as the wallet. Open remote nodes allow to use the Monero network immediately"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
A @node that doesn't run on the same local machine where the Monero @wallet is located is called "Remote Node" and can be private or open.
|
||||
|
||||
A **private remote node** doesn't run on your local machine, but you have full control over it. A classic example is a node running on a VPS or a server. That node is not on your local machine, but you have full control over it. You can even decide to make it become an open node, allowing people to connect to it.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["ring-size"]
|
|||
summary: "total number of possible signers in a ring signature"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
Ring size refers to the total number of possible signers in a @ring-signature. If a ring size of 4 is selected for a given @transaction, this means that there are 3 foreign outputs in addition to your “real” output. A higher ring size number will typically provide more privacy than a lower number. However, reusing an odd, recognizable ring size number for transactions could possibly make transactions stand out.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["ringCT", "ring-CT"]
|
|||
summary: "a way to hide the amount sent in a Monero transaction"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
RingCT, short for Ring Confidential Transactions, is how transaction amounts are hidden in Monero.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ 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"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
In cryptography, a ring signature is a type of digital signature that can be performed by any member of a group of users that each have keys. Therefore, a message signed with a ring signature is endorsed by someone in a particular group of people. One of the security properties of a ring signature is that it should be computationally infeasible to determine *which* of the group members' keys was used to produce the signature.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["scalability"]
|
|||
summary: "How Monero scaling is flexible and can accommodate many transactions as demand changes"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
The size of Monero @blocks (which contain @transactions) is flexible and can accommodate many transactions as demand changes. Formulas determine how the reward miners receive interacts with the number of transactions they choose to include in blocks. The @blockchain can therefore scale to meet changes in transaction volume.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ 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"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
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.
|
||||
|
|
@ -3,7 +3,7 @@ terms: ["smart-mining"]
|
|||
summary: "a process of having a throttled miner mine when it otherwise does not cause drawbacks"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
Smart mining is the process of having a throttled @miner mine when it otherwise does not cause drawbacks.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ 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"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["stealth-address", "stealth-addresses"]
|
|||
summary: "automatic one-time addresses for every transaction"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
Stealth addresses are an important part of Monero's inherent privacy. They allow and require the sender to create random one-time addresses for every @transaction on behalf of the recipient. The recipient can publish just one address, yet have all of his/her incoming payments go to unique addresses on the @blockchain, where they cannot be linked back to either the recipient's published address or any other transactions' addresses. By using stealth addresses, only the sender and receiver can determine where a payment was sent.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["Tail-Emission"]
|
|||
summary: "the block reward at the end of the emission curve"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
Monero block rewards will never drop to zero. Block rewards will gradually drop until tail emission commences at the end of May 2022. At this point, rewards will be fixed at 0.6 XMR per block.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["transaction", "transactions"]
|
|||
summary: "a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
A cryptographically signed container that details the transfer of Monero to a recipient (or recipients).
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["unlock-time"]
|
|||
summary: "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
A special transaction where the recipient can only spend the funds after a future date, as set by the sender.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ 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"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
One of two sets of private and public cryptographic keys that each account has, with the private view key required to view all transactions related to the account.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["wallet", "wallets"]
|
|||
summary: "A wallet stores the information necessary to send and receive Monero"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
A Monero account, or wallet, stores the information necessary to send and receive Moneroj. In addition to sending and receiving, the Monero Wallet software keeps a private history of your transactions and allows you to cryptographically sign messages. It also includes Monero mining software and an address book.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["account", "accounts", "wallet", "wallets", "Account", "Accounts"]
|
|||
summary: "similar in function to a bank account, contains all of your sent and received transactions"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ terms: ["Address-Book"]
|
|||
summary: "Allows you to visit I2P websites/services that have the .i2p domain"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["address", "addresses", "Adresse" , "Adressen"]
|
|||
summary: "either an alias, such as donate.getmonero.org, or a set of 95 characters starting with a 4"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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">888tNkZrPN6JsEgekjMnABU4TBzc2Dt29EPAvkRxbANsAnjyPbb3iQ1YBRk1UXcdRsiKc9dhwMVgN5S9cQUiyoogDavup3H</span>.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ 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 %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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."
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["atomic-units", "atomic-unit"]
|
|||
summary: "Atomic Units refer to the smallest fraction of 1 XMR."
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
Atomic Units refer to the smallest fraction of 1 XMR.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["block", "blocks"]
|
|||
summary: "a container of transactions, a sequence of which forms a blockchain"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ summary: "a distributed ledger of all transactions both past and present, withou
|
|||
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["bootstrap-node", "bootstrap-nodes"]
|
|||
summary: "A node to which a daemon connects to give immediate usability to wallets while syncing"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ terms: ["bulletproofs", "bulletproof"]
|
|||
summary: "a new kind of range proofs replacing RingCT in transactions to obfuscate the amounts sent"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
@RingCT was introduced to obfuscate transaction amounts. One goal of @RingCT was to prove the sum of inputs - outputs in the @transaction was equal to 0, and all outputs were positive numbers.
|
||||
To accomplish this, two kind of ring signatures were constructed: One ring signature for the whole transaction (to prove the sum is 0), and a set of ring signatures for the subsets of transaction bits (to prove the outputs are positive numbers), then combined together using originally Schnorr signatures (and later replaced by Borromean ring signature).
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ terms: ["Canonically-unique-host"]
|
|||
summary: "A host that is canonically resolved to an address or set of addresses"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["change"]
|
|||
summary: "Monero sent as part of a transaction, that returns to your account instead of going to another recipient"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
Monero sent as part of a transaction, that returns to your account instead of going to another recipient.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ terms: ["Clearnet"]
|
|||
summary: "The Internet in which anonymous overlay networks are built upon"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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:
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ 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 %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
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.
|
||||
|
|
@ -3,7 +3,7 @@ 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 %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
Consensus describes a property of distributed networks like Monero where most of the participants follow the rules, and thus reject bad participants.
|
||||
|
|
@ -3,7 +3,7 @@ terms: ["cryptocurrency", "cryptocurrencies", "altcoin", "altcoins", "Kryptowäh
|
|||
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 %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ terms: ["daemon"]
|
|||
summary: "Background process which runs and controls a Monero node"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
'Daemon' is the general term for a piece of software running in the background. In Monero, the Daemon is started through the 'monerod' program. If you run the Daemon locally, you are running a local @node. If the Daemon is running on another device it's a @remote-node. A @wallet, like the CLI or the GUI, needs to connect to a Daemon (local or remote) to relay @transactions to the network.
|
||||
|
||||
It's possible to send commands to the Daemon directly or through the RPC interface. See the [Daemon RPC guide]({{ site.baseurl_root }}/resources/developer-guides/daemon-rpc.html), which contains a detailed explanation (with examples) of the available RPC calls. For more detailed and technical information about the Daemon, see the Monerodocs reference at the bottom of this page.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["denominations", "subunits", "tacoshi", "piconero", "nanonero", "microne
|
|||
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 %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
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.).
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ terms: ["Destination", "Destinations"]
|
|||
summary: "A in-net address that serves as a final endpoint (either local or remote)"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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).
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ terms: ["encryption", "encrypted", "encrypting", "decryption", "decrypted", "dec
|
|||
summary: "The process of encoding messages or information in a way that only authorized parties can decode and read"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
From [Encryption](https://en.wikipedia.org/wiki/Encryption):
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["fluffy blocks", "fluffyblocks"]
|
|||
summary: "a way of saving bandwidth when sending new blocks around the network"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
A @block is made up of a header and @transactions. Fluffy Blocks only contain
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["fungibility", "fungible"]
|
|||
summary: "property of a currency whereby two units can be substituted in place of one another"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
Property of a currency whereby two units can be substituted in place of one another.
|
||||
|
|
|
|||
|
|
@ -4,6 +4,7 @@ terms: ["Kovri"]
|
|||
summary: "C++ router implementation of the I2P network"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
[Kovri](https://gitlab.com/kovri-project/kovri/) is a C++ implementation of the I2P network which was proposed to be integrated in Monero. At the moment the future of this I2P router is unclear and an integration with Monero is not planned.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ terms: ["Locally-unique-host"]
|
|||
summary: "A host defined by you and resolved only by you"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by **you** and resolved only by you; similar to how a [hosts file](https://en.wikipedia.org/wiki/Hosts_(file)) is implemented. Not to be confused with @canonically-unique-host.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ 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"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
The process of cryptographically computing a mathematical proof for a block, containing a number of transactions, which is then added to the blockchain.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["mnemonic-seed", "mnemonic"]
|
|||
summary: "a 13 or 25 word phrase used to backup a Monero account, available in a number of languages"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ 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"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
A device on the Internet running the Monero software, with a full copy of the Monero blockchain, actively assisting the Monero network.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ 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"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
The Monero Core Team released a standard called OpenAlias which permits much more human-readable addresses and "squares" the Zooko's triangle. OpenAlias can be used for any cryptocurrency and is already implemented in Monero, Bitcoin (in latest Electrum versions) and HyperStake.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["paperwallet", "paperwallets", "paper-wallet", "paper-wallets"]
|
|||
summary: "A paper wallet stores the information necessary to send and receive Monero"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
A paper wallet stores the information necessary to send and receive Monero.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["payment-ID", "payment-IDs"]
|
|||
summary: "an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
*Note:* Long Payment IDs have been removed since release 0.15; it's not possible to use them anymore. More info in the [blog post](https://getmonero.org/2019/06/04/Long-Payment-ID-Deprecation.html) that announced their deprecation.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["commitments", "commitment", "pedersen", "pedersen-commitment", "pederse
|
|||
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"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["pruning"]
|
|||
summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node.
|
||||
|
||||
There are three ways to prune:
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ terms: ["randomx", "random-x"]
|
|||
summary: "ASIC-resistant POW algoritm currenctly used by Monero"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
RandomX is a Proof Of Work algorithm developed by Monero contributors and adopted by Monero from release 0.15.
|
||||
|
||||
This innovative POW is optimized for CPUs and it's based on execution of random code and other memory-heavy techniques. The goal is to discourage the use of specialized hardware (like ASICs) for mining Monero. RandomX was created with the intent of keeping mining decentralized and to create a more egalitarian distribution of the block rewards.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ terms: ["remote-node", "remote-nodes"]
|
|||
summary: "Nodes wich are not running in the same machine as the wallet. Open remote nodes allow to use the Monero network immediately"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
A @node that doesn't run on the same local machine where the Monero @wallet is located is called "Remote Node" and can be private or open.
|
||||
|
||||
A **private remote node** doesn't run on your local machine, but you have full control over it. A classic example is a node running on a VPS or a server. That node is not on your local machine, but you have full control over it. You can even decide to make it become an open node, allowing people to connect to it.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["ring-size"]
|
|||
summary: "total number of possible signers in a ring signature"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
Ring size refers to the total number of possible signers in a @ring-signature. If a ring size of 4 is selected for a given @transaction, this means that there are 3 foreign outputs in addition to your “real” output. A higher ring size number will typically provide more privacy than a lower number. However, reusing an odd, recognizable ring size number for transactions could possibly make transactions stand out.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["ringCT", "ring-CT"]
|
|||
summary: "a way to hide the amount sent in a Monero transaction"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
RingCT, short for Ring Confidential Transactions, is how transaction amounts are hidden in Monero.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ 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"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
In cryptography, a ring signature is a type of digital signature that can be performed by any member of a group of users that each have keys. Therefore, a message signed with a ring signature is endorsed by someone in a particular group of people. One of the security properties of a ring signature is that it should be computationally infeasible to determine *which* of the group members' keys was used to produce the signature.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["scalability"]
|
|||
summary: "How Monero scaling is flexible and can accommodate many transactions as demand changes"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
The size of Monero @blocks (which contain @transactions) is flexible and can accommodate many transactions as demand changes. Formulas determine how the reward miners receive interacts with the number of transactions they choose to include in blocks. The @blockchain can therefore scale to meet changes in transaction volume.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ 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"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
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.
|
||||
|
|
@ -3,7 +3,7 @@ terms: ["smart-mining"]
|
|||
summary: "a process of having a throttled miner mine when it otherwise does not cause drawbacks"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
Smart mining is the process of having a throttled @miner mine when it otherwise does not cause drawbacks.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ 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"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["stealth-address", "stealth-addresses", "Schattenadressen", "Schattenadr
|
|||
summary: "automatic one-time addresses for every transaction"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
Stealth addresses are an important part of Monero's inherent privacy. They allow and require the sender to create random one-time addresses for every @transaction on behalf of the recipient. The recipient can publish just one address, yet have all of his/her incoming payments go to unique addresses on the @blockchain, where they cannot be linked back to either the recipient's published address or any other transactions' addresses. By using stealth addresses, only the sender and receiver can determine where a payment was sent.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["Tail-Emission"]
|
|||
summary: "the block reward at the end of the emission curve"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
Monero block rewards will never drop to zero. Block rewards will gradually drop until tail emission commences at the end of May 2022. At this point, rewards will be fixed at 0.6 XMR per block.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["transaction", "transactions"]
|
|||
summary: "a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
A cryptographically signed container that details the transfer of Monero to a recipient (or recipients).
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["unlock-time"]
|
|||
summary: "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
A special transaction where the recipient can only spend the funds after a future date, as set by the sender.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ 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"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
One of two sets of private and public cryptographic keys that each account has, with the private view key required to view all transactions related to the account.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ terms: ["wallet", "wallets"]
|
|||
summary: "A wallet stores the information necessary to send and receive Monero"
|
||||
---
|
||||
|
||||
{% include untranslated.html %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
A Monero account, or wallet, stores the information necessary to send and receive Moneroj. In addition to sending and receiving, the Monero Wallet software keeps a private history of your transactions and allows you to cryptographically sign messages. It also includes Monero mining software and an address book.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ terms: ["account", "accounts", "wallet", "wallets"]
|
|||
summary: "similar in function to a bank account, contains all of your sent and received transactions"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ terms: ["address", "addresses"]
|
|||
summary: "either an alias, such as donate.getmonero.org, or a set of 95 characters starting with a 4"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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">888tNkZrPN6JsEgekjMnABU4TBzc2Dt29EPAvkRxbANsAnjyPbb3iQ1YBRk1UXcdRsiKc9dhwMVgN5S9cQUiyoogDavup3H</span>.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ 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 disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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."
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ terms: ["atomic-units", "atomic-unit"]
|
|||
summary: "Atomic Units refer to the smallest fraction of 1 XMR."
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
Atomic Units refer to the smallest fraction of 1 XMR.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ terms: ["block", "blocks"]
|
|||
summary: "a container of transactions, a sequence of which forms a blockchain"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ 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 disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ terms: ["bootstrap-node", "bootstrap-nodes"]
|
|||
summary: "A node to which a daemon connects to give immediate usability to wallets while syncing"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### 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 not yet synced on the local @node.
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show more
Loading…
Reference in a new issue