Roman #Catholic, husband, father of 11 children, #Bitcoin Core developer, and CTO @npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze ; INTP; I condemn fake "Catholics", cryptobros & pedos; see full bio
Public Key
npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Profile Code
nprofile1qqs0m40g76hqmwqhhc9hrk3qfxxpsp5k3k9xgk24nsjf7v305u6xffcpz3mhxue69uhhyetvv9ujuerpd46hxtnfdu28q7dq
Show more details
Published at
2026-02-03T19:17:41Z Event JSON
{
"id": "b75de0fc480ac8bd2b0780ecd148b03e4dc831d976aac15f0d3bdd31ae95d874" ,
"pubkey": "fdd5e8f6ae0db817be0b71da20498c1806968d8a6459559c249f322fa73464a7" ,
"created_at": 1770146261 ,
"kind": 0 ,
"tags": [
[
"alt",
"User profile for Luke Dashjr"
],
[
"name",
"Luke Dashjr"
],
[
"display_name",
"Luke Dashjr"
],
[
"picture",
"https://luke.dashjr.org/myself/avatar.jpg"
],
[
"about",
"Roman #Catholic, husband, father of 11 children, #Bitcoin Core developer, and CTO @npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze ; INTP;\nI condemn fake \"Catholics\", cryptobros \u0026 pedos; see full bio"
],
[
"nip05",
"[email protected] "
],
[
"lud16",
"[email protected] "
]
],
"content": "{\"display_name\":\"Luke Dashjr\",\"name\":\"Luke Dashjr\",\"picture\":\"https://luke.dashjr.org/myself/avatar.jpg\",\"nip05\":\"[email protected] \",\"about\":\"Roman #Catholic, husband, father of 11 children, #Bitcoin Core developer, and CTO @npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze ; INTP;\\nI condemn fake \\\"Catholics\\\", cryptobros \u0026 pedos; see full bio\",\"lud16\":\"[email protected] \",\"Patreon\":\"https://www.patreon.com/LukeDashjr?utm_medium=social\u0026utm_source=nostr\",\"GitHub Sponsors\":\"https://github.com/sponsors/luke-jr\",\"nip05valid\":true}" ,
"sig": "fbb825818e28c8afce12dabdc7e57fa9f1fba86851ff3e8c0618e487d65affccf227f439f7637e338d83718cfe813072fa8c412e77986f52625d60d25a28943f"
}
Last Notes npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Liar. Hacked despite way above par opsec. And investigating crimes is literally the FBI's job. You're an idiot npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Re "new bugs", note that I mean newly discovered. At least one of these dates back to 2013 (v0.8.0). npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr An update on this thread, for full clarity: There are now a total of 8 new bugs which can cause wallet deletion or corruption. My initial comment applies only to the initial, severe bug that affects people simply using Core30 normally. @nprofile…m9s8 _is_, however, impacted by 6 of the others, which are not triggered by normal end users: 3 of these are "power user" functionality (moving wallet files around manually; creating unexpected files in the wallet directory; or using the `bitcoin-wallet` command line tool) 1 of them requires a low-level disk/filesystem/OS problem during shutdown. The remaining 2 are unrealistic to trigger at all, but hypothetically possible if you start the node software again immediately before it finishes shutting down (within milliseconds), or ... have multiple wallets in the same directory, one of which has recent changes, the node crashes or has a power failure, you start the node again and NOT open the recently-modified wallet, open the other wallet, and shutdown cleanly. All six of these issues will be fixed in a new version of Knots soon. #nevent1q…qzjl npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr FYI, @nprofile…m9s8 is NOT impacted by the Core30 wallet deletion bug. https://x.com/LukeDashjr/status/2008326237962277039?s=20 npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Internet Relay Chat (1980s protocol) for open source development, including Bitcoin from the earliest days (Satoshi's Bitcoin client even used it to find peer IPs!) npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr You're the one lying npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr No, you're wrong. You're acting as if miners have a choice. They don't. They must make blocks that the network accepts, or they're not miners anymore. If they make invalid blocks, *they* are splitting the chain - not the softfork. Furthermore, their invalid blocks don't constitute a real chain: every time the valid chain gets ahead, all the old nodes will drop the invalid blocks and those miners will start over, with huge losses. The only way they can avoid this, is with a counter-fork. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr You're the liar. I said nothing of the sort. And no, softforks _don't_ cause chain splits. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr No, that's a question for Sparrow npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Liar npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Liar npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Reverting a softfork without an upfront expiry is a hardfork npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr I do not support the rules in BIP444 on a permanent basis. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr No, stop trying to scam people with rigged bets npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr The whole concept (as I originally designed it) was for an emergency/reactive UASF. I'm not sure it makes sense any other way. For a non-eventful softfork, you'd want to start it 1-1.5 years into the future. And then with a 1 year expiry still? npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr And run the UASF 😉 npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Obviously. Like gun restrictions. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Except I didn't npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Agree with your second paragraph. I definitely don't _want_ to control Bitcoin. No idea why you think that's at all related to the screenshot, though npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Could always use more hands on deck npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Assuming good faith, Odell, you seem to have this habit of posting before verifying... npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Got a source for that? That would indicate the only reason they haven't done it to Bitcoin yet is building this narrative / waiting for more Core 30 adoption... npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr No, your framing is dishonest. Respectively, each scenario is: - no CSAM: no jail - no CSAM: no jail - no CSAM: no jail - CSAM: jail npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr No, the Core maintainers also function as maintainers in Knots too. Saying I'm the sole maintainer because I roll the releases is like saying Gloria is the sole maintainer of Core 29.x. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr It was never just a Luke project and I was never closed to more involvement. This quote is just FUD, @nprofile…uf96 npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr They're not interested in listening. They're interested in better gaslighting. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr No. Filters work. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Sounds like he's lying to you. Bitcoin is currently on fire and that fact won't change until Core30 is recalled, and Core 30.1 adds the spam filters back. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr There's already 3 signers for the builds, with likely more coming. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Eight, actually* npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr $ gpg --verify SHA256SUMS.asc gpg: assuming signed data in 'SHA256SUMS' gpg: Signature made Fri 10 Oct 2025 05:14:58 PM EDT gpg: using EDDSA key 1A3E761F19D2CC7785C5502EA291A2C45D0C504A gpg: Good signature from "Luke Dashjr (Codesigning) <[email protected] >" [unknown] Primary key fingerprint: 1A3E 761F 19D2 CC77 85C5 502E A291 A2C4 5D0C 504A gpg: Signature made Sat 11 Oct 2025 04:06:25 PM EDT gpg: using RSA key 1D70CBE4B42239445617D33DD316C8140185B647 gpg: Good signature from "shiny (Bitcoin Knots attestations) <[email protected] >" [unknown] Primary key fingerprint: 1D70 CBE4 B422 3944 5617 D33D D316 C814 0185 B647 gpg: Signature made Mon 13 Oct 2025 09:41:15 AM EDT gpg: using RSA key C1BCB7169AF1A07A0C5E471A047509FA0A6D7350 gpg: issuer "[email protected] " gpg: Good signature from "ataraxia009 <[email protected] >" [unknown] Primary key fingerprint: C1BC B716 9AF1 A07A 0C5E 471A 0475 09FA 0A6D 7350 Likely more coming... 29.1 had 7 signers. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr It would take less than that for you to think about it. It was a one-line claim that isn't true. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr That's simply not true at all. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Why do you keep repeating the FUD and denying the problem? This is why people are losing trust in you. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr That doesn't put out the fire, it turns up the heat. Why do you want an airdrop so bad? npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr I tried decentralised funding (via Patreon, GitHub Sponsors, and Bitcoin) for years. It just doesn't get enough donations to be viable. You can disagree with their funding decisions, but at the end, I think we do need organizations like OpenSats to arrange funding. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Only one maintainer ships each Core release. The "on your own" has always been nothing but FUD. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr https://gnusha.org/pi/bitcoindev/CALeFGL0PDjtRt2rfbY4gTkoc+5oNQ0mn_obraE7PrtHuNYFpQw@mail.gmail.com/T/#mb71350c5dfb119efeb92c5ee738b6c8225bf15b6 npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr There's an actual fire tho npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr So inform yourself and recommend Knots NON-blindly🤦♂️ npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr It's way bigger. This is more like gold confiscation npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr To address spam, no. To address Core 30 malware, maybe. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Policy is the right way to implement spam filters. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr No, that's inevitable if Core30 prevails, though. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Even if we survive this attack by Core30, this situation where I personally have to save Bitcoin every few years needs to stop. Bitcoin cannot survive if it's dependent on one man. Others need to step up more. https://x.com/LukeDashjr/status/1975942110047252776 npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Because we've run out of time. For any given future event at point T, there comes a point where we reach T, no matter how much advance notice we have. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr The exploit works because Core neglected to update the spam filters a few years ago, and refuses to fix the vulnerability. And no, you're wrong. Satoshi's spam filters were VERY picky about what was inside transactions. Anything that he didn't foresee being used was rejected. Core30's malicious changes have nothing whatsoever to do with Taproot. Each user decides for himself. Collectively, our nodes form consensus around what is spam and what maybe isn't. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr 2) Ordinals/Inscriptions are just spam. It's basically a scamcoin using proof-of-attacking-Bitcoin as its "algorithm". Taproot witness data does not allow arbitrary data - that's just an abusive *mis*interpretation of script code that Ordinals is doing completely unrelated to Bitcoin. This _is_ a relevant distinction. 3) Satoshi introduced spam filters to deal with the spam issue. So Bitcoin literally _was_ designed to work this way. 4) Again, Bitcoin has used spam filters from the start. It is Core30 that aims to change Bitcoin by removing some. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Braiins no longer runs a pool, they just proxy to Antpool. But again... anything but F2Pool is an improvement for now. Lots of people use DATUM on a Raspberry Pi. Though Pi isn't very good at running a node since the last spam wave. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr We've had months of advance notice of this threat. Not my fault some people waited until it's an immediate emergency. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Liar. Spam filters have proven VERY effective. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr 1) We're not talking about encrypted data. 2) Bitcoin does not support images at all, so it is impossible to store CSAM. Stegonography is another matter entirely (though even in that regard, there's no evidence of CSAM). 3) Spam is not usage, and Bitcoin relies on its users to protect it. WE are Bitcoin's antifragility. 4) Obviously I'm going to recommend OCEAN. Not only am I biased, but it's also better for Bitcoin. But the point is to mitigate this, I'm willing to concede even the would-be-worst pools to mine on are better than F2Pool right now. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Don't mine with F2Pool, and tell everyone you know who does. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr They may very well be liable, but that doesn't change the permanent harm it does to Bitcoin. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr I mean, "child protection" is just child trafficking under colour of law. Of course they want their privacy so they can continue to get away with it... This is like any other criminal saying it. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr F2Pool is actively attacking the network RIGHT NOW. All it takes is one attacker to send them a single instance of CSAM, and Bitcoin users will have to knowingly and intentionally receive, store, and distribute it until the end of time. This will permanently impact Bitcoin adoption regardless of whether governments turn a blind eye or prosecute. If miners are going to switch pools when they do bad things, NOW IS THE TIME. I don't care if you switch to Foundry or even Antpool. Obviously I would prefer you make your own blocks and use OCEAN, but this is too critical and time-sensitive to be picky. We can work on mining decentralization and spam issues over a longer period of time, but CSAM is an insta-kill we MUST avoid. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr But the Inscription exploit still bypasses it in Core. And if it's Core 30, you're still socially signaling that 100k opreturn is legitimate data storage npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Probably should run it by whoever is working on that these days (the charlatan?) npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Why do all nostr relays block VPNs? npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr There's no hard fork, stop listening to liars npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr What do you have against Knots now??? npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Try actually reading what I wrote. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Some people seem to want to argue that there is already CSAM in Bitcoin's blockchain. This is false. Bitcoin today does not support images at all - only arbitrary data up to 80 bytes (or 95 in the coinbase). Exploits like "Inscriptions" work by _misinterpreting_ script code, and _bypassing_ existing policy rules. They are not actually storing images, but merely putting gibberish code on the chain, which they later themselves (not Bitcoin) _misinterpret_ as images. This distinction is very real and relevant. If you don't differentiate between "data that can be misinterpreted to produce CSAM" and "data that correctly interpreted displays CSAM", then literally _all data_ is CSAM, with _no exceptions at all_. This tweet would be CSAM. Google's logo would be CSAM. Your phone's operating system would be CSAM. Literally anything _can_ be misinterpreted as CSAM. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Bitcoin only works if the economy at large uses their own full node npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Custodial FPPS pools are technically very easy in general. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Except that's NOT how censorship resistance works. Censorship resistance comes from anyone being able to mine a block npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr His problem is his insistance on using asmap. It doesn't make sense for this use case. Using asmap means everyone with Comcast as an ISP counts as 1 node. Everyone on Spectrum, just 1 node. It's ridiculous. What a lower percentage with asmap would indicate is a lack of diversity among Knots nodes. Which would make sense, since the bad actors in Core stole the Transifex repo a year ago to prevent people from translating Knots... So non-English-speaking countries would understandably be underrepresented at this point. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Adam is doing a LOT of blatant lying lately :( npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr No, Adam is just gaslighting npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Yes, the update is malware npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Because CSAM is a bigger threat, duh npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr It's all facts npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Nobody is actually against Bitcoin having spam filters. Fees are just another filter, not fundamentally any different from any other filter. Even Core is adding _new_ filters: TRUC and ephemeral dust are two recent examples (mandatory in Core, and optional in Knots). They're just against _you_ having a say in what filters you get to use. They want to dictate that you use the filters _they_ choose. Instead of decentralized policy, they want a centralized policy. (And they're not even choosing sane ones! Who in their right mind wants to relay CSAM???) npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr They _can_, but there's no good reason they _would_. They also have the freedom to _not_ mine the spam, unlike with other pools that force them to do so. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr OCEAN enables miners to use their own updated spam filters. The other pools force them to use obsolete and buggy Core ones. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr I don't think that's correct npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Maybe it's the Downfall meme🧌 npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr This is why we stopped mining namecoin a decade ago npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Liar npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Nothing immoral about this law npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Almost all nodes that matter have to comply with the law npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Using BitTorrent to transfer CSAM will land you in jail. That's just more reason to be concerned npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Hence it's not enough to just use Knots yourself, but the network as a whole must reject Core 30 npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr For years, there has been FUD that Bitcoin's blockchain could be criminalised by storing CSAM on it. For years, the answer has always been that Bitcoin doesn't support data storage, and the offending content is not the blockchain itself, but the additional software used to transform the blockchain into CSAM. By sanctioning data storage, Core 30 is eliminating that argument. There will no longer be any additional software required, your Bitcoin node itself will provide CSAM on demand, using a well-defined and officially supported format. The very reason "CSAM on the chain" was FUD, is being _destroyed_ by Core 30. They are making it a _true_ accusation. No amount of obfuscation will change this fact. This is not the _only_ reason to reject Core 30. But even if it was, it would _still_ be strong reason to do so. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Now for the purely hypothetical: this is only one step away from also displaying the transaction to the recipient, tricking him into thinking he received it. The only thing standing in the way of this on the receiver end is if he is using his own full node! What happens on a Bitcoin standard, if 80% of the merchants aren't using full nodes and are tricked into accepting fake payments like this? #nevent1q…jwfl npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr PSA: There is a supply chain attack on Bitcoin wallets going on. HARDWARE WALLETS AND SIGNAL MAY BE AFFECTED. READ FURTHER. I have not studied the full scope of this attack yet, but from what I hear, it can impact websites/webapps (including "local" webapps like Signal Desktop) and cause them to display a thief's address instead of the intended one. This means hardware wallets will correctly display the actual send-to address, but you the human may compare the address to one that has already been replaced! Regardless of what wallet you use, verify the address you are sending to without trusting a computer. Call your recipient and verify verbally. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr This post is about the next decade or two, not the next 24 hours. Core and Bitcoin cannot both continue to exist. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Define "rollups". npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Bitcoin is not a finished product. We may be on a detour to address spam, and part of the crisis did originate with (mishandling of) the Segwit and Taproot upgrades - but to improve the world, we still need more functionality. Stopping all improvements forever ("ossifying") is fatal. Part of addressing the issues with Core needs to be ensuring we don't repeat the same mistakes: if an upgrade introduces unforeseen vulnerabilities, those need to get addressed in a timely manner. All protocol changes require support from the entire community, so we developers are going to have to earn that reputation back. There are fairly simple, low-risk softforks like CTV, or even a consensus cleanup (though I have reservations about BIP 54), that should not introduce vulnerabilities, and could be a starting point to regain confidence after Core is out of the picture. The next step up is probably native zero-knowledge support, BitVM optimisations, and similar. This is when it *might* make sense to start considering Bitcoin L1 "complete", and capable of handling further improvements and even scaling on true trustless sidechains. We have a long road to get there still, and every step will take consensus - possibly quick mitigation of unforeseen outcomes - but we shouldn't lose sight of the end goal: a decentralised currency that nobody can undermine, and hopefully one day onboard the entire global economy. It's possible to accomplish, but we will have to work for it. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr > hours On a Saturday... Odell has a life. Give him some time lol npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr "won't accept" how? npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Who is forcing you to spam? npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr You can, that's not the point. npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Node policies work. This is the one miner who is actively trying to undermine the p2p relay network with Slipstream, and even they had to stop accepting subsat transactions out of risk of losing blocks because the nodes' relay policy doesn't accept them. **CORE 29.1 IS CHANGING THAT THIS MONTH** https://x.com/PortlandHODL/status/1958520763083825640 npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Be careful out there... The bad actors are now attacking individual Knots nodes. If you have data limits, pay a visit to the maxuploadtarget option (in the GUI under Options -> Network tab -> Try to keep upload traffic under ____ MiB per day - only in Knots) https://x.com/nazgulHODL/status/1959009018602537450?t=aWEE2gViZAAJWTUZGPP5FQ&s=19 npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Very different things npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr No, it didn't fill blocks nor spam at all npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr That could be the next step _after_ we decentralise mining npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr Delaying blocks: not effective with mining centralisation. Compression: actually makes the problem worse (more CPU time) Custom mining templates: OCEAN already gives miners full control npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk Luke Dashjr The last update to Knots was in March... Sounds like this is an Umbrel-specific issue.