tree 木's avatar
tree 木 tree@onion.social 7 months ago
Ethereum building true decentralized state machine for over 10 years, and even though we have immediate consistency and strict ordering, there are still plenty of exploits and room for improvement. Now imagine building something like this on an eventually consistent and unordered event log.... 🤦‍♂
Gzuuus's avatar Gzuuus
I was recently working with state machines over Nostr for coordination between parties. The result is a distributed, event-driven, consistent state management protocol that can be used to model any process. It is also auditable, making it interesting for scientific and supply chain applications. Additionally, it enables the deployment of *smart contract-like* functionalities without the blockchain buzz or shitcoinery. I would love to hear your thoughts. This project was originally inspired by a talk from @npub1nyxg...h9ph during the last @npub1s0ve...rmq5 5. It's also my first time using ngit 🔥 https://gitworkshop.dev/npub1gzuushllat7pet0ccv9yuhygvc8ldeyhrgxuwg744dn5khnpk3gs3ea5ds/relay.ngit.dev/nsm
View quoted note →

Replies (1)

Gzuuus's avatar
Gzuuus gzuuus@contextvm.org 7 months ago
Sure, *decentralized*, sure *immediate consistency*, sure **strict ordering**... Eth is POS, consistency is stochastic, not immediate. The chain has had multiple reorgs during its history... But you are right, the immense amount of money poured over it has attracted very naive devs. Not all, there are very respectable people working on it, but also loads of script kiddies. Anyways, what I'm proposing here is a PoC. The model presented in the spec allow for multiple validators. Eventual consistency can be mitigated through agreement on a relay or group of relays. Unordered event log? nostr events have timestamps, unique IDs, and we also have open timestamps. All of this can create a pretty ordered event log...
↑