|
395 | 395 | "j008-c-label": "Having a total balance over 32 ETH",
|
396 | 396 | "j008-c-explanation": "Your total balance must have rewards above 32 ETH for any partial withdrawals to trigger.",
|
397 | 397 | "j008-d-label": "Submitting requested withdrawal amount with gas payment",
|
398 |
| - "j008-d-explanation": "Once the other criteria are met, reward payments are automatic. Recipients do not need to submit a transaction or pay gas. Amount withdrawn is equal to validator's balance in excess of 32. Custom amounts cannot be requested." |
| 398 | + "j008-d-explanation": "Once the other criteria are met, reward payments are automatic. Recipients do not need to submit a transaction or pay gas. Amount withdrawn is equal to validator's balance in excess of 32. Custom amounts cannot be requested.", |
| 399 | + "k001-prompt": "Which of the following is Ethereum using to scale?", |
| 400 | + "k001-a-label": "Layer 2 rollups", |
| 401 | + "k001-a-explanation": "These help Ethereum scale by bundling transactions, executing them, and then posting the results to Ethereum for validation and securing. Examples or rollups include Arbitrum or Optimism. This is not the only way Ethereum is scaling.", |
| 402 | + "k001-b-label": "Proto-Danksharding", |
| 403 | + "k001-b-explanation": "This provides a temporary and inexpensive storage option for saving rollup data to Mainnet, which currently is responsible for approximately 90% of the cost a user encounters on a rollup. This is not the only way Ethereum is scaling.", |
| 404 | + "k001-c-label": "Danksharding", |
| 405 | + "k001-c-explanation": "This removes the need for every validator and node on the network from being required to store 100% of the data for all rollups, reducing hardware requirements for node operators. This is not the only way Ethereum is scaling.", |
| 406 | + "k001-d-label": "All of the above", |
| 407 | + "k001-d-explanation": "Layer 2 rollups bundle transactions, Proto-Danksharding creates cheap temporary storage for this data, and Danksharding shares the storage burden across all validators—all helping Ethereum scale.", |
| 408 | + "k002-prompt": "After bundling transactions and executing them, what do layer 2 rollups do next?", |
| 409 | + "k002-a-label": "Store the data on a private server", |
| 410 | + "k002-a-explanation": "Results are posted to Mainnet for transparency and public availability, and are not reliant on private servers.", |
| 411 | + "k002-b-label": "Sends the proof to the user for storage", |
| 412 | + "k002-b-explanation": "Users are not expected to hold onto the results of their transaction. This information is posted to Mainnet.", |
| 413 | + "k002-c-label": "Submit the results to Ethereum", |
| 414 | + "k002-c-explanation": "Layer 2 rollups post the results of their transaction execution to Mainnet, securing it in Ethereum's history", |
| 415 | + "k002-d-label": "Delete the result to reduce costs", |
| 416 | + "k002-d-explanation": "Layer 2 rollups post the results of their transaction execution to Mainnet. The cost savings achieved with this approach is by bundling and compressing transaction data, and ultimately storing it in cheap storage that expires once made available to those who need it.", |
| 417 | + "k003-prompt": "How does Proto-Danksharding reduce rollup transaction costs on rollups?", |
| 418 | + "k003-a-label": "Directly increasing the block size", |
| 419 | + "k003-a-explanation": "Proto-Danksharding does not directly increase the gas limit, but does make the storage of rollup data less expensive by making temporary storage available", |
| 420 | + "k003-b-label": "Splitting up which validators are required to store the data", |
| 421 | + "k003-b-explanation": "Although full Danksharding is expected to reduce the need for all validators to store all of the data, this is preceded by Proto-Danksharding which forms a less-expensive, temporary storage option for the data produced by rollups.", |
| 422 | + "k003-c-label": "Significantly increasing hardware requirements for node operators", |
| 423 | + "k003-c-explanation": "This is generally not considered an acceptable option for scaling Ethereum. Great efforts are taken to minimize hardware requirements for operating a node to keep it as accessible as possible.", |
| 424 | + "k003-d-label": "Storing its data in cheaper, temporary 'blob' storage", |
| 425 | + "k003-d-explanation": "Proto-Danksharding introduces a temporary data storage option for rollups to allow them to more cheaply post its results to Mainnet", |
| 426 | + "k004-prompt": "What is a critical next step for rollups to scale Ethereum?", |
| 427 | + "k004-a-label": "Incentivize entities with powerful computers to handle all of the sequencing", |
| 428 | + "k004-a-explanation": "One of the problems with current rollups is the centralized nature of those running the sequencers (those who decide the inclusion and ordering of transactions within a rollup). The goal is to allow anyone to participate, and not rely on a single group or entity in any way.", |
| 429 | + "k004-b-label": "Distribute responsibility for running sequencers and provers across more people", |
| 430 | + "k004-b-explanation": "Control over a rollup typically starts off centralized, which helps get things started, but leaves the network prone to censorship. Decentralizing the process of including transactions so anyone can participate is essential to prevent the possibility of network compromise.", |
| 431 | + "k004-c-label": "Make all rollups conform to the same method of security", |
| 432 | + "k004-c-explanation": "Ethereum benefits from having a wide range of approaches to security within its rollup ecosystem as a form of resiliency.", |
| 433 | + "k004-d-label": "Data oracles to confirm storage of transaction data on private servers", |
| 434 | + "k004-d-explanation": "Rollup data is stored on Ethereum, and does not rely on private servers or databases." |
399 | 435 | }
|
0 commit comments