jakiro
Author: VALERIY ZAAMARAIEV, 1KX Network CTO; Translation: 0xxz@作 作 作 作 作 作 作
1. The theme of this article is: why AO may be a new true “Internet computer”.I will try to build something with it and then form opinions, but so far just summarize what I have learned in EthDenver so far.
2. It is more like a specification rather than implementation.Of course, the code has been written, but this is not the point.Specifications are the key. Once anyone writes its own CU, SU, and MU, it allows anyone to conduct interoperability.In contrast, few people can manage hundreds of thousands of lines.
3. The execution environment can be any environment.No special assumptions.There are currently WASM, but no one is prohibited from EVM.In fact, I dare to bet that someone is studying it now.
4. Erlang model.The easiest way to explain AO to distributed system personnel is: it is just the ERLANG interpreter status on Arweave.Add computing resources to improve the performance of this interpreter.Everything is asynchronous, you don’t need a huge global computer to advance every step.
5. Heterogeneous computing based on economic incentives: Messages in ACTOR models need to be processed, and the needs of the processing here will just attract the required resources.Compare this with the specifications of high -end machines that need to be started.
6. Since the use of ARWEAVE as storage, the team can rely on solutions that have been tested after many years of operation.This makes the overall risk of AO very low.If the current idea fails for some reason, then the feasible model will be easy.
7. No license is required.Many agreements and public chains start from centralization. Thanks again for Arweave. AO was decentralized from the beginning.If we find a centralized component, it is because no one writes alternatives.The key is that it does not need to be centralized at all.
