Timeline for How growing contract storage increases the gas spending?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 16, 2019 at 3:47 | comment | added | RJardines | I just register in this site to vote up for your question. Can you provide any link from a trusted site (ethereum, solidity) that confirm your answer?. If this is true I will be very happy. Thanks in advance. @NickJohnson | |
| Apr 14, 2016 at 14:59 | vote | accept | Henrique Barcelos | ||
| Apr 14, 2016 at 14:39 | comment | added | Nick Johnson |
@HenriqueBarcelos It's loaded whenever you access it - such as with var blah := my_storage_map[foo]. More details of how this is implemented at the EVM and Solidity levels are probably out of scope for this question and for a comment. :)
|
|
| Apr 14, 2016 at 14:35 | comment | added | Henrique Barcelos | I see. In your answer you've said that only the entries my contract explicitly loads in code are loaded in memory. Could you give more details on how this happens? How is this data fetched from the storage? | |
| Apr 14, 2016 at 14:30 | comment | added | Nick Johnson | @HenriqueBarcelos That answer is correct, but it's talking about how much computation you can do in a single transaction. If you have a lot of stored data, but only want to access a fixed amount per transaction, your costs won't go up. | |
| Apr 14, 2016 at 14:28 | comment | added | Henrique Barcelos | Thank's for your answer. Are you saying that this answer doesn't make sense? | |
| Apr 14, 2016 at 14:20 | history | answered | Nick Johnson | CC BY-SA 3.0 |