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/23/2021 10:56] – 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 59: | Line 63: | ||
The storage nodes will have their own API endpoints to access and update data. They' | 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/ | ||
+ | |||
+ | 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 " |