[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]  Yonatan Sompolinsky [@hashdag](/creator/twitter/hashdag) on x 32.3K followers Created: 2025-07-22 18:04:49 UTC "Social consensus" is not a protocol design choice, it's an observation or rather a realization that past a certain stress level (here, a reorg depth) formal consensus is more likely to break than hold, at point which we are at the mercy of the shaky, unreliable social consensus (if it were reliable we wouldn't need consensus or pow. Agreed). Bitcoin/longest chain doesn't and doesn't necessarily pretend to solve this, neither today nor when mining is adopted by multiple country-level actors. I'm curious if you have suggestions for how to upgrade Bitcoin's security from "thermodynamic assurances" to something more robust. The only path I can currently imagine is a responsive-protocol-secured (e.g., DK) hashrate-based dynamic finality window, with corresponding throughput caps, which implicitly defines or aligns the social consensus around hashrate that existed before the attack. XXXXX engagements  [Post Link](https://x.com/hashdag/status/1947719494513922511)
[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]
Yonatan Sompolinsky @hashdag on x 32.3K followers
Created: 2025-07-22 18:04:49 UTC
"Social consensus" is not a protocol design choice, it's an observation or rather a realization that past a certain stress level (here, a reorg depth) formal consensus is more likely to break than hold, at point which we are at the mercy of the shaky, unreliable social consensus (if it were reliable we wouldn't need consensus or pow. Agreed). Bitcoin/longest chain doesn't and doesn't necessarily pretend to solve this, neither today nor when mining is adopted by multiple country-level actors.
I'm curious if you have suggestions for how to upgrade Bitcoin's security from "thermodynamic assurances" to something more robust.
The only path I can currently imagine is a responsive-protocol-secured (e.g., DK) hashrate-based dynamic finality window, with corresponding throughput caps, which implicitly defines or aligns the social consensus around hashrate that existed before the attack.
XXXXX engagements
