🧵 Thread by @oomahq on Twitter regarding the ongoing NFT debate :
The Bitcoin timechain was designed to move 2100 trillion sats in a permissionless way for perpetuity. It's not AWS S3, it wasn't made to store arbitrary bytes of data.
Accepting arbitrary bytes in transactions forces 2 serious negative externalities on voluntary node runners:
1) It makes it way more expensive to maintain their node on the long term.
2) It makes them liable for any illegal content in their jurisdiction that they store on their disk and broadcast freely.
If you decide to put up with these negative externalities you'll make it much more difficult for yourself to fulfill your DUTY to pass on this heirloom to the humans of the 22nd century and beyond in working condition.
The good thing is, you don't have to.
Realize that as a node runner you're a sovereign Bitcoin entity, not a passive watcher.
You can guard the door to YOUR mempool, and collectively we can force these fuckers to spend real resources on building their own lax nodes and mining operations if they want to spam Bitcoin.
Don't let these wreckers psyop you into non-action, or into believing you'd be somehow interfering with the "free market" or the "will of the people".
Realize that the enemies of freedom will bend and twist your own ideals and use them against you at any chance you give them.
So let's stop pleading with spooks like @rodarmor and their hordes of trolls and useful idiots, and let's start moving on the offensive. We must face these bastards head on.
GFY and LFG 🖖
/🧵
kano / Kano
npub1ft…mq3tx
2023-02-04 18:38:20
Author Public Key
npub1ftcgezejty0avuyjgzrkxkj00n92ucfk0qvv7l2jcw5u8mcxngwsrmq3txSeen on
wss://relay.noswhere.comPublished at
2023-02-04 18:38:20Event JSON
{
"id": "1dc6d178d18c76e8dc1ba4208a4db26a4b610bc3378eab116c867ec0d0a5a39b",
"pubkey": "4af08c8b32591fd670924087635a4f7ccaae61367818cf7d52c3a9c3ef069a1d",
"created_at": 1675535900,
"kind": 1,
"tags": [],
"content": "🧵 Thread by @oomahq on Twitter regarding the ongoing NFT debate :\n\nThe Bitcoin timechain was designed to move 2100 trillion sats in a permissionless way for perpetuity. It's not AWS S3, it wasn't made to store arbitrary bytes of data.\n\nAccepting arbitrary bytes in transactions forces 2 serious negative externalities on voluntary node runners:\n\n1) It makes it way more expensive to maintain their node on the long term.\n\n2) It makes them liable for any illegal content in their jurisdiction that they store on their disk and broadcast freely.\n\nIf you decide to put up with these negative externalities you'll make it much more difficult for yourself to fulfill your DUTY to pass on this heirloom to the humans of the 22nd century and beyond in working condition.\n\nThe good thing is, you don't have to.\n\nRealize that as a node runner you're a sovereign Bitcoin entity, not a passive watcher.\n\nYou can guard the door to YOUR mempool, and collectively we can force these fuckers to spend real resources on building their own lax nodes and mining operations if they want to spam Bitcoin.\n\nDon't let these wreckers psyop you into non-action, or into believing you'd be somehow interfering with the \"free market\" or the \"will of the people\".\n\nRealize that the enemies of freedom will bend and twist your own ideals and use them against you at any chance you give them.\n\nSo let's stop pleading with spooks like @rodarmor and their hordes of trolls and useful idiots, and let's start moving on the offensive. We must face these bastards head on.\n\nGFY and LFG 🖖\n\n/🧵",
"sig": "d04ca9fd9d46b51ba4ae4f2f93a18c732b3a845a728988a9af17d6ef90ead1f9fdbdaf339a0fb8b8d1203265b8ead2598742201e75f489aaacf93c16bb91bd6a"
}