There are several advantages where I2P implementation is more suitable over Tor, e.g.
I2P is significantly faster when routing internal traffic, where Tor is optimized for low-bandwidth clients and high-bandwidth exit nodes,
I2P doesn't have floodfill routers hardcoded as Tor's directory of servers,
I2P is a packet-switched network (as opposed to circuit-...
Despite both being advertised as privacy-focused cryptocurrencies, they are very different.
Monero uses ring signatures, RingCT, and stealth addresses to hide information on the blockchain. For every transaction, there is no way for an outside observer to determine the sending address, the amount sent, or the receiving address. Optional ...
On the daemon side (bitmonerod)
P2P Port is the one used to connect with the other nodes on the network (or locally in some cases).
RPC port (Remote Procedure Call) is used to let other applications such as simplewallet or the GUI interact with the daemon, for instance to get information about a block.
Default ports for the daemon are
P2P: 18080 for the ...
At some point in the future, time permitting a better Tor hosting infrastructure may allow Tor to be re-enabled. Right now there are higher priorities. Security concerns ...
I can only speak for Tor: using torsocks can make monerod connect to other nodes via the Tor network.
This will run monerod with Tor:
DNS_PUBLIC=tcp torsocks monerod --p2p-bind-ip 127.0.0.1 --no-igd
If you cannot connect your wallet (which should not use Tor), you may need to add TORSOCKS_ALLOW_INBOUND. Apparently, different systems may or may not need ...
What is SIGAINT
From their website:
What is SIGAINT? SIGAINT is a darknet email service that allows you to send and receive email without revealing your location or identity. We provide this service to help journalists and activists combat the dragnet surveillance that exists on the Internet today. Even if you aren't in conflict with the state or anyone ...
You can run Monero without an open port but others will not be able to connect to your node in order to help synchronize their nodes.
Open port 18080 to allow incoming P2P connections. The RPC port is 18081. print_cn will help you verify your incoming connections are working
If the majority of monerod instances were wrapped with torsocks, but otherwise not Tor-aware, then the network would end up having to concentrate all of its traffic through the few nodes that weren't using torsocks. And I don't know the details of the P2P protocol, but in a lot of designs the discovery system could end up degraded or inefficient as well.
The bitmonerod defaults are:
The wallet's RPC port has no default.
Wallet and daemon may use 53 for DNS, which is optional.
It is recommended to only open the RPC port on your firewall if you need to access RPC from the outside, especially for the wallet.
There is a limit of 5000 entries (P2P_LOCAL_GRAY_PEER_LIST_LIMIT), and they are stored in p2pstate.bin, which is in your daemon's data directory (typically $HOME/.bitmonero).
It is a privacy leak if you connected via clearnet. If that is a problem to you, you can run your node through Tor (see the instructions near the end of README.md in the monero tree).
Firstly, Kovri is an abandoned i2p router implementation. There are plenty of other actively developed i2p routers (such as i2p-zero), all of which can be configured to work with Monero via the various Anonymity Network options.
Second, when discussing anonymity of transactions, there are multiple threat models that need considering. By default, Monero ...
From the Kovri FAQ:
What is the current state of Kovri?
Kovri is in active development and currently pre-alpha. Kovri is not yet integrated with monero but, in addition to several core features, we are developing a client and core API for monero and other applications to use.
Currently, you can use the Kovri to connect to (and partake in) the ...
It seems likely that this would be a good idea to import the raw file. Not only will this possibly be faster, but also avoid spamming the Tor nodes on your way with gigabytes of blocks.
One very large difference in running time when importing a raw file is whether verification is enabled or not. If you already have a raw file you know is good, you can ...
If the vendor also runs a Monero node, and is currently connected to your own node, then their node will see your transaction being forwarded to their node.
If they set things up to keep track of IPs through which they seem transactions come in, they can determine which IP forwarded each transaction to them. This may or may not be the originating node (they'...
Your p2pstate.bin file will keep a record of IP address from your peers. These peers will know that certain IP's are running Monero nodes but will not be able to tell who is creating Monero transactions.
Since there are many nodes online 24/7 a correlation analysis could not prove that a specific node was involved in a given transaction. If a DDoS attack ...
Monero does not have an hidden service as Bitcoin does. This would be needed in order for an external client to connect via Tor. Allowing clients to connect via clearnet would need code changes in Monero so outgoing connections could be made via Tor, while listening for incoming connections could be made normally. Alternatively, allowing proxy connections ...
According to site operator fluffyponyza there should be an error message that explains this:
The site you are visiting is NOT the real MyMonero! Please make sure that in future you type mymonero.com into your address bar, and don't click on links to visit the site. Note that you may also see this message when trying to access MyMonero on Tor, as ...
I had missed the question earlier, sorry for late reply. I run xmr.to and the only reason we advise to connect to us via TOR is to protect your IP address from us knowing it. It has nothing to do with the vendor that anyway only receive BTC from us and never sees your IP whatsoever.
In other words:
There is nothing that links the vendor to you even if you ...
There are detailed instructions for using Monero over TOR on the project homepage: https://github.com/monero-project/monero#using-tor.
Essentially to use the GUI wallet over TOR, you'd need to have a daemon running on TOR also. Then use torsocks when connecting to the daemon.
I find the info in the ANONYMITY_NETWORKS.md document to be somewhat opaque and the cost of misconfiguring your anonymity network could be high.
I wouldn't use the term "opaque", rather they are detailed and expect a certain level of competence. There's really very little "cost of misconfiguring", rather things just wont work if misconfigured. At worst you ...
There is no avoiding editing the firewall rules on Tails. Instructions for running Monero on Tails can be found in the projects README and quoted below:
Using Tor on Tails
TAILS ships with a very restrictive set of firewall rules. Therefore,
you need to add a rule to allow this connection too, in addition to
telling torsocks to allow inbound ...
Your wallet password is local to the wallet. It's not sent to the daemon, which never gets hold of that, nor the wallet keys. Using Tor, information is encrypted between your own tor daemon (though if you're going to use a third party Monero daemon, you might be using a third party Tor daemon, which is even worse) and the destination hidden service, so any ...
Please update your monerod to the latest version 0.10.1.0 Wolfram Warptangent.
There has been a hard fork to introduce RingCT transactions at block 1220517 and if you are running an old version, it will not be able to sync with the network.
There is no way to directly configure Torsocks in the GUI at the time of writing. However, you can run monerod and connect the GUI to your local daemon.
Set the daemon to connect to Tor. Use the guide here.