https://monerodocs.org/running-node/open-node-tor-onion/

https://github.com/monerodocs/md/blob/master/docs/running-node/open-node-tor-onion.md

# Tor: add P2P seed nodes for the Tor network
# For an up-to-date list of working nodes see https://www.ditatompel.com/monero/node-peers
add-peer=4egylyolrzsk6rskorqvocipdo4tqqoyzxnplbjorns7issmgpoxvtyd.onion:18083
add-peer=fagmobguo6u4z4b2ghyg3jegcdpmd4qj4wxkhemph5d5q6dltllveqyd.onion:18083
add-peer=monerokdwzyuml7vfp73fjx5277lzesbrq4nvbl3r3t5ctgodsx34vid.onion:18089
add-peer=b75obarnhi42p7js7wgzo7v3wtiwcgf4bknrwv6ihatop77jivrtwpid.onion:15892
add-peer=5nvd6jbefgto3u74nzzdkcsbqgxyzrkk7bz5qupsdqg4gbuj5valiaqd.onion:18083
add-peer=ozeavjybjbxbvmfcpxzjcn4zklbgohjwwndzenjt44pypvx6jisy74id.onion:18083
add-peer=xcccrsxi2zknef6zl3sviasqg4xnlkh5k3xqu7ytwkpfli3huyfvsjid.onion:18083

# Make the seed nodes permanent to fix monerod issue of not maintaining enough connections,
# based on this reddit comment:
# https://www.reddit.com/r/monerosupport/comments/k3m3x2/comment/ge5ehcy/?utm_source=share&utm_medium=web2x&context=3
add-priority-node=4egylyolrzsk6rskorqvocipdo4tqqoyzxnplbjorns7issmgpoxvtyd.onion:18083
add-priority-node=fagmobguo6u4z4b2ghyg3jegcdpmd4qj4wxkhemph5d5q6dltllveqyd.onion:18083
add-priority-node=monerokdwzyuml7vfp73fjx5277lzesbrq4nvbl3r3t5ctgodsx34vid.onion:18089
add-priority-node=b75obarnhi42p7js7wgzo7v3wtiwcgf4bknrwv6ihatop77jivrtwpid.onion:15892
add-priority-node=5nvd6jbefgto3u74nzzdkcsbqgxyzrkk7bz5qupsdqg4gbuj5valiaqd.onion:18083
add-priority-node=ozeavjybjbxbvmfcpxzjcn4zklbgohjwwndzenjt44pypvx6jisy74id.onion:18083
add-priority-node=xcccrsxi2zknef6zl3sviasqg4xnlkh5k3xqu7ytwkpfli3huyfvsjid.onion:18083

the reddit link goes to some thread about i2p... not about tor... anyway

are all these ports or most wrong?
It took me hours of figuring out and I finally figured out it wasn't me but this config all the 18083 are supposed to be 18080.
I read on this random post from 2 years ago monero-project/monero#8034 (comment) and it immediately started working then...
no idea about the 15892 port

In the Node RPC API section for this entry

--rpc-restricted-bind-ip | IP to listen on with the limited version of API. The limited API can be made public to create an Open Node.
-- | --
--rpc-restricted-bind-port | TCP port to listen on with the limited version of API. To be used in combination with `--rpc-restricted-bind-port.

the rpc-restricted-bind-port says it should be used in combination with rpc-restriced-bind-port. i think it should maybe say used in combination with rpc-restricted-bind-ip

thanks.

The subaddress section implies that subaddresses are enough to maintain separate identities, but in the case of two colluding entities with disparate subaddresses, subaddresses are not sufficient.

The documentation should add a disclaimer that until Janus is mitigated, maintaining entirely separate wallets per desired identity is recommended for utmost privacy.

see:

• https://web.getmonero.org/2019/10/18/subaddress-janus.html
• monero-project/research-lab#62

I can not reach monerodocs.org, so I started to host a mirror of this repo under docs.monero.study.

I looked at this page and couldn't find many of the commands that are listed via the help RPC command.

These include (I didn't test everything, because there were just too many missing):

1. alt_chain_info
2. apropos
3. banned
4. flush_cache
5. mining_status
6. pop_blocks
7. print_net_stats
8. set_bootstrap_daemon
9. ...

For some of these, the equivalent command line switch is shown. However, I'd assume people would prefer to change settings without restarting monerod where possible.

I am doing some research about monero, but i don't find any detained introdution about peer network protocol in monero. So can you introduce peer network protocol of monero in this github project. Thank you!

This repository should be archived, and new contributors should be pointed to https://github.com/MAGICGrants/getmonero.dev

The info here about "white" and "grey" peers is incorrect according to the info in this thread.

Apparently, "white" peers are any peers that your node has completed a handshake with. "Grey" nodes are nodes that your node hasn't tried to connect to yet.

The version on monerodocs.org seems outdated compared to the repository. Can it get updated? Thanks.

22 Feb 2019 was the last time it got deployed and there have been a few changes since then.

No other way to put it.

This is the most incomplete documentation I've come across in quite some time (and that's saying a lot considering we're in the crypto space).

There are multiple pages that are simply incomplete, incorrect or both. And that actually hurts a lot more than it helps.

If I had more personal free time and thought that the "developers" of this project were honest people that had intentions on protecting the project from warlording, then I would definitely be about it. But, unfortunately, I'm not. And I dislike the fact that Monero is built to benefit the pockets of a few (like the core developers ; i.e., 'Spagni').

Change is coming in the near future. The community has mandated it.

rpc-restricted-bind-ipv6-address is not documented.

The option is crucial to setting up an ipv6 public node.

In the config example, most of the hosts specified inside "add-peer" and "add-priority-peer" options have RPC ports instead of P2P ports. Also, a comment there points to a few websites where you could get a list of Monero nodes, but those websites only list RPC addresses.

In lieu of my last pulled issue, I concur with the maintainer of this repo that it would be more constructive to make a pull request rather than point out what I perceive as deficits in the current version.

There are a few places where I'm sure that I can contribute. Let me know what the process for doing that would be (i.e., just a simple pull request, notes on the amendments + reason added[?]), etc.

I was investigating that recently to implement subaddr generation. The algorithm described on monerodocs.org is outdated, probably originating from first proposal of such feature.

This answer on stackexchange describes the right version. And there's a nice JS implementation mentioned at the end.

It would be perfect if there would also be a topic like monerod for other binaries like monero-wallet-rpc.

A overview about all options that can be used with the monero-wallet-rpc would be perfect.

i always found monerodocs a very useful source of information and it's a waste that not many in the Monero community are aware of it's existence,

Would you consider transferring the repo to the Monero Ecosystem project and maintain it from there.

It would have more visibility in the Ecosystem and i would personally be happy to contribute to moerodocs when i can. Please see the readme for info about the Ecosystem and the governance process we adopted