Bitcoin Core Github
44 subscribers
121K links
Download Telegram
📝 BrandonOdiwuor opened a pull request: "gui: add used balance to overview page"
(https://github.com/bitcoin-core/gui/pull/775)
**Second part** of solving https://github.com/bitcoin-core/gui/issues/769

Add used balance to the overview page for wallets with the avoid_reuse flag enabled

### Prerequsite:

- **Part one**: https://github.com/bitcoin/bitcoin/pull/28776

overview page when avoid_reuse is enabled
![Screenshot from 2023-11-02 18-10-06](https://github.com/bitcoin-core/gui/assets/15610188/825a29f9-0558-4957-a079-1cb707421986)

overview page when avoid_reuse is not enabled
![Screenshot from 2023-11-03
...
💬 BrandonOdiwuor commented on issue "`used` balance should be shown on overview page":
(https://github.com/bitcoin-core/gui/issues/769#issuecomment-1792061121)
Created two PRs on this issue:

- Part one: https://github.com/bitcoin/bitcoin/pull/28776
- Part two: https://github.com/bitcoin-core/gui/pull/775
💬 glozow commented on pull request "refactors for subpackage evaluation":
(https://github.com/bitcoin/bitcoin/pull/28758#discussion_r1381323292)
I don't think it's that helpful to list more things this function *doesn't* check.
👋 hebasto's pull request is ready for review: "build: Patch Qt to handle minimum macOS version properly"
(https://github.com/bitcoin/bitcoin/pull/28775)
💬 maflcko commented on pull request "refactor: Remove unused SER_DISK, SER_NETWORK, SER_GETHASH":
(https://github.com/bitcoin/bitcoin/pull/28451#issuecomment-1792178673)
Please review https://github.com/bitcoin/bitcoin/pull/28438 (Use serialization parameters for CTransaction by ajtowns) first.
💬 hebasto commented on pull request "build: use macOS 14 SDK (Xcode 15.0)":
(https://github.com/bitcoin/bitcoin/pull/28622#issuecomment-1792179529)
> > The following patch fixes the Qt build for me:
>
> We wont be taking that patch, but if the problem is that qt fails to respect `-mmacosx-version-min` for some reason, I would assume that should make it fairly obvious where the problem is.

Apparently, direct tests show that `env -u C_INCLUDE_PATH -u CPLUS_INCLUDE_PATH -u OBJC_INCLUDE_PATH -u OBJCPLUS_INCLUDE_PATH -u CPATH -u LIBRARY_PATH /home/hebasto/git/bitcoin/depends/x86_64-apple-darwin/native/bin/clang++ --target=x86_64-apple-darw
...
💬 glozow commented on pull request "MiniMiner changes for package linearization":
(https://github.com/bitcoin/bitcoin/pull/28762#discussion_r1381447100)
added a refactor commit to pull fee amounts into constants
💬 glozow commented on pull request "MiniMiner changes for package linearization":
(https://github.com/bitcoin/bitcoin/pull/28762#discussion_r1381447239)
done
💬 glozow commented on pull request "MiniMiner changes for package linearization":
(https://github.com/bitcoin/bitcoin/pull/28762#discussion_r1381447982)
Done, and updated the expected boost includes for the linter. Unsure if it's preferred to omit those...?
💬 glozow commented on pull request "MiniMiner changes for package linearization":
(https://github.com/bitcoin/bitcoin/pull/28762#discussion_r1381448280)
leaving it as is :sweat_smile:
💬 TheCharlatan commented on pull request "refactor: Simplify CTxMempool/BlockAssembler fields, remove some external mapTx access":
(https://github.com/bitcoin/bitcoin/pull/28391#issuecomment-1792187238)
Updated 105a0f4db4ffdc25d3ad30300c949d46d5d8e647 -> 65839d6267af1f5e0e04aded72cbfa23b56a1237 ([simplifyMemPoolInteractions_4](https://github.com/TheCharlatan/bitcoin/tree/simplifyMemPoolInteractions_4) -> [simplifyMemPoolInteractions_5](https://github.com/TheCharlatan/bitcoin/tree/simplifyMemPoolInteractions_5), [compare](https://github.com/TheCharlatan/bitcoin/compare/simplifyMemPoolInteractions_4..simplifyMemPoolInteractions_5))

* Addressed @ismaelsadeeq's [comment](https://github.com/bitc
...
💬 hebasto commented on pull request "build: use macOS 14 SDK (Xcode 15.0)":
(https://github.com/bitcoin/bitcoin/pull/28622#discussion_r1381461570)
According to https://developer.apple.com/support/xcode/, additionally, `OSX_MIN_VERSION=13.5` should be adjusted as well.
💬 stratospher commented on pull request "test/BIP324: functional tests for v2 P2P encryption":
(https://github.com/bitcoin/bitcoin/pull/24748#issuecomment-1792201473)
Rebased on master.
💬 Sun0fABeach commented on pull request "datacarriersize: Match more datacarrying":
(https://github.com/bitcoin/bitcoin/pull/28408#issuecomment-1792205732)
Concept ACK

Node runners need a builtin option to ignore all modern forms of datacarrying so they don't have to resort to manually patching their nodes.

... and the 'censorship' framing is getting old by now and has been rebutted often enough. If you really hold these principles, then please remove all your email spam filters. Otherwise you're engaging in censorship of a permissionless protocol and thereby impairing an important source of revenue for network users.
👍 dergoegge approved a pull request: "refactors for subpackage evaluation"
(https://github.com/bitcoin/bitcoin/pull/28758#pullrequestreview-1712337150)
Code review ACK b5a60abe8783852f5b31bc1e63b5836530410e65

nit: the commit message in da9aceba217bbded6909f06144eaa1e1a4ebcb69 still has the old names
👍 dergoegge approved a pull request: "Fuzz: Check individual and package transaction invariants"
(https://github.com/bitcoin/bitcoin/pull/28764#pullrequestreview-1712356208)
ACK fcb3069fa307942cf7f3edabcda1be96d615c91f
📝 fanquake opened a pull request: "depends: latest config.guess & config.sub"
(https://github.com/bitcoin/bitcoin/pull/28781)
Before we make any local modifications (i.e #28733) pull the latest files from upstream.
💬 fanquake commented on pull request "depends: Bump to capnproto-c++-1.0.1":
(https://github.com/bitcoin/bitcoin/pull/28735#issuecomment-1792270323)
> so I guess someone can report it upstream?

https://github.com/capnproto/capnproto/issues/1833
💬 vasild commented on pull request "Avoid returning references to mutex guarded members":
(https://github.com/bitcoin/bitcoin/pull/28774#issuecomment-1792279588)
> No write will happen to the datadir cache after the first write, and no reader will have the reference before the first write, no?

That is not obvious to me. `m_cached_blocks_path` can be modified by repeated calls to `ArgsManager::GetBlocksDirPath()` which end up executing:

https://github.com/bitcoin/bitcoin/blob/9b68c9b85efebfa23daec6471b87e9cbb514a006/src/common/args.cpp#L293

`ArgsManager::GetBlocksDirPath()` is called by `init.cpp` and by the GUI, so it is not immediately obvious
...
👍 hebasto approved a pull request: "depends: drop -O1 workaround from arm64 apple Qt build"
(https://github.com/bitcoin/bitcoin/pull/28778#pullrequestreview-1712433808)
ACK 664c87354f9ec5df95346eab72a034296b83914d.

My Guix builds:
```
x86_64
62373549d2884e8ef8f46a77b9a93f64ebfc88603569e9d33b68fc67beaf2226 guix-build-664c87354f9e/output/arm64-apple-darwin/SHA256SUMS.part
597889f1908fdb67a6419177a98935b7119c637a962f03f47270893c5ba3fd6f guix-build-664c87354f9e/output/arm64-apple-darwin/bitcoin-664c87354f9e-arm64-apple-darwin-unsigned.tar.gz
289340354532a54a42b7235c831d13fdb28751c643f0fa0fc417ab195e9b5d90 guix-build-664c87354f9e/output/arm64-apple-darwin
...