Bitcoin Core Github
44 subscribers
120K links
Download Telegram
πŸ’¬ pythcoiner commented on pull request "wallet: warn against accidental unsafe older() import":
(https://github.com/bitcoin/bitcoin/pull/33135#discussion_r2346604199)
nit: should we keep this debug log?
πŸ’¬ pythcoiner commented on pull request "wallet: warn against accidental unsafe older() import":
(https://github.com/bitcoin/bitcoin/pull/33135#discussion_r2346586549)
nit: not sure if those includes are stricly required?
πŸ’¬ pythcoiner commented on pull request "wallet: warn against accidental unsafe older() import":
(https://github.com/bitcoin/bitcoin/pull/33135#discussion_r2346503278)
nit (for consistency)
```suggestion
/** Semantic/safety warnings (includes subdescriptors). */
```
πŸ’¬ HowHsu commented on pull request "help: enrich help text for `-loadblock`":
(https://github.com/bitcoin/bitcoin/pull/33343#discussion_r2346751467)
Hi l0rinc,
I’ve updated the code. Since I’m not very familiar with the Bitcoin Core workflow, I wasn’t sure if it’s appropriate for me to mark this conversation as resolved, but I went ahead and did so. Please feel free to reopen it if that’s not the right process.
πŸ’¬ Raimo33 commented on issue "bench: unrealistic ConnectBlock benchmarks":
(https://github.com/bitcoin/bitcoin/issues/33375#issuecomment-3288478820)
it's not "a little bit of faithfulness" that you sacrifice. you're ignoring the cache completely.
πŸ’¬ Raimo33 commented on pull request "log: show reindex progress in `ImportBlocks`":
(https://github.com/bitcoin/bitcoin/pull/33353#discussion_r2346773084)
precompute the division?
πŸ’¬ Raimo33 commented on pull request "log: show reindex progress in `ImportBlocks`":
(https://github.com/bitcoin/bitcoin/pull/33353#issuecomment-3288490603)
Concept ACK
πŸ’¬ sdaftuar commented on pull request "Cluster mempool implementation":
(https://github.com/bitcoin/bitcoin/pull/28676#discussion_r2346795265)
I didn't want to impose an ordering requirement on transactions being added to staging, which means that every time we add a new transaction, we'd have to loop over all the other transactions to see if any of them depend on the new one, so we get a complexity improvement (quadratic vs linear) by doing it in one pass at the end.
πŸ“ caesrcd opened a pull request: "contrib: add bash completion for new bitcoin command"
(https://github.com/bitcoin/bitcoin/pull/33385)
Adds a bash completion script for the new bitcoin command-line tool (introduced in #31375), which unifies the main Bitcoin Core executables under a single interface. This feature improves usability, reduces errors, and makes the command-line tools more easily discoverable for users working in a Linux bash environment.

The completion script dynamically lists available commands and options by parsing `bitcoin --help` and `bitcoin help`. It also incorporates the existing bash completions for `bi
...
πŸ’¬ stringintech commented on pull request "kernel: Introduce initial C header API":
(https://github.com/bitcoin/bitcoin/pull/30595#discussion_r2346797667)
Ah, I see. Thanks!
Just noticed another potential race condition between user checking for index out of bounds and the actual `btck_chain_get_by_height()` call. Like [here](https://github.com/TheCharlatan/rust-bitcoinkernel/blob/92f9e51555dcafb00702e665c865e5d9715a2f4d/src/lib.rs#L1774:L1786) in the rust wrapper; which could trigger the assert condition. πŸ€”
πŸ“ fanquake reopened a pull request: "contrib: add bash completion for new bitcoin command"
(https://github.com/bitcoin/bitcoin/pull/33385)
Adds a bash completion script for the new bitcoin command-line tool (introduced in #31375), which unifies the main Bitcoin Core executables under a single interface. This feature improves usability, reduces errors, and makes the command-line tools more easily discoverable for users working in a Linux bash environment.

The completion script dynamically lists available commands and options by parsing `bitcoin --help` and `bitcoin help`. It also incorporates the existing bash completions for `bi
...
πŸ’¬ caesrcd commented on pull request "Bash completion for the new bitcoin wrapper command":
(https://github.com/bitcoin/bitcoin/pull/33383#issuecomment-3288553563)
@fanquake I opened a new (third) PR: #33385
Unfortunately, the bot closed it again, likely due to the same heuristic applied to the previously closed PRs (first-time contributor + new file).

However, as requested, the third PR has been created from a new branch. If possible, I kindly ask that this new PR be reopened.
πŸ’¬ sipa commented on pull request "Cluster mempool implementation":
(https://github.com/bitcoin/bitcoin/pull/28676#discussion_r2346822062)
I'm wrong about this: https://godbolt.org/z/zKq3fMrEc

Marking resolved.
πŸ’¬ sdaftuar commented on pull request "Cluster mempool implementation":
(https://github.com/bitcoin/bitcoin/pull/28676#discussion_r2346825428)
Is it possible that we might have failure in the individual setting with a cluster size limit being exceeded, which then is not the case in a package setting, if some additional package transaction conflicts with transactions in the cluster being added to?
πŸ’¬ sdaftuar commented on pull request "Cluster mempool implementation":
(https://github.com/bitcoin/bitcoin/pull/28676#discussion_r2346830449)
Reworked this a bit -- please let me know if this looks better now or if additional comments would be helpful.
πŸ’¬ sdaftuar commented on pull request "Cluster mempool implementation":
(https://github.com/bitcoin/bitcoin/pull/28676#discussion_r2346830740)
Yes, I think so -- I've deleted this comment, as well as the already-commented-out test that is no longer relevant.
πŸ’¬ sdaftuar commented on pull request "Cluster mempool implementation":
(https://github.com/bitcoin/bitcoin/pull/28676#discussion_r2346830781)
Thanks! Guessing this was a rebase error; fixed.
πŸ’¬ sdaftuar commented on pull request "Cluster mempool implementation":
(https://github.com/bitcoin/bitcoin/pull/28676#discussion_r2346830834)
Done.
πŸ’¬ sdaftuar commented on pull request "Cluster mempool implementation":
(https://github.com/bitcoin/bitcoin/pull/28676#discussion_r2346830927)
Fixed, thanks.
πŸ’¬ sdaftuar commented on pull request "Cluster mempool implementation":
(https://github.com/bitcoin/bitcoin/pull/28676#discussion_r2346830947)
Done.