Timeline for Ethereum block architecture
Current License: CC BY-SA 3.0
20 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 29, 2018 at 7:58 | comment | added | Saad Malik | Are new mined transactions included in the block as a 'reference' (e.g: only hash of previously broadcasted transaction in mempool) or is the transaction structure fully inlined in the block? If inlined/copied: there is some redundant data ineffeciency, right? once where transaction is broadcasted into mempool and then when copied to the block? If block transaction references mempool transaction: what happens if a node validating block has an unknown transaction? e.g: transaction is not in node mempool? | |
| Feb 7, 2018 at 16:06 | history | edited | medvedev1088 | CC BY-SA 3.0 |
Typo
|
| Nov 30, 2017 at 9:05 | vote | accept | zanzu | ||
| Apr 13, 2017 at 13:01 | history | edited | CommunityBot |
replaced http://ethereum.stackexchange.com/ with https://ethereum.stackexchange.com/
|
|
| S Nov 25, 2016 at 12:26 | history | suggested | Lee | CC BY-SA 3.0 |
updated broken link
|
| Nov 25, 2016 at 12:02 | review | Suggested edits | |||
| S Nov 25, 2016 at 12:26 | |||||
| Sep 23, 2016 at 16:52 | comment | added | Jus12 | You forgot the difficulty in bitcoin headers. | |
| Jun 11, 2016 at 15:19 | history | bounty ended | q9f | ||
| Jun 10, 2016 at 9:49 | comment | added | zanzu | These links correspond to contract state that has not changed in between blocks. Referencing the state from the previous blocks instead of replicating is more efficient from a block size perspective. | |
| Jun 10, 2016 at 8:31 | comment | added | Sebi | Why are the transactions from block N linked to those of block N+1? | |
| May 28, 2016 at 9:13 | vote | accept | zanzu | ||
| Nov 30, 2017 at 9:05 | |||||
| May 24, 2016 at 8:57 | history | edited | zanzu | CC BY-SA 3.0 |
deleted 178 characters in body
|
| Feb 14, 2016 at 18:34 | history | edited | zanzu | CC BY-SA 3.0 |
added 1 character in body
|
| Feb 1, 2016 at 15:15 | history | edited | zanzu | CC BY-SA 3.0 |
edited body
|
| Feb 1, 2016 at 14:19 | history | edited | zanzu | CC BY-SA 3.0 |
added 4 characters in body
|
| Feb 1, 2016 at 12:34 | comment | added | zanzu | Updated response after consulting the YP. Starting to get clearer now. Thanks! | |
| Feb 1, 2016 at 12:33 | history | edited | zanzu | CC BY-SA 3.0 |
Folding in @eth 's comments
|
| Jan 29, 2016 at 22:53 | comment | added | eth♦ | Uncles is a hash (of a list of uncles), Yellow Paper has: "The Keccak 256-bit hash of the ommers list portion of this block". Codehash is just a hash since contracts are immutable. The pointers point to "hash of whole block header" (the Keccak-256 hash of all the bytes in the block header). To have a full diagram, should really consult the Yellow Paper... | |
| Jan 29, 2016 at 19:47 | history | edited | zanzu | CC BY-SA 3.0 |
added 46 characters in body
|
| Jan 29, 2016 at 17:48 | history | answered | zanzu | CC BY-SA 3.0 |