Closed erciccione closed 1 year ago
Name | Link |
---|---|
Latest commit | a0775b33a74537ad17f128c3e9e8c7dcc6389260 |
Latest deploy log | https://app.netlify.com/sites/barolo-time-757cf9/deploys/6437bff586062700087be693 |
Deploy Preview | https://deploy-preview-2153--barolo-time-757cf9.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
Some feedback from: https://github.com/monero-project/meta/issues/824
Ideally, this would be replaced with a working guide for the currently recommended I2P (either i2p or i2pd, I'm not sure).
i2p-zero has been dead for some time: https://github.com/i2p-zero/i2p-zero
I don't think it is 'dead' per se. According to the readme.md:
Note that I2P-zero is not a re-implementation of I2P. It uses the exact I2P source code from the official I2P GitHub repository.
It is actually quite useful for a project I'm working on with xmr and i2p for programmatically building and controlling tunnels. I had issues with http proxy but it was resolved by compiling new binaries with the build-all-and-zip.sh
script.
Any more feedback on this?
Any more feedback on this?
My vote is to just leave this for now since the guide still works and facilitates setting up remote nodes over i2p. There is a stagenet node at monero.fail setup, following the guide, for testing. The command for connecting is below. Once there is superseding documentation go ahead and remove the current guide.
./monero-x86_64-linux-gnu-v0.18.2.2/monero-wallet-cli --wallet-file stagenet/wallet/<WALLET_FILE> --proxy 127.0.0.1:9051 --daemon-address http://xmr3kaacphwkk4z2gp35bdl47lrrnzimmyqj4oliauqrjzqecofa.b32.i2p:38081 --stagenet --trusted-daemon --daemon-ssl-allow-any-cert
I would leave it alone for now. Plenty of guides online, not many correct, and i2p is broken in monero is configured incorrectly or reconfigured manually.
i'll try to remember to update this after i2p anon inbound is fixed and i2pd etc can be used in place.
Also, iirc, bitcoin still recommends i2p-zero as well.
Some feedback from: monero-project/meta#824
Ideally, this would be replaced with a working guide for the currently recommended I2P (either i2p or i2pd, I'm not sure).
+1 i left a comment here.. moving from i2pzero -> i2pd is quite painless
i2p-zero has been dead for some time: https://github.com/i2p-zero/i2p-zero