In my last article we covered the need for having New High Efficiency Indexing and Database Management Redefined. This matters because I believe that the user experience should be smooth and responsive without requiring people to have to give up their rights to privacy and data security. We can have mechanics that evolve with the applications, and allow communities to self organize if they are just given the right tools to do it.
Today, I want to share what I believe has been one of the biggest shortfall issues in blockchain to date which has disappointed so many people who thought they were using something decentralized, only to find that the data running it, was all under the control of a single actor in many cases.
Perhaps one of the major sticking points to Dapp deployment that has been observed is the handling of large quantities of data. This has often been where Dapp developers introduced significant liabilities as there is no effective means of using blockchain to provide the various methods of storage space, interfaces, or user generated content. This issue has been generally unaddressed by smart contract platforms forcing Dapp developers into centralized hosting solutions.
Looking at the landscape of storage solutions, there are a few options available which could be utilized, but one which stands out that can be efficiently introduced to Peerplays thanks to its DHT-based protocol is the InterPlanetary File System (IPFS). With its combination of requesting nodes connecting to providing nodes utilizing the storage of data by way of hash, any node in the network can now provide a location for a requestor of the needed data.
By enabling this storage feature in nodes, Dapp developers immediately have a way to provide a resilient means of maintaining the data associated with the Dapps while providing the added benefit to end users ensuring the security and permissions are kept in their control.
Provided through something like IPFS. Dapp developers need only provide the initial seeded data of their Dapps and then the users, who can choose to participate in being rewarded for sharing their IPFS stored data, will take care of the rest. Integrity of the data continues to be maintained by the blockchain as it maintains the authoritative record of the verified hash proving the authenticity and integrity of the data to everyone.
In the delicate beginning of a Dapp's lifecycle, developers can censor the user by refusing to host the user data. This can be combated by the end users and other nodes in the network choosing to provide their own node with a simple setting, ensuring the Dapp users are secured against censorship or lost data.
.
.
.
This is the 7th in a series of articles I will be making over the next month. Be sure to subscribe to get notified of future posts to find out where this goes.
Have thoughts on what I shared? Feel free to leave a comment and share!
