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

Banteg’s right, linked libraries should be a last resort. In many cases it’s simpler to extract a helper contract: basically the same thing without the weirdness of linked libs.

external libraries are notoriously hard to debug in solidity since they don't follow the normal calling convention. language devs are unhappy with them too, so it's probably best to avoid them.

They're more like macros: they're inlined, so it's like copy-pasting the modifier code anywhere it's applied.

Building ponder.sh. EVM, TypeScript, open-source enjoyer.

They're more like macros: they're inlined, so it's like copy-pasting the modifier code anywhere it's applied.

https://github.com/ethereum/solidity/issues/6584

What's the explanation for modifiers vs interval functions? I (naively) figured modifiers were syntactic sugar for functions.

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

using storage variables instead of copying everything to memory.
🤌

- Dedupe calls and other ABI encoding into helper functions (encoding+checks get bloaty)
- Dedupe any other logic into functions
- Be smart with calldata/memory/storage keywords, avoid unneeded copies
- Avoid structs, encode data manually, especially if structs fit in one word

What was your journey for mastering Solidity?

this should be obvious but based on what I see in a bunch of contracts it’s not:

- Use custom errors instead of require error strings

There's a 99% chance your ERC 721 doesn't need the enumerable extension