Is there a larger @vyperlang codebase than @ripe_dao and @underscore_hq? Not sure there is. Code is all public. Contracts all live. For those wanting to see it in action, take a look. 👀 Ripe repo: Underscore repo:

We are happy to announce that we have received a $50,000 USDC grant from the @ensdomains Public Goods Working Group to support Vyper's development. Thank you to the @ENS_DAO community for making this possible!!!

Having nonreentrancy by default is a huge paradigm shift in Vyper. Look at this @reentrant modifier, it just screams danger and deserves attention. Then you see it's returning an immutable variable and realize there's no read-only reentrancy here. Safer defaults will save billions.

Using Mamushi in Moccasin to format my simple @vyperlang 🐍 And linting it with Natrix to keep everything in check. In my spare time, I'll try to add it in the framework! Kudos to @bennylada and @111_no_space Check repos👇

When Vyper ships, 🐍 snekmate ships too. You know, at Vyper, we build _with_ each other, not from ivory towers. We're in the trenches _together_. So what's the TLDR for this release: I target now the latest `0.4.3` Vyper version and have shipped mainly two new features: - Utility functions for contract deployments using `CREATE`, `CREATE2`, and `CREATE3`. - A `block_hash` function that extends access to historical block hashes _beyond_ the native 256-block limit (using EIP-2935). Please note that this release will make all 🐍 snekmate contracts now target the new Vyper default EVM version `prague`. I genuinely believe Vyper is still one of the most underappreciated tech in Ethereum. I really encourage people to try it; the snake 🐍 is friendly, promise😄!

already chads at curve (@111_no_space) are using raw_return to implement proxies in vyper!

vyper 0.4.3 was released this week! .. also 0.4.2 was released 3 weeks ago, but we decided to ship more features instead of tweeting about it 😅 highlights are: - raw_create allows low level access to creation opcodes - raw_return allows bypassing ABI encoding for proxy use cases - pragma nonreentrancy on enables nonreentrancy by default

token sale incoming but we are pivoting to standup

I went back to my Mox @vyperlang project, that served as a good practical case and pioneered several contribution ideas 🧐 Due to a lot of external factors, I'll just make the web page in my portfolio and move on. Although anvil-staging runs and its deployed on zksync-sepolia.

Vyper's selector table is highly optimized, possibly some of the most optimized code in any web3 compiler. It can save dozens to hundreds of gas before even entering any user code! Interested in how? You can thank "Sparse, Constant Time Jump Tables", pioneered by Vyper lead @big_tech_sux! Read more below 👇 (link in reply for algo reasons)