< January 2025 >
Su Mo Tu We Th Fr Sa 123456 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31
2022-03-02
<bitcoin-git>
[bitcoin] MarcoFalke merged pull request #24375: Do not use `LocalTestingSetup` in getarg_tests test file. (master...pr/fixt) https://github.com/bitcoin/bitcoin/pull/24375
<bitcoin-git>
bitcoin/master 5d7f225 Kiminuo: Do not use `LocalTestingSetup` in getarg_tests test file.
<bitcoin-git>
bitcoin/master 0652ee7 Rob Fielding: Add size check on meta.key_origin.path
<bitcoin-git>
bitcoin/master 961b9e4 Andrew Chow: wallet: Parse hdKeypath if key_origin is not available
<bitcoin-git>
[bitcoin] laanwj merged pull request #23542: net: open p2p connections to nodes that listen on non-default ports (master...connect_to_any_port) https://github.com/bitcoin/bitcoin/pull/23542
<bitcoin-git>
bitcoin/master 2e38a0e Vasil Dimov: net: add CServiceHash constructor so the caller can provide the salts
<bitcoin-git>
[bitcoin] dongcarl closed pull request #17602: net: Limit # of IPs learned from a DNS seed by family (master...2019-11-lower-nMaxIPs) https://github.com/bitcoin/bitcoin/pull/17602
<bitcoin-git>
[bitcoin] Empact opened pull request #24455: refactor: Split ArgsManager out of util/system (master...2022-03-util-args-manager) https://github.com/bitcoin/bitcoin/pull/24455
<bitcoin-git>
bitcoin/master fc47181 eugene: fuzz: FuzzedFileProvider::write should not return negative value
<bitcoin-git>
bitcoin/master 292a841 MarcoFalke: Merge bitcoin/bitcoin#24449: fuzz: FuzzedFileProvider::write should not re...
2022-02-27
<bitcoin-git>
[bitcoin] Crypt-iQ opened pull request #24449: fuzz: FuzzedFileProvider::write should not return negative value (master...fopencookie_write) https://github.com/bitcoin/bitcoin/pull/24449
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #24441: fuzz: Limit script_format to 100kB (master...2202-fuzzScriptFormat100k-🤙) https://github.com/bitcoin/bitcoin/pull/24441
<bitcoin-git>
[bitcoin] MarcoFalke closed pull request #24028: doc: Explain in the generate* RPC docs that they are only for testing (master...202201_rpcmining_lol_no) https://github.com/bitcoin/bitcoin/pull/24028
<bitcoin-git>
bitcoin/master fa0819e MarcoFalke: doc: Move peer-review paragraph to right section
<bitcoin-git>
bitcoin/master fa2b65b MarcoFalke: doc: Add link to release-process.md in CONTRIBUTING.md
<bitcoin-git>
bitcoin/master fa694f6 MarcoFalke: doc: Explain that feedback needs to be addressed
<bitcoin-git>
[bitcoin] fanquake opened pull request #24440: doc: update maintainer list in REVIEWERS (master...update_reviewers_maintainers) https://github.com/bitcoin/bitcoin/pull/24440
<prayank>
I have seen putin with vitalik in 2017 and bitcoin is obviously better so expecting your infosec team runs the software created in this repository. Please stop this nonsense. No communities or countries ever achieved anything good with such things in past. Humans like you get affected at ground level maybe some people that you consider collateral damage but they are same as you. Nobody would say anything to some extent for some
<jeremyrubin>
it'd also be good if 1 bitcoin.conf could configure >1 signet so i think the [signet.xyz] format is probably right
<jeremyrubin>
It would also be nice if bitcoin core could have multiple signets in the chain configs
<laanwj>
luke-jr: there was some discussion about it at the time and we moved it into bitcoin-core at some point https://github.com/bitcoin-core/bitcoin-acks , but no one picked it up
<jeremyrubin>
or if bitcoin.conf could have multiple [signet.xyz]'s for configging different named signets
<MarcoFalke>
luke-jr: No one signs review comments, so a GitHub employee can hijack Bitcoin Core if maintainers blindly click the merge button without thinking
<laanwj>
one proposed meeting topic this week (you can propose meeting topics during the week with #proposedmeetingtopic): Bitcoin Core contributor survey (ajonas)
<sipa>
I believe that what it states is correct - it just doesn't match the implementation details of how the Bitcoin Core chooses to achieve that. And you're interpreting it as a diff w.r.t. that implementation.
<roasbeef>
sipa: what do you think about this PR: https://github.com/bitcoin/bips/pull/1284 ? it's that change re checksigverify I mentioned a few days ago w/ some slight modifications
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #24433: doc: Explain that feedback needs to be addressed (master...2202-doc-contrib-🐆) https://github.com/bitcoin/bitcoin/pull/24433
<bitcoin-git>
[bitcoin] fanquake closed pull request #24429: Remove the phrase "Experimental" from section what is bitcoin? (master...patch-1) https://github.com/bitcoin/bitcoin/pull/24429
<bitcoin-git>
[bitcoin] ucallmerk opened pull request #24429: Remove the phrase "Experimental" from section what is bitcoin? (master...patch-1) https://github.com/bitcoin/bitcoin/pull/24429
<bitcoin-git>
bitcoin/master f062abe MarcoFalke: Merge bitcoin/bitcoin#24419: lint: remove no-longer used exceptions from l...
<bitcoin-git>
bitcoin/master 5b8f248 fanquake: lint: remove no-longer used exceptions from lint-format-strings.py
2022-02-22
<bitcoin-git>
[bitcoin] jonatack opened pull request #24424: doc: release process chainparams updates (master...release-process-chainparams-updates) https://github.com/bitcoin/bitcoin/pull/24424
<bitcoin-git>
[gui] luke-jr opened pull request #557: Revert "qt: Do not use QObject::tr plural syntax for numbers with a unit symbol" (master...gui_numeric_GBs) https://github.com/bitcoin-core/gui/pull/557
<willcl_ark>
What purpose exactly does the `CTransactionRef` serve? e.g. when processing incoming transactions in https://github.com/bitcoin/bitcoin/blob/master/src/net_processing.cpp#L3289 In the subsequent lines we seem to use a combination of `tx` and `ptx` for various operations and I don't see what the distinction is.
<bitcoin-git>
[bitcoin] laanwj opened pull request #24417: net: Update hardcoded seeds for 23.x (master...2022-02-hardcoded-seeds-update) https://github.com/bitcoin/bitcoin/pull/24417
<laanwj>
provoostenator: anecdotally i've also noticed bitcoin core estimates fees on the low side recently for transactions it makes, haven't encountered not meeting the minrelayfee though
<bitcoin-git>
[bitcoin] MarcoFalke closed pull request #19002: docs: Document that 'fee' is unavailable when there are non-wallet inputs (master...202005-docs-fee) https://github.com/bitcoin/bitcoin/pull/19002
<bitcoin-git>
[bitcoin] dongcarl opened pull request #24410: [kernel 2a/n] Split hashing/index `GetUTXOStats` codepaths, decouple from `coinstatsindex` (master...2022-02-libbitcoinkernel-p2-coinstats-minimal) https://github.com/bitcoin/bitcoin/pull/24410
<bitcoin-git>
[bitcoin] fanquake opened pull request #24409: Always output license/copyright info with `-version` (master...24263_followups) https://github.com/bitcoin/bitcoin/pull/24409
<bitcoin-git>
[bitcoin] vasild opened pull request #24407: fees: make the class FeeFilterRounder thread-safe (master...FeeFilterRounder_thread_safe) https://github.com/bitcoin/bitcoin/pull/24407
<bitcoin-git>
[bitcoin] MarcoFalke merged pull request #24370: rpc, cli: describe quality/recency filtering in getnodeaddresses and -addrinfo (master...mention-quality-filter-in-getnodeaddresses-and-addrinfo) https://github.com/bitcoin/bitcoin/pull/24370
<bitcoin-git>
bitcoin/master fab8cd5 MarcoFalke: Revert "ci: Run fuzzer task for the master branch only"
<bitcoin-git>
bitcoin/master fa27745 MarcoFalke: ci: Bump fuzz tasks to jammy
<bitcoin-git>
bitcoin/master 2ab4fbe fanquake: Merge bitcoin/bitcoin#24292: Revert "ci: Run fuzzer task for the master br...
<hebasto>
provoostenator: nice to see https://github.com/bitcoin-core/gui/pull/555 -- it's very similar to my approach I'm currently working on. The only concern is we are past "string freeze" point -- hope no new and changed strings, although, did not check yet
<bitcoin-git>
[bitcoin] MarcoFalke merged pull request #24339: rpc: Improve RPC help by explicitly mentioning output types (master...feature/2022-02-output-types) https://github.com/bitcoin/bitcoin/pull/24339
<bitcoin-git>
bitcoin/master 1337b93 MarcoFalke: Merge bitcoin/bitcoin#24339: rpc: Improve RPC help by explicitly mentionin...