💬 luke-jr commented on pull request "blockstorage: XOR blocksdir *.dat files":
(https://github.com/bitcoin/bitcoin/pull/28052#issuecomment-1627785475)
AFAIK there is software which reads these files intentionally. IMO they can be expected to adapt, but having the option to disable it seems like a good idea in case they aren't ready right away.
(https://github.com/bitcoin/bitcoin/pull/28052#issuecomment-1627785475)
AFAIK there is software which reads these files intentionally. IMO they can be expected to adapt, but having the option to disable it seems like a good idea in case they aren't ready right away.
💬 luke-jr commented on pull request "[WIP] rpc: doc: Added `longpollid` and `data` params to `template_request` #27998":
(https://github.com/bitcoin/bitcoin/pull/28056#discussion_r1257521442)
```suggestion
{"longpollid", RPCArg::Type::STR, RPCArg::Optional::OMITTED, "Delay processing request until the result would vary significantly from the \"longpollid\" of a prior template."},
```
It doesn't necessarily imply the previous template is expired.
(https://github.com/bitcoin/bitcoin/pull/28056#discussion_r1257521442)
```suggestion
{"longpollid", RPCArg::Type::STR, RPCArg::Optional::OMITTED, "Delay processing request until the result would vary significantly from the \"longpollid\" of a prior template."},
```
It doesn't necessarily imply the previous template is expired.
💬 luke-jr commented on pull request "[WIP] rpc: doc: Added `longpollid` and `data` params to `template_request` #27998":
(https://github.com/bitcoin/bitcoin/pull/28056#discussion_r1257521831)
```suggestion
{"data", RPCResult::Type::STR_HEX, RPCArg::Optional::OMITTED, "Proposed block data to check, encoded in hexadecimal; valid only for mode=\"proposal\""},
```
(https://github.com/bitcoin/bitcoin/pull/28056#discussion_r1257521831)
```suggestion
{"data", RPCResult::Type::STR_HEX, RPCArg::Optional::OMITTED, "Proposed block data to check, encoded in hexadecimal; valid only for mode=\"proposal\""},
```
✅ Brotcrunsher closed a pull request: "Supporting parameter "h" and "?" in -netinfo."
(https://github.com/bitcoin/bitcoin/pull/27830)
(https://github.com/bitcoin/bitcoin/pull/27830)
💬 ItIsOHM commented on pull request "[WIP] rpc: doc: Added `longpollid` and `data` params to `template_request` #27998":
(https://github.com/bitcoin/bitcoin/pull/28056#issuecomment-1627802501)
> This doesn't compile. Ideally, you compile and test any changes locally before opening a pull request.
Hey so I was trying to build it after adding the changes you suggested, but i'm getting this error in VS, as I'm building on Windows 11. Can you please help what this means?

I followed [this](https://github.com/bitcoin/bitcoin/blob/master/build_msvc/README.md) guide and opened `bitcoin.s
...
(https://github.com/bitcoin/bitcoin/pull/28056#issuecomment-1627802501)
> This doesn't compile. Ideally, you compile and test any changes locally before opening a pull request.
Hey so I was trying to build it after adding the changes you suggested, but i'm getting this error in VS, as I'm building on Windows 11. Can you please help what this means?

I followed [this](https://github.com/bitcoin/bitcoin/blob/master/build_msvc/README.md) guide and opened `bitcoin.s
...
💬 sipa commented on pull request "[WIP] rpc: doc: Added `longpollid` and `data` params to `template_request` #27998":
(https://github.com/bitcoin/bitcoin/pull/28056#issuecomment-1627806159)
I strongly recommend not building in Windows/MSVC, as it's a venture on its own to get that to work. In a Linux VM, or WSL2, it should be fairly straightforward.
(https://github.com/bitcoin/bitcoin/pull/28056#issuecomment-1627806159)
I strongly recommend not building in Windows/MSVC, as it's a venture on its own to get that to work. In a Linux VM, or WSL2, it should be fairly straightforward.
💬 ItIsOHM commented on pull request "[WIP] rpc: doc: Added `longpollid` and `data` params to `template_request` #27998":
(https://github.com/bitcoin/bitcoin/pull/28056#issuecomment-1627807815)
> I strongly recommend not building in Windows/MSVC, as it's a venture on its own to get that to work. In a Linux VM, or WSL2, it should be fairly straightforward.
Ohh I see! Then I'll install WSL2 and try building it from there. I suppose [this](https://github.com/bitcoin/bitcoin/blob/master/doc/build-windows.md) guide should be enough to get it working?
(https://github.com/bitcoin/bitcoin/pull/28056#issuecomment-1627807815)
> I strongly recommend not building in Windows/MSVC, as it's a venture on its own to get that to work. In a Linux VM, or WSL2, it should be fairly straightforward.
Ohh I see! Then I'll install WSL2 and try building it from there. I suppose [this](https://github.com/bitcoin/bitcoin/blob/master/doc/build-windows.md) guide should be enough to get it working?
💬 techy2 commented on pull request "fix: delay in TimeOffset applied to AdjustedTime caused by send/receive message queues, correct pointer alignment issue":
(https://github.com/bitcoin/bitcoin/pull/28010#issuecomment-1627833757)
Hola Marco
Sorry, I've been away for a while. Please continue discussion as required
(https://github.com/bitcoin/bitcoin/pull/28010#issuecomment-1627833757)
Hola Marco
Sorry, I've been away for a while. Please continue discussion as required
📝 Dindin1992 opened a pull request: "Dindin"
(https://github.com/bitcoin/bitcoin/pull/28058)
<!--
*** Please remove the following help text before submitting: ***
Pull requests without a rationale and clear improvement may be closed
immediately.
GUI-related pull requests should be opened against
https://github.com/bitcoin-core/gui
first. See CONTRIBUTING.md
-->
<!--
Please provide clear motivation for your patch and explain how it improves
Bitcoin Core user experience or Bitcoin Core developer experience
significantly:
* Any test improvements or new tests that improv
...
(https://github.com/bitcoin/bitcoin/pull/28058)
<!--
*** Please remove the following help text before submitting: ***
Pull requests without a rationale and clear improvement may be closed
immediately.
GUI-related pull requests should be opened against
https://github.com/bitcoin-core/gui
first. See CONTRIBUTING.md
-->
<!--
Please provide clear motivation for your patch and explain how it improves
Bitcoin Core user experience or Bitcoin Core developer experience
significantly:
* Any test improvements or new tests that improv
...
✅ Dindin1992 closed a pull request: "Dindin"
(https://github.com/bitcoin/bitcoin/pull/28058)
(https://github.com/bitcoin/bitcoin/pull/28058)
📝 fanquake locked a pull request: "Dindin"
(https://github.com/bitcoin/bitcoin/pull/28058)
<!--
*** Please remove the following help text before submitting: ***
Pull requests without a rationale and clear improvement may be closed
immediately.
GUI-related pull requests should be opened against
https://github.com/bitcoin-core/gui
first. See CONTRIBUTING.md
-->
<!--
Please provide clear motivation for your patch and explain how it improves
Bitcoin Core user experience or Bitcoin Core developer experience
significantly:
* Any test improvements or new tests that improv
...
(https://github.com/bitcoin/bitcoin/pull/28058)
<!--
*** Please remove the following help text before submitting: ***
Pull requests without a rationale and clear improvement may be closed
immediately.
GUI-related pull requests should be opened against
https://github.com/bitcoin-core/gui
first. See CONTRIBUTING.md
-->
<!--
Please provide clear motivation for your patch and explain how it improves
Bitcoin Core user experience or Bitcoin Core developer experience
significantly:
* Any test improvements or new tests that improv
...
💬 denavila commented on pull request "wallet: Deniability API (Unilateral Transaction Meta-Privacy)":
(https://github.com/bitcoin/bitcoin/pull/27792#issuecomment-1628080840)
Hi @ishaanam and thank you for looking at my PR.
I do agree the implementation can be improved and your feedback helps me greatly.
Here are my thoughts regarding your concerns:
1) I thought about this problem too and indeed spending deniabilized outputs is somewhat challenging.
Obviously, if the user just HODLs, or spends less than a deniabilized UTXO, then all is good.
However if they spend larger amounts, more than one UTXOs would get picked up and that would reveal that they belong
...
(https://github.com/bitcoin/bitcoin/pull/27792#issuecomment-1628080840)
Hi @ishaanam and thank you for looking at my PR.
I do agree the implementation can be improved and your feedback helps me greatly.
Here are my thoughts regarding your concerns:
1) I thought about this problem too and indeed spending deniabilized outputs is somewhat challenging.
Obviously, if the user just HODLs, or spends less than a deniabilized UTXO, then all is good.
However if they spend larger amounts, more than one UTXOs would get picked up and that would reveal that they belong
...
🤔 www222fff reviewed a pull request: "test: Ignore UTF-8 errors in assert_debug_log"
(https://github.com/bitcoin/bitcoin/pull/28035#pullrequestreview-1521251349)
Does this fix applied to both version for python2 and python3?
(https://github.com/bitcoin/bitcoin/pull/28035#pullrequestreview-1521251349)
Does this fix applied to both version for python2 and python3?
📝 hebasto opened a pull request: "refactor: Make more transaction size variables `int32_t`"
(https://github.com/bitcoin/bitcoin/pull/28059)
This PR is a continuation of https://github.com/bitcoin/bitcoin/pull/23962.
It gets rid of two static casts and is useful for https://github.com/bitcoin/bitcoin/pull/25972, see the failed ARM and multiprocess CI jobs.
(https://github.com/bitcoin/bitcoin/pull/28059)
This PR is a continuation of https://github.com/bitcoin/bitcoin/pull/23962.
It gets rid of two static casts and is useful for https://github.com/bitcoin/bitcoin/pull/25972, see the failed ARM and multiprocess CI jobs.
📝 hebasto converted_to_draft a pull request: "refactor: Make more transaction size variables `int32_t`"
(https://github.com/bitcoin/bitcoin/pull/28059)
This PR is a continuation of https://github.com/bitcoin/bitcoin/pull/23962.
It gets rid of two static casts and is useful for https://github.com/bitcoin/bitcoin/pull/25972, see the failed ARM and multiprocess CI jobs.
(https://github.com/bitcoin/bitcoin/pull/28059)
This PR is a continuation of https://github.com/bitcoin/bitcoin/pull/23962.
It gets rid of two static casts and is useful for https://github.com/bitcoin/bitcoin/pull/25972, see the failed ARM and multiprocess CI jobs.
💬 S3RK commented on pull request "Bump unconfirmed ancestor transactions to target feerate":
(https://github.com/bitcoin/bitcoin/pull/26152#discussion_r1257771285)
ah, yes, you're right
(https://github.com/bitcoin/bitcoin/pull/26152#discussion_r1257771285)
ah, yes, you're right
👋 hebasto's pull request is ready for review: "refactor: Make more transaction size variables `int32_t`"
(https://github.com/bitcoin/bitcoin/pull/28059)
(https://github.com/bitcoin/bitcoin/pull/28059)
💬 MarcoFalke commented on pull request "refactor: Make more transaction size variables `int32_t`":
(https://github.com/bitcoin/bitcoin/pull/28059#issuecomment-1628328861)
Not sure. The other types are 64 bit, so this will overflow eventually
(https://github.com/bitcoin/bitcoin/pull/28059#issuecomment-1628328861)
Not sure. The other types are 64 bit, so this will overflow eventually
💬 MarcoFalke commented on pull request "fuzz: Modify tx_pool_standard target to test package processing":
(https://github.com/bitcoin/bitcoin/pull/25778#issuecomment-1628332846)
Closing for now. Maybe this can be picked up as part of one of the package relay PRs.
(https://github.com/bitcoin/bitcoin/pull/25778#issuecomment-1628332846)
Closing for now. Maybe this can be picked up as part of one of the package relay PRs.
✅ MarcoFalke closed a pull request: "fuzz: Modify tx_pool_standard target to test package processing"
(https://github.com/bitcoin/bitcoin/pull/25778)
(https://github.com/bitcoin/bitcoin/pull/25778)