Walletwasabi: [Feature] Improve logging to know from where blocks are downloaded

Created on 17 May 2019  路  5Comments  路  Source: zkSNACKs/WalletWasabi

I configured Wasabi to connect to my own node.
However, I am confused: Why does wasabi try to connect to other peers at all?

image

So I checked the logs:

image

But the logs are not helpful at all to know if it works as expected.

featurenhancement questioresearch

Most helpful comment

The mempool is not yet received from Core, only the blocks.

All 5 comments

The mempool is not yet received from Core, only the blocks.

Also transaction broadcasting happens to random nodes over Tor and over new Tor circuit. This however will not change unless Dandelion is implemented to Core. So we'll need P2P NBitcoin connection even if fully featured Core support is added.

Make sense. One day, I wish we can get a small windows where we can see which IP/TOR we are connected to so I can see if my connection to my Tor node is even working.

You might be interested by this poppup I did long ago https://github.com/NicolasDorier/NBitcoin.SPVSample/blob/master/NBitcoin.SPVSample/ConnectedNodesWindow.xaml (I was even showing download speed)

Clicking on the Peers can show this information in a new Tab.

Done with Bitcoin Core integration.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

MaxHillebrand picture MaxHillebrand  路  3Comments

yahiheb picture yahiheb  路  3Comments

gabridome picture gabridome  路  3Comments

the-metalworker picture the-metalworker  路  3Comments

UkolovaOlga picture UkolovaOlga  路  3Comments