mirror of
https://github.com/monero-project/monero-site.git
synced 2024-09-29 05:51:04 +00:00
luigi1111
GitHub
commit
b1d46c2001
12 changed files with 14 additions and 14 deletions
|
|
@ -355,7 +355,7 @@ faq:
|
|||
qnofunds: I can't see my funds. Did I just lose all my Monero?
|
||||
anofunds: "You probably didn't. It's very hard to simply 'lose' your coins, since they are technically nowhere. Your coins 'live' on the blockchain and are linked to your account through a system of public and private keys secured by cryptography. That's why if you don't see your funds, it's probably because of a technical issue. Take a look at the 'Resources & Help' section at the top of this page for a list of useful resources that will help you identify and fix your problem."
|
||||
qnodetor: How can I connect my node via Tor?
|
||||
anodetor: Support for Tor is still in its infancies, but it's already possible to natively send transactions through the network and to run a Monero daemon on the Tor network. Better Tor and I2P integrations are in progress.
|
||||
anodetor: Support for Tor is still in its infancies, but it's already possible to natively send transactions through the network and to run a Monero @daemon on the Tor network. Better Tor and I2P integrations are in progress.
|
||||
qfullpruned: How do I decide if I should run a full node or a pruned node?
|
||||
afullpruned: "A full @node requires a considerable amount of storage and could take a long time to download and verify the entire blockchain, especially on older hardware. If you have limited storage, a pruned node is recommended. It only stores 1/8th of unnecessary blockchain data while keeping the full transaction history. If plenty of storage is available, a full node is recommended but a pruned node still greatly contributes to the network and improves your privacy."
|
||||
qblockspace: Why does the blockchain need so much space?
|
||||
|
|
@ -369,7 +369,7 @@ faq:
|
|||
qdangerrnode: Is it dangerous to use a remote node? What's the data a node operator can get from me?
|
||||
adangerrnode: "It's always advisable, especially for privacy-conscious users, to use a personal node when transacting on the network to achieve the highest rate of privacy. Some people for convenience prefer to use @remote-node which are not under their control (public nodes). The convenience of not having to deal with a personal copy of the @blockchain comes at a cost: lessened privacy. A remote node operator is able to see from what IP address a transaction comes from (even if cannot see the recipient nor the amount) and in some extreme cases, can make attacks able to reduce your privacy. Some dangers can be mitigated by using remote nodes on the Tor or I2P networks or using a VPN."
|
||||
qantivirus: Why is my antivirus/firewall flagging the Monero software i just downloaded as malware?
|
||||
aantivirus: After you have downloaded the Monero software (GUI and CLI alike), your antivirus or firewall may flag the executables as malware. Some antiviruses only warn you about the possible menace, others go as far as silently removing your downloaded wallet/daemon. This likely happens because of the integrated miner, which is used for mining and for @block verification. Some antiviruses may erroneously consider the miner as dangerous software and act to remove it.
|
||||
aantivirus: After you have downloaded the Monero software (GUI and CLI alike), your antivirus or firewall may flag the executables as malware. Some antiviruses only warn you about the possible menace, others go as far as silently removing your downloaded @wallet / @daemon. This likely happens because of the integrated miner, which is used for mining and for @block verification. Some antiviruses may erroneously consider the miner as dangerous software and act to remove it.
|
||||
aantivirus1: The problem is being discussed and solutions are being elaborated. In the meantime, if you get a warning from your antivirus, make sure the software you downloaded is legitimate (see the guides linked below), then add an exception for it in your antivirus, so that it won't get removed or blocked. If you need assistance, feel free to contact the community.
|
||||
qmoneromeaning: "Why is Monero called 'Monero'?"
|
||||
amoneromeaning: "Monero is an Esperanto word which means 'coin'. Initially Monero was called 'Bitmonero', which translates to 'Bitcoin' in Esperanto. After the community decided to fork from the original maintainer, 'bit' was dropped in favour of simply 'Monero'."
|
||||
|
|
@ -432,7 +432,7 @@ developer-guides:
|
|||
outdated: "Methods are often added / removed / updated and may not be accurately described."
|
||||
rpc: RPC Documentation
|
||||
daemonrpc: Daemon RPC
|
||||
daemonrpc_descr: RPC calls for the daemon. Including input, outputs and examples. In English.
|
||||
daemonrpc_descr: RPC calls for the @daemon. Including input, outputs and examples. In English.
|
||||
walletrpc: Wallet RPC
|
||||
walletrpc_descr: monero-wallet-rpc calls. Including input, outputs and examples. In English.
|
||||
external: External resources
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ Generated new wallet: 4B15ZjveuttEaTmfZjLVioPVw7bfSmRLpSgB33CJbuC6BoGtZrug9TDAmh
|
|||
view key: 4130fa26463d9451781771a8baa5d0b8085c47c4500cefe4746bab48f1d15903
|
||||
**********************************************************************
|
||||
Your wallet has been generated.
|
||||
To start synchronizing with the daemon, use "refresh" command.
|
||||
To start synchronizing with the @daemon, use "refresh" command.
|
||||
Use "help" command to see the list of available commands.
|
||||
Always use "exit" command when closing monero-wallet-cli to save your
|
||||
current session's state. Otherwise, you might need to synchronize
|
||||
|
|
|
|||
|
|
@ -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 not 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 not 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.
|
||||
|
||||
|
|
|
|||
|
|
@ -18,6 +18,6 @@ Open nodes are cool because, as we said above, allow people who are not running
|
|||
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 daemon allows 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.
|
||||
- **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 @daemon allows 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!
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@
|
|||
|
||||
- Copy the Monero binaries to a RAM disk (/dev/shm in Linux, Windows bootable ISOs normally have a Z: drive or something)
|
||||
|
||||
- Don't run the Monero daemon. Instead, using the command line, use monero-wallet-cli to create a new Monero @account
|
||||
- Don't run the Monero @daemon. Instead, using the command line, use monero-wallet-cli to create a new Monero @account
|
||||
|
||||
- When prompted for a name, give it any name, it doesn't really matter
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
With [Qubes](https://qubes-os.org) + [Whonix](https://whonix.org) you can have a Monero wallet that is without networking and running on a virtually isolated system from the Monero daemon which has all of its traffic forced over [Tor](https://torproject.org).
|
||||
|
||||
Qubes gives the flexibility to easily create separate VMs for different purposes. First you will create a Whonix workstation for the wallet with no networking. Next, another Whonix workstation for the daemon which will use your Whonix gateway as it's NetVM. For communication between the wallet and daemon you can make use of Qubes [qrexec](https://www.qubes-os.org/doc/qrexec3/).
|
||||
Qubes gives the flexibility to easily create separate VMs for different purposes. First you will create a Whonix workstation for the wallet with no networking. Next, another Whonix workstation for the @daemon which will use your Whonix gateway as it's NetVM. For communication between the wallet and daemon you can make use of Qubes [qrexec](https://www.qubes-os.org/doc/qrexec3/).
|
||||
|
||||
This is safer than other approaches which route the wallets rpc over a Tor hidden service, or that use physical isolation but still have networking to connect to the daemon. In this way you don't need any network connection on the wallet, you preserve resources of the Tor network, and there is less latency.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
### Purpose and Warning
|
||||
|
||||
Most people don't need this. To use Monero, just start the software and it will synchronize itself with the peer-to-peer network. Normally, this is much faster than downloading and importing the blockchain as detailed in this guide. This is because you'll be downloading from many peers instead of just a single server, and the Monero daemon will verify each block as it's received, instead of verifying separately after downloading.
|
||||
Most people don't need this. To use Monero, just start the software and it will synchronize itself with the peer-to-peer network. Normally, this is much faster than downloading and importing the blockchain as detailed in this guide. This is because you'll be downloading from many peers instead of just a single server, and the Monero @daemon will verify each block as it's received, instead of verifying separately after downloading.
|
||||
|
||||
This option is mostly useful for development, or possibly if some unusual problem is preventing you from syncing the normal way.
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ We first have to ensure that we're sufficiently prepared. This entails the follo
|
|||
|
||||
4. Your Ledger needs to be plugged in and the Ledger Monero app should be running.
|
||||
|
||||
5. Either your daemon (`monerod.exe`) should be running and preferably be fully synced or you should connect to a remote node.
|
||||
5. Either your @daemon (`monerod.exe`) should be running and preferably be fully synced or you should connect to a remote node.
|
||||
|
||||
Now that we're sufficiently prepared, let's start!
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ This guide will show how to perform various operations from the `monero-wallet-c
|
|||
## Checking your balance
|
||||
|
||||
Since the blockchain handling and the wallet are separate programs, many uses of `monero-wallet-cli`
|
||||
need to work with the daemon. This includes looking for incoming transactions to your address.
|
||||
need to work with the @daemon. This includes looking for incoming transactions to your address.
|
||||
Once you are running both `monero-wallet-cli` and `monerod`, enter `balance`.
|
||||
|
||||
Example:
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ On the next page, give your wallet a strong password and confirm it before click
|
|||
|
||||
|
||||
|
||||
Specify your daemon settings and click the `Right` arrow:
|
||||
Specify your @daemon settings and click the `Right` arrow:
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
Below we'll show an example configuration that allows you to run a Monero daemon (eg on a home server or VPS) that you can connect to from another computer running your wallet. We do this over the Tor anonymity network to retrieve the transaction information needed by your wallet. The benefit of this approach is that the daemon (`monerod`) can stay on all of the time sending / receiving blocks, while the wallet can connect when needed and have access to the full blockchain. [Monerujo](https://www.monerujo.io/) should also work via [Orbot](https://guardianproject.info/apps/org.torproject.android/). Because Tor hidden services provide encryption and authentication, you can be confident that your RPC credentials will not be sent in the clear. Tor also solves problems often seen on home servers related to port-forwarding, IP addresses changing, etc -- it just works. This setup will also obfuscate the fact that you are connecting to a remote Monero node. Tested with Monero `v0.15.0.1` connecting a Mac laptop wallet to a remote Linux node (Ubuntu 18.04.2).
|
||||
Below we'll show an example configuration that allows you to run a Monero @daemon (eg on a home server or VPS) that you can connect to from another computer running your wallet. We do this over the Tor anonymity network to retrieve the transaction information needed by your wallet. The benefit of this approach is that the daemon (`monerod`) can stay on all of the time sending / receiving blocks, while the wallet can connect when needed and have access to the full blockchain. [Monerujo](https://www.monerujo.io/) should also work via [Orbot](https://guardianproject.info/apps/org.torproject.android/). Because Tor hidden services provide encryption and authentication, you can be confident that your RPC credentials will not be sent in the clear. Tor also solves problems often seen on home servers related to port-forwarding, IP addresses changing, etc -- it just works. This setup will also obfuscate the fact that you are connecting to a remote Monero node. Tested with Monero `v0.15.0.1` connecting a Mac laptop wallet to a remote Linux node (Ubuntu 18.04.2).
|
||||
|
||||
## Create a Tor hidden service for RPC
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
# monerod
|
||||
|
||||
`monerod` is the daemon software that ships with the Monero tree. It is a console program, and manages the blockchain. While a bitcoin wallet manages both an account and the blockchain, Monero separates these: `monerod` handles the blockchain, and `monero-wallet-cli` handles the account.
|
||||
`monerod` is the @daemon software that ships with the Monero tree. It is a console program, and manages the blockchain. While a bitcoin wallet manages both an account and the blockchain, Monero separates these: `monerod` handles the blockchain, and `monero-wallet-cli` handles the account.
|
||||
|
||||
This guide assumes you have already set up your VPS account and are using SSH to tunnel into the server console.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue