Qortal Project

The future of blockchain platforms

User Tools

Site Tools

Trace: • qortal_minecraft_server
qort_data_hosting_model

Differences

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

Link to this comparison view

Next revision		Previous revision
Last revisionBoth sides next revision
qort_data_hosting_model [10/11/2021 10:50] – created 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|}}
  
-**The Data Storage model of Qortal has yet to be fully designed. Qortal has not yet launched data hosting but we do have a demo version below and data hosting is not too far out!**+**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!**
  
-We came up with a method of data storage that could be better than using IPFS.+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. 
  
-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. +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. 
  
 Here are two examples of sites hosted on a Qortal data node: Here are two examples of sites hosted on a Qortal data node:
Line 21: 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 =====
  
Line 58: Line 64:
   -Everyone's nodes would watch for local changes to the MySQL repo, and submit a transaction automatically when needed.   -Everyone's nodes would watch for local changes to the MySQL repo, and submit a transaction automatically when needed.
  
-Obviously the approach above has major drawbacks for serious / high throughput use cases, and also ones that need to store sensitive data. But it would work in projects that update their data infrequently (e.g. wordpress), so it could be a fairly straightforward way to get started. Most of the foundations are in place for this already.+Obviously the approach above has major drawbacks for serious / high throughput use cases, and also ones that need to store sensitive data. But it would work in projects that update their data infrequently (e.g. WordPress), so it could be a fairly straightforward way to get started. Most of the foundations are in place for this already.
  
 The current plan is to include a java-based version of httrack in the data nodes, so that it can automatically convert a URL and add the static copy to the data chain. After that, we'll have the ability to include a bot in the data nodes that watches a given URL for changes and then automatically creates a static copy and publishes any differences to the chain each time. I'm not sure whether this feature will make it into v1 of data nodes; it will most depend on whether there is a java-based static site downloader already available. If not we'll have to create our own, which will take a while. The current plan is to include a java-based version of httrack in the data nodes, so that it can automatically convert a URL and add the static copy to the data chain. After that, we'll have the ability to include a bot in the data nodes that watches a given URL for changes and then automatically creates a static copy and publishes any differences to the chain each time. I'm not sure whether this feature will make it into v1 of data nodes; it will most depend on whether there is a java-based static site downloader already available. If not we'll have to create our own, which will take a while.
Line 64: Line 70:
 The storage nodes will have their own API endpoints to access and update data. They'll also have the API endpoints that we're already used to, so that you can access blocks and transactions on the data chain. The storage nodes will have their own API endpoints to access and update data. They'll also have the API endpoints that we're already used to, so that you can access blocks and transactions on the data chain.
  
-===== More Notes From CalDescent: ===== +===== More Notes From CalDescent =====
- +
  
 The way public data hosting works at the moment is by using confirmable transactions (so that there is always an on-chain record of updates to each website/service), but rather than a transaction fee, we require a proof of work nonce to be calculated and included with the transaction. The difficulty depends on the size of the files being added to the network. We use a similar PoW nonce for Q-chat transactions. The way public data hosting works at the moment is by using confirmable transactions (so that there is always an on-chain record of updates to each website/service), but rather than a transaction fee, we require a proof of work nonce to be calculated and included with the transaction. The difficulty depends on the size of the files being added to the network. We use a similar PoW nonce for Q-chat transactions.
Line 76: Line 81:
  
 All of the above relates to "public data" only. We will eventually have support for "private data" too, and this would work completely differently. It would likely be a case of paying QORT to host it, which would be paid out to the participating data nodes. But that feature won't be in place for a while. All of the above relates to "public data" only. We will eventually have support for "private data" too, and this would work completely differently. It would likely be a case of paying QORT to host it, which would be paid out to the participating data nodes. But that feature won't be in place for a while.
 +
 +Name registration doubles as a “domain name” for websites and other data hosted by that account (in v3.0). Currently owned domain names will not be possible to transfer registration to your account on Qortal. They are completely separate and there won't be any way of linking them. Traditional domain names rely on "domain authorities" such as ICANN, which are incompatible with Qortal's system and ethos. Best thing to do is just register your existing names with Qortal. There's currently no established convention in terms of domain extensions in Qortal. I expect most names won't have an extension, but it's possible one such as .qort will emerge organically in the future. You should be able to register .com extensions etc within the system if you prefer them over names with no extensions.
 +
 +You can absolutely access it via a separate browser. There are a couple of options:
 +
 +1. Using the API on a public/gateway node such as http://node1.qortal.uk:12393/site/QortalDemo
 +
 +2. Using the “domain mapping” feature with existing DNS - e.g http://www.reqorder.org/ - this site is on the data testnet
 +
 +When setting up domain mapping: you will need to add the domain name to your node(s) and then point the domain at them via DNS. You can have multiple nodes behind a single domain for better redundancy.
 +
 +This “gateway” feature is now developed, so we can already support gateways to the Qortal network via an existing domain. E.g: <code>https://gateway.qortal.org/RegisteredName</code>
 +
 +or
 +
 +<code>https://qortalweb.com/RegisteredName</code>
 +
 +etc.
 +
 +Basically anyone who is willing to can provide access to the entire Qortal network of websites via a domain they own. They just have to enable the gateway service in their node’s settings (and point their domain at the node using DNS). You can always connect the traditional domain name to your Qortal site if you want to. It will just rely on centralised components, unlike using a registered name within Qortal.
 +
 +===== We Use PoW For Data Uploads =====
 +
 +We use PoW for data uploads to reduce the ability for people to spam the chain with data. For most transaction types in Qortal, we use a 0.001 QORT transaction fee. For QDN we decided to remove the fee and replace it with a "nonce", which essentially means a certain amount of computational resources need to be used when publishing data, to slow down requests and reduce spam. We use this approach for Q-Chat messages (most significantly when the account has a zero balance) and also for some existing on-chain transaction types, such as the "MESSAGE" transactions that are used in the trade portal (to allow people to buy QORT without having any QORT to create the trade portal Buy transaction).
 +
 +The main reason for doing this for QDN was because we were planning on putting data hashes on a sidechain that wouldn't support transaction fees. Due to time constraints we ended up putting data hashes on the main chain (there's still lots of capacity there) but once we need to scale up we will need to return to the sidechain idea, and when we do, it will make it easier for both devs and users if we are using a proof of work nonce rather than a transaction fee.
qort_data_hosting_model.txt · Last modified: 07/21/2022 05:25 by gfactor

Page Tools