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 transparency ...
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 ...
Kovri is an alternative implementation in C++ of the I2P protocol which original daemon i2p is written in Java, is bloated and quite difficult to use. Kovri is a fork of the C++ implementation i2pd.
You'll find a quite good answer in Kovri's FAQ
Why should I use Kovri instead of i2pd?
Security: our focus is on securing our software; not rushing to get ...
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 ...
There are three major implementations of I2P routers
Java I2P: the official client by the creators of the protocol. This is by far the most used.
i2pd: a c++ implementation of the client
Kovri: a fork of i2pd by the Monero Project team.
First, let's see why i2pd has been created:
Java I2P has built-in applications for torrents, e-mail and so on. i2pd is ...
As compared to Tor which is the most popular now:
i2pd serves the same efforts as Tor, but on a more p2p level, rather than relying on servers.
i2p lends itself more towards our workload.
Monero i2p nodes will also act as general i2p routers, which increases the size of the i2p mixnet and thus has an upshot for both.
Tor is optimised for low-bandwidth ...
Kovri for all intents and purposes is dead and development towards an I2P Java Router lite alternative continues with I2P-zero and tini2p.
As of September 2, 2019, I2P via proxy is supported in Monero. To run in this mode, start monerod with the options --proxy i2p,127.0.0.1:9000 (for outbound connections) and --anonymous-inbound ...
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
While VPN and Tor usage is much higher that I2P usage on mobile devices today that is also the case for PCs.
There is already an I2P app for Android: https://play.google.com/store/apps/details?id=net.i2p.android
I see no technical reason why Kovri could not eventually implement support for mobile devices.
It depends on where they're listening, but yes in the sense you probably mean.
The I2P protocol underlying Kovri has a signature like any other protocol, and anybody who can see all of your traffic can see that you're using I2P. I don't think I2P even tries to make that hard at all... and if it did there would still be limits to what it could do against a ...
Monero will use I2P to connect nodes together. The goal of this is twofold:
an adversary spying on your network connection, like so many today, will not be able to see whether you are using Monero or not.
A node receiving a relayed transaction will not be able to tell the IP it came from.
A new I2P router, Kovri (https://github.com/monero-project/kovri/) ...
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.
Indeed, the question cited refers to a list of url. The reseed process starts with choosing randomly one of them.
So let's assume that the choosen URL is : https://i2p.mooo.com/netDb/.
Here are the next steps :
Download an SU3 file, which must be named i2pseeds.su3 and located at the root :
curl -k -A "Wget/1.11.4" https://i2p.mooo.com/netDb/i2pseeds.su3 ...
what can they expect when it is rolled out?
The Kovri router will be baked in to the Monero code, so all a user will need to do is select an option indicating whether they want to use the Kovri routing feature or not. I think its still up in the air whether it will be on by default or not. I think it will be on by default.
as though they had set up a ...
Kovri is a C++ implementation of I2P which is Java based.
Kovri is no more than an I2P router. If another coin has wanted to use I2P they could have just bundled it into their node. To my knowledge, none actually has this level of security.
Kovri is open source, and could therefore be used or forked by anyone.
Read more on kovri website
While developed under the monero project umbrella, Kovri will be usable for general I2P usage, not only for monero. Even when used for monero, it will also be usable for other uses, if the user chooses so. Indeed, the advantage of being usable for general I2P traffic means that an observer seeing you using Kovri (which I assume may be possible via ...
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).
while @pebx wrote the Monero-side of the story, here is the answer I found from the i2pd-side of the story:
Kovri and the curious case of code rot
I thought that this discussion should somehow be balanced instead of being an echo-chamber.
When using Kovri alone, the ISP/your employer/whoever is able to see that you are using Kovri, but not what you're doing on Kovri (e.g. using Monero).
When using Kovri with a VPN, the ISP will just be able to see that you're connecting to a VPN. However the VPN provider and their ISP will be able to see that you're connecting to Kovri.
Personally I think ...
I2P's threat model consists of :
Brute force attacks
A brute force attack can be mounted by a global passive or active adversary, watching all the messages pass between all of the nodes and attempting to correlate which message follows which path
I2P's messages are unidirectional and do not necessarily imply that a reply will be sent. ...
Kovri and Monero are 2 distinct stand-alone projects that does not share any source code in common. Even if developers are not the same, it is still the same community (they are both under https://github.com/monero-project, same funding system ). So while there is nothing technically that would prevent Kovri to continue if Monero were to cease, it is highly ...
This is a copy and paste from an exchange on reddit. Answer looking for improvements and / or editing :)
FP - Not a good idea, then nearly the entire network is at risk of being Sybil attacked. Operating a full node in its entirety on hidden services is something that should be reserved for users in highly adversarial environments who can’t use a remote ...
There is none, hence the work on https://github.com/monero-project/kovri/.
A government might make I2P itself illegal, though, and that'd be yet another hurdle. Tor has something to try to look like other traffic (pluggable transports), which could be adapted to Kovri in the future.
See Why is it I2P (garlic routing) well suited for Monero (compared to ...
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'...
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 I2P network: ...
The short answer is yes.
If you connect to the rest of the I2P network (Kovri is a way to do that), some government organizations will undoubtedly be running a node that will attempt to log your IP. They will not know what you are using I2P for (that's the whole point of I2P), but they will know you are running I2P in the first place.
If you run I2P ...
From what I have observed on Reddit and Slack, the Monero and Kovri developers aren't the same people. While these projects are working closely together, I don't think the goal is for Kovri to depend (solely) on Monero. I would recommend to ask your question directly in the #kovri-dev Slack channel, and post the feedback here as an answer.
This question [After Kovri arrives will some full nodes need to remain on clearnet? ] deals with peer discovery through Kovri. How about peer discovery right now if I wanna run a full node in I2P? Will the current client know to connect to only I2P nodes?
Kovri does not yet integrate with Monero. In the future when integrated, there will be three modes: IP ...