Luke Dashjr on Nostr: Bitcoin is not a finished product. We may be on a detour to address spam, and part of ...
Bitcoin is not a finished product. We may be on a detour to address spam, and part of the crisis did originate with (mishandling of) the Segwit and Taproot upgrades - but to improve the world, we still need more functionality. Stopping all improvements forever ("ossifying") is fatal.
Part of addressing the issues with Core needs to be ensuring we don't repeat the same mistakes: if an upgrade introduces unforeseen vulnerabilities, those need to get addressed in a timely manner. All protocol changes require support from the entire community, so we developers are going to have to earn that reputation back.
There are fairly simple, low-risk softforks like CTV, or even a consensus cleanup (though I have reservations about BIP 54), that should not introduce vulnerabilities, and could be a starting point to regain confidence after Core is out of the picture.
The next step up is probably native zero-knowledge support, BitVM optimisations, and similar. This is when it *might* make sense to start considering Bitcoin L1 "complete", and capable of handling further improvements and even scaling on true trustless sidechains. We have a long road to get there still, and every step will take consensus - possibly quick mitigation of unforeseen outcomes - but we shouldn't lose sight of the end goal: a decentralised currency that nobody can undermine, and hopefully one day onboard the entire global economy.
It's possible to accomplish, but we will have to work for it.
Published at
2025-09-08 06:49:03 GMTEvent JSON
{
"id": "bee1909fc3279fedec3185d9f0c0567f88aa17e85ce49c6fa9d408e61bd54e22",
"pubkey": "fdd5e8f6ae0db817be0b71da20498c1806968d8a6459559c249f322fa73464a7",
"created_at": 1757314143,
"kind": 1,
"tags": [
[
"alt",
"A short note: Bitcoin is not a finished product. We may be on a ..."
]
],
"content": "Bitcoin is not a finished product. We may be on a detour to address spam, and part of the crisis did originate with (mishandling of) the Segwit and Taproot upgrades - but to improve the world, we still need more functionality. Stopping all improvements forever (\"ossifying\") is fatal.\n\nPart of addressing the issues with Core needs to be ensuring we don't repeat the same mistakes: if an upgrade introduces unforeseen vulnerabilities, those need to get addressed in a timely manner. All protocol changes require support from the entire community, so we developers are going to have to earn that reputation back.\n\nThere are fairly simple, low-risk softforks like CTV, or even a consensus cleanup (though I have reservations about BIP 54), that should not introduce vulnerabilities, and could be a starting point to regain confidence after Core is out of the picture.\n\nThe next step up is probably native zero-knowledge support, BitVM optimisations, and similar. This is when it *might* make sense to start considering Bitcoin L1 \"complete\", and capable of handling further improvements and even scaling on true trustless sidechains. We have a long road to get there still, and every step will take consensus - possibly quick mitigation of unforeseen outcomes - but we shouldn't lose sight of the end goal: a decentralised currency that nobody can undermine, and hopefully one day onboard the entire global economy.\n\nIt's possible to accomplish, but we will have to work for it.",
"sig": "412138e80c094cc9c79836e7194eb03dc8a6c6a9895443c8f57b0a71938b27937ce38b483721b78c4de569642473613a5de7564ef64860e1f8084842c857b5f1"
}