mirror of
https://github.com/monero-project/monero-site.git
synced 2025-01-11 13:25:12 +00:00
Add Moneropedia 'remote-node' entry to all languages
This commit is contained in:
parent
617f17af8e
commit
b184903ccf
24 changed files with 288 additions and 0 deletions
|
@ -632,6 +632,7 @@ moneropedia:
|
||||||
paperwallet: Paper Wallet
|
paperwallet: Paper Wallet
|
||||||
paymentid: Payment ID
|
paymentid: Payment ID
|
||||||
pedersen-commitment: Pedersen Commitment
|
pedersen-commitment: Pedersen Commitment
|
||||||
|
remote-node: Remote Node
|
||||||
reseed: Reseed
|
reseed: Reseed
|
||||||
ringCT: Ring CT
|
ringCT: Ring CT
|
||||||
ringsignatures: Ring Signature
|
ringsignatures: Ring Signature
|
||||||
|
|
23
_i18n/ar/resources/moneropedia/remote-node.md
Normal file
23
_i18n/ar/resources/moneropedia/remote-node.md
Normal file
|
@ -0,0 +1,23 @@
|
||||||
|
---
|
||||||
|
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"
|
||||||
|
---
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
An **Open remote node** can be used by people who, for their own reasons (usually because of hardware requirements, disk space, or technical abilities), cannot/don't want to run their own node and prefer to relay on one publicly available on the Monero network. Open remote nodes are often simply referred as "remote nodes".
|
||||||
|
|
||||||
|
Using an open node will allow to make a @transaction instantaneously, without the need to download the @blockchain and sync to the Monero network first, but at the cost of the control over your privacy. the Monero community suggests to always run your own node to obtain the maximum privacy possible and to help decentralize the network.
|
||||||
|
|
||||||
|
### Public Nodes
|
||||||
|
|
||||||
|
Open nodes are cool because, as we said above, allow people who are not running their own node to immediately join the Monero network. There are 2 main ways to connect to an open node: Simply get somebody to share with you their node, by asking them to "open it" and provide you with IP address and port, or use a public one.
|
||||||
|
|
||||||
|
Public nodes are reachable in the network using two systems:
|
||||||
|
|
||||||
|
- **Node aggregators**, which are basically lists of open remote nodes. The operators of those nodes decided to add them to the aggregator so that other people can use them. The aggregator will provide to the person who want to use a remote node a simple URL. This URL connects to one of the nodes in the list and will need to be inserted in the Monero wallet (GUI or CLI). The wallet will then contact one of the nodes provided by the URL and will allow the end user to immediately receive and send transactions. One of the most famous node aggregators is [MoneroWorld](https://moneroworld.com/#nodes).
|
||||||
|
- **Native public nodes**. This is one of the new coolest features the Monero devs came up with to improve the user experience and to make easier to connect to the network. The CLI wallet allow to make a node public by simply adding the flag `--public-node`. Doing so, it will be advertised on the P2P network and people will be able to connect to it (or to another public node advertising itself in the same way) using the related option in the GUI and CLI wallets.
|
||||||
|
|
||||||
|
Be aware that using public remote nodes can be risky. Node operators can link transactions to IP addresses. These risks can be mitigated, but you should always avoid using them if you have the possibility. Run your own node!
|
|
@ -633,6 +633,7 @@ moneropedia:
|
||||||
paperwallet: Paper-Wallet
|
paperwallet: Paper-Wallet
|
||||||
paymentid: Payment-ID
|
paymentid: Payment-ID
|
||||||
pedersen-commitment: Pedersen-Commitment
|
pedersen-commitment: Pedersen-Commitment
|
||||||
|
remote-node: Remote Node
|
||||||
reseed: Reseed
|
reseed: Reseed
|
||||||
ringCT: vertrauliche Ringtransaktionen (Ring CT)
|
ringCT: vertrauliche Ringtransaktionen (Ring CT)
|
||||||
ringsignatures: Ringsignatur
|
ringsignatures: Ringsignatur
|
||||||
|
|
23
_i18n/de/resources/moneropedia/remote-node.md
Normal file
23
_i18n/de/resources/moneropedia/remote-node.md
Normal file
|
@ -0,0 +1,23 @@
|
||||||
|
---
|
||||||
|
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"
|
||||||
|
---
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
An **Open remote node** can be used by people who, for their own reasons (usually because of hardware requirements, disk space, or technical abilities), cannot/don't want to run their own node and prefer to relay on one publicly available on the Monero network. Open remote nodes are often simply referred as "remote nodes".
|
||||||
|
|
||||||
|
Using an open node will allow to make a @transaction instantaneously, without the need to download the @blockchain and sync to the Monero network first, but at the cost of the control over your privacy. the Monero community suggests to always run your own node to obtain the maximum privacy possible and to help decentralize the network.
|
||||||
|
|
||||||
|
### Public Nodes
|
||||||
|
|
||||||
|
Open nodes are cool because, as we said above, allow people who are not running their own node to immediately join the Monero network. There are 2 main ways to connect to an open node: Simply get somebody to share with you their node, by asking them to "open it" and provide you with IP address and port, or use a public one.
|
||||||
|
|
||||||
|
Public nodes are reachable in the network using two systems:
|
||||||
|
|
||||||
|
- **Node aggregators**, which are basically lists of open remote nodes. The operators of those nodes decided to add them to the aggregator so that other people can use them. The aggregator will provide to the person who want to use a remote node a simple URL. This URL connects to one of the nodes in the list and will need to be inserted in the Monero wallet (GUI or CLI). The wallet will then contact one of the nodes provided by the URL and will allow the end user to immediately receive and send transactions. One of the most famous node aggregators is [MoneroWorld](https://moneroworld.com/#nodes).
|
||||||
|
- **Native public nodes**. This is one of the new coolest features the Monero devs came up with to improve the user experience and to make easier to connect to the network. The CLI wallet allow to make a node public by simply adding the flag `--public-node`. Doing so, it will be advertised on the P2P network and people will be able to connect to it (or to another public node advertising itself in the same way) using the related option in the GUI and CLI wallets.
|
||||||
|
|
||||||
|
Be aware that using public remote nodes can be risky. Node operators can link transactions to IP addresses. These risks can be mitigated, but you should always avoid using them if you have the possibility. Run your own node!
|
|
@ -633,6 +633,7 @@ moneropedia:
|
||||||
paperwallet: Monedero en Papel
|
paperwallet: Monedero en Papel
|
||||||
paymentid: ID de Pago
|
paymentid: ID de Pago
|
||||||
pedersen-commitment: Compromiso Pedersen
|
pedersen-commitment: Compromiso Pedersen
|
||||||
|
remote-node: Remote Node
|
||||||
reseed: Resembrar
|
reseed: Resembrar
|
||||||
ringCT: Transacción Circular Confidencial
|
ringCT: Transacción Circular Confidencial
|
||||||
ringsignatures: Firmas Circulares
|
ringsignatures: Firmas Circulares
|
||||||
|
|
23
_i18n/es/resources/moneropedia/remote-node.md
Normal file
23
_i18n/es/resources/moneropedia/remote-node.md
Normal file
|
@ -0,0 +1,23 @@
|
||||||
|
---
|
||||||
|
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"
|
||||||
|
---
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
An **Open remote node** can be used by people who, for their own reasons (usually because of hardware requirements, disk space, or technical abilities), cannot/don't want to run their own node and prefer to relay on one publicly available on the Monero network. Open remote nodes are often simply referred as "remote nodes".
|
||||||
|
|
||||||
|
Using an open node will allow to make a @transaction instantaneously, without the need to download the @blockchain and sync to the Monero network first, but at the cost of the control over your privacy. the Monero community suggests to always run your own node to obtain the maximum privacy possible and to help decentralize the network.
|
||||||
|
|
||||||
|
### Public Nodes
|
||||||
|
|
||||||
|
Open nodes are cool because, as we said above, allow people who are not running their own node to immediately join the Monero network. There are 2 main ways to connect to an open node: Simply get somebody to share with you their node, by asking them to "open it" and provide you with IP address and port, or use a public one.
|
||||||
|
|
||||||
|
Public nodes are reachable in the network using two systems:
|
||||||
|
|
||||||
|
- **Node aggregators**, which are basically lists of open remote nodes. The operators of those nodes decided to add them to the aggregator so that other people can use them. The aggregator will provide to the person who want to use a remote node a simple URL. This URL connects to one of the nodes in the list and will need to be inserted in the Monero wallet (GUI or CLI). The wallet will then contact one of the nodes provided by the URL and will allow the end user to immediately receive and send transactions. One of the most famous node aggregators is [MoneroWorld](https://moneroworld.com/#nodes).
|
||||||
|
- **Native public nodes**. This is one of the new coolest features the Monero devs came up with to improve the user experience and to make easier to connect to the network. The CLI wallet allow to make a node public by simply adding the flag `--public-node`. Doing so, it will be advertised on the P2P network and people will be able to connect to it (or to another public node advertising itself in the same way) using the related option in the GUI and CLI wallets.
|
||||||
|
|
||||||
|
Be aware that using public remote nodes can be risky. Node operators can link transactions to IP addresses. These risks can be mitigated, but you should always avoid using them if you have the possibility. Run your own node!
|
|
@ -634,6 +634,7 @@ moneropedia:
|
||||||
paperwallet: portefeuille Papier
|
paperwallet: portefeuille Papier
|
||||||
paymentid: ID de paiement
|
paymentid: ID de paiement
|
||||||
pedersen-commitment: Engagement de Pedersen
|
pedersen-commitment: Engagement de Pedersen
|
||||||
|
remote-node: Remote Node
|
||||||
reseed: Réensemencement
|
reseed: Réensemencement
|
||||||
ringCT: Transactions confidentielles de cercle
|
ringCT: Transactions confidentielles de cercle
|
||||||
ringsignatures: Signature de Cercle
|
ringsignatures: Signature de Cercle
|
||||||
|
|
23
_i18n/fr/resources/moneropedia/remote-node.md
Normal file
23
_i18n/fr/resources/moneropedia/remote-node.md
Normal file
|
@ -0,0 +1,23 @@
|
||||||
|
---
|
||||||
|
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"
|
||||||
|
---
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
An **Open remote node** can be used by people who, for their own reasons (usually because of hardware requirements, disk space, or technical abilities), cannot/don't want to run their own node and prefer to relay on one publicly available on the Monero network. Open remote nodes are often simply referred as "remote nodes".
|
||||||
|
|
||||||
|
Using an open node will allow to make a @transaction instantaneously, without the need to download the @blockchain and sync to the Monero network first, but at the cost of the control over your privacy. the Monero community suggests to always run your own node to obtain the maximum privacy possible and to help decentralize the network.
|
||||||
|
|
||||||
|
### Public Nodes
|
||||||
|
|
||||||
|
Open nodes are cool because, as we said above, allow people who are not running their own node to immediately join the Monero network. There are 2 main ways to connect to an open node: Simply get somebody to share with you their node, by asking them to "open it" and provide you with IP address and port, or use a public one.
|
||||||
|
|
||||||
|
Public nodes are reachable in the network using two systems:
|
||||||
|
|
||||||
|
- **Node aggregators**, which are basically lists of open remote nodes. The operators of those nodes decided to add them to the aggregator so that other people can use them. The aggregator will provide to the person who want to use a remote node a simple URL. This URL connects to one of the nodes in the list and will need to be inserted in the Monero wallet (GUI or CLI). The wallet will then contact one of the nodes provided by the URL and will allow the end user to immediately receive and send transactions. One of the most famous node aggregators is [MoneroWorld](https://moneroworld.com/#nodes).
|
||||||
|
- **Native public nodes**. This is one of the new coolest features the Monero devs came up with to improve the user experience and to make easier to connect to the network. The CLI wallet allow to make a node public by simply adding the flag `--public-node`. Doing so, it will be advertised on the P2P network and people will be able to connect to it (or to another public node advertising itself in the same way) using the related option in the GUI and CLI wallets.
|
||||||
|
|
||||||
|
Be aware that using public remote nodes can be risky. Node operators can link transactions to IP addresses. These risks can be mitigated, but you should always avoid using them if you have the possibility. Run your own node!
|
|
@ -631,6 +631,7 @@ moneropedia:
|
||||||
paperwallet: Portafoglio cartaceo
|
paperwallet: Portafoglio cartaceo
|
||||||
paymentid: ID Pagamento
|
paymentid: ID Pagamento
|
||||||
pedersen-commitment: Pedersen Commitment
|
pedersen-commitment: Pedersen Commitment
|
||||||
|
remote-node: Remote Node
|
||||||
reseed: Reseed
|
reseed: Reseed
|
||||||
ringCT: Ring CT
|
ringCT: Ring CT
|
||||||
ringsignatures: Firma ad anello
|
ringsignatures: Firma ad anello
|
||||||
|
|
23
_i18n/it/resources/moneropedia/remote-node.md
Normal file
23
_i18n/it/resources/moneropedia/remote-node.md
Normal file
|
@ -0,0 +1,23 @@
|
||||||
|
---
|
||||||
|
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"
|
||||||
|
---
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
An **Open remote node** can be used by people who, for their own reasons (usually because of hardware requirements, disk space, or technical abilities), cannot/don't want to run their own node and prefer to relay on one publicly available on the Monero network. Open remote nodes are often simply referred as "remote nodes".
|
||||||
|
|
||||||
|
Using an open node will allow to make a @transaction instantaneously, without the need to download the @blockchain and sync to the Monero network first, but at the cost of the control over your privacy. the Monero community suggests to always run your own node to obtain the maximum privacy possible and to help decentralize the network.
|
||||||
|
|
||||||
|
### Public Nodes
|
||||||
|
|
||||||
|
Open nodes are cool because, as we said above, allow people who are not running their own node to immediately join the Monero network. There are 2 main ways to connect to an open node: Simply get somebody to share with you their node, by asking them to "open it" and provide you with IP address and port, or use a public one.
|
||||||
|
|
||||||
|
Public nodes are reachable in the network using two systems:
|
||||||
|
|
||||||
|
- **Node aggregators**, which are basically lists of open remote nodes. The operators of those nodes decided to add them to the aggregator so that other people can use them. The aggregator will provide to the person who want to use a remote node a simple URL. This URL connects to one of the nodes in the list and will need to be inserted in the Monero wallet (GUI or CLI). The wallet will then contact one of the nodes provided by the URL and will allow the end user to immediately receive and send transactions. One of the most famous node aggregators is [MoneroWorld](https://moneroworld.com/#nodes).
|
||||||
|
- **Native public nodes**. This is one of the new coolest features the Monero devs came up with to improve the user experience and to make easier to connect to the network. The CLI wallet allow to make a node public by simply adding the flag `--public-node`. Doing so, it will be advertised on the P2P network and people will be able to connect to it (or to another public node advertising itself in the same way) using the related option in the GUI and CLI wallets.
|
||||||
|
|
||||||
|
Be aware that using public remote nodes can be risky. Node operators can link transactions to IP addresses. These risks can be mitigated, but you should always avoid using them if you have the possibility. Run your own node!
|
|
@ -634,6 +634,7 @@ moneropedia:
|
||||||
paperwallet: Paper Wallet
|
paperwallet: Paper Wallet
|
||||||
paymentid: Payment ID
|
paymentid: Payment ID
|
||||||
pedersen-commitment: Pedersen Commitment
|
pedersen-commitment: Pedersen Commitment
|
||||||
|
remote-node: Remote Node
|
||||||
reseed: Reseed
|
reseed: Reseed
|
||||||
ringCT: Ring CT
|
ringCT: Ring CT
|
||||||
ringsignatures: Ring Signature
|
ringsignatures: Ring Signature
|
||||||
|
|
23
_i18n/nl/resources/moneropedia/remote-node.md
Normal file
23
_i18n/nl/resources/moneropedia/remote-node.md
Normal file
|
@ -0,0 +1,23 @@
|
||||||
|
---
|
||||||
|
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"
|
||||||
|
---
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
An **Open remote node** can be used by people who, for their own reasons (usually because of hardware requirements, disk space, or technical abilities), cannot/don't want to run their own node and prefer to relay on one publicly available on the Monero network. Open remote nodes are often simply referred as "remote nodes".
|
||||||
|
|
||||||
|
Using an open node will allow to make a @transaction instantaneously, without the need to download the @blockchain and sync to the Monero network first, but at the cost of the control over your privacy. the Monero community suggests to always run your own node to obtain the maximum privacy possible and to help decentralize the network.
|
||||||
|
|
||||||
|
### Public Nodes
|
||||||
|
|
||||||
|
Open nodes are cool because, as we said above, allow people who are not running their own node to immediately join the Monero network. There are 2 main ways to connect to an open node: Simply get somebody to share with you their node, by asking them to "open it" and provide you with IP address and port, or use a public one.
|
||||||
|
|
||||||
|
Public nodes are reachable in the network using two systems:
|
||||||
|
|
||||||
|
- **Node aggregators**, which are basically lists of open remote nodes. The operators of those nodes decided to add them to the aggregator so that other people can use them. The aggregator will provide to the person who want to use a remote node a simple URL. This URL connects to one of the nodes in the list and will need to be inserted in the Monero wallet (GUI or CLI). The wallet will then contact one of the nodes provided by the URL and will allow the end user to immediately receive and send transactions. One of the most famous node aggregators is [MoneroWorld](https://moneroworld.com/#nodes).
|
||||||
|
- **Native public nodes**. This is one of the new coolest features the Monero devs came up with to improve the user experience and to make easier to connect to the network. The CLI wallet allow to make a node public by simply adding the flag `--public-node`. Doing so, it will be advertised on the P2P network and people will be able to connect to it (or to another public node advertising itself in the same way) using the related option in the GUI and CLI wallets.
|
||||||
|
|
||||||
|
Be aware that using public remote nodes can be risky. Node operators can link transactions to IP addresses. These risks can be mitigated, but you should always avoid using them if you have the possibility. Run your own node!
|
|
@ -633,6 +633,7 @@ moneropedia:
|
||||||
paperwallet: Papierowy portfel
|
paperwallet: Papierowy portfel
|
||||||
paymentid: Numer identyfikacyjny płatności
|
paymentid: Numer identyfikacyjny płatności
|
||||||
pedersen-commitment: Zobowiązanie Pedersena
|
pedersen-commitment: Zobowiązanie Pedersena
|
||||||
|
remote-node: Remote Node
|
||||||
reseed: Reseed
|
reseed: Reseed
|
||||||
ringCT: Poufne Transakcje Pierścieniowe
|
ringCT: Poufne Transakcje Pierścieniowe
|
||||||
ringsignatures: Podpis pierścieniowy
|
ringsignatures: Podpis pierścieniowy
|
||||||
|
|
23
_i18n/pl/resources/moneropedia/remote-node.md
Normal file
23
_i18n/pl/resources/moneropedia/remote-node.md
Normal file
|
@ -0,0 +1,23 @@
|
||||||
|
---
|
||||||
|
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"
|
||||||
|
---
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
An **Open remote node** can be used by people who, for their own reasons (usually because of hardware requirements, disk space, or technical abilities), cannot/don't want to run their own node and prefer to relay on one publicly available on the Monero network. Open remote nodes are often simply referred as "remote nodes".
|
||||||
|
|
||||||
|
Using an open node will allow to make a @transaction instantaneously, without the need to download the @blockchain and sync to the Monero network first, but at the cost of the control over your privacy. the Monero community suggests to always run your own node to obtain the maximum privacy possible and to help decentralize the network.
|
||||||
|
|
||||||
|
### Public Nodes
|
||||||
|
|
||||||
|
Open nodes are cool because, as we said above, allow people who are not running their own node to immediately join the Monero network. There are 2 main ways to connect to an open node: Simply get somebody to share with you their node, by asking them to "open it" and provide you with IP address and port, or use a public one.
|
||||||
|
|
||||||
|
Public nodes are reachable in the network using two systems:
|
||||||
|
|
||||||
|
- **Node aggregators**, which are basically lists of open remote nodes. The operators of those nodes decided to add them to the aggregator so that other people can use them. The aggregator will provide to the person who want to use a remote node a simple URL. This URL connects to one of the nodes in the list and will need to be inserted in the Monero wallet (GUI or CLI). The wallet will then contact one of the nodes provided by the URL and will allow the end user to immediately receive and send transactions. One of the most famous node aggregators is [MoneroWorld](https://moneroworld.com/#nodes).
|
||||||
|
- **Native public nodes**. This is one of the new coolest features the Monero devs came up with to improve the user experience and to make easier to connect to the network. The CLI wallet allow to make a node public by simply adding the flag `--public-node`. Doing so, it will be advertised on the P2P network and people will be able to connect to it (or to another public node advertising itself in the same way) using the related option in the GUI and CLI wallets.
|
||||||
|
|
||||||
|
Be aware that using public remote nodes can be risky. Node operators can link transactions to IP addresses. These risks can be mitigated, but you should always avoid using them if you have the possibility. Run your own node!
|
|
@ -634,6 +634,7 @@ moneropedia:
|
||||||
paperwallet: Carteira em Papel
|
paperwallet: Carteira em Papel
|
||||||
paymentid: ID de Pagamento
|
paymentid: ID de Pagamento
|
||||||
pedersen-commitment: Comprometimento de Pedersen
|
pedersen-commitment: Comprometimento de Pedersen
|
||||||
|
remote-node: Remote Node
|
||||||
reseed: Reseed
|
reseed: Reseed
|
||||||
ringCT: Ring CT
|
ringCT: Ring CT
|
||||||
ringsignatures: Assinaturas em anel
|
ringsignatures: Assinaturas em anel
|
||||||
|
|
23
_i18n/pt-br/resources/moneropedia/remote-node.md
Normal file
23
_i18n/pt-br/resources/moneropedia/remote-node.md
Normal file
|
@ -0,0 +1,23 @@
|
||||||
|
---
|
||||||
|
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"
|
||||||
|
---
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
An **Open remote node** can be used by people who, for their own reasons (usually because of hardware requirements, disk space, or technical abilities), cannot/don't want to run their own node and prefer to relay on one publicly available on the Monero network. Open remote nodes are often simply referred as "remote nodes".
|
||||||
|
|
||||||
|
Using an open node will allow to make a @transaction instantaneously, without the need to download the @blockchain and sync to the Monero network first, but at the cost of the control over your privacy. the Monero community suggests to always run your own node to obtain the maximum privacy possible and to help decentralize the network.
|
||||||
|
|
||||||
|
### Public Nodes
|
||||||
|
|
||||||
|
Open nodes are cool because, as we said above, allow people who are not running their own node to immediately join the Monero network. There are 2 main ways to connect to an open node: Simply get somebody to share with you their node, by asking them to "open it" and provide you with IP address and port, or use a public one.
|
||||||
|
|
||||||
|
Public nodes are reachable in the network using two systems:
|
||||||
|
|
||||||
|
- **Node aggregators**, which are basically lists of open remote nodes. The operators of those nodes decided to add them to the aggregator so that other people can use them. The aggregator will provide to the person who want to use a remote node a simple URL. This URL connects to one of the nodes in the list and will need to be inserted in the Monero wallet (GUI or CLI). The wallet will then contact one of the nodes provided by the URL and will allow the end user to immediately receive and send transactions. One of the most famous node aggregators is [MoneroWorld](https://moneroworld.com/#nodes).
|
||||||
|
- **Native public nodes**. This is one of the new coolest features the Monero devs came up with to improve the user experience and to make easier to connect to the network. The CLI wallet allow to make a node public by simply adding the flag `--public-node`. Doing so, it will be advertised on the P2P network and people will be able to connect to it (or to another public node advertising itself in the same way) using the related option in the GUI and CLI wallets.
|
||||||
|
|
||||||
|
Be aware that using public remote nodes can be risky. Node operators can link transactions to IP addresses. These risks can be mitigated, but you should always avoid using them if you have the possibility. Run your own node!
|
|
@ -638,6 +638,7 @@ moneropedia:
|
||||||
paperwallet: Бумажный кошелёк
|
paperwallet: Бумажный кошелёк
|
||||||
paymentid: Идентификатор платежа
|
paymentid: Идентификатор платежа
|
||||||
pedersen-commitment: Обязательство Педерсена
|
pedersen-commitment: Обязательство Педерсена
|
||||||
|
remote-node: Remote Node
|
||||||
reseed: Повторное заполнение
|
reseed: Повторное заполнение
|
||||||
ringCT: Ring CT
|
ringCT: Ring CT
|
||||||
ringsignatures: Кольцевая подпись
|
ringsignatures: Кольцевая подпись
|
||||||
|
|
23
_i18n/ru/resources/moneropedia/remote-node.md
Normal file
23
_i18n/ru/resources/moneropedia/remote-node.md
Normal file
|
@ -0,0 +1,23 @@
|
||||||
|
---
|
||||||
|
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"
|
||||||
|
---
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
An **Open remote node** can be used by people who, for their own reasons (usually because of hardware requirements, disk space, or technical abilities), cannot/don't want to run their own node and prefer to relay on one publicly available on the Monero network. Open remote nodes are often simply referred as "remote nodes".
|
||||||
|
|
||||||
|
Using an open node will allow to make a @transaction instantaneously, without the need to download the @blockchain and sync to the Monero network first, but at the cost of the control over your privacy. the Monero community suggests to always run your own node to obtain the maximum privacy possible and to help decentralize the network.
|
||||||
|
|
||||||
|
### Public Nodes
|
||||||
|
|
||||||
|
Open nodes are cool because, as we said above, allow people who are not running their own node to immediately join the Monero network. There are 2 main ways to connect to an open node: Simply get somebody to share with you their node, by asking them to "open it" and provide you with IP address and port, or use a public one.
|
||||||
|
|
||||||
|
Public nodes are reachable in the network using two systems:
|
||||||
|
|
||||||
|
- **Node aggregators**, which are basically lists of open remote nodes. The operators of those nodes decided to add them to the aggregator so that other people can use them. The aggregator will provide to the person who want to use a remote node a simple URL. This URL connects to one of the nodes in the list and will need to be inserted in the Monero wallet (GUI or CLI). The wallet will then contact one of the nodes provided by the URL and will allow the end user to immediately receive and send transactions. One of the most famous node aggregators is [MoneroWorld](https://moneroworld.com/#nodes).
|
||||||
|
- **Native public nodes**. This is one of the new coolest features the Monero devs came up with to improve the user experience and to make easier to connect to the network. The CLI wallet allow to make a node public by simply adding the flag `--public-node`. Doing so, it will be advertised on the P2P network and people will be able to connect to it (or to another public node advertising itself in the same way) using the related option in the GUI and CLI wallets.
|
||||||
|
|
||||||
|
Be aware that using public remote nodes can be risky. Node operators can link transactions to IP addresses. These risks can be mitigated, but you should always avoid using them if you have the possibility. Run your own node!
|
|
@ -633,6 +633,7 @@ moneropedia:
|
||||||
paperwallet: Kâğıt Cüzdan
|
paperwallet: Kâğıt Cüzdan
|
||||||
paymentid: Ödeme ID
|
paymentid: Ödeme ID
|
||||||
pedersen-commitment: Pedersen Üstlenmesi
|
pedersen-commitment: Pedersen Üstlenmesi
|
||||||
|
remote-node: Remote Node
|
||||||
reseed: Tekrar-tohum
|
reseed: Tekrar-tohum
|
||||||
ringCT: Halka CT
|
ringCT: Halka CT
|
||||||
ringsignatures: Halka İmza
|
ringsignatures: Halka İmza
|
||||||
|
|
23
_i18n/tr/resources/moneropedia/remote-node.md
Normal file
23
_i18n/tr/resources/moneropedia/remote-node.md
Normal file
|
@ -0,0 +1,23 @@
|
||||||
|
---
|
||||||
|
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"
|
||||||
|
---
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
An **Open remote node** can be used by people who, for their own reasons (usually because of hardware requirements, disk space, or technical abilities), cannot/don't want to run their own node and prefer to relay on one publicly available on the Monero network. Open remote nodes are often simply referred as "remote nodes".
|
||||||
|
|
||||||
|
Using an open node will allow to make a @transaction instantaneously, without the need to download the @blockchain and sync to the Monero network first, but at the cost of the control over your privacy. the Monero community suggests to always run your own node to obtain the maximum privacy possible and to help decentralize the network.
|
||||||
|
|
||||||
|
### Public Nodes
|
||||||
|
|
||||||
|
Open nodes are cool because, as we said above, allow people who are not running their own node to immediately join the Monero network. There are 2 main ways to connect to an open node: Simply get somebody to share with you their node, by asking them to "open it" and provide you with IP address and port, or use a public one.
|
||||||
|
|
||||||
|
Public nodes are reachable in the network using two systems:
|
||||||
|
|
||||||
|
- **Node aggregators**, which are basically lists of open remote nodes. The operators of those nodes decided to add them to the aggregator so that other people can use them. The aggregator will provide to the person who want to use a remote node a simple URL. This URL connects to one of the nodes in the list and will need to be inserted in the Monero wallet (GUI or CLI). The wallet will then contact one of the nodes provided by the URL and will allow the end user to immediately receive and send transactions. One of the most famous node aggregators is [MoneroWorld](https://moneroworld.com/#nodes).
|
||||||
|
- **Native public nodes**. This is one of the new coolest features the Monero devs came up with to improve the user experience and to make easier to connect to the network. The CLI wallet allow to make a node public by simply adding the flag `--public-node`. Doing so, it will be advertised on the P2P network and people will be able to connect to it (or to another public node advertising itself in the same way) using the related option in the GUI and CLI wallets.
|
||||||
|
|
||||||
|
Be aware that using public remote nodes can be risky. Node operators can link transactions to IP addresses. These risks can be mitigated, but you should always avoid using them if you have the possibility. Run your own node!
|
|
@ -632,6 +632,7 @@ moneropedia:
|
||||||
paperwallet: 纸钱包
|
paperwallet: 纸钱包
|
||||||
paymentid: 付款ID
|
paymentid: 付款ID
|
||||||
pedersen-commitment: Pedersen Commitment
|
pedersen-commitment: Pedersen Commitment
|
||||||
|
remote-node: Remote Node
|
||||||
reseed: Reseed
|
reseed: Reseed
|
||||||
ringCT: 环交易
|
ringCT: 环交易
|
||||||
ringsignatures: 环签名
|
ringsignatures: 环签名
|
||||||
|
|
23
_i18n/zh-cn/resources/moneropedia/remote-node.md
Normal file
23
_i18n/zh-cn/resources/moneropedia/remote-node.md
Normal file
|
@ -0,0 +1,23 @@
|
||||||
|
---
|
||||||
|
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"
|
||||||
|
---
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
An **Open remote node** can be used by people who, for their own reasons (usually because of hardware requirements, disk space, or technical abilities), cannot/don't want to run their own node and prefer to relay on one publicly available on the Monero network. Open remote nodes are often simply referred as "remote nodes".
|
||||||
|
|
||||||
|
Using an open node will allow to make a @transaction instantaneously, without the need to download the @blockchain and sync to the Monero network first, but at the cost of the control over your privacy. the Monero community suggests to always run your own node to obtain the maximum privacy possible and to help decentralize the network.
|
||||||
|
|
||||||
|
### Public Nodes
|
||||||
|
|
||||||
|
Open nodes are cool because, as we said above, allow people who are not running their own node to immediately join the Monero network. There are 2 main ways to connect to an open node: Simply get somebody to share with you their node, by asking them to "open it" and provide you with IP address and port, or use a public one.
|
||||||
|
|
||||||
|
Public nodes are reachable in the network using two systems:
|
||||||
|
|
||||||
|
- **Node aggregators**, which are basically lists of open remote nodes. The operators of those nodes decided to add them to the aggregator so that other people can use them. The aggregator will provide to the person who want to use a remote node a simple URL. This URL connects to one of the nodes in the list and will need to be inserted in the Monero wallet (GUI or CLI). The wallet will then contact one of the nodes provided by the URL and will allow the end user to immediately receive and send transactions. One of the most famous node aggregators is [MoneroWorld](https://moneroworld.com/#nodes).
|
||||||
|
- **Native public nodes**. This is one of the new coolest features the Monero devs came up with to improve the user experience and to make easier to connect to the network. The CLI wallet allow to make a node public by simply adding the flag `--public-node`. Doing so, it will be advertised on the P2P network and people will be able to connect to it (or to another public node advertising itself in the same way) using the related option in the GUI and CLI wallets.
|
||||||
|
|
||||||
|
Be aware that using public remote nodes can be risky. Node operators can link transactions to IP addresses. These risks can be mitigated, but you should always avoid using them if you have the possibility. Run your own node!
|
|
@ -631,6 +631,7 @@ moneropedia:
|
||||||
paperwallet: Paper Wallet
|
paperwallet: Paper Wallet
|
||||||
paymentid: Payment ID
|
paymentid: Payment ID
|
||||||
pedersen-commitment: Pedersen Commitment
|
pedersen-commitment: Pedersen Commitment
|
||||||
|
remote-node: Remote Node
|
||||||
reseed: Reseed
|
reseed: Reseed
|
||||||
ringCT: Ring CT
|
ringCT: Ring CT
|
||||||
ringsignatures: Ring Signature
|
ringsignatures: Ring Signature
|
||||||
|
|
23
_i18n/zh-tw/resources/moneropedia/remote-node.md
Normal file
23
_i18n/zh-tw/resources/moneropedia/remote-node.md
Normal file
|
@ -0,0 +1,23 @@
|
||||||
|
---
|
||||||
|
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"
|
||||||
|
---
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
An **Open remote node** can be used by people who, for their own reasons (usually because of hardware requirements, disk space, or technical abilities), cannot/don't want to run their own node and prefer to relay on one publicly available on the Monero network. Open remote nodes are often simply referred as "remote nodes".
|
||||||
|
|
||||||
|
Using an open node will allow to make a @transaction instantaneously, without the need to download the @blockchain and sync to the Monero network first, but at the cost of the control over your privacy. the Monero community suggests to always run your own node to obtain the maximum privacy possible and to help decentralize the network.
|
||||||
|
|
||||||
|
### Public Nodes
|
||||||
|
|
||||||
|
Open nodes are cool because, as we said above, allow people who are not running their own node to immediately join the Monero network. There are 2 main ways to connect to an open node: Simply get somebody to share with you their node, by asking them to "open it" and provide you with IP address and port, or use a public one.
|
||||||
|
|
||||||
|
Public nodes are reachable in the network using two systems:
|
||||||
|
|
||||||
|
- **Node aggregators**, which are basically lists of open remote nodes. The operators of those nodes decided to add them to the aggregator so that other people can use them. The aggregator will provide to the person who want to use a remote node a simple URL. This URL connects to one of the nodes in the list and will need to be inserted in the Monero wallet (GUI or CLI). The wallet will then contact one of the nodes provided by the URL and will allow the end user to immediately receive and send transactions. One of the most famous node aggregators is [MoneroWorld](https://moneroworld.com/#nodes).
|
||||||
|
- **Native public nodes**. This is one of the new coolest features the Monero devs came up with to improve the user experience and to make easier to connect to the network. The CLI wallet allow to make a node public by simply adding the flag `--public-node`. Doing so, it will be advertised on the P2P network and people will be able to connect to it (or to another public node advertising itself in the same way) using the related option in the GUI and CLI wallets.
|
||||||
|
|
||||||
|
Be aware that using public remote nodes can be risky. Node operators can link transactions to IP addresses. These risks can be mitigated, but you should always avoid using them if you have the possibility. Run your own node!
|
Loading…
Reference in a new issue