Add links to 'remote-node' in Downloads page and 'bootstrap-node' Moneropedia entry

This commit is contained in:
erciccione 2020-03-02 19:41:25 +01:00
parent 82b2246a43
commit 617f17af8e
No known key found for this signature in database
GPG Key ID: 762AF8C608E56CDF
2 changed files with 3 additions and 3 deletions

View File

@ -157,7 +157,7 @@ downloads:
hardware: Hardware Wallets
gui_intro: The GUI wallet provides a nice user interface, adaptable to all kinds of users, but it is especially recommended for less technical people who want to quickly send and receive XMR.
simplemode: Simple mode
simplemode1: Created for less technical users who only want to use Monero in the easiest and quickest way possible. Open the wallet, automatically connect to a remote node, send/receive XMR, done!
simplemode1: Created for less technical users who only want to use Monero in the easiest and quickest way possible. Open the wallet, automatically connect to a @remote-node, send/receive XMR, done!
advancedmode: Advanced mode
advancedmode1: With all the advanced features you could need. Ideal for seasoned Monero users who prefer to have full control of their wallet and node
merchantpage: Merchant page
@ -187,7 +187,7 @@ downloads:
transacttor: Transactions over Tor/I2P
transacttor1: For an additional layer of privacy
bootstrapnode: Bootstrap node
bootstrapnode1: Use a remote node while downloading the blockchain locally, this will allow you to use Monero immediately and switch to your local node once it's completely synced
bootstrapnode1: Use a @remote-node while downloading the blockchain locally, this will allow you to use Monero immediately and switch to your local node once it's completely synced
rpc: RPC Wallet and Daemon
rpc1: included in the archive
payforrpc: Pay-for-RPC

View File

@ -5,7 +5,7 @@ summary: "A node to which a daemon connects to give immediate usability to walle
### 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.
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.
To allow the @wallet to be immediately usable, the daemon on the local @node uses a bootstrap node to which the RPC request are proxying to, giving access to the missing @blocks.