<zzz123>
Pad found it and published exploit code on X: https://x.com/123456/status/1899101800701050931 and realistically he's pretty attractive for how elite he is at what he does. I'm definitely not him btw <nervous laughter>
<zzz123>
Let's not give him credit. Social climbing in blockchain is more important than computer science, right Ava?
<zzz123>
tl;dr pwned, again, happy to help kevin@envadr.io
zzz123 has left #bitcoin-core-dev [#bitcoin-core-dev]
<darosior>
well, looks like he's so elite he pwned twitter too, post wont load
<bitcoin-git>
[bitcoin] marcofleon opened pull request #32025: validation, fix: Use wtxid instead of txid in `CheckEphemeralSpends` (master...2025/03/fix-txid-to-wtxid) https://github.com/bitcoin/bitcoin/pull/32025
<laanwj>
zzz123: please use security@bitcoincore.org to report vulnerabilities, posting them to public social media is irresponsible, and also many of us don't have x accounts
<bitcoin-git>
[bitcoin] hebasto opened pull request #32027: cmake: Add `NO_CACHE_IF_FAILED` option for checking linker flags (master...250310-nocache) https://github.com/bitcoin/bitcoin/pull/32027
bugs_ has joined #bitcoin-core-dev
salvatoshi has quit [Ping timeout: 276 seconds]
<bitcoin-git>
[bitcoin] hebasto opened pull request #32028: Update `secp256k1` subtree to latest master (master...250310-secp-subtree) https://github.com/bitcoin/bitcoin/pull/32028
zeropoint has joined #bitcoin-core-dev
zzz123 has joined #bitcoin-core-dev
<zzz123>
start syncing a fresh bitcoind and run this against it https://pastebin.com/raw/skn7DhP9 - edit your remote bitcoind ip into '127.0.0.1' in a text editor - install go - save this: https://pastebin.com/raw/skn7DhP9 as attack.go - and type 'go run attack.go' - and observe the sync slowdown. confirmed denial-of-service in the latest release
Talkless has joined #bitcoin-core-dev
<darosior>
What do people think of adding the "coinbasetxn" field to the getblocktemplate result? What's the reason it was never introduced in the first place?
<darosior>
cc luke-jr ^
cotsuka has quit [Remote host closed the connection]
cotsuka has joined #bitcoin-core-dev
<sipa>
darosior: i believe because it's something the pool should set, not bitcoind, but GBT never got traction for pool-to-hasher communication
<sipa>
it can only be decided by bitcoind if it knows the payout addresses, for example
jespada has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
tapscript has joined #bitcoin-core-dev
salvatoshi has joined #bitcoin-core-dev
tapscript has quit [Quit: Client closed]
tapscript has joined #bitcoin-core-dev
sliv3r__ has joined #bitcoin-core-dev
sliv3r__ has quit [Client Quit]
jespada has joined #bitcoin-core-dev
goat-c has joined #bitcoin-core-dev
<zzz123>
re: new dos - global resource limits on getdata associated w/ blocks. maybe a global 100ms throttle between requests.. rather than just per ip addr limits - restrict total bandwidth that can be dedicated to sharing block data. alternatively - dynamic serving that adjusts based on network conditions, e.g. nodes stressing each other and redirecting
<zzz123>
new connections to healthy nodes with open slots? spitballing. what type of degradation if any would a patch for getdata block spam produce? dos attack code = https://pastebin.com/raw/skn7DhP9 - edit 127.0.0.1 to your remote bitcoind machine's ip, save as `whatever.go` and `go run whatever.go`
jrayhawk has quit [Ping timeout: 260 seconds]
goat-c has quit [Quit: Client closed]
jrayhawk has joined #bitcoin-core-dev
Guest96 has joined #bitcoin-core-dev
tapscript has quit [Quit: Client closed]
Guest96 has quit [Quit: Client closed]
jespada has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
zzz123 has quit [Quit: Client closed]
Talkless has quit [Quit: Konversation terminated!]