Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 74
Generated: 20:16:47
Here is an updated version of my email to the bitcoindev ML, which fixes a typo: Hi list - I was hoping to post this on the PR, but it's still locked so I will post it here. I don't really have any other methods of addressing the public as my X account has also been suspended due to trolls reporting it. I did create a Nostr account, but Nostr doesn't seem to have many users. There is a wild misconception floating around that the BIP I am proposing is a "legal threat from Ocean Mining". This could not be further from the truth, and I suspect this nonsense is being pushed by people who would love to see Bitcoin become a data storage service. I would like to take this opportunity to correct the record. Though I am in direct communication with some Ocean employees (and the BIP was originally drafted by one of them), I am not affiliated with Ocean in any way. I am just a Bitcoin dev who is concerned about the implications of Core 30 having been released and gaining adoption. The references to "legal risks" in the BIP are not "threats". They are warnings about a major legal and moral threat that has been created by Bitcoin Core 30's officially designating Bitcoin as a storage service for files up to 100kB. Specifically, there is an unknown level of risk that node operators could be classified as sex offenders (or some other type of criminals depending on the content) for possessing and distributing toxic content. This threat does not come from me, or from Ocean, but rather from Core 30 and its effect on node operators themselves, their consciences, and the communities in which they live. Core 30 forces every single node operator, from the moment toxic content is posted to the blockchain until the end of time, to be complicit in sexual (or other) crimes via possession and distribution of illegal data. So now that Core 30 is gaining adoption, it's very likely that, given the choice of whether to participate in Bitcoin or not, most normal people will simply choose not to participate, and then Bitcoin becomes just another BSV. If Core had just left the OP_RETURN limit where it was, no significant legal threat would exist, and no consensus changes would be urgently needed. I am not saying "I'm going to sue you if you don't support the fork". That is ridiculous. I am saying "you probably want to support this fork if aiding and abetting sex offenders (and potentially being one yourself) does not appeal to you, and you may not want to run a node once Core 30's new default policies become the standard (which is about to happen)." Most Bitcoiners I know signed up for permissionless money, and believe strongly in the freedom to transact, even for people who do things we don't like, since the vision of a maximally neutral monetary standard is why we're all here in the first place. Because Bitcoin's purpose is to be permissionless money, simply storing and forwarding a record of an "illegal" purchase is acceptable to most node operators, because that is the price of entry for trustless, digital money. Storing and forwarding actual illegal content, in the clear, however, is not a problem Bitcoin was ever intended to solve, nor something in which Bitcoin node operators are interested in participating. Indeed, permissionless censorship-resistant data storage is probably not a sustainable idea, without some kind of periodic payment to the person tasked with storing the data. In any case, forcing all Bitcoin node operators to knowingly commit crimes totally unrelated to the operation of Bitcoin as permissionless money, for the rest of eternity, is obviously a foolish idea and will quickly lead to node centralization and irrelevance if we do not act. Yet this heavy-handed and completely unnecessary imposition is precisely what Core 30 achieves, unless it is enthusiastically opposed by the community. Even in the best case, Core 30's new default policies set a terrible precedent that must be immediately reversed. Since almost all forms of illegal data can be avoided by limiting data fields to 256 bytes, BIP-444 seems like a no-brainer to me, because it neatly dodges the dark fate that awaits us down the data storage path. Having engaged many principled Bitcoiners on this topic for a long time, I can confidently say that Bitcoiners overwhelmingly support keeping Bitcoin as permissionless money, and overwhelmingly oppose Bitcoin's block space being used for data storage. Limiting large data storage in consensus, as BIP-444 does, is the easiest way I can see to give everyone what they want. So even if BIP-444 does not activate in its exact current form, I am dedicating myself to helping Bitcoin re-affirm its commitment to permissionless money while re-affirming its opposition to data storage. I am incorporating all feedback I am hearing (which is a lot!) into the next draft of the BIP. Thanks again to everyone for your thoughtful and respectful engagement on this matter critically important to the future of Bitcoin. Together we will find the way forward. Sincerely, Dathon
2025-10-28 20:41:26 from 1 relay(s) 53 replies ↓
Login to reply

Replies (74)

nostr:nprofile1qqsqfjg4mth7uwp307nng3z2em3ep2pxnljczzezg8j7dhf58ha7ejgpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcprfmhxue69uhhxetwv35hgtnwdaekvmrpwfjjucm0d5hszxthwden5te0wpex2mtfw4kjuurjd9kkzmpwdejhgtcuauf96 Look who was forced onto a more censorship resistant platform. (Many such cases.)
2025-10-28 20:51:01 from 1 relay(s) ↑ Parent 1 replies ↓ Reply
I guess this is the guy who wrote that bip. Don't just read one side - one side is claiming there was a legal threat. I haven't been able find it, and its looking like that was an example of influencers misleading people. nostr:nevent1qqsp58r0x6vwcmjlz6nldtm7wdj8ggw6cvpkjq4e2wyedrgkd3dlm5sppemhxue69uhkummn9ekx7mp0qgsw3p5pela795rxxff34kgfafsaawhnkqp8ehmgm2my49dgx9fjclcrqsqqqqqp9ct463
2025-10-28 20:56:56 from 1 relay(s) ↑ Parent 5 replies ↓ Reply
Since author of BIP 444 clarified the Legal Threat FUD, let's see what else nostr:nprofile1qqsqfjg4mth7uwp307nng3z2em3ep2pxnljczzezg8j7dhf58ha7ejgprpmhxue69uhhqun9d45h2mfwwpexjmtpdshxuet5qyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqnz0fd0 comes up with to FUD about BIP 444. It seems like nostr:nprofile1qqsw3p5pela795rxxff34kgfafsaawhnkqp8ehmgm2my49dgx9fjclcpzemhxue69uhkzarvv9ejumn0wd68ytnvv9hxgqg7waehxw309anx2etywvhxummnw3ezucnpdejz7mrpdenj7etn37n9fy is humble enough to accept the mistake and he is open to make some improvements in the next draft of BIP 444. If gay retarded core devs would have done the same thing before forcing V30 (aka malware) on us, we wouldn't be talking about this BIP. Anyways, I can't wait to hear LIAR OR FUCK OFF from nostr:nprofile1qqsqfjg4mth7uwp307nng3z2em3ep2pxnljczzezg8j7dhf58ha7ejgprpmhxue69uhhqun9d45h2mfwwpexjmtpdshxuet5qyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqnz0fd0. nostr:nevent1qqsp58r0x6vwcmjlz6nldtm7wdj8ggw6cvpkjq4e2wyedrgkd3dlm5szyr5gdqw0l03dqe3j2vddjz02v80t4uasqf7d76x6ke9ft2p32vk87qcyqqqqqqgyqdlel
2025-10-28 21:02:24 from 1 relay(s) ↑ Parent Reply
Since there's now good evidence against this "legal threat" narrative I think you should take the L on this and admit you were wrong. nostr:nevent1qvzqqqqqqypzp6yxs88lhcksvce9xxkep84xrh467wcqylxldrdtvj544qc4xtrlqqsp58r0x6vwcmjlz6nldtm7wdj8ggw6cvpkjq4e2wyedrgkd3dlm5smfptyd
2025-10-28 21:18:18 from 1 relay(s) ↑ Parent Reply
Any time there is a way to add arbitrary data to the blockchain, the risk exists for something someone doesn’t want in their node. If you were sincere in wanting to remove said unwanted data, you would develop a BIP that would let node operators delete arbitrary data from their historical record database as well as add filters, but still maintain the merkle root and “tip of the chain”. Oh, wait, that’s what OP_RETURN pruning does. I guess that doesn’t fit the narrative.
2025-10-28 21:49:26 from 1 relay(s) ↑ Parent Reply
Welcome to Nostr. Bitcoin is THE Global Most Secure Decentralized Unconfiscatable Peer-to-Peer Scarce Hard Sovereign Freedom Money, The Greatest Store of Value and The Strongest Hope for Humanity.
2025-10-28 22:58:14 from 1 relay(s) ↑ Parent Reply
How can anything illegal be limited? You can simple break data up and do multiple transaction and add more and more utxo bloat to the chain. Your entire BIP was put Onchain as bip444 complaint transaction. Your acquiescence to fear is pathetic.
2025-10-29 04:14:48 from 1 relay(s) ↑ Parent Reply
The risk you allude to always existed (and probably will always exist) because 1) it was always possible to mine a block with illegal content in an OP_RETURN, and 2) illegal content can always be embedded in the blockchain using various other methods (even if your BIP is adopted). Fortunately, there appears to be pretty broad consensus among experts in law that this is not a real risk, anyways: https://protos.com/exclusive-lawyers-call-bitcoin-core-v30-csam-concerns-overblown/
2025-10-29 05:37:38 from 1 relay(s) ↑ Parent 5 replies ↓ Reply
I might be wrong but, if there is illegal content in the op return of a minned block, it doesn't matter if you have core or knots. You will be storing and distributing it anyways, right? For what I understood the difference between them is in the transaction you admit and broadcast to the mempool It's all a question. I'm not sure if i've got it right #asknostr
2025-10-29 07:16:59 from 1 relay(s) ↑ Parent Reply
You sir, are a fucking legend. nostr:nprofile1qyv8wumn8ghj7urjv4kkjatd9ec8y6tdv9kzumn9wsq3vamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet5qqsqfjg4mth7uwp307nng3z2em3ep2pxnljczzezg8j7dhf58ha7ejgqgzx3h on the other hand...
2025-10-29 09:18:26 from 1 relay(s) ↑ Parent 1 replies ↓ Reply
You low life. He's not alluding to any risk, he's stating some facts. Another fact that you already know is that your mates and Core v30 allow CSAM and other horrors to be stored by default, in larger quantities and much simpler. To push that, or simply not be against it, is a crime that no expert needs to risk asses.
2025-10-29 09:25:27 from 1 relay(s) ↑ Parent Reply
Thank you for actually engaging with this question. I read that article back when it came out and I'm not convinced just reaching out informally to a few lawyers is enough due diligence. At least not when the risk is this high. Even then 1/7 of them actually was concerned about it. If we roll with that as the only evidence that was gathered we have a 1/7 chance Bitcoin will be deemed illegal in the future. I'd be more reassured if we had any lawyers actually seriously look into the risks involved. Or had some statements from government bodies that'd be involved that we're in the clear. (FCC in the US? Equivalent EU bodies?)
2025-10-29 09:31:06 from 1 relay(s) ↑ Parent Reply
That one lawyer did not even want to stake his name and reputation to defend his claim. As such we also have no way to determine how credible this person is to begin with. Judging by all other responses, not credible at all.
2025-10-29 09:56:12 from 1 relay(s) ↑ Parent 1 replies ↓ Reply
If BIP-444 (or something like it) doesn't activate, then everyone will be required to knowingly possess and distribute whatever nasty things end up in the chain, in the clear, for the rest of eternity.
2025-10-29 14:18:13 from 1 relay(s) ↑ Parent 1 replies ↓ Reply
The difference is that pre-Core-30, Bitcoin did not officially support large file storage. So node operators had much less culpability. As for the "lawyer consensus" in that article you linked, you must not have read it if your conclusion is that "this is not a real risk". Almost all of the lawyers in the article said it's a risk. The question is whether Core 30 meaningfully increases the risk. I think it's obvious that it does, as I said above. Data spam is a slippery slope. We have to draw the line somewhere, and this may be our last chance to draw the line. BIP-444 is the line.
2025-10-29 14:59:03 from 1 relay(s) ↑ Parent 1 replies ↓ Reply
There is nothing “official” in Bitcoin. I think it’s obvious that Core 30 does not meaningfully increase the risk, because as pointed out these same risks already existed. If node operators are nevertheless concerned about legal risks if they run Core 30, they can just run a different node implementation, whether that’s an older version of Bitcoin Core, Bitcoin Knots, or whatever.
2025-10-29 15:23:39 from 1 relay(s) ↑ Parent Reply
Meh. I read their responses differently I guess. All said there was some risk although most tended to think it was overblown. Now even with the slightest risk, what exactly is the benefit? It’s zero. Nobody wanted or needed this. Doubling or quadrupling the original limit would’ve provided for about any monetary use case people were discussing.
2025-10-29 21:21:10 from 1 relay(s) ↑ Parent Reply
Bitcoin Core was, until recently, the closest thing we had to something "official", because until recently, Core tried to represent a supermajority of its users. I don't agree at all that "it's obvious" that Core 30 doesn't meaningfully increase risk. "These same risks", namely Core 30 officially sanctioning large file data storage on the blockchain, have certainly never existed before. Running a different client does not change anything if the de facto standsard on the network is that data storage is an official use case. But forking will change things, because it reverses the official sanctioning into an official rejection of the data use case.
2025-10-30 05:07:01 from 1 relay(s) ↑ Parent 1 replies ↓ Reply
**** This just in.. pedoland under 'pedo software' "crisis" **** The U.S. is the only UN member state that has not yet ratified the Convention on the Rights of the Child. As of July 2025, child marriage is legal in 34 states.
2025-10-30 22:10:45 from 1 relay(s) ↑ Parent Reply
**** This just in.. pedoland under 'pedo software' "crisis" **** The U.S. is the only UN member state that has not yet ratified the Convention on the Rights of the Child. As of July 2025, child marriage is legal in 34 states.
2025-10-30 22:56:45 from 1 relay(s) ↑ Parent Reply
I think anyone but the most gullible can by now see your overt dishonesty and broken logic. Had you at least staked your own name and reputation on this proposal I'd maybe consider spelling it out to you one more time-- but alas.
2025-10-31 08:06:46 from 1 relay(s) ↑ Parent Reply
nostr:nprofile1qyxhwumn8ghj7cnjvghxjme0qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcqyr7at68k4cxms9a7pdca5gzf3svqd95d3fj9j4vuyj0nyta8x3j2whad7ya 2 warnings about bip-444: In the case of an offensive block, what happens to all legal txs within that same block? it'd be terrible to reverse good txs. Images/videos/files shouldn't be allowed at all, better than to monitor for the most unpleasant things, right? the worst experience for anyone monitoring it.
2025-10-31 09:31:59 from 1 relay(s) ↑ Parent Reply
nostr:nevent1qvzqqqqqqypzpyq49dlcmlaul3rz7hqz7y30wt3m4evvevzegvfk0cneqgzw2aqpqyt8wumn8ghj76rfwd6zumn0wd68ytnvv9hxgtcppemhxue69uhkummn9ekx7mp0qqs0x6hee4qulk0qkt3vaenxlsy46aehey6stcf874yjs4xn7frxk2g9tc0vz
2025-10-31 16:04:23 from 1 relay(s) ↑ Parent Reply
Claims of confiscation are just FUD. A competent person tried to find an example of a TXO that could be confscated by BIP444 and came up with nothing. But to be completely sure, I'm adding a UTXO height check in the next draft of the BIP.
2025-11-01 20:29:19 from 1 relay(s) ↑ Parent Reply
The author of BIP-444 is here on Nostr if you want to follow him. Apparently the Coretard “anti-censorship” champions managed to get his acc on Twitter banned. Figures. nostr:nevent1qqsp58r0x6vwcmjlz6nldtm7wdj8ggw6cvpkjq4e2wyedrgkd3dlm5s4d5e4g
2025-11-04 13:42:34 from 1 relay(s) ↑ Parent Reply
Bitcoin is anti-fragile. It is rather resistant to censorship but of course one still must actually try to evade the censorship. It is pseudonymous not anonymous, but you can be anonymous if you need to. The question you are responsible for answering is, do you need to be anonymous? Do you need to resist your government or are you happy enough with your chains?
2025-11-05 02:36:02 from 1 relay(s) ↑ Parent Reply