⚡️2FakTor⚡️

Fixed anyway on this commit https://github.com/janoside/btc-rpc-explorer/commit/01585b7825afe0eb3e8f6cf39e9e135a20c8c2dd you need to re-compile from the source code without point to the latest 3.4.0 BTW: @janoside you should renovate your GPG and release a...

> @twofaktor do you mean to say I should re-compile from `master` instead of `3.4.0`? Yes! Or to add `deprecatedrpc=warnings` in `bitcoin.conf` whatever you prefer

> [@twofaktor](https://github.com/twofaktor) I tried that, but when I run `npm i` on master, the operation fails with a really long exception :( > > ``` > npm warn deprecated [email protected]:...

> Fixed in v3.5 What about https://github.com/janoside/btc-rpc-explorer/pull/727 and https://github.com/janoside/btc-rpc-explorer/pull/699 ??

> How often are you restarting your NR service? lately, almost every day > > And is the flow here that you: > > * have the NR running >...

> I'm very sorry to hear that but understand. Once the nodes are combined in the coming months then this problem should disappear hopefully, although its something to be looking...

BTW: To discard possible error triggers, I'm testing running NR and socks5 client, but not connecting any persistent app to the socks5 let's see if it continues to fail or...

More logs about nym-socks5-client without to request connections to it during 2 days: ``` Nov 22 14:43:46 raspibolt2fa nym-socks5-client[3527966]: 2023-11-22T13:43:46.291Z INFO nym_socks5_client_core::socks::server > Listening on 0.0.0.0:1080 Nov 22 14:43:46 raspibolt2fa...

> @twofaktor have you ran into this since, there's been a lot of releases since this event happened, i will close the ticket, but if you comment and re-open it...

+1 useful option to keep a cleaner streamer profile