Jon Atack answered this on Twitter. First install and start I2P (version 2.35 or above).
$ apt install i2pd
$ systemctl enable i2pd.service
$ systemctl start i2pd.service
In your bitcoin.conf file add (I will assume you want to use both Tor and I2P but remove debug=tor and onlynet=onion if not interested in Tor):
The node side of Bitcoin Core treats wallet transactions as any other transaction. They aren't treated any differently from transactions received over the network. So once the transaction is added to the node's mempool, it will be broadcast to connected nodes in the same way that any other transaction would be relayed.
All you can do is to ...
Is it possible the problem for that to be related to TOR, considering that I can connect to and open channels with public nodes just fine?
No, that's very unlikely. (and contradictory)
Are the channels you created announced ?
Are your two nodes connected to the network ? For a node to find a route it needs to be connected to the peer-to-peer network to ...
After some digging, I find out more about the answer.
In bitcoin core, it is possible to NOT broadcast your own transactions with "walletbroadcast=0" option
See more details at https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009422.html, https://en.bitcoin.it/wiki/Privacy ("Tor and tor broadcasting"), and https://github....
I think everybody using Tor with the newest Core has the same problem, including myself. There’s a Good explanation here why this is happening:
My solution was to roll back (for now) to the previous version. It now works fine.
I still do not understand why this appears not to be ...
Nothing interesting happens if github bans bitcoin, the repository will be uploaded on a different host. Git is a decentralized application and several mirrors exist already. The contributors also have local copies of the repository so no code will be lost.
The biggest problem would be that the github issues and comments will be lost since they are a github ...
Those are incoming connections coming through the proxy, which have no other possible identifier than coming from localhost (where the proxy daemon is running). The "sending" port number is effectively irrelevant for this situation. If you don't want incoming connections through the proxy, don't configure them to be allowed.
Yes but not by default.
C-lightning uses a pluggable Bitcoin backend. The default one, bcli, will use the bitcoin-cli executable to make requests to a bitcoind.
It exposes bitcoin-cli's rpcconnect startup option to lightningd which does not not support onion hosts. And you probably don't want it to as it is not meant to be exposed.
If you want to run C-...
There has been some discussion today before the Bitcoin Core PR review club session on the subject of Tor v3 support. I haven't been through the above answers to comment on whether any of it needs updating.
But Jon Atack pointed out on IRC some good additional resources on getting started with Tor. There is the Bitcoin wiki and the Bitcoin Core documentation....