What are the 5-10 most important onchain use cases every single core dev should deeply understand?

(summer of) protocol {support | guild | fellowship} ☀️


not necessarily "use cases" but i feel like core devs could understand the app devs better by focusing on:

- indexing: big centralization point, to present the data well and fast, everyone is serving blockchain data from the centralized databases, the end user doesn't have any verification. Problem is much deeper than "using infra rpc is bad, we need light clients" — it's just impossible to build a good ux on top of a light client as well

- embedded wallets: no consumer app will work well if the user needs to download another app (a wallet) to use the consumer app. wallets need to be abstracted / embedded. it also breaks a lot of assumptions about decentralization, i feel like all core devs assume everyone in the world will have a perfectly set up metamask at all times

of course! this is one of the good examples — works in theory but then in reality it's hard to use

one example is that you usually want to set up your own data schema with your own access patterns, indexes and mixed with your proprietary data — so even if you use graph to read from the node, you will most likely pipe it through your own db

@woj have you heard of the indexing project The Graph? And if so, why don't they solve your problem?