-
@ ⚡️2FakTor⚡️
2024-06-12 13:04:53
Notice to node MiniBolt runners: It turns out that the I2P devs have opened an issue on the Bitcoin Core GitHub repo commenting that because they gave the option to enable the `notransit=true` parameter in the official documentation:
[...] If you prefer not to relay any public I2P traffic and only allow I2P traffic from programs connecting through the SAM proxy, e.g. Bitcoin Core, you can set the no transit option to true [...] are having a heavy load on the I2P network since last December 19. Also comment that it is advisable to share as much bandwidth and transit tunnels as we can, to increase anonymity with coverage traffic, by contributing more to the I2p network than we consume.
So they ask that we deactivate that option that you use activated. With all this, he already updated the "Privacy" section by removing that setting.
The steps to delete this configuration once we have already configured it, are the following:
With the "admin" user, stop i2pd:
```
$ sudo systemctl stop i2pd
```
Comment line 93 with "#" at the beginning of it (notransit = true), save and exit
```
$ sudo nano /var/lib/i2pd/i2pd.conf --line numbers
```
Start i2pd again:
```
$ sudo systemctl start i2pd
```
And that's it, you could take a look at Bitcoin Core to see that it has detected i2pd running again after the reboot with:
```
$ tail --lines 500 -f /home/bitcoin/.bitcoin/debug.log
```
If for whatever reason you don't see that I2P is up in Bitcoin Core after the restart, `$ sudo systemctl restart bitcoind` and look again at the logs of the same
More info in the rollback commit:
https://github.com/twofaktor/minibolt/commit/99cae67a5150bb5b7deae3674cc958eb31c74a75