them on the call. specifically how that impacts asynchronous / parallel processing. for example, multiple metagraphs are submitting snapshots into the network in parallel and they have different smart contract executions they need to occur in the global executor. do these get executed in parallel or are they forced into a sequential process to update the global state synchronously?
Missed it,.. what was reply to this...
focus will be on having a global executor that allows solidity code to be executed between metagraphs..essentially supporting EVM compatible smart contracts. eventually more executors can be introduced such as a WASM container executor as well.
So they will eventually run in parallel!?
well theoretically yes, but see my follow-up question in terms of parallelizing the actual execution of code itself.
On the gL0, the smart contract layer will necessarily be sequential. EVM executors will be supported on metagraphs also though which will allow them to run smart contract operations in parallel (compared to other metagraphs) and only submit the result to the gL0. There will be a balance that needs to be found with the fee mechanism to encourage all processing that doesn't need to run on the gL0 to run on a metagraph. We've also discussed "limited" EVM processing capabilities as an additional option on the gL0 that would potentially be cheaper. This would be akin to the validations that are run against ZK proofs on Ethereum L2s.
Обсуждают сегодня