Here is from ChatGPT 4o. Love it so much
Why AO is Not Fully Decentralized, Trustless, and Lacks Finality
Centralization in Computation
In traditional decentralized blockchains, every node participates in the computation and validation process, ensuring that no single entity has control over the entire network. However, AO delegates computation to specialized Compute Units (CUs). While these CUs compete to offer their services, the reliance on a limited number of specialized units introduces potential centralization risks. If a significant portion of computation is handled by a few dominant CUs, the system could become vulnerable to central points of failure or influence.
Dependence on External Storage (Arweave)
AO relies on Arweave for storing the message log that forms the basis of its âholographic state.â While Arweave is a decentralized storage solution, AOâs dependence on an external system means that the integrity and availability of AOâs state are contingent on Arweaveâs reliability. This introduces a layer of dependency that contrasts with the self-contained nature of traditional blockchains, where all state data is maintained and validated within the network itself.
Limited Trustlessness in Computation
Traditional blockchains achieve trustlessness by ensuring that all nodes validate transactions and compute state changes independently. In AO, computation is outsourced to CUs, and although the results can be verified through deterministic execution and the immutable message log, the initial computation process is not inherently trustless. Users must trust that the chosen CU performs the computation correctly unless they verify the results themselves, which may not always be feasible.
Potential for Centralized Control in Scheduling
AOâs Scheduler Units (SUs) assign a unique, incremental number to each message, determining their order. The centralized assignment of slots introduces a potential risk of manipulation or bias in message ordering. If the SUs are controlled by a few entities, they could influence the sequence of message processing, affecting the fairness and neutrality of the system.
Verifiability Challenges
While AO provides mechanisms for verifiability through deterministic execution and the availability of the message log on Arweave, the process requires additional steps compared to traditional blockchains. Users or other nodes must actively replay the message log to verify computations, which adds complexity and potential barriers to trustless verification. This reliance on additional verification steps could deter users from fully trusting the system without conducting their own checks.
Lack of Finality
A crucial feature of many blockchain systems is the concept of finality, where once a transaction is confirmed, it is permanently added to the blockchain and cannot be altered or reversed. AO lacks this feature because its state is implied by the message log on Arweave and can be recalculated at any time by replaying the log. This means there is no absolute guarantee that a computed state is final and unchangeable, which undermines the confidence that users and applications can have in the immutability of the systemâs state.
Conclusion
While AO introduces innovative mechanisms for achieving consensus and scalability, it diverges from the core principles of decentralization, trustlessness, and finality found in traditional blockchains. The delegation of computation to specialized units, dependence on external storage, the need for active verification, and the absence of finality introduce elements that compromise its decentralized and trustless nature. These factors make AO a unique system with different design principles, but not a fully decentralized or trustless blockchain.