π achow101 merged a pull request: "net: Decrease nMaxIPs when learning from DNS seeds"
(https://github.com/bitcoin/bitcoin/pull/29850)
(https://github.com/bitcoin/bitcoin/pull/29850)
π¬ josibake commented on pull request "Silent payment index (for light wallets and consistency check)":
(https://github.com/bitcoin/bitcoin/pull/28241#discussion_r1575031937)
Added a new function `GetSerializedSilentPaymentsPublicData` that returns a `CPubKey`.
(https://github.com/bitcoin/bitcoin/pull/28241#discussion_r1575031937)
Added a new function `GetSerializedSilentPaymentsPublicData` that returns a `CPubKey`.
π¬ josibake commented on pull request "Silent payment index (for light wallets and consistency check)":
(https://github.com/bitcoin/bitcoin/pull/28241#discussion_r1575032154)
also lol at the `// TODO` comment
(https://github.com/bitcoin/bitcoin/pull/28241#discussion_r1575032154)
also lol at the `// TODO` comment
π¬ mzumsande commented on pull request "validation: improve performance of CheckBlockIndex":
(https://github.com/bitcoin/bitcoin/pull/28339#discussion_r1575035825)
fixed
(https://github.com/bitcoin/bitcoin/pull/28339#discussion_r1575035825)
fixed
π¬ mzumsande commented on pull request "validation: improve performance of CheckBlockIndex":
(https://github.com/bitcoin/bitcoin/pull/28339#discussion_r1575039039)
> I agree it could potentially be confused with the active chain in new code, and that would be a bug.
I added a comment in `CheckBlockIndex()` describing why these can differ.
(https://github.com/bitcoin/bitcoin/pull/28339#discussion_r1575039039)
> I agree it could potentially be confused with the active chain in new code, and that would be a bug.
I added a comment in `CheckBlockIndex()` describing why these can differ.
π¬ mzumsande commented on pull request "validation: improve performance of CheckBlockIndex":
(https://github.com/bitcoin/bitcoin/pull/28339#discussion_r1575039363)
done, thanks!
(https://github.com/bitcoin/bitcoin/pull/28339#discussion_r1575039363)
done, thanks!
π¬ mzumsande commented on pull request "validation: improve performance of CheckBlockIndex":
(https://github.com/bitcoin/bitcoin/pull/28339#discussion_r1575039633)
changed to an assert.
(https://github.com/bitcoin/bitcoin/pull/28339#discussion_r1575039633)
changed to an assert.
π¬ mzumsande commented on pull request "validation: improve performance of CheckBlockIndex":
(https://github.com/bitcoin/bitcoin/pull/28339#issuecomment-2070114863)
[e880ee0 ](https://github.com/bitcoin/bitcoin/commit/e880ee0a634f0be5079d39328fa5e118452553a9)to [3c3895c](https://github.com/bitcoin/bitcoin/commit/3c3895ccfa108e10f4a0b1a78f64ffedade1fd11):
Addressed review feedback.
(https://github.com/bitcoin/bitcoin/pull/28339#issuecomment-2070114863)
[e880ee0 ](https://github.com/bitcoin/bitcoin/commit/e880ee0a634f0be5079d39328fa5e118452553a9)to [3c3895c](https://github.com/bitcoin/bitcoin/commit/3c3895ccfa108e10f4a0b1a78f64ffedade1fd11):
Addressed review feedback.
π¬ darosior commented on pull request "sign: don't assume we are parsing a sane TapMiniscript":
(https://github.com/bitcoin/bitcoin/pull/29853#discussion_r1575040757)
I think it emphases the wrong thing: we are not testing it's failing, we are testing it's not crashing. That's why i didn't do it. Anyways it's not really important and there is already a comment highlighting this. Done.
(https://github.com/bitcoin/bitcoin/pull/29853#discussion_r1575040757)
I think it emphases the wrong thing: we are not testing it's failing, we are testing it's not crashing. That's why i didn't do it. Anyways it's not really important and there is already a comment highlighting this. Done.
π¬ laanwj commented on issue "RFC: In guix compile the GUI sequentially from everything else?":
(https://github.com/bitcoin/bitcoin/issues/29914#issuecomment-2070147285)
FWIW in #29923 i've removed all the GUI specific dependencies except for Qt itself.
(https://github.com/bitcoin/bitcoin/issues/29914#issuecomment-2070147285)
FWIW in #29923 i've removed all the GUI specific dependencies except for Qt itself.
π theStack approved a pull request: "test: Fix intermittent timeout in p2p_tx_download.py"
(https://github.com/bitcoin/bitcoin/pull/29933#pullrequestreview-2015285694)
ACK fa6c300a9926a1d35fdd0a80f59ea39769bd2596
Thanks for fixing!
(https://github.com/bitcoin/bitcoin/pull/29933#pullrequestreview-2015285694)
ACK fa6c300a9926a1d35fdd0a80f59ea39769bd2596
Thanks for fixing!
π¬ RandyMcMillan commented on pull request "Feature: Use different datadirs for different signets":
(https://github.com/bitcoin/bitcoin/pull/29838#issuecomment-2070170967)
You may be able to allow cascading signet
configurations by having a user configured βprefixβ setting.
This may also translate better to a gui dialogue later on as well (hot swapping signets from the gui).
[signet]
prune=1000
prefix=<short_string1>
signetchallenge=1234abcβ¦
signetseednode=...
prefix=<short_string2>
signetchallenge=5678defβ¦
signetseednode=...
(https://github.com/bitcoin/bitcoin/pull/29838#issuecomment-2070170967)
You may be able to allow cascading signet
configurations by having a user configured βprefixβ setting.
This may also translate better to a gui dialogue later on as well (hot swapping signets from the gui).
[signet]
prune=1000
prefix=<short_string1>
signetchallenge=1234abcβ¦
signetseednode=...
prefix=<short_string2>
signetchallenge=5678defβ¦
signetseednode=...
π¬ Sjors commented on pull request "doc: add LLVM instruction for macOS < 13":
(https://github.com/bitcoin/bitcoin/pull/29934#discussion_r1575067094)
That's not that long ago though, and we have `OSX_MIN_VERSION=11.0` for now.
(https://github.com/bitcoin/bitcoin/pull/29934#discussion_r1575067094)
That's not that long ago though, and we have `OSX_MIN_VERSION=11.0` for now.
π¬ laanwj commented on issue "RFC: Formal description of the RPC API":
(https://github.com/bitcoin/bitcoin/issues/29912#issuecomment-2070215202)
> I vaguely recall an issue or discussion around machine-readable API specs in the past, but I cannot find it. I believe @laanwj commented on it.
Much of it is already there, just not exposed. The `RPCHelpMan`/`RPCResult` structure for `help` handling was intended to be a start of formalizing the API, and to have some form of introspection. E.g. types are already checked against the spec while testing. It could be extended to include other data that's needed.
The same data that's used for
...
(https://github.com/bitcoin/bitcoin/issues/29912#issuecomment-2070215202)
> I vaguely recall an issue or discussion around machine-readable API specs in the past, but I cannot find it. I believe @laanwj commented on it.
Much of it is already there, just not exposed. The `RPCHelpMan`/`RPCResult` structure for `help` handling was intended to be a start of formalizing the API, and to have some form of introspection. E.g. types are already checked against the spec while testing. It could be extended to include other data that's needed.
The same data that's used for
...
π€ fjahr reviewed a pull request: "test: Validate UTXO snapshot with coin height > base height & amount > MAX_MONEY supply"
(https://github.com/bitcoin/bitcoin/pull/29617#pullrequestreview-2015164071)
Code review ACK 6428b363e68fee51a455ebd4f9bf7ed6d813caa8
Ignore the nit unless there is other feedback to address or you need to rebase.
(https://github.com/bitcoin/bitcoin/pull/29617#pullrequestreview-2015164071)
Code review ACK 6428b363e68fee51a455ebd4f9bf7ed6d813caa8
Ignore the nit unless there is other feedback to address or you need to rebase.
π¬ fjahr commented on pull request "test: Validate UTXO snapshot with coin height > base height & amount > MAX_MONEY supply":
(https://github.com/bitcoin/bitcoin/pull/29617#discussion_r1574985012)
nit: `exceeds`
(https://github.com/bitcoin/bitcoin/pull/29617#discussion_r1574985012)
nit: `exceeds`
π¬ levantah commented on issue "Release schedule for 27.0":
(https://github.com/bitcoin/bitcoin/issues/29028#issuecomment-2070239920)
This may be also off-topic. Feel free to delete even without reading.
Just to explain where I am coming from, there was a Chaincode Labs Bitcoin seminar done partly by some Core developers and for each run of a test-case it would download Bitcoin binary to Github infrastructure by calling this: `wget -q https://bitcoincore.org/bin/bitcoin-core-26.0/bitcoin-26.0-x86_64-linux-gnu.tar.gz`. It was rather slow. Now imagine hundreds of students. A Bottleneck I would say.
I have no idea how someo
...
(https://github.com/bitcoin/bitcoin/issues/29028#issuecomment-2070239920)
This may be also off-topic. Feel free to delete even without reading.
Just to explain where I am coming from, there was a Chaincode Labs Bitcoin seminar done partly by some Core developers and for each run of a test-case it would download Bitcoin binary to Github infrastructure by calling this: `wget -q https://bitcoincore.org/bin/bitcoin-core-26.0/bitcoin-26.0-x86_64-linux-gnu.tar.gz`. It was rather slow. Now imagine hundreds of students. A Bottleneck I would say.
I have no idea how someo
...
π€ instagibbs reviewed a pull request: "p2p: opportunistically accept 1-parent-1-child packages"
(https://github.com/bitcoin/bitcoin/pull/28970#pullrequestreview-2015296846)
reviewed through 7d220c6a5c0e0c5e8cfe79ebd2eae6e845d1d983
tested and confirmed fuzz coverage is hitting meaningful `GetChildrenFrom*` results
continuing longer range testing
(https://github.com/bitcoin/bitcoin/pull/28970#pullrequestreview-2015296846)
reviewed through 7d220c6a5c0e0c5e8cfe79ebd2eae6e845d1d983
tested and confirmed fuzz coverage is hitting meaningful `GetChildrenFrom*` results
continuing longer range testing
π¬ instagibbs commented on pull request "p2p: opportunistically accept 1-parent-1-child packages":
(https://github.com/bitcoin/bitcoin/pull/28970#discussion_r1575059642)
nit
```Suggestion
BOOST_CHECK(orphanage.GetChildrenFromSamePeer(parent1, node2).empty());
BOOST_CHECK(orphanage.GetChildrenFromSamePeer(parent2, node2).empty());
```
(https://github.com/bitcoin/bitcoin/pull/28970#discussion_r1575059642)
nit
```Suggestion
BOOST_CHECK(orphanage.GetChildrenFromSamePeer(parent1, node2).empty());
BOOST_CHECK(orphanage.GetChildrenFromSamePeer(parent2, node2).empty());
```
π¬ instagibbs commented on pull request "p2p: opportunistically accept 1-parent-1-child packages":
(https://github.com/bitcoin/bitcoin/pull/28970#discussion_r1575061630)
nit
```Suggestion
// There shouldn't be any children of this tx in orphanage
```
(https://github.com/bitcoin/bitcoin/pull/28970#discussion_r1575061630)
nit
```Suggestion
// There shouldn't be any children of this tx in orphanage
```