Bitcoin Core Github
44 subscribers
120K links
Download Telegram
πŸ’¬ polespinasa commented on pull request "rpc: generatetomany":
(https://github.com/bitcoin/bitcoin/pull/32468#issuecomment-2893727699)
> Perhaps we can make the second argument of `generateblock` optional, and if there is no set of txs provided then mine the mempool.

This is implemented here 8b5dd8a5f135ce1aaf80d8c28943f503f4ee19d4
With a small difference, if no set of txs is provided then we mine the mempool, if an empty set is provided we mine an empty block (original behaviour of the RPC).

Note: for the moment fee collector is not implemented if a set of tx is set manually
πŸ’¬ vasild commented on pull request "Broadcast own transactions only via short-lived Tor or I2P connections":
(https://github.com/bitcoin/bitcoin/pull/29415#issuecomment-2893760250)
`32488cfd6c...fb12a062b8`: rebase due to conflicts
πŸ’¬ Sjors commented on pull request "Add checkBlock() to Mining interface":
(https://github.com/bitcoin/bitcoin/pull/31981#issuecomment-2893793850)
Trivial rebase after #32562, dropped changes in RPC code and added a comment in the test.
πŸ’¬ hebasto commented on pull request "cmake: Remove `ENABLE_{SSE41,AVX2,X86_SHANI,ARM_SHANI}` from `bitcoin-build-config.h`":
(https://github.com/bitcoin/bitcoin/pull/32551#issuecomment-2893800893)
Rebased to resolve a conflict with the merged bitcoin/bitcoin#32477.
πŸ€” polespinasa reviewed a pull request: "rpc: Round verificationprogress to 1 for a recent tip"
(https://github.com/bitcoin/bitcoin/pull/32528#pullrequestreview-2853652269)
tACK fa53098472521de9d5b3cc42983043c240b7c321

Left a small comment
πŸ’¬ polespinasa commented on pull request "rpc: Round verificationprogress to 1 for a recent tip":
(https://github.com/bitcoin/bitcoin/pull/32528#discussion_r2097622471)
I guess `GetConsensus().nPowTargetSpacing` returns 10min?

If so, could we use this even if the block being validated is not within the 2h range? I think we could just never rely on miner-set timestamps.
πŸ‘ willcl-ark approved a pull request: "doc: add missing copyright headers"
(https://github.com/bitcoin/bitcoin/pull/31864#pullrequestreview-2853699729)
ACK c7c3bfadfc6e294547cbc0077a175845c0633906

This changeset:

- Adds copyright headers to files where they're missing
- Updates copyright headers which are missing "group" info (i.e. to whom the copyright is granted)

It does **not** update all headers with "-present". This is left for a future change.

I did a cursory check on git files to see if any had been missed using:

```bash
❯ fd -e cpp -e h -e py -E src/secp256k1 -E src/leveldb -E src/minisketch -E src/crc32 | xargs rg --pc
...
πŸ“ hebasto opened a pull request: "subprocess: Backport upstream changes"
(https://github.com/bitcoin/bitcoin/pull/32567)
A list of the backported PRs:
- https://github.com/arun11299/cpp-subprocess/pull/119

The following PRs were skipped for backporting:
- https://github.com/arun11299/cpp-subprocess/pull/118 because there is no changes in the header code.

Required for https://github.com/bitcoin/bitcoin/pull/32566.
πŸ’¬ hebasto commented on pull request "subprocess: Backport upstream changes":
(https://github.com/bitcoin/bitcoin/pull/32567#issuecomment-2893909163)
cc @laanwj
πŸ’¬ hebasto commented on pull request "Use subprocess library for notifications":
(https://github.com/bitcoin/bitcoin/pull/32566#discussion_r2097661935)
Backported from upstream in https://github.com/bitcoin/bitcoin/pull/32567.
πŸ’¬ fanquake commented on pull request "subprocess: Backport upstream changes":
(https://github.com/bitcoin/bitcoin/pull/32567#issuecomment-2893928418)
Can't this just go in with #32566? Why does it need it's own PR?
πŸ€” rkrux reviewed a pull request: "wallet: Fix logging of wallet version"
(https://github.com/bitcoin/bitcoin/pull/32553#pullrequestreview-2853743852)
ACK 4b2cd0b41ff4800c8801f2c44883eaec60a035fa

I can see the difference in the logs, certainly better to have.

**Master**
```
2025-05-20T10:31:39Z init message: Loading wallet…
2025-05-20T10:31:39Z [test] Wallet file version = 10500, last client version = 299900
2025-05-20T10:31:40Z [test] Descriptors: 13, Descriptor Keys: 1 plaintext, 0 encrypted, 1 total.
```

**PR**
```
2025-05-20T10:22:15Z init message: Loading wallet…
2025-05-20T10:22:15Z [test] Last client version = 299900
2
...
πŸ’¬ hebasto commented on pull request "subprocess: Backport upstream changes":
(https://github.com/bitcoin/bitcoin/pull/32567#issuecomment-2893947117)
> Can't this just go in with #32566? Why does it need it's own PR?

It would be easier to track backports.
⚠️ maflcko reopened an issue: "intermittent issue in rpc_signer.py (enumeratesigners timeout)"
(https://github.com/bitcoin/bitcoin/issues/32524)
https://cirrus-ci.com/task/5094568045051904?logs=ci#L4419

```
[18:26:32.573] test_framework.authproxy.JSONRPCException: 'enumeratesigners' RPC took longer than 1200.000000 seconds. Consider using larger timeout for calls that take longer to return. (-344)
```

Looking at the full log, the test is just idle and then times out. However, there is no indication why the RPC does not proceed.
πŸ’¬ maflcko commented on issue "intermittent issue in rpc_signer.py (enumeratesigners timeout)":
(https://github.com/bitcoin/bitcoin/issues/32524#issuecomment-2893966294)
It even happens on gcc-14, it seems:

https://cirrus-ci.com/task/5476449961902080?logs=ci#L5506
πŸš€ fanquake merged a pull request: "doc: add missing copyright headers"
(https://github.com/bitcoin/bitcoin/pull/31864)
πŸš€ fanquake merged a pull request: "wallet: Fix logging of wallet version"
(https://github.com/bitcoin/bitcoin/pull/32553)
πŸš€ fanquake merged a pull request: "Reintroduce external signer support for Windows"
(https://github.com/bitcoin/bitcoin/pull/29868)
πŸ“ fanquake opened a pull request: "depends: use "mkdir -p" when installing xproto"
(https://github.com/bitcoin/bitcoin/pull/32568)
It looks like the mkdir detection in xproto is broken on Alpine. Ensure we always use `mkdir -p`.

Fixes #32494.
πŸ’¬ fanquake commented on pull request "wallet: Fix logging of wallet version":
(https://github.com/bitcoin/bitcoin/pull/32553#issuecomment-2894002871)
Backported to `29.x` in #32292.