-
Notifications
You must be signed in to change notification settings - Fork 72
Create Monero tutorials #95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,71 @@ | ||
| Monero | ||
| ================== | ||
|
|
||
| ## Connect to remote nodes. | ||
|
|
||
| To connect Monero nodes, you have to configure the wallet software: | ||
|
|
||
| In [Feather wallet](http://rwzulgcql2y3n6os2jhmhg6un2m33rylazfnzhf56likav47aylq.b32.i2p/): File -> Settings -> Network -> Proxy > i2p, with this option all network traffic will be routed over i2p, including websocket connection (if enabled). | ||
|
|
||
| ## Connection between other I2P nodes. | ||
|
|
||
| Warning: The usage of I2P network is still considered experimental; | ||
|
|
||
| Sync the blockchain over I2P isn't supported and there are a few pessimistic cases where privacy is leaked. | ||
|
|
||
| The design is intended to maximize privacy of the source of a transaction by broadcasting it over an anonymity network, while relying on clearnet for the remainder of messages to make surrounding node attacks (via sybil) more difficult. | ||
|
|
||
|
|
||
| 1) Configure i2pd to create server type tunnel and put in your `./tunnels.conf` file: | ||
|
|
||
| [monero-node] | ||
| type = server | ||
| host = 127.0.0.1 | ||
| port = 18085 # Anonymous inbound port | ||
| keys = monero-node.dat | ||
|
|
||
| 2) Restart i2pd or send `SIGHUP` signal. | ||
|
|
||
| 3) Find your b32 address of the node. | ||
|
|
||
| Go to webconsole -> [I2P tunnels page](http://127.0.0.1:7070/?page=i2p_tunnels). Look for Server tunnels and you will see address like \<long random string\>.b32.i2p next to monero-node. | ||
| Or get with curl: `curl http://127.0.0.1:7070/?page=i2p_tunnels 2>&1 | grep -Eo "[a-zA-Z0-9./?=_%:-]*" | grep "18085"` | ||
|
|
||
| The node is now available in Invisible Internet. You can check the node's status by visiting \<long random string\>.b32.i2p/get_info. | ||
HardenedSteel marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| 4) Update your monero.conf file; | ||
|
|
||
| anonymous-inbound=XXX.b32.i2p,127.0.0.1:18085 | ||
| tx-proxy=i2p,127.0.0.1:4447,disable_noise | ||
|
|
||
| Replace XXX with your b32 address. | ||
|
|
||
|
|
||
| ## Setup I2P service on already running public node. | ||
|
|
||
| Open wallet inteface (the "RPC") allows anyone to connect their wallets to Monero network through the node. This is useful for users who don't run their own nodes and connecting over i2p. | ||
|
|
||
| If you already have a node with public RPC and now want to run i2p service, follow those steps: | ||
|
|
||
| 1) Make sure the node is running and configured with a restricted rpc port by adding `rpc-restricted-bind-port=18089` to your monerod startup flags or config file. | ||
|
|
||
| 2) Configure i2pd to create server type tunnel and put in your `./tunnels.conf` file: | ||
|
|
||
| [monero-node-rpc] | ||
HardenedSteel marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| type = server | ||
| host = 127.0.0.1 | ||
| port = 18089 # Restricted RPC port | ||
| keys = monero-node-rpc.dat # or same key file with P2P if you want one and same address. | ||
|
|
||
| 3) Restart i2pd or send `SIGHUP` signal. | ||
|
|
||
| 4) Find your b32 address of the node. | ||
This comment was marked as outdated.
Sorry, something went wrong. |
||
|
|
||
| Go to webconsole -> [I2P tunnels page](http://127.0.0.1:7070/?page=i2p_tunnels). Look for Server tunnels and you will see address like \<long random string\>.b32.i2p next to monero-node. | ||
This comment was marked as resolved.
Sorry, something went wrong.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can be confusing for beginners. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Its more confusing if you don't have a desktop environment. can add both instructions though?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @nahuhh doesn't work, i2pd webconsole doesn't show the ports There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 👀👀 it does on my system. Weird. Will check for another method |
||
| Or get with curl: `curl http://127.0.0.1:7070/?page=i2p_tunnels 2>&1 | grep -Eo "[a-zA-Z0-9./?=_%:-]*" | grep "18089"` | ||
|
|
||
| The node is now available in Invisible Internet. You can check the node's status by visiting \<long random string\>.b32.i2p/get_info. | ||
|
|
||
| 6) (Optional) Register short and memorable .i2p domain on [reg.i2p](http://reg.i2p). | ||
|
|
||
| 7) (Optional) Publish the node on [monero.fail](https://monero.fail). | ||
This comment was marked as resolved.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.