3
Rough consensus: how Ethereum core upgrades work
12d • macbudkowski.eth •

@timdaub.eth this might be something for us to write about the mobile wallets
I appreciate the effort to outline the process for app developers to influence Ethereum’s core development through rough consensus. However, this guideline doesn’t address the immediate challenges we face. Many components of the ecosystem, such as wallets, indexing software, and Layer 2 solutions, have been privatized by the Ethereum Foundation. These tools now primarily cater to DeFi projects because that’s where the money is. As a result, our needs are sidelined. For instance, our applications require permanent data storage and efficient key delegation, but current solutions don’t support this. Mobile implementations are lacking, as DeFi primarily operates on desktops with infrequent transactions. Additionally, wallets are designed to safeguard private keys for transactions, whereas our apps would benefit from quick transactions and temporary keys. Engaging with core developers hasn’t alleviated these issues. They often propose optimizations that don’t align with our needs. I’ve previously commented on unnecessary optimizations in the Ethereum Magicians Forum. Core developers, often affiliated with the Ethereum Foundation, have more time to push their agendas, while I’m constrained by the demands of sustaining our startup. I can’t dedicate endless hours to advocating for our needs within Ethereum. So, while the guideline is well-intentioned, it doesn’t solve our problems.