ConsenSysMesh / web3studio-projects

Discussion board for web3studio projects
4 stars 1 forks source link

MeshUp #35

Open humbitious opened 5 years ago

humbitious commented 5 years ago

Who hasn't had the experience of wishing you could have the features of product a, b and c in one product? In software, can modularity be at a stage where we could start to realize this in a way that is truly satisfying to the user? And could we now do this in a way that allows the makers of different "lego" parts/features (even ones that aren't remote services but on-board code libraries/components) to get paid for being part of different assemblages? The problem here is that code, once copied, is easy to copy again. But what if a few things were in place:

1) A decentralized (could be centralized) service that "redhat's" the code...signs the compile and certifies that the code in the runtime is the code that everyone judged to not contain anything naughty.

2) Part of the compile process in #1 inserts into the final signed runtime a call to a smart contract that executes [some economic condition...like an agreement between the maker of the feature and the seller of a particular assemblage containing the feature to pay the feature maker x% of revenue].