<bitcoin-git>
[bitcoin] ariard closed pull request #25600: p2p: Advertise `NODE_FULL_RBF` and connect to 4 outbound full-rbf peers if `-mempoolfullrbf` is set (master...2022-07-fullrbf-p2p) https://github.com/bitcoin/bitcoin/pull/25600
<bitcoin-git>
[bitcoin] fanquake opened pull request #26474: [23.x] guix: use `--build={arch}-guix-linux-gnu` in cross toolchain (23.x...23_x_aarch64_on_aarch64) https://github.com/bitcoin/bitcoin/pull/26474
<bitcoin-git>
[bitcoin] hebasto opened pull request #26473: test: Randomize data in `getarg_tests/logargs` test (master...221108-logargs) https://github.com/bitcoin/bitcoin/pull/26473
<bytes1440000>
Will "bitcoin core devs" ever consider importance of knots maintained by luke dashjr?
<bitcoin-git>
[bitcoin] russeree opened pull request #26469: rpc: getblock: implement with block height as input parameter. (master...merge_getblock_getblock_hash) https://github.com/bitcoin/bitcoin/pull/26469
<vasild>
PaperSword: you probably already figured it out, but: yes, yes. See ToIntegral() and RPCArg::m_names, or try bitcoin-cli -named getblock blockhash=00000000000000000b46c6a2bd4725568f62b7a859a53bf63de962099a5c3753 verbose=0
<bitcoin-git>
[bitcoin] achow101 opened pull request #26467: bumpfee: Allow the user to choose which output is change (master...bumpfee-choose-change-txout) https://github.com/bitcoin/bitcoin/pull/26467
<sipa>
To me, monotonicity of tx validity is such a fundamental principle underlying bitcoin, that I'd need a very good reason to even consider acking it.
<_aj_>
height_or_hash is pretty awkward with bitcoin-cli, you have to say '"00000abcdef12345.."' so that an int looks different to a string
<gribble>
https://github.com/bitcoin/bitcoin/issues/16439 | cli/gui: support "@height" in place of blockhash for getblock on client side by ajtowns · Pull Request #16439 · bitcoin/bitcoin · GitHub
<_aj_>
PaperSword: past feedback has been that that's better done on the client side, so that branch implements in bitcoin-cli and the gui, rather than serverside. #16439
<bitcoin-git>
[bitcoin] theStack opened pull request #26462: wallet: fix crash on loading descriptor wallet containing legacy key type entries (master...202211-wallet_fix_crash_on_descriptor_wallet_load) https://github.com/bitcoin/bitcoin/pull/26462
2022-11-05
<bytes1440000>
more: michaelfolkson i will create something different because he ACKs on "faith", Greg Maxwell wrote a paragraph but wasn't aware rust-bitcoin is also affected
<bitcoin-git>
[bitcoin] luke-jr reopened pull request #21319: RPC/Blockchain: Optimise getblock for simple disk-hex case (master...getblock_optimise) https://github.com/bitcoin/bitcoin/pull/21319
<luke-jr>
[23:27:19] <luke-jr> I'm confused about the relay txs thing. jonatack seems to be implying the meaning has changed in his PRs (latest https://github.com/bitcoin-core/gui/pull/676), but I don't see that anywhere?
<bitcoin-git>
[bitcoin] jonatack opened pull request #26457: [24.x] backports for tx relay changes in getpeerinfo/netinfo/gui (24.x...24_x_backports) https://github.com/bitcoin/bitcoin/pull/26457
2022-11-04
<luke-jr>
I'm confused about the relay txs thing. jonatack seems to be implying the meaning has changed in his PRs (latest https://github.com/bitcoin-core/gui/pull/676), but I don't see that anywhere?
<bitcoin-git>
[bitcoin] petertodd opened pull request #26454: Allow `bumpfee` for txs that don't signal BIP-125 (master...2022-feebump-without-optin) https://github.com/bitcoin/bitcoin/pull/26454
<bitcoin-git>
[bitcoin] fanquake merged pull request #26418: Fix signing of multi_a and rawtr scripts with wallets that only have corresponding keys (master...fix-psbt-multia) https://github.com/bitcoin/bitcoin/pull/26418
<sipa>
Taproot spends have been standard since https://github.com/bitcoin/bitcoin/pull/20165, in 0.21.0 (though only relevant for mainnet since 0.21.1, as .0 didn't have activation).
<BlueMatt[m]>
so, kinda annoying that no flush happens if bitcoin core is idle for an hour, but ultimately the issue could also appear in prod if there's a reorg while a node that just crashed is offline
<BlueMatt[m]>
the issue was basically that some folks were running bitcoin core on regtest and calling `generatetoaddress`, some software was seeing the block, persisting its "latest chain tip", then the bitcoin node was crashing (even after an hour, but basically docker container shutdown was just kill'ing) and on restart the block was gone. the aforementioned software would then later load its "latest chain tip", not have any idea where that
<bitcoin-git>
[bitcoin] jamesob opened pull request #26419: log: mempool: log removal reason in validation interface (master...2022-10-log-mempool-removal-reason) https://github.com/bitcoin/bitcoin/pull/26419
<bitcoin-git>
[bitcoin] achow101 opened pull request #26418: Fix signing of multi_a and rawtr scripts with wallets that only have corresponding keys (master...fix-psbt-multia) https://github.com/bitcoin/bitcoin/pull/26418
2022-10-28
<bitcoin-git>
[bitcoin] mzumsande opened pull request #26417: test: fix intermittent failure in feature_index_prune.py (master...202210_testfix_indexprune) https://github.com/bitcoin/bitcoin/pull/26417
<bitcoin-git>
[bitcoin] achow101 closed pull request #26416: Initialize optional members of ChainstateManagerOpts to nullopt (master...fix-warnings) https://github.com/bitcoin/bitcoin/pull/26416
<bitcoin-git>
[bitcoin] achow101 opened pull request #26416: Initialize optional members of ChainstateManagerOpts to nullopt (master...fix-warnings) https://github.com/bitcoin/bitcoin/pull/26416
<bitcoin-git>
[bitcoin] achow101 closed pull request #24975: bench: remove from available_coins with reference, vout size (master...pool_bench) https://github.com/bitcoin/bitcoin/pull/24975
<bitcoin-git>
[bitcoin] andrewtoth opened pull request #26415: rpc,rest: read raw block in getblock verbosity 0 and rest_block bin and hex (master...read-raw-block) https://github.com/bitcoin/bitcoin/pull/26415
<josie[m]>
id start contributing to the bitcoin GUI if we had built in tetris :D
<laanwj>
fjahr: hah yes... a long time ago there used to be this awful system that paid out per commit... this encouraged a lot of people to try to get *something* into bitcoin core, the most trivial and cosmetic changes
<achow101>
luke-jr: I think org owners are also the only ones that can add new members? and also migrate repos in/out of the org (e.g. we might want to move libmultiprocess into bitcoin-core)
<luke-jr>
FWIW, lack of bitcoin org ownership prevented me from adding Kalle to the bips repo a while back, but I'm not sure I want that kind of access (in terms of becoming a possible target)
<achow101>
speaking of permissions, of the current owners of the bitcoin and bitcoin-core orgs, only 1 is a current maintainer, the rest former
<jonatack>
lightlike: that twitter poll only had 160 respondants; it may be interesting to do one from an account with more reach like the bitcoin core org one