A place for talking about the Ethereum Virtual Machine on Farcaster.

- Keep all strings under 32 bytes
- Replace modifiers with internal functions
- Linked libraries 😈  

(cc @maks)

- Keep all strings under 32 bytes
- Replace modifiers with internal functions
- Linked libraries 😈  

(cc @maks)
https://warpcast.com/maks/0xb0fda8ff

I'm eth newbie..just learning
(working on @farcaster)

terminally.online

using storage variables instead of copying everything to memory.
🤌

Security researcher!
Secured over 100 projects in the last 4 years!

It’s something I was always finding peculiar, but not declaring all the variables in memory, e.g. You have a struct and a mapping, instead of copying that element in mem, you just access it. It’s more expensive on usage but less on storage.

This is because when you declare a storage variable for a struct, you’re just loading the storage pointer. You can then use that pointer to load the members of that struct individually.

Unless you end up loading all the members of the struct, you’ll save some SLOADs.

Doesn’t change the bytecode size, tho