Content
@
0 reply
0 recast
0 reaction
Trent
@trent
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
2 replies
3 recasts
22 reactions
Soubhik Deb
@soubhik
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.
1 reply
0 recast
1 reaction
Soubhik Deb
@soubhik
But the other direction from knowledge common to software common is kinda fuzzy to me right now. For example decentralized RPC is a development in knowledge common but doesn’t seem to have upstream impact on software common of Ethereum.
1 reply
0 recast
1 reaction
Trent
@trent
I may have made the distinction btwn software/knowledge/infra in the piece to describe them but in reality they are all nested within each other. Clearest example is the capital circuit/infra being embedded within the software commons
0 reply
0 recast
0 reaction
