Binance Square
LIVE
LIVE
SJ Crypto
--
6.9k views
See original
📍Can the blockchain impossible triangle be solved by DAGing transaction execution? 丨Aleph Zero one-page report #AZERO This project, which uses the DAG structure as an intermediate execution link, is the reason why I spent several days producing this content 🗝️This article also explores several issues outside the project: What is DAG? / What is the difference between parallelism and concurrency? /Feasibility of DAG-based execution layer DAG solution Currently, popular projects in the market, such as KAS, CFX, and the past Avalanche, have adopted this architecture, which is also called a natural expansion solution 🔻The content of this article is not completely the same as the content of the long picture report, please watch them together~ DAG architecture has the characteristics of high concurrency, and concurrency and parallelism are two different concepts. Because I also plan to produce EVM parallel content, it is necessary to make some extensions based on these two topics 🗝️Concurrency can be understood as a chef can cook several dishes at the same time, while parallelism can be understood as 2 or more chefs cooking several dishes at the same time As for how DAG is presented, I have also introduced it in the picture, so I will not repeat it. In short, the block generation of DAG is like sprinkling a handful of sand. At present, the relevant usage solutions in the industry are basically based on the variation of DAG Specifically how to change❓ In a word, it is: use the consensus mechanism developed independently to re-sort the blocks in the network to distinguish the primary and secondary. This is the case with KAS, CFX, and AZERO🔺 That is why I said in the picture that if the DAG structure is used alone, it cannot be said that this is a blockchain (after all, you are not a chain) And the biggest difference between AZERO and KAS, CFX and other solutions is that the application of DAG is only used for the execution link, and the external explicit architecture is still chain-like (I have reproduced some technical principles in the picture, I hope it can help you understand) This solution does have a certain feasibility. In the past, one of the three-chain structure of Avalanche adopted the DAG solution, but it was later abandoned. In fact, AZERO’s current implementation logic is a bit similar to Avalanche, which still adopted the DAG solution at the time, but AZERO has more single-chain genes 📍If you don’t understand the DAG of the execution layer, I will give another individual understanding to help you understand: Ethereum’s L2 Rollup solution is actually a solution that abstracts the execution layer It’s just that Ethereum adopts the method of submitting multiple transactions in a package. Imagine if an L2 adopts the DAG architecture to process transactions and also completes consensus on the Ethereum mainnet, then it is not impossible. AZERO is actually implemented and completed in this way. As for whether this target has investment value, based on my judgment of its historical trend, I think it has, and the reasons are also listed in the figure. But it’s enough to do medium-term swings. If you hold it for a long time, it’s easy to stay in the same place after a cycle, so you also need to pay more attention to the secondary price and run when it’s high. 📍This kind of secondary trend is much better than those that go down all the way. "Dancing with the banker, I’m not afraid of it having a banker, I’m afraid it’s a dead fish"

📍Can the blockchain impossible triangle be solved by DAGing transaction execution? 丨Aleph Zero one-page report #AZERO

This project, which uses the DAG structure as an intermediate execution link, is the reason why I spent several days producing this content

🗝️This article also explores several issues outside the project: What is DAG? / What is the difference between parallelism and concurrency? /Feasibility of DAG-based execution layer

DAG solution Currently, popular projects in the market, such as KAS, CFX, and the past Avalanche, have adopted this architecture, which is also called a natural expansion solution

🔻The content of this article is not completely the same as the content of the long picture report, please watch them together~

DAG architecture has the characteristics of high concurrency, and concurrency and parallelism are two different concepts. Because I also plan to produce EVM parallel content, it is necessary to make some extensions based on these two topics

🗝️Concurrency can be understood as a chef can cook several dishes at the same time, while parallelism can be understood as 2 or more chefs cooking several dishes at the same time

As for how DAG is presented, I have also introduced it in the picture, so I will not repeat it. In short, the block generation of DAG is like sprinkling a handful of sand. At present, the relevant usage solutions in the industry are basically based on the variation of DAG

Specifically how to change❓

In a word, it is: use the consensus mechanism developed independently to re-sort the blocks in the network to distinguish the primary and secondary. This is the case with KAS, CFX, and AZERO🔺

That is why I said in the picture that if the DAG structure is used alone, it cannot be said that this is a blockchain (after all, you are not a chain)

And the biggest difference between AZERO and KAS, CFX and other solutions is that the application of DAG is only used for the execution link, and the external explicit architecture is still chain-like

(I have reproduced some technical principles in the picture, I hope it can help you understand)

This solution does have a certain feasibility. In the past, one of the three-chain structure of Avalanche adopted the DAG solution, but it was later abandoned. In fact, AZERO’s current implementation logic is a bit similar to Avalanche, which still adopted the DAG solution at the time, but AZERO has more single-chain genes

📍If you don’t understand the DAG of the execution layer, I will give another individual understanding to help you understand: Ethereum’s L2 Rollup solution is actually a solution that abstracts the execution layer

It’s just that Ethereum adopts the method of submitting multiple transactions in a package. Imagine if an L2 adopts the DAG architecture to process transactions and also completes consensus on the Ethereum mainnet, then it is not impossible.

AZERO is actually implemented and completed in this way. As for whether this target has investment value, based on my judgment of its historical trend, I think it has, and the reasons are also listed in the figure.

But it’s enough to do medium-term swings. If you hold it for a long time, it’s easy to stay in the same place after a cycle, so you also need to pay more attention to the secondary price and run when it’s high.

📍This kind of secondary trend is much better than those that go down all the way.

"Dancing with the banker, I’m not afraid of it having a banker, I’m afraid it’s a dead fish"

Disclaimer: Includes thrid-party opinions. No financial advice. May include sponsored content. See T&Cs.
0
Replies 1
Explore the lastest crypto news
⚡️ Be a part of the latests discussions in crypto
💬 Interact with your favorite creators
👍 Enjoy content that interests you
Email / Phone number
Relevant Creator
LIVE
@SJCrypto

Explore More From Creator

--

Latest News

View More
Sitemap
Cookie Preferences
Platform T&Cs