0 reply
0 recast
0 reaction
2 replies
0 recast
3 reactions
1 reply
0 recast
2 reactions
1 reply
0 recast
3 reactions
So yeah about that, I used to be excited about /ao until I started building on it. The first important thing is how "state" works on AO, - smartweave was stateless and the whole idea of lazy evaluation paired well with our axiom of "Don't trust; Verify".
Now since AO is stateful, here is what it implies
• Apps just trust the results of state evaluation from AO's MUs, SUs and CUs;
this is just web2, nothing new here, already get that with cloudflare + AWS
• Or mabye apps want to evaluate state themselves from the logs to verify results returned from AO;
we've been there, it's smartweave, no need for MUs, SUs and CUs
• Or maybe apps don't want to evaluate state themselves, so they request more CUs to check each other's work and hold each other accountable;
well isn't that PoS. you would be either be building out your own PoS network of CUs, or trying to use existing public networks like Ethereum or Solana for compute on AO.
Still not infinitely scalable, plus it's a lot of work. 1 reply
0 recast
1 reaction
