The identity of Ethereum validators isn’t public either. For all I know a state could already have the majority of votes/validators, distributed in sock puppets which could be coordinated to make an attack at any given time. And that attack could be anything from rejecting certain transactions to actually splitting the network in two and then the “community” tries to force their opinion on what is ethereum or what is ethereum classic 2. If you had done revocations or delegations in the meantime, good luck hoping the community would pick the chain with your operations in. Compare that with a chain which always has a confirmed history but maybe under certain conditions could become read-only for a while. Sure it would suck but there would be no ambiguity to be solved subjectively, which sounds like a better property for an identity system.
This might sound unlikely but so does converting around more than 45% of bitcoin’s hash rate into bad actors. Even if you think they have individually low interest in the sidechain, that is still a huge amount of hash you would need.
Another point is that the surface area of complexity of a PoS system is bigger than PoW, and Ethereum is already tainted by consensus bugs and accidental forks.
As for the peg outs, there are working to phase out the federation model and make it so the chain does the peg outs, just like it handles the peg ins without touching a federation already. They are blocked on the bitcoin (bitvm2/opcodes) side of things, really.
Technical Debt
npub14w…u3rwx
2026-10-14 12:35:04 UTC
in reply to nevent1q…v0ar
Author Public Key
npub14w4qnk43lsllls2qnldj3vfcxtx5qvtsf3xlvxv9yha8afrxhmfqju3rwxPublished at
2026-10-14 12:35:04 UTCEvent JSON
{
"id": "1e325feede14e2ef3e54ed971d3657f676843297ce9c23d221c6043c245c1cb7",
"pubkey": "abaa09dab1fc3fffc1409fdb28b13832cd4031704c4df6198525fa7ea466bed2",
"created_at": 1791981304,
"kind": 1,
"tags": [
[
"e",
"f9d09a5cd4b0a5811dee6dd306295b71388cc684bd04514f43bf12f2262438dd",
"",
"root"
],
[
"e",
"a87f180a7d99f767b57c60d92034e36d2f94f01ed05a4b5e988b2cd491947878",
"",
"reply"
],
[
"p",
"d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23"
],
[
"p",
"abaa09dab1fc3fffc1409fdb28b13832cd4031704c4df6198525fa7ea466bed2"
],
[
"p",
"e09eb3c8af93b5d33aabfeea594ea73e2dabc3aaee5c645ffa35675d68572324"
],
[
"p",
"ee6ea13ab9fe5c4a68eaf9b1a34fe014a66b40117c50ee2a614f4cda959b6e74"
],
[
"client",
"Nostur",
"31990:9be0be0fc079548233231614e4e1efc9f28b0db398011efeecf05fe570e5dd33:1685868693432"
]
],
"content": "The identity of Ethereum validators isn’t public either. For all I know a state could already have the majority of votes/validators, distributed in sock puppets which could be coordinated to make an attack at any given time. And that attack could be anything from rejecting certain transactions to actually splitting the network in two and then the “community” tries to force their opinion on what is ethereum or what is ethereum classic 2. If you had done revocations or delegations in the meantime, good luck hoping the community would pick the chain with your operations in. Compare that with a chain which always has a confirmed history but maybe under certain conditions could become read-only for a while. Sure it would suck but there would be no ambiguity to be solved subjectively, which sounds like a better property for an identity system.\n\nThis might sound unlikely but so does converting around more than 45% of bitcoin’s hash rate into bad actors. Even if you think they have individually low interest in the sidechain, that is still a huge amount of hash you would need.\n\nAnother point is that the surface area of complexity of a PoS system is bigger than PoW, and Ethereum is already tainted by consensus bugs and accidental forks.\n\nAs for the peg outs, there are working to phase out the federation model and make it so the chain does the peg outs, just like it handles the peg ins without touching a federation already. They are blocked on the bitcoin (bitvm2/opcodes) side of things, really.",
"sig": "d2d19f766c4228c53bde7c76386a813912627799058b964aadc9812e0333f1e486cba733409d89df75c5aa5ba1a80e00c68f172c6c16477031eb3f3412cb0f8f"
}