|
1 | 1 | # Chapter 15: Using i2p |
2 | 2 |
|
3 | | -The Invisible Internet Project (I2P) is a fully encrypted private network layer. It uses a distributed [network database](https://geti2p.net/en/docs/how/network-database) and encrypted unidirectional tunnels between your and your peers. |
| 3 | +There are alternatives to Tor. One is the Invisible Internet Project (I2P), a fully encrypted private network layer. It uses a distributed [network database](https://geti2p.net/en/docs/how/network-database) and encrypted unidirectional tunnels between peers. The biggest difference between Tor and i2P is that Tor is fundamentally a proxy network that offers internet services in a private form, while i2p is fundamentally a sequestered network that offers i2p services only to the i2p network, creating a "network within a network". |
4 | 4 |
|
5 | | -Basic differences between Tor and i2p: |
6 | | - |
7 | | -| | Tor | i2p | |
8 | | -| :--- | :---: | ---: | |
9 | | -| Routing | [Onion](https://www.onion-router.net/) | [Garlic](https://geti2p.net/en/docs/how/garlic-routing) | |
10 | | -| Network Database | Trusted [Directory Servers](https://blog.torproject.org/possible-upcoming-attempts-disable-tor-network) | [Distributed network database](https://geti2p.net/en/docs/how/network-database) | |
11 | | -| Relay | **Two-way** encrypted connections between each Relay | **One-way** connections between every server in its tunnels | |
12 | | -| Hidden services | Slow | Fast | |
13 | | - |
14 | | -Comparison in detail: https://geti2p.net/en/comparison/tor |
15 | | - |
16 | | -Ports required by i2p: |
17 | | - |
18 | | -1. Outbound (Internet facing): a random port between 9000 and 31000 is selected however its better if all ports are open and it doesn't affect your security. You can check firewall status using `sudo ufw status verbose` which shouldn't deny outgoing by default. |
19 | | - |
20 | | -2. Inbound (Internet facing): Optional |
21 | | - |
22 | | -Local ports: https://geti2p.net/en/faq#ports |
23 | | - |
24 | | -It is not installed by [Bitcoin Standup](https://github.com/BlockchainCommons/Bitcoin-Standup-Scripts) right now as i2p support was recently added in Bitcoin core. However, you can try it manually by following the steps mentioned in [Section One](15_1_i2p_service.md). |
| 5 | +i2p is not currently installed by [Bitcoin Standup](https://github.com/BlockchainCommons/Bitcoin-Standup-Scripts), as i2p support was recently added in Bitcoin Core. However, this chapter explains how to manually install it. |
25 | 6 |
|
26 | 7 | ## Objectives for This Chapter |
27 | 8 |
|
28 | 9 | After working through this chapter, a developer will be able to: |
29 | 10 |
|
30 | | - * Run Bitcoin Core as an I2P (Invisible Internet Project) service |
| 11 | + * Run Bitcoin Core as an i2p (Invisible Internet Project) service |
31 | 12 |
|
32 | 13 | Supporting objectives include the ability to: |
33 | 14 |
|
34 | 15 | * Understand the i2p Network |
35 | | - * Learn difference between Tor and i2p |
| 16 | + * Learn the difference between Tor and i2p |
36 | 17 |
|
37 | 18 | ## Table of Contents |
38 | 19 |
|
39 | | -* [Section One: Bitcoin Core as an I2P (Invisible Internet Project) service](15_1_i2p_service.md) |
| 20 | +* [Section One: Bitcoin Core as an I2P (Invisible Internet Project) service](15_1_i2p_service.md) |
0 commit comments