<_aj_>
hmm, estimatesmartfee 10 conservative --> 267sat/vb ; 10 economical --> 51sat/vb ; mempool.space low/med/high pri --> 42/45/48 sat/vb. should we think about changing the default to economical?
Guyver2 has left #bitcoin-core-dev [Closing Window]
<vasild>
brunoerg: lightlike: yeah, could be. Maybe it should try more aggressive. What I observe now is that currently my node has 0 outbound i2p connections. Last i2p outbound was established 2 hours ago, it is apparenly disconnected now but I do not know when it was disconnected. Was it disconnected like 1h50min ago or 5min ago? In those 2 hours there are 11 attempts to connect to i2p peers, all failed
<vasild>
our logging is not symmetric - we log when a new peer is connected, but not when disconnected (assuming -debug=net is not enabled)
<hebasto>
luke-jr: people on Transifex.com are not happy with add Knots resources to translate. A quote from their complains: "If the bitcoin-knots ressources are supposed to belong the a forked project of bitcoin-core (bitcoin-knots), i would prefer a new project being setup here on Transifex, since its kinda hijacking the main bitcoin core project and binding translation effort from members who want to support the bitcoin core
<hebasto>
project from my impression."
<hebasto>
s/add/added/
<hebasto>
laanwj: ^ what do you think?
mudsip has joined #bitcoin-core-dev
mudsip has quit [Client Quit]
<laanwj>
@hebasto i tend to agree with them, i don't understand the reasoning why it came this way in the first place, why isn't there a seperate transifex project for knots?
<laanwj>
as i see it this just complicated stuff for us, and for translators
<hebasto>
luke-jr: please remove Knots resource file from the Bitcoin Core project on Transifex.com
mudsip has joined #bitcoin-core-dev
mudsip has quit []
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 256 seconds]
Common has joined #bitcoin-core-dev
Common_ has joined #bitcoin-core-dev
Common_ has quit [Remote host closed the connection]
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
zeropoint has joined #bitcoin-core-dev
aleggg has quit [Ping timeout: 272 seconds]
gribble has joined #bitcoin-core-dev
Guest48 has joined #bitcoin-core-dev
pablomartin has joined #bitcoin-core-dev
Guest48 has quit [Client Quit]
<vasild>
laanwj: I dunno about thread-local in FreeBSD. I could perform some tests. How exactly is it (was) broken? Let me try to dig some more info...
<laanwj>
i'm not sure whether it didn't work or didn't compile, it was a long time ago
<laanwj>
i think it's a good thing to reconsider these kind of workarounds once in a while 😄
<laanwj>
but yes running some basic tests should be enough, eg compiling and running bitcoind with thread local support (ir uses it for some logging stuff IIRC)
Talkless has joined #bitcoin-core-dev
<laanwj>
tbh i would be surprised if the BSDs don't have that in order yet, less certain about mingw
Talkless has quit [Ping timeout: 268 seconds]
abubakarsadiq has joined #bitcoin-core-dev
puchka has quit [Ping timeout: 268 seconds]
jonatack has joined #bitcoin-core-dev
puchka has joined #bitcoin-core-dev
Jadi has quit [Quit: Jadi]
Jadi has joined #bitcoin-core-dev
Guest49 has joined #bitcoin-core-dev
Guest49 has quit [Client Quit]
<lightlike>
vasild: yes, that might be helpful. we only log new outbound connections unconditionally, so the disconnect log would need to make that distinction too to prevent log spamming by inbounds.