<bitcoin-git>
bitcoin/master 0c7785b Martin Zumsande: init, validation: Improve handling if VerifyDB() fails due to insufficient...
<bitcoin-git>
bitcoin/master d6f781f Martin Zumsande: validation: return VerifyDBResult::INTERRUPTED if verification was interru...
<bitcoin-git>
[bitcoin] ishaanam opened pull request #27145: wallet: when a block is disconnected, update transactions that are no longer conflicted (master...mark_not_conflicted_inactive) https://github.com/bitcoin/bitcoin/pull/27145
<bitcoin-git>
[bitcoin] fanquake merged pull request #26595: wallet: be able to specify a wallet name and passphrase to migratewallet (master...migratewallet-by-name-and-passphrase) https://github.com/bitcoin/bitcoin/pull/26595
<bitcoin-git>
bitcoin/master 6bdbc5f Andrew Chow: rpc: Allow users to specify wallet name for migratewallet
<bitcoin-git>
bitcoin/master 7fd125b Andrew Chow: wallet: Be able to unlock the wallet for migration
<bitcoin-git>
bitcoin/master 61bb4e7 Leonardo Lazzaro: lint: enable E722 do not use bare except
2023-02-21
<bitcoin-git>
[bitcoin] achow101 merged pull request #26347: wallet: ensure the wallet is unlocked when needed for rescanning (master...rescanblockchain_unlock_wallet) https://github.com/bitcoin/bitcoin/pull/26347
<bitcoin-git>
bitcoin/master 6a5b348 ishaanam: test: test rescanning encrypted wallets
<bitcoin-git>
bitcoin/master 493b813 ishaanam: wallet: ensure that the passphrase is not deleted from memory when being u...
<bitcoin-git>
[bitcoin] fanquake merged pull request #27113: rpc: Use a FlatSigningProvider in decodescript to allow inferring descriptors for scripts larger than 520 bytes (master...decodescript-flatsigningprovider) https://github.com/bitcoin/bitcoin/pull/27113
<bitcoin-git>
bitcoin/master 73ec4b2 Andrew Chow: tests: decodescript can infer descriptors for scripts >520 bytes
<bitcoin-git>
bitcoin/master 7cc7822 Andrew Chow: rpc: Use FlatSigningProvider in decodescript
<bitcoin-git>
bitcoin/master e996219 fanquake: Merge bitcoin/bitcoin#27113: rpc: Use a FlatSigningProvider in decodescrip...
<hebasto>
is there any reason for Bitcoin Core binaries to support files larger than 2 GiB on 32-bit systems?
<bitcoin-git>
[bitcoin] fanquake closed pull request #27098: refactor: don't avoid sys/types.h when building for Windows (master...windows_can_use_sys_types) https://github.com/bitcoin/bitcoin/pull/27098
<bitcoin-git>
bitcoin/master a804f3c Seibart Nedor: wallet: extract and reuse RPC argument format definition for outputs
<bitcoin-git>
[bitcoin] achow101 opened pull request #27113: rpc: Use a FlatSigningProvider in decodescript to allow inferring descriptors for scripts larger than 520 bytes (master...decodescript-flatsigningprovider) https://github.com/bitcoin/bitcoin/pull/27113
<bitcoin-git>
[bitcoin] fanquake closed pull request #25523: build: Fail early and show actionable messages if autogen deps are missing (master...autogen-assert-deps) https://github.com/bitcoin/bitcoin/pull/25523
<vasild>
hebasto: wrt https://github.com/bitcoin/bitcoin/pull/27060#issuecomment-1431519355 "... adding more commits after reviewing and ACKing of previous ones ..." - what usually happens with big PRs that are split is that a different set of reviewers review the sub-PRs. How would that work if everything is kept in one unmerged PR and new commits are appended to it?
<bitcoin-git>
[bitcoin] fanquake merged pull request #26844: Net: Pass `MSG_MORE` flag when sending non-final network messages (round 2) (master...MSG_MORE) https://github.com/bitcoin/bitcoin/pull/26844
<bitcoin-git>
bitcoin/master 691eaf8 Matt Whitlock: Pass MSG_MORE flag when sending non-final network messages
<bitcoin-git>
bitcoin/master 5ecd14a fanquake: Merge bitcoin/bitcoin#26844: Net: Pass `MSG_MORE` flag when sending non-fi...
<bitcoin-git>
[bitcoin] TheCharlatan closed pull request #27103: Blockstorage: Dont access gArgs to get blocks_dir (master...blockstorageArgs) https://github.com/bitcoin/bitcoin/pull/27103
<bitcoin-git>
[bitcoin] TheCharlatan opened pull request #27103: Blockstorage: Dont access gArgs to get blocks_dir (master...blockstorageArgs) https://github.com/bitcoin/bitcoin/pull/27103
<bitcoin-git>
[gui] hebasto opened pull request #711: refactor: Disable unused special members functions in `UnlockContext` (master...230214-unlock) https://github.com/bitcoin-core/gui/pull/711
<bitcoin-git>
[bitcoin] fanquake opened pull request #27099: build: produce a .zip for macOS distribution (master...macdeploy_use_zip) https://github.com/bitcoin/bitcoin/pull/27099
<sipa>
Possibly. It's worth e.g. trying a few and benchmarking on varied hardware (e.g. including raspberry pis and similar hardware, which seem popular for bitcoin nodes)
<bitcoin-git>
[bitcoin] fanquake opened pull request #27098: refactor: don't avoid sys/types.h on when building for Windows (master...windows_can_use_sys_types) https://github.com/bitcoin/bitcoin/pull/27098
<bitcoin-git>
[bitcoin] SomberNight opened pull request #27097: descriptors: fix docstring (param [in] vs [out]) (master...20230214_desc_docstring) https://github.com/bitcoin/bitcoin/pull/27097
<josie>
I'm reading through some old discussions regarding obfuscating bitcoin data and while it was done for chainstate, it was never implemented for blocks. I haven't seen any objections to doing it on blocks in the discussions (aside from general objections to obfuscating the any data to begin with), but perhaps I'm missing something. Was there a reason it was never done for blocks?
<bitcoin-git>
[bitcoin] achow101 merged pull request #27080: Wallet: Zero out wallet master key upon locking so it doesn't persist in memory (master...2023_02_WipeMasterKeyOnLock) https://github.com/bitcoin/bitcoin/pull/27080
<bitcoin-git>
bitcoin/master 2c1fe27 Andrew Chow: Merge bitcoin/bitcoin#27080: Wallet: Zero out wallet master key upon locki...