Content pfp
Content
@
0 reply
0 recast
0 reaction

Joaquim Verges pfp
Joaquim Verges
@joaquim
We published an EIP for dynamic contracts! The tooling (CLI, SDKs, dashboard) we're building around this EIP is game changing, can't wait to get it all out there! https://ethereum-magicians.org/t/erc-7504-dynamic-contracts/15551
3 replies
3 recasts
15 reactions

typeof.eth 🔵 pfp
typeof.eth 🔵
@typeof.eth
This is dope, seems like an improvement on the diamond pattern. Turns out it’s way easier to understand an upgradable proxy pattern when you don’t have to parse through a bunch of jeweler analogies. nit: I feel like there’s a more descriptive name than dynamic contracts.
1 reply
0 recast
2 reactions

Joaquim Verges pfp
Joaquim Verges
@joaquim
Yes! The weird analogy based jargon of the diamond pattern is what pushed us to do our own, much more lean and simplified version. Naming is hard though, any suggestions for the main concept of one-to-many proxy contract systems? Here's the repo btw: https://github.com/thirdweb-dev/dynamic-contracts
3 replies
0 recast
4 reactions

typeof.eth 🔵 pfp
typeof.eth 🔵
@typeof.eth
Might start using this right now, btw. I'm currently doing some contract size limit shenanigans on a side project that this pattern would help clean up.
1 reply
0 recast
1 reaction

shazow pfp
shazow
@shazow.eth
Great work! Some name ideas, roughly in my order of preference: MultiProxy, Multiplexer, Dispatcher (or DispatchProxy)
1 reply
0 recast
2 reactions

typeof.eth 🔵 pfp
typeof.eth 🔵
@typeof.eth
Modular Proxy Pattern, Faceted Proxy Pattern, Mosaic Contract Pattern, Multiplexed (or Mux) Proxy Pattern h/t @shazow.eth, Segmented Relay Pattern. FWIW, the reason dynamic contracts doesn't feel right to me is that "dynamic contarcts" is super vague, and that (I'd argue) this isn't really dynamic.
1 reply
0 recast
1 reaction