1 year ago i was in the process of writing my first smart contract
2day i am a coauthor(!!) of seaport 1.2
very lucky & grateful to have the opportunity to work with the 🐐s 🫡
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? ⤵️
honored to contribute to punks lore by bringing metadata for the new wrapper fully onchain 🙏
the punks metadata was put onchain in 2021, but it wasn’t actually associated with the og punks or wrapper contract…
until now 😎
shout out to my fellow onchain maxis 🫡
6/ Ͼ721 is immutable, permissionless, efficient, and leverages the
@larvalabs
PunksData contract from 2021 for fully onchain metadata.
Huge shout out to
@optimizoor
for a wildly optimized 721 base, and
@emo_eth
for a metadata contract to parse PunksData into a valid tokenURI.
bittersweet personal news: today was my last at
@opensea
🫡
v grateful to
@z0age
+ team for the opportunity to learn & grow as a dev, and to
@dfinzer
and
@NadavAHollander
for taking bets on protocols like seaport & seadrop
excited for whatever the future may bring 😎
long-term, i fully believe that non-EVM chains are destined to fail against EVM chains – for the simple reason that that would be very convenient for me personally
Today is my last day at
@manifoldxyz
. Nothing but love for the team and grateful for my time there ❤️
What's next?
@emo_eth
and I are teaming up again to work on something new in consumer crypto, more coming soon...
honestly love what
@ensvision
is doing, building on top of seaport + existing conduit token approvals...
this is why we built seaport, y'all - for the good of the whole ecosystem 🥲
> makes a decentralized, permissionless marketplace protocol anyone can use
> competing marketplace uses that protocol
> "HOW BLUR OUTSMARTED OPENSEA BY USING SEAPORT"
> mfw
solidity protip:
fixed-length array elements *do* take up consecutive storage slots in solidity
distributionsArray is a uint256[2]; here we conditionally load the second element by adding 1 to the storage slot if j == 1 (learned this branchless optimization from
@optimizoor
)
Excited to share that
@emo_eth
and I raised a preseed round led by
@variantfund
earlier this year.
With a solid vision for the ideal client for Farcaster & more, we're ready to start building new experiences on top of a mix of onchain & offchain data.
got a new personal computer, and as we all know, setting up your dev environment is always annoying
so i'm asking chatgpt to generate idempotent setup scripts for various things
this is fantastic
> makes a decentralized marketplace anyone can use, at a single address users can trust, with shared liquidity across all adopters
> builds a calldata attribution system for per-marketplace volume analytics
> nft project forks it anyway, breaks all that
> mfw
@worm_emoji
@AlexMasmej
yeah, seems to save 253 bytes with the same compiler settings
specifying more optimizer runs results in more gas-efficient code but larger code size, so anywhere you can shave off bytes from the contract code can lead to gas savings (19066 optimizer runs in the deployed version)
Random Foundry tip.
Don't remap your dependencies with a trailing "src/".
Rather, use "src" in the actual import paths written in your contracts.
This is to ensure compatibility with Hardhat projects.
"Well $DZHV was deployed via proxies, it's not special"
So that's actually the unique tech here, taking a look at the discourse in the telegram earlier, the dev laid out the tech.
More or less, created an evolving contract essentially. Pretty crazy stuff.
looks like the hardhat solidity vscode extension supports foundry projects now
it's 100x better than the "normal" one
and if you're working in the seaport repo - it's your only option, since one of the test contracts completely breaks the other ext lmao
🚀 𝗟𝗼𝗼𝗸𝘀𝗥𝗮𝗿𝗲 𝗩𝟮 𝗶𝘀 𝗻𝗼𝘄 𝗹𝗶𝘃𝗲! 🚀
Rolled out rn:
- Fee dropped to 0.5%
- Gas 50% cheaper than Blur
- One-signature bulk listing
- Buy 70+ NFTs at once
- Sellers get ETH instead of WETH
Full deets 👇
Today, we’re unveiling a new stablecoin, PayPal USD (PYUSD). It’s designed for payments and is backed by highly liquid and secure assets. Starting today and rolling out in the next few weeks, you’ll be able to buy, sell, hold and transfer PYUSD. Learn more
are we sure that the correct take re:arkham is
"arkham is evil"
and not something more like
"maybe we should stop pretending public blockchains are anonymous and work towards making privacy-preserving tech more widespread"
bb's first "MEV" LARP
seaport wasn't deployed on Base Goerli, so there was 112 gETH sitting at the address from (presumably misconfigured) bots/scripts
so i deployed seaport and claimed it 🤠
SLIMESHOP isn't the first collection to let you combine layers to make dynamic NFTs on-chain
but it might be the most gas-efficient.
Ethereum is expensive, but the contracts that power SLIMESHOP make composable NFT collections viable on Ethereum (imho)
Let's break down how 👇
had an excellent time learning and meeting some folks at the rust x evm day yesterday, def many cool folks i did not manage to meet as well
attendance was stacked, shout out
@gakonst
@paradigm
LARPed as a rust dev and hacked out a couple new forge cheat codes too 🤫
amateur scientists making dangerous and toxic alloys in their homes, in fruitless pursuits of a magical substance with seemingly impossible physical properties...
alchemy is SO BACK baby!!!
do contracts really call supportsInterface on each other? what does it solve? a bad behaving contract can just lie pretending it supports every interface and you would only notice if you check a magic return value. which tools have eip-165 integrated?
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)
mini-thread on erc7015 and proof-of-provenance:
provenance for nfts is actually kind of tricky, since a creator might not deploy their own contract, and owners can be set by anyone
many scams pretend they were created by big artists by declaring their wallets as the "owner"
why is on-chain creator fee enforcement hard?
lots of reasons, but counterfactual contracts especially
it's easy to block an exchange or wrapper – if you know its address. but what if that's impossible to know beforehand?
enter counterfactual contracts
i forked Solarray to add some unhinged helpers to do things like resize dynamic arrays (yes, i know vyper supports this natively)
will probably open a PR eventually, but for now, just saving my own sanity writing tests
i’d be fine with seaport losing out to other protocols if the future of tokens is non-composability and server-side signatures
i personally don’t see that as a fight worth winning
uhhh
did anyone else know that you can just re-declare a variable (which will duplicate it onto the stack) to avoid stacc-too-thicc errors?
or did i just "discover" some stacc2dank alpha
...
i just learned that you can scroll through DIFFERENT GITHUB COPILOT SUGGESTIONS by pressing option+] and [
and you can OPEN A WINDOW WITH ALL ALTERNATE CHANGES to review and accept the best one with control+enter
what the fuck
Seaport v1.4 has been deployed and is ready for production use!
0x00000000000001ad428e4906aE43D8F9852d0dD6
Version 1.4 addresses a few issues on Seaport v1.2 & v1.3, "developer preview" versions not recommended for production use
Let's go over v1.4 changes & lessons learned ⤵️
check out the latest Over Abstraction episode with
@emo_eth
from Seaport to hear about:
+seaport’s architecture
+how zones unlock new types of dynamics
+future of royalty enforcement
+harberger taxes and potential for new types of revenue
I had the great pleasure of designing and building these smart contracts with
@ralxzryan
and
@stephanminkj
We're committed to making this space both safer and more accessible, by providing secure tools and experiences for the whole ecosystem 😎
@0xQuit
@ANoNakamoto
@0xWave
@0xBender
token incorrectly specifies 18 decimals in metadata, but we should only be parsing that for ERC-1155 tokens, not ERC-721s
raised w team
was not at all nervous about AGI until someone said blockchains could become their "substrate"
big computer you can't turn off, that can pay people for running (+ perpetuating) code? self-replicating, self-evolving digital fungus
cool, cool
best start building the basilisk 🫡
a few weeks ago i did interviews, coding puzzles, all the silly bullshit, all to get a "junior engineer" offer from smg/consensys for half the pay and double the hours i quoted. they even cited the fact that i don't have degree
companies that demand degrees are not worth your