This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
qora_original_data_hosting_model [08/16/2021 15:21] – created gfactor | qora_original_data_hosting_model [11/02/2023 14:18] (current) – [THIS IS NOT THE MODEL QORTAL USES, THIS WAS THE MODEL OF THE QORA PROJECT] crowetic | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== QORA Original Data Hosting Model ====== | ====== QORA Original Data Hosting Model ====== | ||
{{: | {{: | ||
+ | |||
+ | =====THIS IS NOT THE MODEL QORTAL USES, THIS WAS THE MODEL OF THE QORA PROJECT===== | ||
+ | |||
+ | This page is here to explain WHY the QORA model was deemed unworthy and REPLACED by the [[qortal_data_network_qdn|Qortal Data Network model]]. | ||
+ | |||
QORA had a model that was based on uploading data to the chain itself. In order to place data upon the QORA hosting, a user would have to register a name to use as a ' | QORA had a model that was based on uploading data to the chain itself. In order to place data upon the QORA hosting, a user would have to register a name to use as a ' | ||
Line 24: | Line 29: | ||
This is good in theory, but bad in practice, when dealing with data actually on the blockchain. As when the system ends up getting a lot of users, the data would quickly become too large for the computers of the users to hold... making it eventually inevitable that the system would need a total rework once the data got to a point that it was filling the largest hard drives itself... So the long-term potential of this model is lacking. | This is good in theory, but bad in practice, when dealing with data actually on the blockchain. As when the system ends up getting a lot of users, the data would quickly become too large for the computers of the users to hold... making it eventually inevitable that the system would need a total rework once the data got to a point that it was filling the largest hard drives itself... So the long-term potential of this model is lacking. | ||
- | The bloat, is the main issue that Qortal didn't use the on-chain storage model. | + | The bloat, is the main issue that Qortal didn't use the on-chain storage model. However, there is also the issue that no matter which user uploaded data, due to the QORA data model, EVERY user would have that data ON THEIR COMPUTER. This made it so that if there was ' |
===Issue #2 - Data Uploads In Transactions (of a limited size, and lack of proper coding for data uploads)=== | ===Issue #2 - Data Uploads In Transactions (of a limited size, and lack of proper coding for data uploads)=== |