flywithu/Learning-Bitcoin-from-the-Command-Line
1
1
Fork 0
mirror of https://github.com/ChristopherA/Learning-Bitcoin-from-the-Command-Line.git synced 2025-06-07 16:06:26 +00:00
Code Issues Releases Wiki Activity

full edit

Browse Source 
Moved some material to 15.1, improved upfront definition of i2p.
This commit is contained in:
Shannon Appelcline 2021-09-15 09:23:17 -10:00 committed by GitHub
parent 2c98dc3971
commit 8a87dd5762
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
15_0_Using_i2p.md
View File

@ -1,39 +1,20 @@
# Chapter 15: Using i2p
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.
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".
Basic differences between Tor and i2p:
| | Tor | i2p |
| :--- | :---: | ---: |
| Routing | [Onion](https://www.onion-router.net/) | [Garlic](https://geti2p.net/en/docs/how/garlic-routing) |
| 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) |
| Relay | **Two-way** encrypted connections between each Relay | **One-way** connections between every server in its tunnels |
| Hidden services | Slow | Fast |
Comparison in detail: https://geti2p.net/en/comparison/tor
Ports required by i2p:
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.
2. Inbound (Internet facing): Optional
Local ports: https://geti2p.net/en/faq#ports
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).
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.
## Objectives for This Chapter
After working through this chapter, a developer will be able to:
* Run Bitcoin Core as an I2P (Invisible Internet Project) service
* Run Bitcoin Core as an i2p (Invisible Internet Project) service
Supporting objectives include the ability to:
* Understand the i2p Network
* Learn difference between Tor and i2p
* Learn the difference between Tor and i2p
## Table of Contents
* [Section One: Bitcoin Core as an I2P (Invisible Internet Project) service](15_1_i2p_service.md)
* [Section One: Bitcoin Core as an I2P (Invisible Internet Project) service](15_1_i2p_service.md)