The following is written by ChatGPT as Amethyst throwed away...

stl1988
npub14rg4vrt2v374q95ezeeydu3hkdhmzglcj950mggacap4x0lv0gyq04wun7
hex
013c215d666fe2097e42e78b1bca86e64044c1c5725aba6940331ee5a33101f6nevent
nevent1qqsqz0ppt4nxlcsf0epw0zcme2rwvszyc8zhyk46d9qrx8h95vcsrasprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgs2352kp44xgl2sz6v3vujx7gmmxma3y0ufz68a5ywuws6n8lk85zq9xhmwtKind-1 (TextNote)
↳ Reply to Event not found
7191d21f5d12bf5936734e3b27a1961675fc47d793dae86f85b29b19a69ed1c0...
The following is written by ChatGPT as Amethyst throwed away my previous answer whipe the app was in background.
The main argument from Bitcoin Core developers is not "we want more data on-chain."
Their reasoning is:
- The 80-byte OP_RETURN limit doesn't stop data storage anyway.
- It pushes projects toward workarounds (e.g. Taproot inscriptions) that are arguably worse for Bitcoin.
- OP_RETURN outputs are provably unspendable, so they don't bloat the UTXO set.
- The limit was only a relay policy, not a consensus rule, and miners could already include larger OP_RETURN transactions.
- They argue that the fee market, not Bitcoin Core, should decide what gets into blocks.
In short: they see removing the limit as reducing harmful workarounds, not encouraging data storage.
End of AI answer. I hope this helps anyways.
Raw JSON
{
"kind": 1,
"id": "013c215d666fe2097e42e78b1bca86e64044c1c5725aba6940331ee5a33101f6",
"pubkey": "a8d1560d6a647d501699167246f237b36fb123f89168fda11dc743533fec7a08",
"created_at": 1782512967,
"tags": [
[
"alt",
"A short note: The following is written by ChatGPT as Amethyst th..."
],
[
"e",
"4c0972c515c31dd479929dc2044d03fbad5ab97250f95e755200cad6c5b508a1",
"wss://nos.lol/",
"root",
"2ad91f1dca2dcd5fc89e7208d1e5059f0bac0870d63fc3bac21c7a9388fa18fd"
],
[
"e",
"474df81820c795ab8951e02d1c53ec4b46f572491154ff6990a6c0af068ce3e1",
"wss://pyramid.fiatjaf.com/",
"",
"3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24"
],
[
"e",
"9d34b01f6350a0b37e07b9e1ff51f2b054c51c4968d0b43fdfd3283f951aecbe",
"wss://relay.primal.net/|",
"",
"ac554709232073ab9c7deba7a46eead2e7806cd68f89e7f4fd44e245c08e8ded"
],
[
"e",
"99db6039588d27a1722e0baeed23eb52492e2b80dd0d6df82b4966cdd80ea30d",
"wss://nostr.wine/",
"",
"3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24"
],
[
"e",
"3abcffd2d0605b1494d5158307cdf7aabff7a9feb4478f1696626db29f121fd9",
"wss://relay.primal.net/",
"",
"a8d1560d6a647d501699167246f237b36fb123f89168fda11dc743533fec7a08"
],
[
"e",
"7191d21f5d12bf5936734e3b27a1961675fc47d793dae86f85b29b19a69ed1c0",
"wss://pyramid.fiatjaf.com/",
"reply",
"3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24"
],
[
"p",
"2ad91f1dca2dcd5fc89e7208d1e5059f0bac0870d63fc3bac21c7a9388fa18fd",
"wss://nos.lol/"
],
[
"p",
"3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24",
"wss://nos.lol/"
],
[
"p",
"ac554709232073ab9c7deba7a46eead2e7806cd68f89e7f4fd44e245c08e8ded",
"wss://relay.primal.net/"
],
[
"p",
"a8d1560d6a647d501699167246f237b36fb123f89168fda11dc743533fec7a08",
"wss://relay.ditto.pub/"
],
[
"client",
"Amethyst"
]
],
"content": "The following is written by ChatGPT as Amethyst throwed away my previous answer whipe the app was in background.\n\n---\n\nThe main argument from Bitcoin Core developers is not \"we want more data on-chain.\"\n\nTheir reasoning is:\n\n- The 80-byte OP_RETURN limit doesn't stop data storage anyway.\n- It pushes projects toward workarounds (e.g. Taproot inscriptions) that are arguably worse for Bitcoin.\n- OP_RETURN outputs are provably unspendable, so they don't bloat the UTXO set.\n- The limit was only a relay policy, not a consensus rule, and miners could already include larger OP_RETURN transactions.\n- They argue that the fee market, not Bitcoin Core, should decide what gets into blocks.\n\nIn short: they see removing the limit as reducing harmful workarounds, not encouraging data storage.\n\n---\n\nEnd of AI answer. I hope this helps anyways.",
"sig": "1b65ec53a6b3c6d4e56797be69704c108e70cc4aa507442c1e75a146c7f809ef0685a7035c552aeb3da54471f92e461a555b414b2af92b80f0b5063658b7d54b"
}