<@freenodecom>
The new channel is ##bitcoin-core-dev
< bitcoin-git>
[bitcoin] mjdietzx opened pull request #22067: Test and document a basic M-of-N multisig using descriptor wallets and PSBTs (master...multisig_descriptor_wallet_psbt_signing_flow) https://github.com/bitcoin/bitcoin/pull/22067
< bitcoin-git>
[bitcoin] practicalswift opened pull request #22065: Mark `CheckTxInputs` `[[nodiscard]]`. Avoid UUM in fuzzing harness `coins_view`. (master...nodiscard-CheckTxInputs) https://github.com/bitcoin/bitcoin/pull/22065
< bitcoin-git>
[bitcoin] hebasto opened pull request #22063: build: Use Qt archive of the same version as the compiled binaries (master...210525-version) https://github.com/bitcoin/bitcoin/pull/22063
< bitcoin-git>
[bitcoin] MarcoFalke merged pull request #22057: test: use MiniWallet (P2PK mode) for feature_dersig.py (master...202105-test-use_miniwallet_for_dersig) https://github.com/bitcoin/bitcoin/pull/22057
< bitcoin-git>
bitcoin/master 8600934 MarcoFalke: Merge bitcoin/bitcoin#22057: test: use MiniWallet (P2PK mode) for feature_...
< bitcoin-git>
bitcoin/master 3e05a57 Sebastian Falbesoner: test: use MiniWallet (P2PK mode) for feature_dersig.py
< wumpus>
anyone running testnet nodes: can you please pastebin and send me the output of "bitcoin-cli getnodeaddresses 0 | grep -E '[a-z0-9]{56}\.onion'" , i'd like to make a PR that replaces the seed nodes for testnet, just going to pick a few
< bitcoin-git>
[bitcoin] jonatack opened pull request #22056: doc: describe in fuzzing.md how to reproduce a CI crash (master...fuzzing-doc-describe-how-to-reproduce-ci-crash) https://github.com/bitcoin/bitcoin/pull/22056
< bitcoin-git>
[bitcoin] champo opened pull request #22049: rpc: allow specifying min chain depth for inputs in fund calls (master...psbt_coin_control) https://github.com/bitcoin/bitcoin/pull/22049
< bitcoin-git>
[bitcoin] theStack opened pull request #22048: test: MiniWallet: introduce enum type for output mode (master...202105-test-improve_miniwallet) https://github.com/bitcoin/bitcoin/pull/22048
< bitcoin-git>
[bitcoin] amadeuszpawlik opened pull request #22044: High fee check for -blockmintxfee option (master...sanitize_21893) https://github.com/bitcoin/bitcoin/pull/22044
< jonatack>
wumpus: idk but see things like "cc: fatal error", "clang: error: linker command failed due to signal (use -v to see invocation)" and "make[2]: *** [Makefile:5887: qt/bitcoin-qt] Error 254"
< bitcoin-git>
[bitcoin] jonatack opened pull request #22043: rpc, test: addpeeraddress test coverage, code simplify/constness (master...addpeeraddress-improvements) https://github.com/bitcoin/bitcoin/pull/22043
< bitcoin-git>
[bitcoin] instagibbs opened pull request #22042: Replace size/weight estimate tuple with struct for named fields (master...named_size_tuple) https://github.com/bitcoin/bitcoin/pull/22042
< bitcoin-git>
[bitcoin] hebasto opened pull request #22041: build: Make --enable-suppress-external-warnings the default (master...210524-sew) https://github.com/bitcoin/bitcoin/pull/22041
< bitcoin-git>
bitcoin/master dc7eb64 Sebastian Falbesoner: test: MiniWallet: add P2PK support
< bitcoin-git>
[bitcoin] dhruv opened pull request #22029: [fuzz] Add serialization to transport deserialization test (master...v1-transport-serializer-fuzzing) https://github.com/bitcoin/bitcoin/pull/22029
< bitcoin-git>
[bitcoin] fanquake merged pull request #22002: Fix crash when parsing command line with -noincludeconf=0 (master...2105-parseCommandlineCrash) https://github.com/bitcoin/bitcoin/pull/22002
< bitcoin-git>
bitcoin/master 3f3c4d2 fanquake: Merge bitcoin/bitcoin#22002: Fix crash when parsing command line with -noi...
< bitcoin-git>
[bitcoin] hebasto opened pull request #22025: refactor: Make CAddrMan protected members private ones (master...210523-cam) https://github.com/bitcoin/bitcoin/pull/22025
2021-05-22
< bitcoin-git>
[bitcoin] hebasto closed pull request #20243: rpc, wallet: Expose wallet id in getwalletinfo RPC output (master...201026-wid) https://github.com/bitcoin/bitcoin/pull/20243
< bitcoin-git>
[gui] hebasto reopened pull request #342: wallet: Move wallets loading out from the main GUI thread (master...210521-wallet) https://github.com/bitcoin-core/gui/pull/342
< bitcoin-git>
[gui] hebasto closed pull request #342: wallet: Move wallets loading out from the main GUI thread (master...210521-wallet) https://github.com/bitcoin-core/gui/pull/342
< bitcoin-git>
[gui] hebasto opened pull request #343: Improve the GUI responsiveness when progress dialogs are used (master...210522-ppd) https://github.com/bitcoin-core/gui/pull/343
< bitcoin-git>
[bitcoin] jonatack opened pull request #22021: rpc: bumpfee/psbtbumpfee fixes and updates (master...bumpfee-psbt-doc-fixes) https://github.com/bitcoin/bitcoin/pull/22021
2021-05-21
< bitcoin-git>
[bitcoin] achow101 opened pull request #22019: wallet: Introduce SelectionResult for encapsulating a coin selection solution (master...selectionresult) https://github.com/bitcoin/bitcoin/pull/22019
< bitcoin-git>
[gui] hebasto opened pull request #342: wallet: Move wallets loading out from the main GUI thread (master...210521-wallet) https://github.com/bitcoin-core/gui/pull/342
< bitcoin-git>
[bitcoin] achow101 opened pull request #22017: Update Windows code signing certificate (master...2021-win-codesign-cert) https://github.com/bitcoin/bitcoin/pull/22017
< bitcoin-git>
[bitcoin] Sjors opened pull request #22016: rpc: add period_start to version bits statistics (master...2021/05/versionbits_period_start) https://github.com/bitcoin/bitcoin/pull/22016
< vasild>
I think IRC is autmatically filtering people that find it hard to setup from joining here and suggesting bitcoin switches to POS or changes the 21M supply...
< vincenzopalazzo>
I think that the accessibility should be a good things in any case. Give the possibility to all the people to join e read all the event that happen in bitcoin dev is a good starting point I think
< jonatack>
"we really want to support your community to migrate smoothly to v3 (or less traumatizing as possible). We can coordinate with the Tor Comms team to have social media posts when v2 onion support is removed from bitcoin core."
< bitcoin-git>
[bitcoin] ajtowns opened pull request #22013: net: ignore block-relay-only peers when skipping DNS seed (master...202105-ignoreblockrelayfordnsskip) https://github.com/bitcoin/bitcoin/pull/22013
< bitcoin-git>
[bitcoin] achow101 opened pull request #22009: wallet: Decide which coin selection solution to use based on waste metric (master...cs-waste-2) https://github.com/bitcoin/bitcoin/pull/22009
2021-05-20
< bitcoin-git>
bitcoin/master e2b55cd Hennadii Stepanov: Merge bitcoin-core/gui#335: test: Use QSignalSpy instead of QEventLoop
< bitcoin-git>
bitcoin/master 7eea659 Jarol Rodriguez: qt, test: use qsignalspy instead of qeventloop
< achow101>
We have created Bitcoin Core Code Signing LLC registerd in Delaware and the cert will be issued to this new LLC
< BlueMatt>
(the actual freenode admins have been fairly friendly to bitcoin stuff, at least after a *ton* of effort on the part of some of the #bitcoin mods, most of those admins have moved to libera now)
< BlueMatt>
michaelfolkson: the people behind the freenode acquisition have been known hostile to bitcoin for years, I kinda suggested moving, but wasnt worth the effort, this seems like a good excuse more than anything.
< wumpus>
created an issue wrt collecting torv3/i2p addresses in the crawler https://github.com/sipa/bitcoin-seeder/issues/92 even though there's no point in adding them to the actual DNS seeds, it would still be useful to have a way to keep tabs on them for the hardcoded seeds updates
< bitcoin-git>
[bitcoin] laanwj merged pull request #21843: p2p, rpc: enable GetAddr, GetAddresses, and getnodeaddresses by network (master...getnodeaddresses-by-network) https://github.com/bitcoin/bitcoin/pull/21843
< bitcoin-git>
bitcoin/master a49f3dd Jon Atack: p2p: allow CAddrMan::GetAddr() by network, add doxygen
< bitcoin-git>
bitcoin/master c38981e João Barbosa: p2p: pull time call out of loop in CAddrMan::GetAddr_()
< bitcoin-git>
bitcoin/master d35ddca Jon Atack: p2p: enable CAddrMan::GetAddr_() by network, add doxygen
< sipa>
ggus: see PM, note that the project is called "bitcoin core"; there is an unrelated piece of software called bitcore too
< bitcoin-git>
[bitcoin] 0xB10C opened pull request #22006: tracing: first tracepoints and documentation on User-Space, Statically Defined Tracing (USDT) (master...2021-05-initial-usdt-support) https://github.com/bitcoin/bitcoin/pull/22006
< wumpus>
i mean i think tor deprecating tor v2 hidden services is well known at this point to tor users (they have been pretty loud about it), but bitcoin users might not know what to do dunno
< wumpus>
it would be more useful to have bitcoin specific instructions
< wumpus>
I can post to the notification list (bitcoin-core-dev) and to the bitcoin core twitter account (would make sense to PR a new blog item to bitcoincore.org first, so it's possible to post a link to that)
< vasild>
ggus: there is bitcoin-dev@lists.linuxfoundation.org but I doubt it is the best way to reach users, maybe others would have better ideas, wumpus?
< ggus>
vasild: about #2: amazing! so we just need to ask people to upgrade their bitcoin core software
< ggus>
vasild: do you have suggestions of mailing lists or forums that we should announce this? for the news, we can contact some news outlet. And do you know which tools people are using to automatically deploy a bitcoin node, so we can contact the developers?
< vasild>
ggus: hmm, actually in the 1. case, if the user just edits torrc and changes the v2 onion service to v3, then an old bitcoin core (<0.21) would be able to accept incoming tor connections, but if it wants to make outgoing connections to v3 addresses, then an upgrade to >=0.21 is needed
< vasild>
automatically to v3, but an upgrade to bitcoin core 0.21 is needed
< vasild>
ggus: on warning those node operators, I have no idea, maybe some mailing list or blog (that gets picked by news web sites) may help. On helping them migrate to v3 - there are two cases - 1. statically configured onion service in torrc, the users need to edit their torrc, no need to upgrade bitcoin core; 2. an onion service that is automatically created by bitcoin core - this will be switched
< ggus>
hi all, this is gus from the tor project. i don't know if this is the right channel to ask, but very soon tor project will deprecate and remove v2 onion services. i've checked that ~15% of bitcoin nodes are running over tor and many of them are running v2 onion. do you have thoughts on how we could warn these node operators and help them migrate to v3 onion services?
< wumpus>
real_or_random: no idea if libera supports recursive namespaces, tbh i'm fine with the bitcoin core channels being under the bitcoin namespace no need to make this too complicated
< Kiminuo>
I'm interested in the process of "merging of PRs in Bitcoin Core repo" in general. So I understand that a PR needs a certain number of code review ACKs to be eligible for merging. But what happens then? What actually makes a person to click the "merge" button?
< nkuttler>
nothing was decided for #bitcoin* yet
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #22002: Fix crash when parsing command line with -noincludeconf=0 (master...2105-parseCommandlineCrash) https://github.com/bitcoin/bitcoin/pull/22002
< real_or_random>
shouldn't bitcoin and bitcoin-core be different namespaces even?
< kinlo>
I can handle reservation for #bitcoin-* channels
< hebasto>
wumpus: maybe reserve #bitcoin-core-gui as well?
< BlueMatt>
jeremyrubin: eg, I'm suggesting #rust-bitcoin move to #bitcoin-rust (as #rust-* is technically owned by anyone who registers a rust organization)
< BlueMatt>
jeremyrubin: relevant bitcoiners have the "bitcoin" group registered, so it probably makes sense to move more towards #bitcoin-X
< jeremyrubin>
wumpus: ##ctv-bip-review, ##taproot{-bip-review,activation,}, ##miniscript, #sapio, #bitcoin-workshops, #bitmetas, #rust-bitcoin are all maybe good to nab if you can reserve them?
< aj>
#bitcoin-anything is reserved apparently, i tried registering bitcoin-signet. presuably kalle can set it up if desired
< wumpus>
#bitcoin-core-dev, #bitcoin-builds, #bitcoin-core-pr-reviews have been reserved at least, if you need any more let me know
2021-05-19
< bitcoin-git>
[bitcoin] reemuru opened pull request #21999: test: Run mempool_updatefromblock even with wallet disabled (master...test) https://github.com/bitcoin/bitcoin/pull/21999
< kinlo>
bitcoin channels are covered, individual accounts might be a good precaution
< bitcoin-git>
[bitcoin] rnicoll opened pull request #21998: test: Set mock time before creating block (master...validate-block-test-time) https://github.com/bitcoin/bitcoin/pull/21998
< jeremyrubin>
might be worthwhile chatting with Andrew about what his plans are re: freenode... I've chatted with him once or twice, seems like he generally wants to support bitcoin
< bitcoin-git>
[bitcoin] jonatack opened pull request #21996: p2p: pass strings to NetPermissions::TryParse functions by const ref (master...NetPermissions-TryParse-pass-strings-by-const-ref) https://github.com/bitcoin/bitcoin/pull/21996
< bitcoin-git>
[bitcoin] hebasto opened pull request #21995: build: Make built dependency packages reproducible (master...210519-repro) https://github.com/bitcoin/bitcoin/pull/21995
< bitcoin-git>
[bitcoin] practicalswift closed pull request #21964: Document that `ser_float_to_uint32` is not the inverse of `ser_uint32_to_float` (master...document-serialization-gotcha) https://github.com/bitcoin/bitcoin/pull/21964