Ethereum

AMA about the EF, I'll answer whatever I can!

the organizational philosophy is "subtraction".
Where is the EF self-subtraction plan?
Does it not exist because "your" salary depends on it not existing?

(1) No such thing. You are implying we are centralized. That Ethereum is "systematically depending on the consent or input of (any) one atomic party". If this is true, it should no longer be as soon as possible.

The only role of a centralized incorporated entity representing Ethereum should be to interface with other centralized entities. EF is not doing that.

Sure. EF has done some good along the years. Very well. Protocol Guild should get today 10% of EF treasury vested over 5 years.

ETH global and other events should also get 10% over X years.

Sure, maybe another 10% for current research.

Rest should be redistributed on the basis of clear rules by the people that pay for it all - Ether holders. We have the infrastructure for it. Imagine the EF asking publicly for organizational solutions. Why has that not happened? Is that idea banned? But I guess its priority is to be a corporation that serves the 200+ people that can go around and say they invented Ethereum or something.

I think we haven't always been effective at communicating subtraction, let me try here:

- Ethereum is too big and too important to be supported only by one org

- So the EF needs to both (1) do the most critical things that only we can do, (2) build up and empower a strong ecosystem around us who can share the burden

- There are at least two parts to (2). One part is about making sure we are not getting in the way of others. People will not take action themselves to solve some problem if everyone is under the impression "Oh, it's all the EF's responsibility". Another part is very actively helping the people who *do* step up to solve a problem or build organizations that help share those burdens. We've done that with ETHGlobal, Protocol Guild, L2Beat, Nomic Foundation (hardhat developers), 0xPARC, ENS, and several others. 

- So "subtraction" is not just about fading into nothing. It is about creating the conditions under which the EF can be less of a dependency, and that requires helping build up others.