0age
1,473 posts
- There's a well-known phenomenon in software development: often, you'll "plateau" for a while before discovering a new trick, tool, or workflow that radically upgrades your capabilities Recently discovered one such trick & want to share with my fellow smart contract optimizors 👇
- Big 48 hours for Seaport — after a brief Solidity / Vyper holy war, we're now underway building a Vyper implementation with some of the brightest minds in the ecosystem. Will be fascinating to compare the two holistically once it's complete. Gotta say, I love build-a-bear
- chain abstraction is all the rage right now value transfer across chains must become totally seamless this is the vision for cross-chain UniswapX been building out one of the primitives to help get there — a new protocol for reusable resource locks: The Compact 🤝 let's 🧵
- I generally stay “in character” and commit to the pseudonymous crypto dev bit but recent events are too painful not to share our home and entire community has been absolutely obliterated by the Palisades wildfires overwhelmingly grateful for everyone’s safety in evacuating in
- Today, we're open-sourcing an early proof-of-concept implementation of Seaport Gossip, a peer-to-peer network for discovering and broadcasting Seaport listings What is Seaport Gossip, why is it important, and how can you get involved in building it alongside us? Let's dig in:
- Leaking some alpha on how to easily mine create2 salts to deploy contracts to efficient addresses. I've been using my trusty eGPU for years to great effect, but it's actually very fast and inexpensive to use the cloud (h/t @arr00 for the demonstration). Here's how to do it 👇
- The Seaport version 1.2 contract is now deployed to many EVM chains! 0x00000000000006c7676171937C444f6BDe3D6282 The current Seaport contract (v1.1) is still usable & will be as long as whatever chain it's on keeps chugging; v1.2 is a new contract So, what's v1.2 all about? ⤵️
- Introducing ret↩rn.eth 0x00000000000061aD8EE190710508A818aE5325C3 A generative audiovisual work where all metadata is stored & rendered onchain — i.e. a Music NFT™ An ERC721A contract, minting as an Ξ0.05 open edition for 72 hours Here’s the story & tech behind it ↵
- Overwhelmed by the response to the Seaport protocol — want to take a moment to thank my coauthors, @d1ll0nk + @transmissions11, for their truly exemplary contributions, and to @emo_eth, @_LeFevre_, @stephanminkj, @Slokh, and many others at @opensea for getting us to this moment.
- I've been "wearing" a green rectangle for half a decade, and by now it has become a core component of my pseudonymous identity With the help of StableDiffusion, I've created a new NFT collection to better express my personal aesthetics with 64 variations on the theme: ⬛🟩⬛.eth
- Sharing the winning 0xMonaco car from team @opensea — no crazy low-level tricks or pricing techniques, just high-level strategies & tactics that break up the race into phases: sit back early on, maintain forward momentum, go full blitzkrieg at the end
- Ever find yourself curious what the current memory layout looks like on a contract, but don't have ready access to more advanced tools? You can just set `bytes` as the return value to the function in question, then drop a call to this little function at your preferred breakpoint
- Here's an easy way to distinguish intermediate Solidity devs from advanced devs: How well do you understand default ABI encoding? If you can describe how to encode an array of structs that themselves contain arrays of structs, you're advanced (GPT-4? Intermediate Solidity dev)
