Timeline for Getter functions for loop security
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 14, 2019 at 19:37 | comment | added | goodvibration | @KevinWad: You too mate :) | |
| Oct 14, 2019 at 19:36 | comment | added | Kevin Wad | Ok thank yo, I will email you can delete the email now. Best regards | |
| Oct 14, 2019 at 18:48 | comment | added | Kevin Wad | Hi can give me your email again, I thought I would retrieve from here but the message has been deleted. Best regards | |
| Sep 16, 2019 at 14:10 | comment | added | goodvibration | @KevinWad: You two mate :) | |
| Sep 16, 2019 at 13:49 | comment | added | goodvibration | @KevinWad: I'm pretty sure that you won't be able to deploy a contract once the generated byte-code (compiled contract) exceeds a certain size, because the gas amount required for deploying it will be larger than the block gas-limit (which is normally around 80M I think). | |
| Sep 16, 2019 at 13:39 | comment | added | Kevin Wad | Thank you very much for this very clear answer ! Also I was wondering if there is a limit in the number of getter functions a smart contract can have. As a full stack dev it is very tempting to create a lot of getter function to facilitate futur front end developpements. But I suspect there should be a drawback if I create too much, right ? | |
| Sep 16, 2019 at 13:36 | vote | accept | Kevin Wad | ||
| Sep 16, 2019 at 10:37 | history | answered | goodvibration | CC BY-SA 4.0 |