Content pfp
Content
@
0 reply
0 recast
2 reactions

@
0 reply
0 recast
0 reaction

Spencer Graham 🧢 pfp
Spencer Graham 🧢
@spengrah.eth
very cool! The big trade-off I see of the endpoint => dispatcher (storage) => implementation pattern is significant increase in complexity for users and/or front ends, since they now have to know which endpoint to call for each of the public functions in the protocol. Is that accurate?
1 reply
0 recast
1 reaction

zerosnacks.eth pfp
zerosnacks.eth
@zerosnacks
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