My favorite part about the BIP110 failure is that Roughnecks are still mining their shitcoin at full Bitcoin difficulty. It’ll take about a month for them to even be able to sell any and it’ll be at an opportunity cost of like $20 million USD. It only gets worse from there. (But they’re going to hard fork and likely screw that up, too.)

@Roughnecks110 Oh dear, you think I'm trying to sabotage something that's already dead? No, I'm just dunking for fun. Enjoy your hardfork! I hope you opt for Luke's buggy RIPEMD160 code and use it to instamine.

@Roughnecks110 Oh dear, you think I'm trying to sabotage something that's already dead? No, I'm just dunking for fun. Enjoy your hardfork! I hope you opt for Luke's buggy RIPEMD160 code and use it to instamine.

It wasn't me. Although this is kind of hilarious. Not only does it embed contiguous arbitrary data in a BIP-110 compatible txn, it exploits a default policy delta where Knots is *more* permissive than Core to get the txn mined by a Knots miner only. Genius proof of concept. 🫡

Luke preparing to eat his pet rabbit. Relayed exclusively by Knots. bitcoin-cli getrawtransaction 07a7dd129f95b9a087d5925b319e15262b58483d7c5f36d8b3dca02546a50264 | xxd -r -p | tail -c +1483 > image.jxl

@Roughnecks110 Oh jeez, one of those five had this *awful* image of Luke in it getting ready to eat his pet rabbit... How could you guys include such spam? bitcoin-cli getrawtransaction 07a7dd129f95b9a087d5925b319e15262b58483d7c5f36d8b3dca02546a50264 | xxd -r -p | tail -c +1483 > image.jxl

@Roughnecks110 Oh jeez, one of those five had this *awful* image of Luke in it getting ready to eat his pet rabbit... How could you guys include such spam? bitcoin-cli getrawtransaction 07a7dd129f95b9a087d5925b319e15262b58483d7c5f36d8b3dca02546a50264 | xxd -r -p | tail -c +1483 > image.jxl

BIP110 ADVENT: Endgame Embed *entire directories* of arbitrary data contiguously in BIP110 valid blocks using compressed archives (tar.gz) -Knots standard (exclusively!) up to 400kB I had Roughnecks mine a tx with some of the most dangerous malware in the world. Not for the faint of heart! bitcoin-cli getrawtransaction 9c34287f805e622b86ac140ef10475750214cf60c3310441b9b9ea9f429bb1bc|xxd -r -p |tail -c +1073|gunzip -c>mystery.tar Thanks to the insider at Ocean who made this possible.

Since we're about 48 hrs away from the BIP-110 "mandatory" signaling height, I wanted to quickly share my private node crawler stats. Over the past several weeks, I gave a program of mine more spending power than is probably reasonable. It spent a not insignificant amount of BTC deduplicating nodes. Enjoy. Raw node counts (% of total) 🔵 Total: 131,762 ⚫️ Bitcoin Core: 99,401 (75.4%) ⚫️ Bitcoin Knots: 30,755 (23.3%) ⚫️ Other: 1,606 (1.2%) Raw BIP-110 signaling counts (% of total) 🔸 Bitcoin Core: 17 (0.01%) 🔸 Bitcoin Knots: 19,388 (14.7%) 🔸 Other: 0 (Unknown) 🔹 Total: 19,405 (14.7%) Nodes found to be duplicates (% of version) 🔴 Bitcoin Core: 17,892 (17.8%) 🔴 Bitcoin Knots: 18,049 (58.7%) 🔴 Other: Unknown 🔴 Total duplicates: 35,941 (27.2% of total) Deduplicated node counts (% of unique) 🟢 Bitcoin Core: 81,672 (85.1%) 🟢 Bitcoin Knots: 12,706 (9.6%) 🟢 Other: 1,606 (1.7%) 🟢 Total unique: 95,984 (72.8% of total) Of the 19,388 Bitcoin Knots BIP-110 nodes discovered signaling for BIP-110, 71% of them were eliminated as duplicates, above average for the Knots nodes, leaving only 5,663 BIP-110 signaling nodes. That puts non-duplicate BIP-110 signaling nodes at 5.9% of non-duplicate nodes. My criteria for deduplication includes the basics (same IP) and some additional more advanced sleuthing of available data. Additionally, you may have already surmised from my intro that part of it also involves strategically sending real transactions. Will keep the exact details private so that it can't be easily gamed in the future. It is impossible to find ALL duplicate nodes, however false positives are somewhat unlikely with my methodology. If my software has flagged a group of nodes as duplicate, there's an extremely high probability that its either the exact same node (with multiple IPs) or in the exact same location. If a node wasn't able to be tested thoroughly enough to be confident for whatever reason, and isn't deemed duplicate by conventional means (same IP, for example) then it isn't considered a duplicate and gives it the benefit of the doubt. If I get more time, I may start publishing some more detailed stats more regularly, since it seems my crawler successfully finds a large amount of nodes beyond those listed every public crawler. Unfortunately it's not cheap to handle the deduplication aspect, so will need to figure out how feasible that is to continue. It also involves operating from dozens of IPs to get connected to a supermajority of the network, which is pretty bandwidth intense. Anyway, figured I'd share, since I don't think anyone is actually doing this at all at this level. There's a lot more to this, too. Some of it might scare privacy conscious people... so I'll probably keep my publicly shared info limited to node stats.

@ScarcityMan This is like saying the ability to turn left is a 'loophole' and making it illegal. Congratulations, you've (1) nerfed something useful, and (2) didn't even block the ability -- people can just turn right 270 degrees to achieve the same effect.