vectorized.eth (@optimizoor) 's Twitter Profile
vectorized.eth

@optimizoor

✯ solady.org ⟠ @soundxyz_ ⊛ @asterixlabs

ID: 1496567813737091075

linkhttp://kyaa.xyz calendar_today23-02-2022 19:29:29

18,18K Tweet

33,33K Followers

10,10K Following

vectorized.eth (@optimizoor) 's Twitter Profile Photo

Told my mum about the security budget issue of Bitcoin. She said, the point is to flip it, dump it on someone else and 走路, just like how everyone does it in the property market, who cares what happens 10 years later.

vectorized.eth (@optimizoor) 's Twitter Profile Photo

Why should we even do it? OP stack uses Solady’s FastLZ to calculate calldata compression gas savings to pass back to users. It was initially intended mainly for NFT metadata compression. It’s “over-engineered toys” until it’s not.

0xprincess (@0x9212ce55) 's Twitter Profile Photo

Hawa Shiro ˖◛⁺⑅♡ The problem in "fan tokens" is ownership: there's no value in a creation of a token, all the value is the content and it is created and controlled by the artist. Marketing teams for a token might get less than 2% of the supply if the token would've been created by the artist

jchoy.eth (@0xjchoy) 's Twitter Profile Photo

1/ Saw a tweet(x.com/solady777/stat…) about SSTORE gas costs and got curious. So I looked into all the EIPs that tried to reduce Ethereum’s storage cost. Here’s a quick summary of what I found: 🧵

Shiro ˖◛⁺⑅♡ (@shiro57102) 's Twitter Profile Photo

Day eight of drawing eth chan until 10k Ethereum (ETH) last 24h Price: $2,563.32 (+3.28%) Volume: $15.11B Trend: eth chan is happy because Vitalik sama noticed her Today some very ugly people launched a low quality memecoin out of eth chan character, again I want to

Day eight of drawing eth chan until 10k 

Ethereum (ETH) last 24h
Price: $2,563.32 (+3.28%)  
Volume: $15.11B  
Trend: eth chan is happy because Vitalik sama noticed her 

Today some very ugly people launched a low quality memecoin out of eth chan character, again I want to
vectorized.eth (@optimizoor) 's Twitter Profile Photo

Say you charge someone 3% of their swap fees. Then you say this swap fee is REV, and thus the user should be happy because this makes their remaining 97% worth more. That’s the magic of REV.

0xprincess (@0x9212ce55) 's Twitter Profile Photo

Many people liked this idea, so here it is: Eth Chan is now waiting for you at Ethereum(.)moe! (yes, that's a real website) I'll share more info in the thread below.

kaden.eth (@0xkaden) 's Twitter Profile Photo

🧵How memory works under the hood in the EVM and how this knowledge led me to recently discover a ✨critical vulnerability✨ Oh and if you're new to assembly, don't worry, it's simpler than you think Memory Layout Starting with the basics, Solidity reserves the following 4

🧵How memory works under the hood in the EVM and how this knowledge led me to recently discover a ✨critical vulnerability✨

Oh and if you're new to assembly, don't worry, it's simpler than you think

Memory Layout

Starting with the basics, Solidity reserves the following 4
kaden.eth (@0xkaden) 's Twitter Profile Photo

If solady has a million fans then I am one of them If solady has ten fans then I am one of them If solady has only one fan then that is me If solady has no fans then that means I am no longer on earth If the world is against solady then I am against the world

vectorized.eth (@optimizoor) 's Twitter Profile Photo

EVM is actually fking fast and scalable execution wise. They just refuse to acknowledge it, because I’m not writing 5000 word threads, podcasts, bribing KOLs. Who wrote the fastest Solidity log2, sqrt, cbrt, etc. ever? Me. So trust me bro. uint256 slow is skill issue.

Ben {chmark} Adams ⟠ (@ben_a_adams) 's Twitter Profile Photo

vectorized.eth 7.3 minute L1 trace on Nethermind; 4.4sec is running byte code (1%); of that 81.6% is loading data. Evm execution is mostly bored with only 0.184% (809ms) of the 7.3minutes elapsed running CPU intensive Evm byte code

<a href="/optimizoor/">vectorized.eth</a> 7.3 minute L1 trace on Nethermind; 4.4sec is running byte code (1%); of that 81.6% is loading data.

Evm execution is mostly bored with only 0.184% (809ms) of the 7.3minutes elapsed running CPU intensive Evm byte code