Open Mitchellpkt opened 6 years ago
Done
However, MAP-TOKYO is not yet running as a remote node.
To enable use of MAP-TOKYO as remote node by a wallet, Unrestricted RPC will need to be enabled on port 18081. This will require the following 2 changes on MAP-TOKYO:
map_vps_setup_files/monerod-archive-remote-node.conf
as /etc/monerod-archive.conf
and restart monerod-archive
.sudo ufw allow from any to any port 18081 proto tcp
@serhack @Mitchellpkt , please grant approval for these changes ?
Running a unrestricted RPC is not the best option. Theoretically you could execute any RPC commands described in https://getmonero.org/resources/developer-guides/daemon-rpc.html . That will not cause any critical problems.
But please read Are there risk running a remote node without --restricted-rpc ?. The answer could be yes or no, it's up to you.
The shell commands are okay.
Oh! I agree with you and I want Restricted mode then.
I was going off the definition of restricted-rpc
in the monerod help: "Restrict RPC to view only commands and do not return privacy sensitive data in RPC calls". Here, I thought "view only" would mean it could not receive transactions. I see that is not what this meant.
I just remembered I wrote up documentation on what Restricted RPC actually did. I have posted it here: https://github.com/Mitchellpkt/monero_archival_project/wiki/Monerod-Restricted-RPC-Mode
I have updated map_vps_setup_files/monerod-archive-remote-node.conf
to use Restricted RPC Mode.
Steps to resolve this issue:
map_vps_setup_files/monerod-archive-remote-node.conf
as /etc/monerod-archive.conf
and restart monerod-archive.
b. Open firewall: sudo ufw allow from any to any port 18081 proto tcp
Hack together a quick wiki page about how to connect to Tokyo as a remote node.
Note, the goal here is to connect data about propagation of transactions that originate at our nodes. R & D purposes.
If you want privacy, I would suggest NOT connecting to one of our nodes operating at --log-level > 9000