Qortal Project

The future of blockchain platforms

User Tools

Site Tools

Trace:
qort_data_hosting_model

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
qort_data_hosting_model [02/07/2022 08:22] – gfactorqort_data_hosting_model [07/21/2022 05:13] – gfactor
Line 1: Line 1:
 ====== QORT Data Hosting Model ====== ====== QORT Data Hosting Model ======
 {{:qortal_official_logo_transparent_.png?400|}} {{:qortal_official_logo_transparent_.png?400|}}
 +{{::54582a96-0c0c-4f3a-b6b1-8b0ed0a9b9bc.jpeg?400|}}
  
-**Qortal Data Network (QDN) is LIVE! Although there is a data size limit of 350MB as we begin building this into a scalable solution to rebuild the Internet as we know it. Bear with us!**+**Qortal Data Network (QDN) is LIVE! Although there is a data size limit of 500MB as we begin building this into a scalable solution to rebuild the Internet as we know it. Bear with us!** 
 + 
 +QDN is a 100% FREE solution to rebuilding the Internet in a decentralized fashion. Instead of paying third-parties for a domain name, simply register a name on Qortal and own that domain for LIFE. Then you’ll be able to host your own website with whatever data you’d like - free from any censorship or control by Big Tech. You simply host your data on your Qortal node, and a tiny hash is registered on Qortal’s chain to log your ownership. Your data is NOT hosted on Qortal’s chain, as that would not be a scalable solution for rebuilding the Internet ;-). The data is hosted on your hardware, and the website link is found in Qortal’s UI under the ‘Websites’ section. The person wanting to browse your site will then click the link, and download the data to their node in order to view it. Yes, it’s kind of a strange concept but is our first phase of rolling out a truly decentralized solution. The data is encrypted during transfer, and can be either 1) deleted after viewing or 2) supported as a peer. The latter option means you can choose to ‘Follow’ that website and run a redundant copy of that data - which keeps the website live if the original host’s node goes offline for whatever reason. This also increases the speed of accessing the data by the rest of the network. By working hand-in-hand, we can support each other in building a web of data that is unhackable and self-empowering.  
 + 
 +Now what if you come across ‘illicit’ content during your QDN browsing? Simply click the red x next to the website you’ve viewed and delete the data. Of course this raises a lot of concerns for the typical user and we completely understand. Please keep in mind that we are building a set of layers to Qortal’s infrastructure and perfecting this will take time. The plan is to develop a White List that users can choose to opt into, which we can work together to build and essentially block out the illicit content. We will also have another White List for kids, like a YouTube for kids, so parents can feel confident that their child is safely browsing the Qortal Network. True decentralization means we have truly no control over what others post, but we reserve control over our own nodes and the data we choose to access.  
 + 
 +Data can be relayed through our nodes, in order for other nodes to communicate. All of this data is end-to-end encrypted, and is also chunked so the data is not relayed on a single node. The data being relayed is only on your node long enough to conduct the transfer, and is deleted afterwards automatically. Users can choose to opt out of relay mode if their lack of understanding with this matter raises too much concern. Getting data around the network is difficult and requires more fine tuning- even with relay mode enabled (which helps the network). To disable relay mode, add this setting to your json settings:  
 + 
 +<code>"relayModeEnabled": false</code> 
 + 
 +QDN is accessible to everyone and does not cost anything. The only cost is registering a name (current name registration fee can be found on the [[Qortal Status Updates]] page. 
  
 We came up with a method of data storage that could be better than using IPFS. We have a working prototype already which works in a similar way to IPFS but we hope will be a lot more user friendly. It’s only for static sites at the moment (HTML, JS, CSS, images, other static assets) so you would need to either build it directly as a static site, or take a static copy of an existing site using a tool such as httrack, SiteSucker, Simply Static, etc.  We came up with a method of data storage that could be better than using IPFS. We have a working prototype already which works in a similar way to IPFS but we hope will be a lot more user friendly. It’s only for static sites at the moment (HTML, JS, CSS, images, other static assets) so you would need to either build it directly as a static site, or take a static copy of an existing site using a tool such as httrack, SiteSucker, Simply Static, etc. 
Line 19: Line 30:
  
 Public data is only encrypted in terms of the account that put the data there, the encryption only controls the MODIFICATION of that data. Private data, on the other hand, will be fully encrypted. We’re not entirely certain yet on how we'll decide which private data is held by other nodes. Potentially we will just have an option to allow private data to be stored as a duplicate on your node. You’ll be rewarded for that data from the fees the person putting the data up will pay for the data to be stored/duplicated on the network. So as a data node you will have the option to allow private data to be stored, then as the person wanting that data stored/duplicated, you will pay a fee for however many duplicate copies you would like to store. The fee then goes to the data node that ends up storing that duplicate copy.  Public data is only encrypted in terms of the account that put the data there, the encryption only controls the MODIFICATION of that data. Private data, on the other hand, will be fully encrypted. We’re not entirely certain yet on how we'll decide which private data is held by other nodes. Potentially we will just have an option to allow private data to be stored as a duplicate on your node. You’ll be rewarded for that data from the fees the person putting the data up will pay for the data to be stored/duplicated on the network. So as a data node you will have the option to allow private data to be stored, then as the person wanting that data stored/duplicated, you will pay a fee for however many duplicate copies you would like to store. The fee then goes to the data node that ends up storing that duplicate copy. 
- 
-Public data will be 100% FREE and use the same transaction methodology that Q-Chat uses, to put up the data hashes on the data chain. This means that Qortal web hosting and other public data functionality will be 100% feeless, and accessible to anyone (regardless of whether they hold QORT or not). The only reason a person looking to host data on Qortal would need QORT, would be to register a name, which is a ONE TIME FEE, and the name is then owned forever (until potentially sold in the future 'names market'). 
  
 Here’s the code being worked on so far for the data hosting: https://github.com/CalDescent14/qortal-data Here’s the code being worked on so far for the data hosting: https://github.com/CalDescent14/qortal-data
- 
 ===== Notes From CalDescent ===== ===== Notes From CalDescent =====
  
qort_data_hosting_model.txt · Last modified: 07/21/2022 05:25 by gfactor

Page Tools