This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
qort_new_data_hosting_model [08/17/2021 14:23] – gfactor | qort_new_data_hosting_model [10/11/2021 10:42] – [QORT New Data Hosting Model] gfactor | ||
---|---|---|---|
Line 8: | Line 8: | ||
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 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’s an example site that is hosted on a Qortal data node: http:// | + | Here’s an example site that is hosted on a Qortal data node: |
+ | |||
+ | http:// | ||
+ | |||
+ | http:// | ||
It’s an older static copy of the Qortal wiki so it is not up to date. | It’s an older static copy of the Qortal wiki so it is not up to date. | ||
Line 18: | Line 22: | ||
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/ | 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/ | ||
- | For public | + | Public |
Here’s the code being worked on so far for the data hosting: https:// | Here’s the code being worked on so far for the data hosting: https:// | ||
Line 47: | Line 51: | ||
-Add a MySQL resource and publish the initial database schema and data. This would create a transaction on chain and sync the associated data around the network. | -Add a MySQL resource and publish the initial database schema and data. This would create a transaction on chain and sync the associated data around the network. | ||
- | -Add a PHP resource and publish your initial PHP files | + | -Add a PHP resource and publish your initial PHP files. |
- | -Inside your PHP database class you would point it to the Qortal MySQL instance, which could be something like `qortal:// | + | -Inside your PHP database class you would point it to the Qortal MySQL instance. This would essentially map to http:// |
-Deploy the PHP resource which would add a transaction and sync its data around the network. | -Deploy the PHP resource which would add a transaction and sync its data around the network. | ||
-Other users could then run the PHP app (and database) using by visiting `http:// | -Other users could then run the PHP app (and database) using by visiting `http:// | ||
Line 54: | Line 58: | ||
-Everyone' | -Everyone' | ||
- | <p>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.</p> | + | 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 storage nodes will have their own API endpoints to access and update data. They' | ||
+ | |||
+ | ===== 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. | ||
+ | |||
+ | Then, in order for the data itself to replicate, the creator must have viewers of the data, or followers of their account. This allows good data to propagate, whereas data that has no viewers or followers wouldn' | ||
+ | |||
+ | The idea behind using a nonce rather than a transaction fee removes the cost barrier so encourages people to use the system. But since the uploader has to perform some difficult proof of work calculations each time, it prevents someone from easily spamming the chain. | ||
+ | |||
+ | Also, the data hashes are being written to a completely separate chain for scalability reasons (it doesn' | ||
+ | |||
+ | All of the above relates to " |