<bitcoin-git>
[bitcoin] glozow opened pull request #26933: mempool: disallow txns under min relay fee, even in packages (master...2023-01-package-mempoolmin-only) https://github.com/bitcoin/bitcoin/pull/26933
<bitcoin-git>
[bitcoin] fanquake merged pull request #26457: [24.x] backport rpc: skip getpeerinfo for a peer without CNodeStateStats (24.x...24_x_backports) https://github.com/bitcoin/bitcoin/pull/26457
<bitcoin-git>
bitcoin/24.x 2b87e90 fanquake: Merge bitcoin/bitcoin#26457: [24.x] backport rpc: skip getpeerinfo for a p...
<bitcoin-git>
bitcoin/24.x e72313e Martin Zumsande: rpc: Require NodeStateStats object in getpeerinfo
<bitcoin-git>
[bitcoin] dergoegge opened pull request #26930: fuzz: Actually use mocked mempool in tx_pool target (master...2023-01-determ-fuzz-tx-pool) https://github.com/bitcoin/bitcoin/pull/26930
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #26929: rpc: Throw more user friendly arg type check error (1.5/2) (master...2301-rpc-arg-type-check-error-nice-🤔) https://github.com/bitcoin/bitcoin/pull/26929
<bitcoin-git>
[bitcoin] achow101 merged pull request #25877: refactor: Do not use CScript for tapleaf scripts until the tapleaf version is known (master...202208_tapleaf_script) https://github.com/bitcoin/bitcoin/pull/25877
<sipa>
There is one open question I now think of, which is how to deal with Bitcoin Core PRs that depend on new features (specifically, #23432 currently).
<sipa>
In the libsecp256k1 meeting monday we decided to aim for a roughly every-3-months release schedule, every second one of which synchronized with the bitcoin core releases (~1 month before feature freeze).
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #26924: refactor: Add missing includes to fix gcc-13 compile error (master...2301-iwyu-gcc-13-📔) https://github.com/bitcoin/bitcoin/pull/26924
<bitcoin-git>
[bitcoin] MarcoFalke merged pull request #26906: test: add an easy way to run linters locally (master...2023-01-lint-container) https://github.com/bitcoin/bitcoin/pull/26906
<bitcoin-git>
[gui] john-moffett opened pull request #698: gui: Show labels for multiple SendToSelf addresses (master...2023_01_LabelsForPayToSelf) https://github.com/bitcoin-core/gui/pull/698
<bitcoin-git>
[bitcoin] theStack opened pull request #26920: doc: add release note for #25957 (fast wallet rescan) (master...202301-doc-add_release_note_25957) https://github.com/bitcoin/bitcoin/pull/26920
<bitcoin-git>
[bitcoin] fanquake opened pull request #26919: scripted-diff: use RPCArg::Optional::OMITTED over OMITTED_NAMED_ARG (master...remove_omitted_named_arg) https://github.com/bitcoin/bitcoin/pull/26919
<bitcoin-git>
[bitcoin] furszy opened pull request #26910: wallet: migrate wallet, exit early if no legacy data exist (master...2022_wallet_prevent_descriptors_migration) https://github.com/bitcoin/bitcoin/pull/26910
<bitcoin-git>
[bitcoin] mzumsande opened pull request #26909: addrdb: prevent peers.dat corruptions by only serializing once (master...202301_peersdat_corruption) https://github.com/bitcoin/bitcoin/pull/26909
<bytes1440000>
you have no clues about a few things... I will share once this CoC is taken seriously. And how this last maintainer wants to be boss of bitcoin. Maybe last 2 maintainers to add them in PR were mistake and not reviewed properly.
<bitcoin-git>
bitcoin/master 9b86114 Hennadii Stepanov: ci: Use pyenv's `python-build` to install Python in lint task
<bitcoin-git>
[bitcoin] jamesob opened pull request #26906: test: add an easy way to run linters locally (master...2023-01-lint-container) https://github.com/bitcoin/bitcoin/pull/26906
<bitcoin-git>
[bitcoin] fanquake merged pull request #26625: test: Run mempool_packages.py with MiniWallet (master...2212-test-mini-wallet-🕎) https://github.com/bitcoin/bitcoin/pull/26625
<bitcoin-git>
bitcoin/master faec09f MarcoFalke: test: Return chain of MiniWallet txs from MiniWallet chain method
<bitcoin-git>
bitcoin/master fa2d821 MarcoFalke: test: Return wtxid from create_self_transfer_multi
<bitcoin-git>
[gui] MarcoFalke opened pull request #697: Remove reindex special case from the progress bar label (master...2301-gui-reindex-👖) https://github.com/bitcoin-core/gui/pull/697
<bitcoin-git>
[bitcoin] fanquake opened pull request #26904: build: move rpc/request from util lib to common (master...move_rpc_request_out_util) https://github.com/bitcoin/bitcoin/pull/26904
<bitcoin-git>
[bitcoin] rodentrabies opened pull request #26902: wallet: do not backdate locktime if it may lead to fingerprinting (master...avoid-locktime-backdating) https://github.com/bitcoin/bitcoin/pull/26902
<bitcoin-git>
[bitcoin] brunoerg opened pull request #26899: p2p: set `-dnsseed` and `-listen` false if `maxconnections=0` (master...2023-01-maxconnections-0) https://github.com/bitcoin/bitcoin/pull/26899
<bitcoin-git>
[bitcoin] mruddy closed pull request #26535: reindex: allow finalized blk files to use read-only permissions (master...issue_2039_readonly_finalized_blk_files) https://github.com/bitcoin/bitcoin/pull/26535
<gribble>
https://github.com/bitcoin/bitcoin/issues/25957 | wallet: fast rescan with BIP157 block filters for descriptor wallets by theStack · Pull Request #25957 · bitcoin/bitcoin · GitHub
<bitcoin-git>
[bitcoin] theStack opened pull request #26892: test: refactor: simplify p2p_permissions.py by using MiniWallet (master...202301-test-use_MiniWallet_in_p2p_permissions) https://github.com/bitcoin/bitcoin/pull/26892
2023-01-14
<bytes1440000>
vasild: Sorry I could not help you. My life would be easier if I didn't get in to this stuff and had no personal gains. I tried and knew there would be some sheeps or politics. I failed. You are good and we need you in bitcoin.
<gribble>
https://github.com/bitcoin/bitcoin/issues/26720 | wallet: coin selection, dont return results that exceed the max allowed weight by furszy · Pull Request #26720 · bitcoin/bitcoin · GitHub
<bitcoin-git>
[bitcoin] furszy opened pull request #26889: wallet: set keypool size instead of access global args manager from spkm (master...2022_spkm_keypool_size) https://github.com/bitcoin/bitcoin/pull/26889
<bitcoin-git>
[bitcoin] vasild opened pull request #26888: net: simplify the call to vProcessMsg.splice() (master...simplify_vProcessMsg_splice) https://github.com/bitcoin/bitcoin/pull/26888
<bitcoin-git>
[bitcoin] MarcoFalke merged pull request #26882: test: skip sqlite3 tests if it isn't available (master...func_tests_check_import_sqlite) https://github.com/bitcoin/bitcoin/pull/26882
<bitcoin-git>
bitcoin/master eea73d4 fanquake: test: skip sqlite3 tests if it isn't available
<bitcoin-git>
bitcoin/master 3283403 MarcoFalke: Merge bitcoin/bitcoin#26882: test: skip sqlite3 tests if it isn't available
<jnewbery>
Incidentally, I do agree with you that some of the processes around Bitcoin Core are broken at the moment. There are a small number of developers doing very important and very good work (including people that you regularly attack), but sadly that good work is often drowned out by interminable PRs and irc discussions about politics instead of code.
<jnewbery>
It's striking that neither of the two people making the accusations or pushing for vasild to become maintainer have made *any* meaningful contributions to Bitcoin Core. And yet they make incessent demands on contributors' and maintainers' time and attention and then demand justification when they don't get that attention.
<jnewbery>
michaelfolkson: I haven't been involved with Brink or Bitcoin Core for over a year, and yet I continue to get tagged in PRs and irc with accusations that I've deliberately broken code, been "aggressive" or am involved in some shady cabal that controls Bitcoin Core.
<gribble>
https://github.com/bitcoin/bitcoin/issues/25923 | p2p: always provide CNodeStateStats and getpeerinfo/netinfo/gui updates by jonatack · Pull Request #25923 · bitcoin/bitcoin · GitHub
<jnewbery>
bytes1440000: I haven't been involved in day-to-day Bitcoin Core development for over a year. The only reason I commented on #25923 was that I was tagged by vasild with the comment "a bug is a bug, even if it was done on purpose.". My response was to correct several mistakes made by both vasild and jonatack in their comments on that PR.
<bitcoin-git>
[bitcoin] fanquake merged pull request #26691: Update secp256k1 subtree to libsecp256k1 version 0.2.0 (master...secp256k1) https://github.com/bitcoin/bitcoin/pull/26691
<bitcoin-git>
bitcoin/master 3d8a6ae Pieter Wuille: Update secp256k1 subtree to upstream libsecp256k1 version 0.2.0
<bitcoin-git>
bitcoin/master 9d47e7b Pieter Wuille: Squashed 'src/secp256k1/' changes from 44c2452fd3..21ffe4b22a
<bitcoin-git>
bitcoin/master 4462cb0 Pieter Wuille: Adapt to libsecp256k1 API changes
<michaelfolkson>
Longer term we might have to think about how we route around this small group. We can't continue like this if we want Bitcoin Core to stay open source
<bytes1440000>
1. A project like bitcoin core that is considered one of the top 10 critical open source C++ project would get a maintainer for module that matters the most for a bitcoin node after QA