Open alkum opened 2 years ago
I second the request. It'll also help to bolster the number of nodes on the I2P network.
MANY THANKS for adding i2p support. This is a great first step.
Perhaps consider adding i2pacceptincoming=1
in bitcoin.conf to allow other i2p nodes to connect to the mynode, and, until the I2P bitcoin network becomes more robust, consider adding a couple i2p seed nodes.
The following have high uptime:
addnode=a5qsnv3maw77mlmmzlcglu6twje6ttctd3fhpbfwcbpmewx6fczq.b32.i2p:0 addnode=sedndhv5vpcgdmykyi5st4yqhdxl3hpdtglta4do435wupahhx6q.b32.i2p:0 addnode=zsxwyo6qcn3chqzwxnseusqgsnuw3maqnztkiypyfxtya4snkoka.b32.i2p:0
I actually had that in there and then I read the default was 1 so I took it out.
Is it possible to reach the myNode web UI via I2P?
Not currently.
Please add support for I2P to myNode, similar to tor.
Each exposed service would then get an I2P address (like
cidcbr4jpvorsegnk5ehkpydf57fpl2vw5cdzvqre74byv4knv5a.b32.i2p
taken from https://plebnet.wiki/wiki/Plebnet_Playground).This would provide users with a 2nd "plug-and-play" way to access their nodes from the internet (in addition to tor). VPN and port forwarding via the home router are of course also available, but need a bigger time investment to setup, so few people will realistically use them.
Additional context RaspiBolt is also looking into it: https://github.com/raspibolt/raspibolt/issues/953