What if we don't *need* global consensus to solve the double spend problem?
▷ validators don't talk to each other directly, instead maintaining a local, totally ordered log
▷ transactions finalize in one round-trip (200ms), without being ordered
▷ ordering-sensitive applications can build custom sequencing gadgets, on top
In this log-based structure, consensus is deprioritized against finality. We move from 'blockchains' to 'blocklessness', moving the cycles onwards.
The @poddotnetwork team (led by @shresth3103 @abresas) has been exploring this design space and other 'golden geese' in crypto (like sparse clients), that often go understudied.
They are worth the follow if you're looking for builders with strong opinions and understanding of the crypto design space.
ZK es una solución complicada para el problema equivocado. Sí, ahora no necesitamos todos los nodos para ejecutar el bloque, solo verificar una prueba zk. Pero, ¿por qué los nodos tuvieron que ejecutar todas las transacciones para empezar? En términos de web2, ¿por qué mi televisor en Europa procesaría su pago de café en Brasil?