Ethereum

on hiatus • experiments: megapot.io // virtuoso.club • previously swe @coinbase, amazon

Should smart contracts be modifiable by devs?

1. Yes
2. No
3. Other

Question by @0xasdf
https://i.imgur.com/l7D5kkQ.jpeg

The pulse of the Farcaster community | Follow for new surveys 📋 | By @ba and @cojo.eth | Visit weponder.io for results. 

2.  I wish more projects would go the Uniswap route of just deploying solid contracts every once in a while with a reasonable migration path between them. Design contracts so they don't need to be upgraded. Just pause and redeploy in the event of an emergency. Malicious upgrade risk is rarely worth the benefits IMO.

Project needs are constantly evolving. I think Uniswap is still early and doesnt it get confusing between versions? New version every year makes liquidity scattered. Uniswap hooks might be a way around it but we don’t know. Immutability is everything. But we need a good design

Uniswap has built their product in a way so it accounts for that broken UX. It could have easily been worse and by no means is it ideal. This is the same kind of reasoning that wallet UX is good when it’s not.

I’m all for immutability. It’s the reason why we are here. But Uniswap would have been with no routing.

Not confusing at all. The frontend always automatically routes swaps using the best routes, which are most likely on v3, sometimes v2, rarely v1. Impermanent Loss is worse on older exchanges, but they have more Lindy (pros and cons), so LPs can decide when to migrate at their own pace.

Maximized autonomy is good 👍