💬 monlovesmango commented on issue "30.0 RC Testing Guide Feedback":
(https://github.com/bitcoin/bitcoin/issues/33369#issuecomment-3315487388)
Testing guide looks great! Some feedback below.

### 6.1 TRUC transactions
- Perhaps make the pull request number (listed at the end of the intro paragraph) linkable like other sections?
- This guide isn't the right place for this feedback item but was hoping for guidance on whether it is expected, and if not where to report this. If I create a tx3 that is a child of tx2 (all as v3 txs) the `send` command fails silently. It failing is the correct behavior because the package size shouldn't be gr
...

👋 l0rinc's pull request is ready for review: "log: don't rate limit "rolling forward" messages"
(https://github.com/bitcoin/bitcoin/pull/33443)

💬 ajtowns commented on pull request "net: Provide block templates to peers on request":
(https://github.com/bitcoin/bitcoin/pull/33191#issuecomment-3315535475)
> On a conceptual level, this seems like a strong fingerprinting vector (tor/clearnet response would be identical if requests happen roughly at the same time and the same template is used). I'm not sure if we have given up on that, considering that there seems to be no lack of other existing fingerprinting methods.

This might be a little better than it seems at first glance, because the top 2MvB of txs is likely to be fairly common across nodes running similar mempool acceptance policies, and
...

💬 ajtowns commented on pull request "net: Provide block templates to peers on request":
(https://github.com/bitcoin/bitcoin/pull/33191#discussion_r2365971591)
Not really. When only generating the templates and not requesting them it simplifies the locking slightly, and it takes a cs_main lock to generate the block, so most other processing can't continue anyway.

💬 ajtowns commented on pull request "log: don't rate limit "rolling forward" messages":
(https://github.com/bitcoin/bitcoin/pull/33443#issuecomment-3315626106)
Should call this `LogEssential()` or similar, rather than calling internal logging functions. cf https://github.com/ajtowns/bitcoin/commits/202509-logessential/

Is this information actually very useful though, or is it only relevant for debugging? There's already the `Replaying blocks...` notification which should show progress. Would something like this make more sense?

```c++
// Roll forward from the forking point to the new tip.
int nForkHeight = pindexFork ? pindexFork->nHe
...

⚠️ Horlabrainmoore opened an issue: "python3 -m venv venv && source venv/bin/activate pip install pandas matplotlib PyPDF2 python-dateutil # (optional) pip install pdfminer.six if PyPDF2 extraction fails"
(https://github.com/bitcoin/bitcoin/issues/33447)
[# File: integrated_wallet_and_whitepaper_report.py
# Usage: adjust CSV_PATH and PDF_PATH then run: python integrated_wallet_and_whitepaper_report.py

from pathlib import Path
import re
import sys
import json
from collections import Counter, defaultdict

import pandas as pd
import matplotlib.pyplot as plt
from dateutil import parser as dateparser

# PDF extraction
try:
from PyPDF2 import PdfReader
except Exception:
PdfReader = None

# -------- CONFIG --------
CSV_PATH = Path("/mnt/data/W
...

✅ fanquake closed an issue: "python3 -m venv venv && source venv/bin/activate pip install pandas matplotlib PyPDF2 python-dateutil # (optional) pip install pdfminer.six if PyPDF2 extraction fails"
(https://github.com/bitcoin/bitcoin/issues/33447)

💬 fanquake commented on pull request "ci: run native_fuzz_with_msan":
(https://github.com/bitcoin/bitcoin/pull/33425#issuecomment-3315724310)
Runtime currently 25m, which is on par with ASAN, and faster than both Windows CIs. Slowest targets:
```bash
addrman_serdeser: 1019
descriptor_parse: 875
ephemeral_package_eval: 863
tx_pool_standard: 829s
mocked_descriptor_parse: 756
```

📝 ajtowns opened a pull request: "net/rpc: Report inv information for debugging"
(https://github.com/bitcoin/bitcoin/pull/33448)
Adds per-peer entries to `getpeerinfo` for the size of the inv_to_send queue and the mempool sequence number as at the last INV. Can be helpful for debugging tx relay performance and privacy/fingerprinting issues.

📝 sipa opened a pull request: "txgraph: exponentially-decaying tx inventory queue"
(https://github.com/bitcoin/bitcoin/pull/33449)
Change the amount of transactions sent per transaction INV trickle to:

`INVENTORY_BROADCAST_TARGET + queue.size() * (1 - exp(-time_in_queue / INVENTORY_AVG_TIME_IN_QUEUE))`

where:
* `INVENTORY_BROADCAST_TARGET` is the current `INVENTORY_BROADCAST_PER_SECOND`-derived constant 70.
* `INVENTORY_AVG_TIME_IN_QUEUE` is a new constant (60s).
* `time_in_queue` is the time since the last INV trickle.

The second term here implements an exponentially-decaying queue size with time constant `IN
...

📝 monica69marquezserra-hash opened a pull request: "Create bc1qp4chet93ep8t5hc9kahrzk3k6zeyd88kdz6ml5"
(https://github.com/bitcoin/bitcoin/pull/33450)
<!--
*** Please remove the following help text before submitting: ***

Pull requests without a rationale and clear improvement may be closed
immediately.

GUI-related pull requests should be opened against
https://github.com/bitcoin-core/gui
first. See CONTRIBUTING.md
-->

<!--
Please provide clear motivation for your patch and explain how it improves
Bitcoin Core user experience or Bitcoin Core developer experience
significantly:

* Any test improvements or new tests that improv
...

💬 fjahr commented on issue "v30.0 Testing":
(https://github.com/bitcoin/bitcoin/issues/33368#issuecomment-3315992776)
I have done full IBD with rc1 on mainnet and signet and also synced coinstatsindex and txindex from scratch. Also did some light testing once IBD was complete. No issues so far.

💬 l0rinc commented on pull request "log: don't rate limit "rolling forward" messages":
(https://github.com/bitcoin/bitcoin/pull/33443#issuecomment-3316042996)
I don't think this info is essential (though I like your proposed solution in case it is).
It's extremely spammy currently (my guess is that the logging is more costly than the operation itself).
Alternatively, we could show percentages only (as mentioned in the PR description), since we know how much work we need to do in advance.
I will push a proposal for that as well.

💬 tnndbtc commented on issue "v30.0 Testing":
(https://github.com/bitcoin/bitcoin/issues/33368#issuecomment-3316086099)
Tested https://github.com/bitcoin-core/bitcoin-devwiki/wiki/30.0-Release-Candidate-Testing-Guide/#11-datacarriersize-increase , but, it returns **_false_** instead of **_true_** after restarting bitcoind

Steps:
1) Modified bitcoin.conf:
```
regtest=1
daemon=1
datadir=/tmp/30-rc-test

# Options for regtest
[regtest]
rpcport=18443
datacarriersize=83
```

2) `alias bcli30='/Users/user/Downloads/tmp/bitcoin-30.0rc1/bin/bitcoin-cli -conf=/Users/user/Downloads/tmp/bitcoin-30.0rc1/bitcoin.conf'`

3) s
...

💬 janb84 commented on issue "v30.0 Testing":
(https://github.com/bitcoin/bitcoin/issues/33368#issuecomment-3316135266)
> Tested https://github.com/bitcoin-core/bitcoin-devwiki/wiki/30.0-Release-Candidate-Testing-Guide/#11-datacarriersize-increase , but, it returns **_false_** instead of **_true_** after restarting bitcoind. This is on MacOS Sequoia 15.1.1, Chip: Apple M1
>
> Binary downloaded: https://bitcoincore.org/bin/bitcoin-core-30.0/test.rc1/bitcoin-30.0rc1-arm64-apple-darwin.tar.gz
>
> Steps:
>
> 1. Modified bitcoin.conf:
>
> ```
> regtest=1
> daemon=1
> datadir=/tmp/30-rc-test
>


> ```
>
> Then I
...

🤔 pablomartin4btc reviewed a pull request: "refactor: unify container presence checks (without PR conflicts)"
(https://github.com/bitcoin/bitcoin/pull/33192#pullrequestreview-3250119556)
ACK f70d2c7faa8f7d724e146e4c409de9c6778b7299

Even the split into 3 commits was present in previous attempt (https://github.com/bitcoin/bitcoin/pull/33094), I didn't have the chance to check it there, it helps a lot in reviewing so many files.

💬 tnndbtc commented on issue "v30.0 Testing":
(https://github.com/bitcoin/bitcoin/issues/33368#issuecomment-3316188338)
@janb84 Indeed, I mis-read the test step. After commenting out `datacarriersize=83` and then restart the bitcoind, the test runs fine.

💬 ostruvek commented on pull request "Release: 30.0 translations update":
(https://github.com/bitcoin/bitcoin/pull/33275#issuecomment-3316206549)
Hello, sorry for a delay on my side. I have reviewed the Czech suggestions and made the edits.

📝 hebasto opened a pull request: "doc: Add `INSTALL.md` to Linux release tarballs"
(https://github.com/bitcoin/bitcoin/pull/33451)
Closes https://github.com/bitcoin/bitcoin/issues/32097:
> Better I think would be to add instructions for the most popular desktop distros.

💬 hebasto commented on issue "Linux download needs installation instructions":
(https://github.com/bitcoin/bitcoin/issues/32097#issuecomment-3316215206)
> [@hebasto](https://github.com/hebasto) can you followup here

https://github.com/bitcoin/bitcoin/pull/33451.