It’s not about shitcoins.
How do you know why OP_CAT was removed?
As an engineer, do you think it’s a good idea to enable powerful technology IN THE BASE CHAIN that has few known limits so essentially nobody knows how it could be abused?
Satoshi’s design philosophy was clearly to limit functionality to keep the system simple and safe. He made the system robust by deliberately removing codes that might increase the attack surface of the network.
It’s not appropriate to apply start up thinking - move fast and break things - to the core system protecting the world’s money and our hope for the future.
If you’re wrong, and it somehow disrupts the underlying incentives that underpin everything … how easy is it to undo it? We can’t, can we?
How I see it:
+ Devs are humans. Even the smartest among us are not omniscient and make mistakes (eg witness discount).
+ All code has bugs. Even if the code is technically bug free, it can still change the complex incentives that make the network work.
+ We don’t have a scaling problem yet. When we do have one in the future, we should allow the pain of it to motivate innovation on upper layers so that we can avoid any unnecessary changes to the base protocol.
+ We should only allow changes to the base protocol that safely fix an existential problem that we know cannot be fixed in any other way.
+ The Bitcoin network is for many, many future generations. We need to think long term and not rush out changes to the core protocol. A decade or two to consider options is a blink of an eye in the life of the network.
techfeudalist /
npub1nz…0yxqu
2024-08-09 01:22:29
in reply to nevent1q…fwgx
Author Public Key
npub1nz3cd3mx4jf9paxwrdgqvchaprjdge9pj9t58mkusw74q5saajkqu0yxquPublished at
2024-08-09 01:22:29Event JSON
{
"id": "da72396b2af8afc6c27d56ee904ca903fd822f784f4b7fbbc6c3c3deaa3135ca",
"pubkey": "98a386c766ac9250f4ce1b500662fd08e4d464a1915743eedc83bd50521decac",
"created_at": 1723166549,
"kind": 1,
"tags": [
[
"e",
"9ef7e80eb6a4284b576cb798d00995b4b49ef5ff1950940923382f049b567412",
"wss://nostr-relay.derekross.me",
"root"
],
[
"e",
"7c4ea3e74c4cafc41bfb7e89c70dd6ec45b22dcb0993086c6bd8dba9770099b1",
"",
"reply"
],
[
"p",
"e1ff3bfdd4e40315959b08b4fcc8245eaa514637e1d4ec2ae166b743341be1af"
],
[
"p",
"e88a691e98d9987c964521dff60025f60700378a4879180dcbbb4a5027850411"
],
[
"p",
"3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24"
]
],
"content": "It’s not about shitcoins. \n\nHow do you know why OP_CAT was removed? \n\nAs an engineer, do you think it’s a good idea to enable powerful technology IN THE BASE CHAIN that has few known limits so essentially nobody knows how it could be abused? \n\nSatoshi’s design philosophy was clearly to limit functionality to keep the system simple and safe. He made the system robust by deliberately removing codes that might increase the attack surface of the network. \n\nIt’s not appropriate to apply start up thinking - move fast and break things - to the core system protecting the world’s money and our hope for the future.\n\nIf you’re wrong, and it somehow disrupts the underlying incentives that underpin everything … how easy is it to undo it? We can’t, can we?\n\nHow I see it:\n\n+ Devs are humans. Even the smartest among us are not omniscient and make mistakes (eg witness discount). \n\n+ All code has bugs. Even if the code is technically bug free, it can still change the complex incentives that make the network work. \n\n+ We don’t have a scaling problem yet. When we do have one in the future, we should allow the pain of it to motivate innovation on upper layers so that we can avoid any unnecessary changes to the base protocol. \n\n+ We should only allow changes to the base protocol that safely fix an existential problem that we know cannot be fixed in any other way. \n\n+ The Bitcoin network is for many, many future generations. We need to think long term and not rush out changes to the core protocol. A decade or two to consider options is a blink of an eye in the life of the network.",
"sig": "90b3aff9634401094dd0af15ac56a2804e8f405c9619393805ebd8af3eb0d0ed71cbcf23025766aea36f216afe03e6809bb822ee8870eafc44def957c67dac6f"
}