<bitcoin-git>
[bitcoin] secp512k2 opened pull request #31259: doc: Fix missing comma in JSON example in REST-interface.md (master...patch-3) https://github.com/bitcoin/bitcoin/pull/31259
<laanwj>
@libera_irc_timothy:bitcoin.ninja: correct, joinmarket doesn't support descriptor wallets :( if you have problems compiling bdb, i'd recommend trying bdb 5.x (easiest to install it from your distro) before passing any scary flags to bdb 4.8 build
<bitcoin-git>
[bitcoin] naiyoma closed pull request #31256: feature: RPC show decompiled P2SH redeemScript and P2WSH witnessScript (master...feature/rpc-show-redeemscript-in-P2WSH-and-P2SH) https://github.com/bitcoin/bitcoin/pull/31256
<bitcoin-git>
[bitcoin] naiyoma opened pull request #31256: feature: RPC show decompiled P2SH redeemScript and P2WSH witnessScript (master...feature/rpc-show-redeemscript-in-P2WSH-and-P2SH) https://github.com/bitcoin/bitcoin/pull/31256
<bitcoin-git>
[bitcoin] fanquake closed pull request #31255: contrib: correct default build path in man pages (master...20241108-manpages) https://github.com/bitcoin/bitcoin/pull/31255
<bitcoin-git>
[bitcoin] rkrux opened pull request #31255: contrib: correct default build path in man pages (master...20241108-manpages) https://github.com/bitcoin/bitcoin/pull/31255
<bitcoin-git>
[bitcoin] polespinasa opened pull request #31252: rpc: print P2WSH redeemScript in getrawtransaction (master...p2wsh_redeem) https://github.com/bitcoin/bitcoin/pull/31252
<bitcoin-git>
[bitcoin] furszy opened pull request #31251: test: report a more detailed failure during utf8 response decoding (master...2024_test_report_invalid_response) https://github.com/bitcoin/bitcoin/pull/31251
<bitcoin-git>
[bitcoin] achow101 opened pull request #31250: wallet: Disable creating and loading legacy wallets (master...disable-legacy-wallets) https://github.com/bitcoin/bitcoin/pull/31250
<bitcoin-git>
[bitcoin] achow101 opened pull request #31249: test: Add combinerawtransaction test to rpc_createmultisig (master...combinerawtx-test) https://github.com/bitcoin/bitcoin/pull/31249
<bitcoin-git>
[bitcoin] achow101 opened pull request #31248: test: Rework wallet_migration.py to use previous releases (master...migratewallet-prev-rels) https://github.com/bitcoin/bitcoin/pull/31248
<bitcoin-git>
[bitcoin] achow101 opened pull request #31243: descriptor: Move filling of keys from `DescriptorImpl::MakeScripts` to `PubkeyProvider::GetPubKey` (master...descriptor-direct-fill) https://github.com/bitcoin/bitcoin/pull/31243
<bitcoin-git>
[bitcoin] achow101 opened pull request #31242: wallet, desc spkm: Return SigningProvider only if we have the privkey (master...wallet-signingprov-no-h) https://github.com/bitcoin/bitcoin/pull/31242
<bitcoin-git>
[bitcoin] furszy opened pull request #31241: wallet: remove BDB dependency from wallet migration benchmark (master...2024_bench_migration_remove_bdb_dependency) https://github.com/bitcoin/bitcoin/pull/31241
<josie>
stickies-v: we had discussed not running master vs PR branch on each run to save compute, but ultimately felt it was better to just accept the compute so that we have more guarantees its an apples to apples comparison (like changing bitcoin.conf options)
<josie>
stickies-v: that should be fixed soon (tm). regarding master changing, the idea is we will only sync benchcoin up with bitcoin-core master manually, once weve got agreement in the WG to choose a new base to benchmark against. long term, wed like to make it fully parameterized where you can pick a specific commit to bench your PR against (master at a certain point in time, another PR, etc)
<stickies-v>
josie: in https://github.com/bitcoin-dev-tools/benchcoin, it seems `results.json` only contains a run for PR head. Since `master` is ~going to be different for each PR, doing a run on `master` too might be helpful to isolate effects from other recent commits? Then again, doubles the compute for what will presumably be heavy workloads, so might not be worth the trade off. Just wondering what your thoughts are, i guess
<kanzure>
maybe post a question publicly and ask if anyone was using just the bitcoin-core-dev announcement list specifically, or thinks it should continue to exist, i would hate to break something important
<achow101>
and the announcements occur in a ton of other places too, including bitcoin-dev
<kanzure>
oh right, it occurs to me that bitcoin-core-dev is not supported on gnusha.org/url at the moment, does anyone have strong opinions about this. announcement emails always went out to bitcoin-dev AFAIK so they are captured there at least.
<kanzure>
lists.linuxfoundation.org is no more and is no longer hosting the mailing list static archives at this time (not just for bitcoin-dev but ~everything including some LKML stuff?)
<achow101>
#topic bitcoin-dev mailing list archive links (kanzure)
<gribble>
https://github.com/bitcoin/bitcoin/issues/29675 | wallet: Be able to receive and spend inputs involving MuSig2 aggregate keys by achow101 · Pull Request #29675 · bitcoin/bitcoin · GitHub
<josie>
next will be rebasing the bitcoin core PRs on top of that. for a list of the PRs / status, im keeping the tracking issue up to date (bitcoin/bitcoin#28536)
<gribble>
https://github.com/bitcoin/bitcoin/issues/1519 | GUI: change language selection format to "language - country (locale name)" by Diapolo · Pull Request #1519 · bitcoin/bitcoin · GitHub
<josie>
ive been incorporating all of the review comments / feedback from coredev on the bitcoin-core/secp256k1#1519, hoping to finish that this week
<josie>
we have a workflow where someone can take their branch and open it as a PR against https://github.com/bitcoin-dev-tools/benchcoin and this will automatically kick off a benchmark and publish the final results as artifacts on the PR
<kanzure>
#proposedmeetingtopic bitcoin-dev mailing list archive links
<bitcoin-git>
[bitcoin] edilmedeiros opened pull request #31240: RFC: doc: Fix dead links to mailing list archives (master...fix-mailing-list-links) https://github.com/bitcoin/bitcoin/pull/31240
<bitcoin-git>
[bitcoin] vasild opened pull request #31239: test: clarify log messages when handling SOCKS5 proxy connections (master...socks5proxy_log) https://github.com/bitcoin/bitcoin/pull/31239
<bitcoin-git>
[bitcoincore.org] azuchi opened pull request #1083: Add japanese translations for security advisories fixed in v26 (master...ja-translate-security-advisory-26) https://github.com/bitcoin-core/bitcoincore.org/pull/1083
2024-11-05
<timothy>
sipa: I don't know if the documentation is outdated, but: "At the moment, only legacy wallets (descriptors=false) work with Joinmarket. This means that Bitcoin Core needs to have been built with legacy wallet (Berkeley DB) support."
<timothy>
hi, do you see some (security?) problem to disable mutex (--disable-mutexsupport) on db4.8 before linking to bitcoin-core (I need it for joinmarket) since it doesn't build correctly on new aarch64 processors
<bitcoin-git>
[bitcoin] mzumsande opened pull request #31223: net, init: derive default onion port if a user specified a -port (master...202410_portplus1) https://github.com/bitcoin/bitcoin/pull/31223
<Chris_Stewart_5>
sipa: When working on #29589 mzumsande pointed out I introduced some inconsistent behavior wrt to IsSmallInteger() in solver.cpp, I noticed that it doesn't appear to handle OP_0. Is that intentional? https://github.com/bitcoin/bitcoin/pull/29589#discussion_r1828276434
<bitcoin-git>
[bitcoin] dergoegge opened pull request #31221: ci: Split out native fuzz jobs for macOS and windows (take 2) (master...2024-10-native-fuzz) https://github.com/bitcoin/bitcoin/pull/31221
<darosior>
kanzure: ive seen 697 is in March in your archive, but this is not the correct email. This link corresponds to Suhas' email with an attached writeup which summarizes the weaknesses in Bitcoin's merkle tree implementation.
<darosior>
https://gnusha.org/url?https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2019-February/016697.html returns a 404
<kanzure>
huh, i just tested that. weird. anyway, for now use https://gnusha.org/url?https:/lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-July/014726.html
<bitcoin-git>
[bitcoin] hebasto closed pull request #31214: guix: Do not set `C{PLUS}_INCLUDE_PATH` variables for Darwin builds (master...241104-guix-inc-paths) https://github.com/bitcoin/bitcoin/pull/31214
<bitcoin-git>
[bitcoin] vasild opened pull request #31215: rpc: increase the defaults for -rpcthreads and -rpcworkqueue (master...rpcthreads) https://github.com/bitcoin/bitcoin/pull/31215
<bitcoin-git>
[bitcoin] hebasto opened pull request #31214: guix: Do not set `C{PLUS}_INCLUDE_PATH` variables for Darwin builds (master...241104-guix-inc-paths) https://github.com/bitcoin/bitcoin/pull/31214
<bitcoin-git>
[bitcoin] maflcko closed pull request #31030: test: use context managers and add file existence checks in feature_fee_estimation.py (master...master) https://github.com/bitcoin/bitcoin/pull/31030
<bitcoin-git>
[bitcoin] JeremyRand opened pull request #31206: doc: Use relative hyperlinks in release-process.md (master...doc-release-process-relative-links) https://github.com/bitcoin/bitcoin/pull/31206
<bitcoin-git>
[bitcoin] Abdulkbk opened pull request #31205: Improve lockunspent validation for vout (master...improve-lockunspent-validation) https://github.com/bitcoin/bitcoin/pull/31205
2024-11-02
<bitcoin-git>
qa-assets/main ae7fb7d marcofleon: Add inputs for txdownloadman txdownloadman_impl and clusterlin_depgraph_sim
<bitcoin-git>
qa-assets/main 41a2769 maflcko: Merge pull request #211 from marcofleon/main
<bitcoin-git>
[bitcoin] fanquake merged pull request #31187: ci: Do not error on unused-member-function in test each commit (master...2024-10-unused-methods-CI) https://github.com/bitcoin/bitcoin/pull/31187
<bitcoin-git>
bitcoin/master 54d07dd Sergi Delgado Segura: ci: Do not error on unused-member-function in test each commit
<bitcoin-git>
bitcoin/master 4a0251c merge-script: Merge bitcoin/bitcoin#31187: ci: Do not error on unused-member-function in...
<bitcoin-git>
[gui-qml] pablomartin4btc opened pull request #430: Allow IPv6 in Proxy settings and moving validation out from the UI into the model/ interface (main...qml-ipaddress-allow-ipv6) https://github.com/bitcoin-core/gui-qml/pull/430
<bitcoin-git>
[bitcoin] brunoerg opened pull request #31203: fuzz: fix `implicit-integer-sign-change` in wallet_create_transaction (master...2024-11-fuzz-fix-create-transaction) https://github.com/bitcoin/bitcoin/pull/31203
2024-10-31
<bitcoin-git>
[bitcoin] darosior opened pull request #31198: init: warn, don't error, when '-upnp' is set (master...2024_upnp_unbreak_gui) https://github.com/bitcoin/bitcoin/pull/31198
<cfields>
jonatack: the wgs are for Bitcoin Core the software project. Those are a different thing...
<josie>
personally, i think there should be an important distinction between BIPs (broader bitcoin ecosystem) and bitcoin core (implementation). if you are interested in running a bips irc channel / or a wg, id be happy to join tho, as im interested in both
<sipa>
that also seems like something that deserves discussion from a wider group than just bitcoin core contributors
<josie>
theres also a lot of interest outside of bitcoin core in implementing silent payments so we'll also be running a discord (ew) for other dev teams (bdk, ledger, rust-bitcoin, bitshala, electrs, etc) with the help of some folks from the bitcoin design community
<josie>
after that, ill be working on rebasing all of the bitcoin core PRs with help from novo__ (hes been working on a receiving PR with labels support for the bitcoin core wallet)
<gribble>
https://github.com/bitcoin/bitcoin/issues/1519 | GUI: change language selection format to "language - country (locale name)" by Diapolo · Pull Request #1519 · bitcoin/bitcoin · GitHub
<josie>
for silent payments, the focus is still the libsecp256k1 PR (bitcoin-core/secp256k1#1519)
<josie>
the main focus for us will be reproducibility, auditability, and determinism. once we have that nailed down, we will actually start using this to benchmark some existing PRs in bitcoin core
<dergoegge>
No real update today but i've created a irc channel: #bitcoin-core-fuzzing