zerosnacks.eth

@zerosnacks

61 Following

82 Followers

zerosnacks.eth pfp

Ever wondered why it’s called WETH9? It uses Kelvin versioning which counts its version number down to 0 rather than up from it https://github.com/dapphub/ds-weth/commit/becce32937cec782bef35f69eb6bcf3e74688c41

0 reply

0 recast

1 reaction

zerosnacks.eth pfp

Make sure you read the Space Trilogy too!

0 reply

0 recast

1 reaction

zerosnacks.eth pfp

Running this kind of infrastructure is a constant battle against misuse to maintain uptime and avoid a degraded experience for regular users With Etherscan V2 users would only need to get a single API key for all the networks which does simplify things

0 reply

0 recast

0 reaction

zerosnacks.eth pfp

Reminder: if you recently updated Foundry and your build starts breaking with stack too deep set `optimizer = true` in your foundry.toml We’ve recently stopped enabling the optimizer by default and now require you to enable it explicitly https://github.com/foundry-rs/foundry/issues/2486

0 reply

1 recast

1 reaction

zerosnacks.eth pfp

Reminder: if you recently updated Foundry and your build starts breaking with stack too deep set `optimizer = true` in your foundry.toml We’ve recently stopped enabling the optimizer by default and now require you to enable it explicitly https://github.com/foundry-rs/foundry/issues/2486

0 reply

1 recast

1 reaction

zerosnacks.eth pfp

https://github.com/foundry-rs/foundry/issues/8345 👀

1 reply

0 recast

1 reaction

0xrusowsky pfp

@0xrusowsky.eth

first article on revm is finally here! in this opening post, i look into the core building blocks of the evm and their implementation. https://0xrusowsky.github.io/blog/articles/revm-pt1/

5 replies

5 recasts

32 reactions

zerosnacks.eth pfp

Under the hood it will use the eth_call RPC method which means you can just .call() https://github.com/gakonst/ethers-rs/blob/88095ba47eb6a3507f0db1767353b387b27a6e98/ethers-contract/src/call.rs#L280

0 reply

0 recast

1 reaction

zerosnacks.eth pfp

The benefits come down to not having the function selector clashing problem and being able to run multiple spec-compliant tokens side-by-side. In the Diamond Standard that looks like this: https://x.com/hiddentao/status/1688943233056063488

0 reply

0 recast

0 reaction

zerosnacks.eth pfp

The idea behind Reflex is that complexity of the implementation logic is abstracted away into a framework rather than part of the application. The implementation then, the hot path, is highly optimized.

1 reply

0 recast

0 reaction

zerosnacks.eth pfp

No problem, the increased complexity in the diagram comes from the inheritance tree but is not representative I think of the developer experience. The best way to get an idea of what the developer experience looks like is https://github.com/chromaxyz/reflex-template.

1 reply

0 recast

0 reaction

zerosnacks.eth pfp

I would say that is accurate and a trade-off to make. The main advantage is that it completely avoids the function selector clashing problem of the Diamond Proxy standard. What we’ve been doing at Chroma is to use a Lens module for all the view methods and group relevant external methods together.

0 reply

0 recast

1 reaction

zerosnacks.eth pfp

soundxyz uses deterministic clones https://github.com/soundxyz/sound-protocol/blob/main/contracts/core/SoundCreatorV1.sol

1 reply

0 recast

2 reactions

zerosnacks.eth pfp

For an in-depth breakdown of all the features and implementation details see https://github.com/chromaxyz/reflex/blob/development/docs/IMPLEMENTERS.md

0 reply

0 recast

0 reaction

zerosnacks.eth pfp

https://github.com/chromaxyz/reflex

1 reply

0 recast

0 reaction

zerosnacks.eth pfp

0 reply

0 recast

3 reactions