Bitcoin Core Github
44 subscribers
120K links
Download Telegram
⚠️ henark opened an issue: "test: Create and maintain a test coverage risk matrix for consensus-critical modules"
(https://github.com/bitcoin/bitcoin/issues/32852)
Problem: While coverage reports exist, there is no formal process for prioritizing test development based on risk. Academic analysis and CVE history show that bugs in high-complexity, consensus-critical code are the most dangerous. A latent bug in a low-coverage area of validation.cpp is far more severe than one in the GUI.

Proposal: Introduce a documented process and associated tooling (e.g., a CI script) that combines code complexity metrics (e.g., cyclomatic complexity) with test coverage da
...
⚠️ henark opened an issue: "p2p: Implement proactive check for stale connections to mitigate eclipse attack vectors"
(https://github.com/bitcoin/bitcoin/issues/32853)
Problem: Eclipse attacks rely on monopolizing a node's connection slots. While Bitcoin Core rotates connections, a sophisticated attacker can attempt to keep connections open but unresponsive, or feed them low-utility data to prevent them from being dropped. The current 90-minute inactivity timeout may be too long.

Proposal: Implement a more proactive health check for peer connections. Beyond the simple ping message, this could involve a challenge-response mechanism that lightly queries the pee
...
⚠️ henark opened an issue: "research: Investigate feasibility of applying formal modeling to critical C++ consensus logic"
(https://github.com/bitcoin/bitcoin/issues/32854)
Problem: There is a significant assurance gap between the formally verified libsecp256k1 library and the unverified C++ code that implements the consensus rules which use it. Academic work has focused on modeling the protocol, not the C++ implementation. This gap is where subtle, critical bugs like CVE-2018-17144 can arise.

Proposal: Initiate a research track to explore the application of formal verification tools for C++ (e.g., Frama-C++, VeriFast, TIS-Analyzer) to a small but critical piece o
...
💬 achow101 commented on pull request "wallet: Remove ISMINE_WATCHONLY and watchonly from RPCs":
(https://github.com/bitcoin/bitcoin/pull/32618#issuecomment-3025100533)
Removed the `include_watchonly=True`.
achow101 closed an issue: "refactor: Standardize logging levels and increase granularity in P2P and mempool modules"
(https://github.com/bitcoin/bitcoin/issues/32851)
💬 achow101 commented on issue "refactor: Standardize logging levels and increase granularity in P2P and mempool modules":
(https://github.com/bitcoin/bitcoin/issues/32851#issuecomment-3025113896)
Please do not use AI to spam open issues.
💬 achow101 commented on pull request "doc: clarify that the "-j N" goes after the "--build build" part":
(https://github.com/bitcoin/bitcoin/pull/32846#issuecomment-3025180099)
ACK 0e9f409db3b7b08aef75ce39765b018b69cc8e9d
🚀 achow101 merged a pull request: "doc: clarify that the "-j N" goes after the "--build build" part"
(https://github.com/bitcoin/bitcoin/pull/32846)
💬 pablomartin4btc commented on pull request "rpc, test: Fix JSON parsing errors in unloadwallet and getdescriptoractivity RPCs":
(https://github.com/bitcoin/bitcoin/pull/32845#discussion_r2178357373)
... it would make the code clearer... and we can handle the errors within that function instead... Thanks! Checking it...
💬 ryanofsky commented on pull request "ipc: Handle unclean shutdowns better":
(https://github.com/bitcoin/bitcoin/pull/32345#issuecomment-3025223286)
Rebased a67f3b07d4a1ea9289d4f7d5d3536fe2033b67b4 -> 0a9a1940782fad8dc3494c4aacee0a06c030eb5c ([`pr/ipc-stop.15`](https://github.com/ryanofsky/bitcoin/commits/pr/ipc-stop.15) -> [`pr/ipc-stop.16`](https://github.com/ryanofsky/bitcoin/commits/pr/ipc-stop.16), [compare](https://github.com/ryanofsky/bitcoin/compare/pr/ipc-stop.15-rebase..pr/ipc-stop.16)) after https://github.com/bitcoin-core/libmultiprocess/pull/186 merge. Marking ready for review again
🤔 ishaanam reviewed a pull request: "test: check P2SH sigop count for coinbase tx"
(https://github.com/bitcoin/bitcoin/pull/32850#pullrequestreview-2976751489)
ACK d6aaffcb11adcf47480fcc5081af9dcb732decf3
🤔 w0xlt reviewed a pull request: "wallet: Replace CWalletTx::mapValue and vOrderForm with explicit class members"
(https://github.com/bitcoin/bitcoin/pull/32763#pullrequestreview-2976772441)
ACK https://github.com/bitcoin/bitcoin/pull/32763/commits/9a8fd16e67755e336de683c0158d4fdd2b4ddfe8.
`value_map` and `order_form` (and therefore `WalletOrderForm` and `WalletValueMap`) lack clarity, making replacing with well-defined fields a much better approach.
🤔 ismaelsadeeq reviewed a pull request: "refactor: CFeeRate encapsulates FeeFrac internally"
(https://github.com/bitcoin/bitcoin/pull/32750#pullrequestreview-2976133077)
The current iteration is looking better, I will do another round of review and testing tomorrow.

Just a few nits after a short glance
💬 ismaelsadeeq commented on pull request "refactor: CFeeRate encapsulates FeeFrac internally":
(https://github.com/bitcoin/bitcoin/pull/32750#discussion_r2178028452)
nit: be less ambiguous?
```suggestion
const CAmount feerate_per_kvb = GetFeePerK();
```
💬 ismaelsadeeq commented on pull request "refactor: CFeeRate encapsulates FeeFrac internally":
(https://github.com/bitcoin/bitcoin/pull/32750#discussion_r2178446483)
nit:
includes are alphabetical
💬 pablomartin4btc commented on pull request "rpc, test: Fix JSON parsing errors in unloadwallet and getdescriptoractivity RPCs":
(https://github.com/bitcoin/bitcoin/pull/32845#discussion_r2178453208)
Also, RPC `migratewallet` calls the same function so I could refactor that instance too.