Skip to content
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

Create Monero tutorials #95

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

HardenedSteel
Copy link
Contributor

No description provided.

[monero-node]
type = server
host = 127.0.0.1
port = 18080 # P2P port
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
port = 18080 # P2P port
port = 18085 # P2P port

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why different port used?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

18080 is the p2p port. Anonymous inbound uses custom/new ports


4) Update your monero.conf file;

anonymous-inbound=XXX.b32.i2p:18080,127.0.0.1:18080
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
anonymous-inbound=XXX.b32.i2p:18080,127.0.0.1:18080
anonymous-inbound=XXX.b32.i2p,127.0.0.1:18085

type = server
host = 127.0.0.1
port = 18089 # Restricted RPC port
keys = monero-node.dat
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
keys = monero-node.dat
keys = monero-rpc.dat

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think its better to keep one key file to have one address instead separate addresses for RPC and P2P

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For privacy, i personally think its better to have rpc and the node uncorrelated

you can use the same key for both, but imo you shouldn't share your p2p address


4) 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.

This comment was marked as resolved.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can be confusing for beginners.

Copy link

Choose a reason for hiding this comment

The 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?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nahuhh doesn't work, i2pd webconsole doesn't show the ports

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👀👀 it does on my system. Weird. Will check for another method


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.

This comment was marked as resolved.

docs/tutorials/monero.md Show resolved Hide resolved

3) Restart i2pd or send `SIGHUP` signal.

4) Find your b32 address of the node.

This comment was marked as outdated.

docs/tutorials/monero.md Outdated Show resolved Hide resolved
docs/tutorials/monero.md Outdated Show resolved Hide resolved
docs/tutorials/monero.md Show resolved Hide resolved
docs/tutorials/monero.md Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants