The proposal itself could be very minimal.
Similar to how the “tokenURI(uint tokenId)” methodology might return a content material addressable URI corresponding to “ipfs://<cid>”, this “licenseURI(uint tokenId)” might return “ipfs://<cid>”, which would come with the hash of the legally binding license doc.
To make this totally automated, some license paperwork themselves might grow to be standardized, very like how numerous open supply initiatives use MIT/Apache/GPL and many others.
If we assume a small variety of such standardized contract sorts, it turns into attainable to construct a totally automated market contract that ONLY lists contracts with sure recognized licensing mannequin.
For instance, all of the sudoswap sort marketplaces could question “licenseURI()” and it could return a sure IPFS URI, and relying on the end result, it could checklist it on {the marketplace} or not. So in a method it is vitally minimal however nonetheless very ricardian, as a result of you need to use the hash of the content material in triggering different third get together contract behaviors.
