Editing Datachain (section)

= Future work =

All of the major problems with a datachain seem to be solved when the DAS has tight restrictions on the parameters for accepted solutions. For example, rather than saying a solution can come from anywhere you have a big list of hashes and tell the network to process files in that search space. This is an easy way to solve things as there is a huge amount of data in torrents that fit that definition – but its still slightly impractical.

In the future one can imagine a datachain being used to run decentralized, autonomous, websites based around organizing content mined from other services that fit a certain pattern. The content would be provided by miners who maintain the chain in exchange for a reward where the chain is kept around so long as the content is found to be useful. This would be quite an interesting spin on dynamic, user-generated content websites while providing a robust platform for keeping such information available.

Another idea is to use something that I call a “programmatic organization” to incentivize the creation of '''new''' content. For example, you could specify that submissions could only come from certain places (organizations) after a certain point in time and remove some of the restrictions for submissions. This would mean introducing third-party trust (so no longer a DAS) but could be another interesting structure for funding new content.

I can think of some more programmatic organizations that might make sense in this context: like article production type stuff comes to mind where payment is guaranteed based on pattern matching regardless of how the employer acts. Then when it comes to the more specialized case of a datachain as a DAS you might also have things like search engines that would benefit from being funded by the user for content procurement.

There are definitely more datachains left to discover and different types of DAS but the rest I’ll leave up to the reader to discover.
pandoc version 3.6.1