A few weeks ago I published  "Capital and enclosure in software commons: Linux & Ethereum" 

- intros to Common, commons
- commons enclosure/capture
- how the Linux + Ethereum commons are structured
- how capital engages w/ these commons

A few weeks ago I published  "Capital and enclosure in software commons: Linux & Ethereum" 

- intros to Common, commons
- commons enclosure/capture
- how the Linux + Ethereum commons are structured
- how capital engages w/ these commons

https://trent.mirror.xyz/GDDRqetgglGR5IYK1uTXxLalwIH6pBF9nulmY9zarUw

Consulting and advising for crypto protocols and projects like FastLane and Privy. Prev product @rainbow, work for Uniswap Fdn, Biconomy, Socket and others 

* core protocol consigliere @ Ethereum Foundation
* funding core devs with @protocolguild (member)
* creating artifacts @ Stateful Works

Would love to hear people’s thoughts, esp @basche42

How would you characterize the interaction between the software common and knowledge common? Seems like impact flow is downstream from software common to knowledge common. An example is EIP-4788. That development in software commons removed potential enclosure of beacon state oracles by rent seeking entities.