_:n614aa5bd32a0492cbb7a9864757a4845xb0
<http://schema.org/articleBody>
" [ad_1]\r\n<br><!-- SC_OFF --><div class=\"md\"><p>I'm studying the executable beacon chain proposal right here, and I've a few questions and I'd admire if somebody extra versed within the Ethereum know-how stack may help reply. </p> <p>I reproduce the snippets I'm confused about, and the questions I've beneath.</p> <p>Within the proposal you could have the next:</p> <blockquote> <p>Eth2-client sends an executable information to the eth1-engine. Eth1-engine updates it interior state by processing the info and returns true if consensus checks have been handed and false in any other case. Superior use instances, like prompt deposit processing, might require full transaction receipts within the end result as effectively</p> </blockquote> <p>Questions: 1. How can Eth2-client ship executable information to the eth1-engine. Is it not the case that the Eth2-client solely have data about Beacon blocks? How are these executable by eth1-engine? 2. I believed the concept is to maneuver consensus performance to the beacon-chain? How come it's potential for eth1-engine to nonetheless have the ability to verify if consensus guidelines are handed?</p> <p>Additionally, you could have:</p> <blockquote> <p>Eth2-client sends earlier block hash and eth1 state root, coinbase, timestamp and all different data (aside of transaction checklist) that's required to create executable information. Eth1-engine returns an occasion of ExcecutableData.</p> </blockquote> <ol> <li>How can an Eth2-client ship issues like eth1 state root, coinbase and so on to the Eth1-engine? These items of data look very eth1 centric, how does the Eth2-client come to have this items of data?</li> </ol> <p>Then later we have now:</p> <blockquote> <p>We modify process_block perform within the following approach:</p> </blockquote> <pre><code>def process_block(state: BeaconState, block: BeaconBlock) -&gt; None: process_block_header(state, block) process_randao(state, block.physique) # process_eth1_data(state, block.physique) was right here process_operations(state, block.physique) process_executable_data(state, block.physique) </code></pre> <p>Questions:</p> <ol> <li>What precisely is the tip results of the Eth2-client processing executable information? Why ought to the Eth2-client course of executable information? And what issues would processing this executable information result in?</li> </ol> </div><!-- SC_ON --> &#032; submitted by &#032;  /u/finlaydotweber  <br /> <span></span> &#032; <span>[comments]</span>\r\n<br>[ad_2]\r\n<br><a href=\"https://www.reddit.com/r/ethereum/comments/t8uqst/questions_about_the_executable_beacon_chain/\">Source link </a>"
<https://bvcryptonews.com/questions-concerning-the-executable-beacon-chain-proposal/>