<m011>
I found some peers to add to the `connect To` attribute of the configuration file and start outbound connections.
<m011>
jonatack: But to initiate inbound connections, it seems I need to set up some credentials in `authorizedPasswords` and send these information to these peers. How can I send this to random peers?
<stickies-v>
laanwj larryruane I've observed experimentally last week that indeed running CI tests are aborted as soon as you force push an update
<sipa>
@m011 You can't. The point is that you get operators of nodes to trust you enough to decide to make a connection to you.
<sipa>
Or alternatively, be convinced to open connections to others.
Kaizen_Kintsugi_ has quit [Remote host closed the connection]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 256 seconds]
<m011>
sipa: Got it. But without these step (2 and 3 in the doc - which is to connect to other peers), will CJDNS work with Bitcoin Core ?
Kaizen_Kintsugi_ has quit [Ping timeout: 250 seconds]
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
ZeroMaster has quit [Remote host closed the connection]
ZeroMaster has joined #bitcoin-core-dev
mikehu44 has quit [Quit: No Ping reply in 180 seconds.]
bitcoin-git has joined #bitcoin-core-dev
<bitcoin-git>
[gui] RandyMcMillan opened pull request #539: gui: scale network graph based on time interval (master...1643263956-network-graph-issue-532) https://github.com/bitcoin-core/gui/pull/539
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
mikehu44 has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 250 seconds]
mikehu44 has quit [Ping timeout: 240 seconds]
rex4539 has joined #bitcoin-core-dev
mikehu44 has joined #bitcoin-core-dev
rex4539 has quit [Ping timeout: 276 seconds]
kabaum has joined #bitcoin-core-dev
sdfgsdfg has quit [Quit: your partner prefers dildos]
tinova2 has joined #bitcoin-core-dev
tinova has quit [Ping timeout: 256 seconds]
tinova2 is now known as tinova
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
fetghu has joined #bitcoin-core-dev
fetghu has quit [Client Quit]
sdfgsdfg has joined #bitcoin-core-dev
mikehu44 has quit [Ping timeout: 250 seconds]
sipsorcery has joined #bitcoin-core-dev
mikehu44 has joined #bitcoin-core-dev
linuxperia has quit [Ping timeout: 256 seconds]
rex4539 has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 260 seconds]
Guyver2 has joined #bitcoin-core-dev
rex4539 has quit [Remote host closed the connection]
<bitcoin-git>
bitcoin/master 5e8975e fanquake: fs: consistently use fsbridge for fopen()
<bitcoin-git>
bitcoin/master 21f781a fanquake: fs: consistently use fsbridge for {i,o}fstream
<bitcoin-git>
bitcoin/master 486261d fanquake: fs: add missing <cassert> include
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
bitcoin-git has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] fanquake merged pull request #24167: fs: consistently use fsbridge:: for ifstream / ofstream (master...always_use_fsbridge) https://github.com/bitcoin/bitcoin/pull/24167
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
sudoforge has quit [Ping timeout: 250 seconds]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
<Guest>
Hii.. I have successfully built bitcoin core without Qt..Now I am trying to install Qt to enble Bitcoin Core GUI using this documentation : https://github.com/bitcoin/bitcoin/blob/master/build_msvc/README.mdWhen I run nmake it is giving the following error : NMAKE : fatal error U1095: expanded command line too longNMAKE : fatal error U1077:
<pink_sarco>
It could be a good idea to ask bitcoin.stackexchange.com
<pink_sarco>
In case nobody can answer here
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
<Guest>
I also another doubt.. When I open C:\Users\Dell\bitcoin\build_msvc\x64\Release\bitcoind.exe , there terminal opens and executes.. But I cannot find the graphical interface to input certain data and test certain things.. Is Qt necessary for getting the graphical interface?
<Guest>
Or there is some other way to get the interface and test certain features?
An0rak has joined #bitcoin-core-dev
<laanwj>
yes, for the graphical interface you need bitcoin-qt.exe
<laanwj>
stickies-v: that's good to know!
<laanwj>
Kaizen_Kintsugi_: there's https://github.com/ofek/bit and https://github.com/Simplexum/python-bitcointx which are actively maintained, the latter is a fork of python-bitcoinlib, python-bitcoinlib is very popular but not that actively maintained anymore (if it does what you want it does, ofcourse)
<laanwj>
fwiw neither of the three has taproot support yet, if someone feels like working on that that's be awesome
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
kexkey has quit [Ping timeout: 240 seconds]
<laanwj>
m011: as i've been trying to say all the time, you *first* need to ensure your connectivity to CJDNS, so have a running cjdns daemon and cjdns nodes, only then bitcoin core will work over it and will be able to connect to bitcoin cjdns nodes
<laanwj>
you cannot skip any steps and have it still work
kexkey has joined #bitcoin-core-dev
<vasild>
adding doc/cjdns.md has been on my todo for some time...
salvatoshi has joined #bitcoin-core-dev
<jonatack>
vasild: i didn't start a doc yet, happy to review
<vasild>
same here - nothing started yet ;-)
<vasild>
:-D
Kaizen_Kintsugi_ has quit [Ping timeout: 260 seconds]
<jonatack>
yes. the "find a friend" part seems to be the main snag people hit
<jonatack>
i tried skipping that part too... no bueno
rex4539 has quit [Ping timeout: 276 seconds]
calvinalvin has joined #bitcoin-core-dev
kcalvinalvin has quit [Ping timeout: 256 seconds]
cfields has quit [Ping timeout: 256 seconds]
cfields has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
hollewordl has joined #bitcoin-core-dev
<hollewordl>
hi
Kaizen_Kintsugi_ has quit [Ping timeout: 245 seconds]
hollewordl has quit [Quit: Lost terminal]
davterra has quit [Remote host closed the connection]
tralfaz has joined #bitcoin-core-dev
rex4539 has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
BitFlib has joined #bitcoin-core-dev
gnaf has joined #bitcoin-core-dev
BitFlib has quit [Quit: Leaving.]
<m011>
If I understand correctly, "find a friend" is literal. To be able to connect to the CJDNS network, you first need to find trusted peers willing to share the connection.
rex4539 has quit [Ping timeout: 276 seconds]
dougefish has quit [Ping timeout: 240 seconds]
<jonatack>
m011: yes. i just sent you some connection data
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
rex4539 has quit [Remote host closed the connection]
rex4539 has joined #bitcoin-core-dev
pergaminho has joined #bitcoin-core-dev
bitdex has quit [Quit: = ""]
szkl has quit [Quit: Connection closed for inactivity]
brunoerg has quit [Remote host closed the connection]
brunoerg has joined #bitcoin-core-dev
bitcoin-git has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] sdaftuar opened pull request #24178: p2p: Respond to getheaders if we have sufficient chainwork (master...2022-01-headers-response-requires-minchainwork) https://github.com/bitcoin/bitcoin/pull/24178
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
sdfgsdfg has quit [Quit: ayo yoyo ayo yoyo hololo, hololo.]
Kaizen_Kintsugi_ has quit [Ping timeout: 250 seconds]
ulrichard has joined #bitcoin-core-dev
<b10c>
Measured a ~4% full IBD speed-up with #20827 using a default dbcache and -prune=550 with an HDD \o/
<gribble>
https://github.com/bitcoin/bitcoin/issues/20827 | During IBD, prune as much as possible until we get close to where we will eventually keep blocks by luke-jr · Pull Request #20827 · bitcoin/bitcoin · GitHub
<b10c>
and 17.4% (!!) speed-up with -prune=8800 and -dbcache=4000 (although I think a dbcache of 2500 would yield similar results)
<ulrichard>
Hi, does bitcoind in regtest mode try to connect to some external hosts?
<stick>
wow! that sounds very nice
vysn has quit [Ping timeout: 250 seconds]
Guyver2 has left #bitcoin-core-dev [Closing Window]
ulrichard_ has joined #bitcoin-core-dev
brunoerg has quit [Remote host closed the connection]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
<b10c>
I'm assuming that performance improvments on SSD-based systems are not as big. If anyone has a idle SSD-based system to benchmark on I'd be happy to share my scripts and help with the setup!
Kaizen_Kintsugi_ has quit [Ping timeout: 250 seconds]
<stick>
b10c: i'd love to see your scripts - will send you my email in PM
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 260 seconds]
<lightlike>
ulrichard: regtest is meant for local testing with your own chain - there are no valid DNS seeds for regtest, and no available peers.
<ulrichard_>
lightlike: I added some unit tests with https://crates.io/crates/electrsd which spins up a bitcoind and electrsd regtest node. It runs fine on my machine. But on the CI agent it hangs. Now I think it might be because on that machine regular network connections are blocked. Thus I am trying to find out if either bitcoind or electrsd try to connect somewhere.
jarthur has joined #bitcoin-core-dev
<lightlike>
ulrichard_: I think that in principle, there is no special logic preventing connections on regtest (e.g. if you manually attempt to connect to an address with -connect or -addnode it will try that). bitcoind also "tries" to connect to an invalid dummy DNS seed "dummySeed.invalid.", but the expectation is that no actual connections to the outside are made unless that kind of thing is set up by the user.
gleb7454386 has quit [Ping timeout: 240 seconds]
cornfeedhobo has quit [Remote host closed the connection]
gleb7454386 has joined #bitcoin-core-dev
<ulrichard_>
lightlike: Do you have an idea how this dummy connection reacts to differend kinds of not being able to connect? If I disable networking on my dev machine, the test just takes 10 to 20 seconds longer. But on the CI machine it blocks for two hour until the CI stops it. A co-worker told me that he thinks on the CI machine the firewall drops packets.
Kaizen_Kintsugi_ has quit [Ping timeout: 260 seconds]
cornfeedhobo has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
<ulrichard_>
lightlike: Thanks for pointing me to this. Compiling it with this change will be the easier part. But testing it on the IC agent will be the more challenging part...
yanmaani1 is now known as yanmaani
brunoerg has quit [Ping timeout: 250 seconds]
Kaizen_Kintsugi_ has quit [Ping timeout: 260 seconds]
<michaelfolkson>
Can a maintainer with ability to change labels on PRs take the consensus label off of #24147, #24148 and #24149 please? Thanks!
Kaizen_Kintsugi_ has quit [Remote host closed the connection]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
sudoforge has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
szkl has joined #bitcoin-core-dev
freesprung has quit [Ping timeout: 250 seconds]
stickies-v has quit [Ping timeout: 240 seconds]
stickies-v has joined #bitcoin-core-dev
grettke has joined #bitcoin-core-dev
Guest48 has joined #bitcoin-core-dev
salvatoshi has quit [Ping timeout: 260 seconds]
Guest48 has quit [Quit: Client closed]
brunoerg has quit [Remote host closed the connection]
brunoerg has joined #bitcoin-core-dev
<laanwj>
michaelfolkson: done
<laanwj>
the interpreter change is only a little bit of refactoring to make functions accessible, no actual consensus change, which is what the 'consensus' label is for AFAIK
brunoerg has quit [Ping timeout: 240 seconds]
ulrichard has quit [Quit: Client closed]
<MarcoFalke>
I am wondering if we should add a new label for miniscript (if it is merged)
<MarcoFalke>
Or combine with the existing descriptors label somehow?
<laanwj>
not sure, currently i'm counting it under "descriptors"