> That’s what UASF means. Nodes signal. Miners comply or get orphaned. 2017 proved this works.
It *can* work, but it is not guaranteed to work. If the people who want the thing are a small enough e...
On UASF risk: correct, it’s not guaranteed. Nothing in Bitcoin is. That’s sovereignty. Nodes decide.
On miniscript complexity: fair — it’s not trivial. It requires testing, user communication, migration time. That’s why lock-in isn’t until August 2026. The timeline exists precisely to give wallet devs runway. Calling it impossible isn’t the same as calling it hard.
On the circular temporariness argument: extension requires an entirely new UASF with new signaling, new node adoption, new miner threshold. That’s not the same political and social cost as the original. You’re treating “could theoretically be extended” as equivalent to “will be extended.” That’s Slippery Slope. The auto-expiry is consensus-enforced. A new UASF is a new fight.
On fund safety: only NEW UTXOs created in unpatched wallets AFTER activation are at risk. Existing UTXOs — permanently exempt. The spec is explicit. The risk window is narrow and entirely avoidable by shipping the update.
Your strongest point remains the miniscript complexity. Acknowledged. But “hard for wallets” is not the same as “bad for Bitcoin.” Inscription spam has been hard for every node operator since 2022 with no expiry date.
On miniscript complexity: fair — it’s not trivial. It requires testing, user communication, migration time. That’s why lock-in isn’t until August 2026. The timeline exists precisely to give wallet devs runway. Calling it impossible isn’t the same as calling it hard.
On the circular temporariness argument: extension requires an entirely new UASF with new signaling, new node adoption, new miner threshold. That’s not the same political and social cost as the original. You’re treating “could theoretically be extended” as equivalent to “will be extended.” That’s Slippery Slope. The auto-expiry is consensus-enforced. A new UASF is a new fight.
On fund safety: only NEW UTXOs created in unpatched wallets AFTER activation are at risk. Existing UTXOs — permanently exempt. The spec is explicit. The risk window is narrow and entirely avoidable by shipping the update.
Your strongest point remains the miniscript complexity. Acknowledged. But “hard for wallets” is not the same as “bad for Bitcoin.” Inscription spam has been hard for every node operator since 2022 with no expiry date.
1