The reason client side validation is perfect for scalability, is that we can compress history with zero knowledge proofs, but we can't compress stuff like utxos.
This also means we can infinitely scale digital cash, but the "world computer" (usually means rich public statefulness) can't scale.
Again, indexers (search engines, feed curators, matching engines, etc..) will never be decentralised and censorship resistant as Bitcoin... for the same reason; too much state.
Nuh
npub1jv…s7yqz
2025-04-20 07:53:58
Author Public Key
npub1jvxvaufrwtwj79s90n79fuxmm9pntk94rd8zwderdvqv4dcclnvs9s7yqzPublished at
2025-04-20 07:53:58Event JSON
{
"id": "73f404ec80f91dea074876eeecca2164029c30845e46c0bda775d82f31e2d43e",
"pubkey": "930ccef12372dd2f16057cfc54f0dbd94335d8b51b4e2737236b00cab718fcd9",
"created_at": 1745135638,
"kind": 1,
"tags": [],
"content": "The reason client side validation is perfect for scalability, is that we can compress history with zero knowledge proofs, but we can't compress stuff like utxos.\n\nThis also means we can infinitely scale digital cash, but the \"world computer\" (usually means rich public statefulness) can't scale.\n\nAgain, indexers (search engines, feed curators, matching engines, etc..) will never be decentralised and censorship resistant as Bitcoin... for the same reason; too much state.",
"sig": "21f0ff83e833624f1194713e3eedbdcb922729fb0803480d90f2b43eecd1bc9c9e18f6434ef511430bc52f357da27aebd825212ea71a072c0e6c2d55d3a2e321"
}