Trendaavat aiheet
#
Bonk Eco continues to show strength amid $USELESS rally
#
Pump.fun to raise $1B token sale, traders speculating on airdrop
#
Boop.Fun leading the way with a new launchpad on Solana.
I think the main reason why most blockchains have not adopted async execution is simple: when users see that their tx is confirmed, they expect the result to be available as their further actions depend on it.
While with deferred execution it's possible to locally simulate the result for non-contentious state (such as transfers/approvals), these are also the kinds of txs that don't add much overhead to a synchronous execution as well, which makes async execution a much less attractive alternative considering the additional development costs and tx processing conditionality on the end client (checking if a tx may touch a contentious state which is non-trivial, and choosing to wait for the result from the chain or locally simulate it).
11.8. klo 03.59
Doing some writing today about asynchronous execution (aka deferred execution).
This is one of the "big ideas" of Monad that will seem obvious in hindsight: that as soon as transaction order is determined, state is determined.
You might not know this, but in most blockchains including Ethereum and Solana, the nodes evaluating a list of transactions (i.e. a block) must also agree upon the result of that list of transactions (i.e. the state root after those transactions) as part of the voting process.
That requires them to execute those transactions prior to responding with a vote, which obviously greatly shrinks the amount of work they can be expected to do. This expectation is too strict, and is one of the big reasons why blockchain throughput is so limited.
1,42K
Johtavat
Rankkaus
Suosikit