💬 ismaelsadeeq commented on pull request "cluster mempool: introduce TxGraph":
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953022822)
In "txgraph: (tests) add simulation fuzz test" 1f06bc1e4a8108f1430bcd20fc391c9f663a2e4b
using real in the comments here is a bit confusing as you represent the actual tx graph as real
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953022822)
In "txgraph: (tests) add simulation fuzz test" 1f06bc1e4a8108f1430bcd20fc391c9f663a2e4b
using real in the comments here is a bit confusing as you represent the actual tx graph as real
💬 sipa commented on pull request "cluster mempool: introduce TxGraph":
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953411421)
It follows from the property that PostLinearize results in chunks that do not consist of multiple disconnected components: if a higher-feerate chunk is appended to a lower-feerate one, it must mean they get separated.
I'm happy to elaborate briefly in this comment, but perhaps this is also not the place to provide deeper more theoretical reasons why the properties hold.
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953411421)
It follows from the property that PostLinearize results in chunks that do not consist of multiple disconnected components: if a higher-feerate chunk is appended to a lower-feerate one, it must mean they get separated.
I'm happy to elaborate briefly in this comment, but perhaps this is also not the place to provide deeper more theoretical reasons why the properties hold.
💬 andrewtoth commented on pull request "Add -pruneduringinit option to temporarily use another prune target during IBD":
(https://github.com/bitcoin/bitcoin/pull/31845#issuecomment-2654905595)
Can't we just do an IBD without pruning, then shutdown and restart with a prune height set? Or just call `pruneblockchain` after we are done IBD?
(https://github.com/bitcoin/bitcoin/pull/31845#issuecomment-2654905595)
Can't we just do an IBD without pruning, then shutdown and restart with a prune height set? Or just call `pruneblockchain` after we are done IBD?
💬 murchandamus commented on issue "Update BnB upper bound to use `min_viable_change`":
(https://github.com/bitcoin/bitcoin/issues/26466#issuecomment-2654913988)
That’s a great idea!
(https://github.com/bitcoin/bitcoin/issues/26466#issuecomment-2654913988)
That’s a great idea!
💬 sipa commented on pull request "cluster mempool: introduce TxGraph":
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953458099)
If we're going to expend run-time cost to perform the check, we might as well drop the requirement that Ref refers to this graph entirely. Given that we're not expecting to ever have multiple TxGraph objects in production, this feels like overkill.
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953458099)
If we're going to expend run-time cost to perform the check, we might as well drop the requirement that Ref refers to this graph entirely. Given that we're not expecting to ever have multiple TxGraph objects in production, this feels like overkill.
💬 sipa commented on pull request "cluster mempool: introduce TxGraph":
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953460271)
I'd rather not refer to implementation details in the public interface.
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953460271)
I'd rather not refer to implementation details in the public interface.
💬 murchandamus commented on issue "wallet: Branch and Bound producing change":
(https://github.com/bitcoin/bitcoin/issues/31830#issuecomment-2654938578)
The issue appears to have been introduced by myself in #28366 in the commit https://github.com/bitcoin/bitcoin/pull/28366/commits/7aa7e30441fe77bf8e8092916e36b004bbbfe2a7#diff-d473ed8396f9451afb848923cfcfaa630c9811a78e07f3ae1ffd3a65da218accR796.
Branch and Bound uses `target + cost_of_change` as the upper bound inclusive of the solution space. In the mentioned PR, it also uses "cost_of_change` as the value for `min_viable_change` in the `RecalculateWaste` call. However, `min_viable_change` den
...
(https://github.com/bitcoin/bitcoin/issues/31830#issuecomment-2654938578)
The issue appears to have been introduced by myself in #28366 in the commit https://github.com/bitcoin/bitcoin/pull/28366/commits/7aa7e30441fe77bf8e8092916e36b004bbbfe2a7#diff-d473ed8396f9451afb848923cfcfaa630c9811a78e07f3ae1ffd3a65da218accR796.
Branch and Bound uses `target + cost_of_change` as the upper bound inclusive of the solution space. In the mentioned PR, it also uses "cost_of_change` as the value for `min_viable_change` in the `RecalculateWaste` call. However, `min_viable_change` den
...
💬 mzumsande commented on issue "Stuck in Endless Pre-Syncing Headers Loop":
(https://github.com/bitcoin/bitcoin/issues/26391#issuecomment-2654943412)
> I think the most useful course of actual here is detecting the presence of a high-PoW header-invalid chain, and reporting it to the user as a sign of likely corruption. Unsure what that would mean for anything other than the GUI, though.
We actually have this kind of check (`CheckForkWarningConditions`) but have it disabled during IBD for no good reason I can see (at least after #19905). I'll work on a PR suggesting to use this check in the pre-sync header loop situation (and also rework it,
...
(https://github.com/bitcoin/bitcoin/issues/26391#issuecomment-2654943412)
> I think the most useful course of actual here is detecting the presence of a high-PoW header-invalid chain, and reporting it to the user as a sign of likely corruption. Unsure what that would mean for anything other than the GUI, though.
We actually have this kind of check (`CheckForkWarningConditions`) but have it disabled during IBD for no good reason I can see (at least after #19905). I'll work on a PR suggesting to use this check in the pre-sync header loop situation (and also rework it,
...
💬 fanquake commented on pull request "ci: switch MSAN to use prebuilt Clang binaries":
(https://github.com/bitcoin/bitcoin/pull/31850#discussion_r1953473331)
https://github.com/llvm/llvm-project/releases/tag/llvmorg-20.1.0-rc2
(https://github.com/bitcoin/bitcoin/pull/31850#discussion_r1953473331)
https://github.com/llvm/llvm-project/releases/tag/llvmorg-20.1.0-rc2
💬 sipa commented on pull request "cluster mempool: introduce TxGraph":
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953481542)
Indeed.
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953481542)
Indeed.
💬 sipa commented on pull request "cluster mempool: introduce TxGraph":
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953484318)
It's a tiny number, as it's bounded by $\mathcal{O}(\log n)$, so it didn't feel right to use the same `DepGraphIndex` or `GraphIndex` type.
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953484318)
It's a tiny number, as it's bounded by $\mathcal{O}(\log n)$, so it didn't feel right to use the same `DepGraphIndex` or `GraphIndex` type.
⚠️ InnDe opened an issue: "Wallet passpharse"
(https://github.com/bitcoin/bitcoin/issues/31852)
### Is there an existing issue for this?
- [x] I have searched the existing issues
### Current behaviour
I’m using a passphrase for my encrypted wallets—8 in total.
This passphrase is: (space “thekey” \ \ \ \ \ \ \ \ \ \ \ \ \)
“ \ \ \ \ \ \ \ \ \ \ \ \ \)”
I use this passphrase for all my wallets (total: 2.4 BTC), but now it doesn’t work as usual. I tried creating a new wallet with the same passphrase, and I encountered the same issue.
You can review my question and all the comments her
...
(https://github.com/bitcoin/bitcoin/issues/31852)
### Is there an existing issue for this?
- [x] I have searched the existing issues
### Current behaviour
I’m using a passphrase for my encrypted wallets—8 in total.
This passphrase is: (space “thekey” \ \ \ \ \ \ \ \ \ \ \ \ \)
“ \ \ \ \ \ \ \ \ \ \ \ \ \)”
I use this passphrase for all my wallets (total: 2.4 BTC), but now it doesn’t work as usual. I tried creating a new wallet with the same passphrase, and I encountered the same issue.
You can review my question and all the comments her
...
👍1
💬 sipa commented on pull request "cluster mempool: introduce TxGraph":
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953494478)
Done.
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953494478)
Done.
💬 sipa commented on pull request "cluster mempool: introduce TxGraph":
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953494661)
Done.
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953494661)
Done.
💬 sipa commented on pull request "cluster mempool: introduce TxGraph":
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953495202)
Done.
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953495202)
Done.
💬 sipa commented on pull request "cluster mempool: introduce TxGraph":
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953495306)
Done.
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953495306)
Done.
💬 sipa commented on pull request "cluster mempool: introduce TxGraph":
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953495533)
Done.
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953495533)
Done.
💬 sipa commented on pull request "cluster mempool: introduce TxGraph":
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953496332)
I've reworded this a bit.
(https://github.com/bitcoin/bitcoin/pull/31363#discussion_r1953496332)
I've reworded this a bit.
💬 pinheadmz commented on issue "Wallet passpharse":
(https://github.com/bitcoin/bitcoin/issues/31852#issuecomment-2654987498)
I think stack exchange is the best place for this usage question but you need to be a bit more cool to people who are trying to help you there. The issue tracker here is only for technical issues with the software. If you actually discover one of those (maybe like, walletpassphrase doesn't work if passphrase contains a backslash?) please open an issue for that.
You can update this issue if you can rephrase it according to our guidelines otherwise it's likely to be closed as won't-fix
(https://github.com/bitcoin/bitcoin/issues/31852#issuecomment-2654987498)
I think stack exchange is the best place for this usage question but you need to be a bit more cool to people who are trying to help you there. The issue tracker here is only for technical issues with the software. If you actually discover one of those (maybe like, walletpassphrase doesn't work if passphrase contains a backslash?) please open an issue for that.
You can update this issue if you can rephrase it according to our guidelines otherwise it's likely to be closed as won't-fix
💬 achow101 commented on issue "Wallet passpharse":
(https://github.com/bitcoin/bitcoin/issues/31852#issuecomment-2654987869)
Does your passphrase has quotes (`"` or `'`) in it? If so, you will need to escape them when using the RPC console. If your password also has the space character, then entire passphrase will need to be surrounded with quotes so that the space is recognized as part of the passphrase.
(https://github.com/bitcoin/bitcoin/issues/31852#issuecomment-2654987869)
Does your passphrase has quotes (`"` or `'`) in it? If so, you will need to escape them when using the RPC console. If your password also has the space character, then entire passphrase will need to be surrounded with quotes so that the space is recognized as part of the passphrase.