I listened to the episodes on the OP_RETURN limits and CORE ...

3663a0e0adb2b3b1...

npub1xe36pc9dk2emzulxw0tp8ytlthpty80ry89w5rw3k28fdyzalprq0au0nh

hex

2a64d7dadb0ba33619da180850a2a433674c819034de5e61851f652906412d4d

nevent

nevent1qqsz5exhmtdshgekr8dpszzs52jrxe6vsxgrfhj7vxz37effqeqj6ngprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsrvcaquzkm9va3w0n884snj9l4ms4jrh3jrjh2phgm9r5kjpwls3sfpgvlq

Kind-1 (TextNote)

2026-06-28T05:04:27Z

↳ Reply to Event not found

cbb018b8b8839b7fb563efd61d253a4eff37d0205cc9aff494c757f47e1d4972...

I listened to the episodes on the OP_RETURN limits and CORE 30.0. My questions for you:

Why is the size limit increased because it fits a specific business case? I don't think it should change for any business... the business should work within the existing system. IMO, bloating the software simply generates problems., and has the potential to negatively impact the blockchain in the long run.

Why is there no mention of specifically CSAM in the shows? It is not just generic "spam" that can be added to the OP_RETURN. Increasing the OP_RETURN allows the entire CSAM jpg to be easily stored and viewed. Whereas the 80bytes makes it more challenging to do so.

Concluding that there will always be spam, so we just have to deal with it and increase the size of non-transactional data allowed. Well, by increasing the possible size over time, then the types of spam that can be added can change... parts of a jpg > jpgs > gifs > mp4s.

Anyway, thanks for forwarding the podcasts... appreciate it!

Raw JSON

{
  "kind": 1,
  "id": "2a64d7dadb0ba33619da180850a2a433674c819034de5e61851f652906412d4d",
  "pubkey": "3663a0e0adb2b3b173e673d613917f5dc2b21de321caea0dd1b28e96905df846",
  "created_at": 1782623067,
  "tags": [
    [
      "e",
      "2b9699bf6744332bf58f9626ec771915a2a5cd00bce374a82addc01bbbe4503b",
      "",
      "root"
    ],
    [
      "e",
      "cbb018b8b8839b7fb563efd61d253a4eff37d0205cc9aff494c757f47e1d4972",
      "",
      "reply"
    ],
    [
      "p",
      "3663a0e0adb2b3b173e673d613917f5dc2b21de321caea0dd1b28e96905df846",
      "",
      "mention"
    ],
    [
      "p",
      "de5d34f29113446cf081d8850cfeb37c2014434cec2803bcc089df65568df8b4"
    ],
    [
      "r",
      "wss://nostr.bitcoiner.social/"
    ],
    [
      "r",
      "wss://nos.lol/",
      "read"
    ],
    [
      "r",
      "wss://nostrelay.circum.space/"
    ],
    [
      "client",
      "Primal Web"
    ]
  ],
  "content": "I listened to the episodes on the OP_RETURN limits and CORE 30.0.  My questions for you:\n\nWhy is the size limit increased because it fits a specific business case?  I don't think it should change for any business... the business should work within the existing system.  IMO, bloating the software simply generates problems., and has the potential to negatively impact the blockchain in the long run.\n\n\nWhy is there no mention of specifically CSAM in the shows?  It is not just generic \"spam\" that can be added to the OP_RETURN.  Increasing the OP_RETURN allows the entire CSAM jpg to be easily stored and viewed.  Whereas the 80bytes makes it more challenging to do so.\n\nConcluding that there will always be spam, so we just have to deal with it and increase the size of non-transactional data allowed.  Well, by increasing the possible size over time, then the types of spam that can be added can change... parts of a jpg \u003e jpgs  \u003e gifs  \u003e mp4s.\n\nAnyway, thanks for forwarding the podcasts... appreciate it!",
  "sig": "96d98841c275adb337d763f55e8184fd5ef49f6c7e5155fb097356f0db1e53e464a7e2ef63828e6eadd2e8e25f9824f54a51bd2e299604e6c941adf9c50e70b7"
}