💬 delta1 commented on pull request "wallet: remove unused 'accept_no_keys' arg from decryption process":
(https://github.com/bitcoin/bitcoin/pull/29375#issuecomment-1925863898)
ACK 2bb25ce5023c4d56c8b11e9c75f9f8bd69894452

Nice cleanup.

💬 delta1 commented on pull request "test: fix intermittent failure in `rpc_setban.py --v2transport`, run it in CI":
(https://github.com/bitcoin/bitcoin/pull/29372#issuecomment-1925867216)
tested ACK cc87ee4c3934028e78a59de509951ff7226ec80d

💬 sipa commented on issue "BIP324 tracking issue":
(https://github.com/bitcoin/bitcoin/issues/27634#issuecomment-1925871180)
There are a few minor follow-ups to consider still, but I believe this issue can be closed. Thanks everyone for getting us this far!

✅ sipa closed an issue: "BIP324 tracking issue"
(https://github.com/bitcoin/bitcoin/issues/27634)

⚠️ A420mfer opened an issue: "I put my http in a comment as Bitcoin Core and someone changed it to Bitcoin locked..can you please tell me what I should do?"
(https://github.com/bitcoin/bitcoin/issues/29381)

✅ fanquake closed an issue: "I put my http in a comment as Bitcoin Core and someone changed it to Bitcoin locked..can you please tell me what I should do?"
(https://github.com/bitcoin/bitcoin/issues/29381)

⚠️ A420mfer opened an issue: "Bitcoin Core changed to Bitcoin locked.."
(https://github.com/bitcoin/bitcoin/issues/29382)
I'm not a very smart person and I published my http in thinking that was the place to ask for help and it seems someone changed it to Bitcoin locked..and now when I try to go to the server the page won't load and the server was to my JS anywhere app..can anyone help me? I also opened an app called node and when I did all of a sudden it gave me a new http. I'm not sure what to do but I need help badly..it's been years since I set up my node and recently had been trying to set it up in a new phone
...

✅ willcl-ark closed an issue: "Bitcoin Core changed to Bitcoin locked.."
(https://github.com/bitcoin/bitcoin/issues/29382)

💬 willcl-ark commented on issue "Bitcoin Core changed to Bitcoin locked..":
(https://github.com/bitcoin/bitcoin/issues/29382#issuecomment-1925899323)
This issue tracker is used to track technical issues related to the Bitcoin Core code base.

General bitcoin questions and/or support requests are best directed to the [Bitcoin StackExchange](https://bitcoin.stackexchange.com/) or the #bitcoin IRC channel on the [Libera Chat](https://libera.chat/) network.

For proposed protocol changes you can post to the bitcoin-dev [mailing list](https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev).

For general bitcoin discussion you can try
...

💬 willcl-ark commented on issue "Update security.md with all PGP fingerprints":
(https://github.com/bitcoin/bitcoin/issues/29366#issuecomment-1925899691)
@ariard does being able to contact the persons who have chosen to be listed resolve this issue for you?

💬 A420mfer commented on issue "Bitcoin Core changed to Bitcoin locked..":
(https://github.com/bitcoin/bitcoin/issues/29382#issuecomment-1925901895)
Thank you!

💬 willcl-ark commented on issue "Unnecessary symbols being exported in `libbitcoinconsensus.so`":
(https://github.com/bitcoin/bitcoin/issues/26698#issuecomment-1925907159)
Can we close this following #29189 ?

✅ hebasto closed an issue: "Unnecessary symbols being exported in `libbitcoinconsensus.so`"
(https://github.com/bitcoin/bitcoin/issues/26698)

💬 fanquake commented on issue "Unnecessary symbols being exported in `libbitcoinconsensus.so`":
(https://github.com/bitcoin/bitcoin/issues/26698#issuecomment-1925907331)
Yep.

:lock: fanquake locked an issue: "Bitcoin Core changed to Bitcoin locked.."
(https://github.com/bitcoin/bitcoin/issues/29382)

💬 murchandamus commented on pull request "wallet: Add CoinGrinder coin selection algorithm":
(https://github.com/bitcoin/bitcoin/pull/27877#issuecomment-1925913171)
Added a longer textual explanation on how the algorithm can be thought in terms of the search graph it walks.

💬 04487 commented on issue "Update security.md with all PGP fingerprints":
(https://github.com/bitcoin/bitcoin/issues/29366#issuecomment-1925914511)
FHfh3647@$#....

در تاریخ یکشنبه ۴ فوریهٔ ۲۰۲۴،‏ ۲۳:۴۱ Will Clark ***@***.***>
نوشت:

> @ariard <https://github.com/ariard> does being able to contact the
> persons who have chosen to be listed resolve this issue for you?
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/bitcoin/bitcoin/issues/29366#issuecomment-1925899691>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ATSXOP5EWS64IO7D2MF4IBLYR7TQZAVCNFSM6AAAAABCVT75OCVHI2DSMVQWIX3
...

💬 ariard commented on issue "Update security.md with all PGP fingerprints":
(https://github.com/bitcoin/bitcoin/issues/29366#issuecomment-1925939033)
> The full recipients list of [security@bitcoincore.org](mailto:security@bitcoincore.org) is intentionally kept private in order to reduce the risk of targeted attacks against those who receive those emails. Only the people who are willing to take that risk have their fingerprints published.

As a sec researcher, you’re exposing your own skin too by handling sensitive information to unknown members of a list.
Encrypting communications and knowing who are the endpoints to guarantee infosec eth
...

💬 achow101 commented on issue "Update security.md with all PGP fingerprints":
(https://github.com/bitcoin/bitcoin/issues/29366#issuecomment-1925943156)
> Encrypting communications and knowing who are the endpoints to guarantee infosec ethics are best practices in my eyes.

Then encrypt your emails to any of the published keys and no one else on the list will be able to read your emails.

💬 ariard commented on issue "Update security.md with all PGP fingerprints":
(https://github.com/bitcoin/bitcoin/issues/29366#issuecomment-1925945051)
> Then encrypt your emails to any of the published keys and no one else on the list will be able to read your emails.

Thanks if the 3 published PGP fingerprints can add an authoritative dedicated mail. No wish to go through email alias.
You don’t answer my second q on infosec ethics, and transparency if re-sharing of sensitive info with unknown members.