Sustainability of those building dev tooling in crypto is and has always been a pretty big issue. Here is how we are solving it 👇 Traditionally the options are: 1. Big company ends up building their own tooling and opens it up for everyone (e.g. Golang by Google). This is generally quite good until the company decides it doesn't care about the space anymore. Too brittle for Ethereum. 2. Dev tooling is tied to a broader product (intel's C++ compiler that was heavily integrated into intel servers). This is a walled garden. Very good for intel users, doesn't help anyone else. 3. Dev tooling is sold commercially (SaaS). Given crypto is still nascent, expecting new teams to pay up is pretty bad. Also SaaS is dead with AI. 4. You don't get paid. You just do it because you love it. This is fine, now with LLMs, especially for small SDKs. But it doesn't work for large scale projects that require teams for constant upkeep. E.g. compilers, language, L2Beat etc. So wat do? And NO the answer isn't EF pays for these devs continuously. The @ethereum Foundation aims to withstand the 'walk away' test i.e. not have teams dependant on itself, especially for grants. Hence @nachortti has been working on 'Project Odin': work with each of large-scale, complex, heavily used and open-source project on Ethereum and getting them to sustainability. Shout-out to @vyperlang who will be doing formal verfication work to sustain the project! Auditing, building POCs or stand-alone products for enterprise, partnerships are relatively easy wins for this archetype of builders since they are generally experts and brilliant engineers in what they do. Next time: before asking for a grant, think how can Project Odin help you. Think alternate sources of generating revenue.