User Tools
node_types
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| node_types [04/27/2023 18:24] – [Data Nodes] gfactor | node_types [04/27/2023 18:26] – [Full Nodes vs Top-Only Nodes] gfactor | ||
|---|---|---|---|
| Line 14: | Line 14: | ||
| Note: from Caldescent May 12, 2022 additional information: | Note: from Caldescent May 12, 2022 additional information: | ||
| The archive folder is the blockchain. It's what makes you a full node. If you delete them, you essentially become a topOnly node (but you should really do that by setting " | The archive folder is the blockchain. It's what makes you a full node. If you delete them, you essentially become a topOnly node (but you should really do that by setting " | ||
| - | Also, I think the default | + | Also, I think the default |
| - | So best not to delete it - if you don't have the SSD space then use the topOnly setting instead | + | |
| ===== Lite Nodes ===== | ===== Lite Nodes ===== | ||
| Line 22: | Line 21: | ||
| ===== Data Nodes ===== | ===== Data Nodes ===== | ||
| - | Data nodes in Qortal are a Qortal node with an added ‘module’ (the ‘Data Module’) installed giving that node the ability to store and host data for access by others. Initially, the only type of data storage that is be possible | + | Data nodes in Qortal are a Qortal node with an added ‘module’ (the ‘Data Module’) installed giving that node the ability to store and host data for access by others. Initially, the only type of data storage that is possible |
| The first concept to implement is that the only data to be hosted on a user’s data node, is the data that the user of the node viewed or follows. A data node user who views a website or anything hosted on a data namespace will become a ‘peer’ for that data (hosting a copy of it on their data node as well). This system functions very similarly to that of the ‘torrent’ network, wherein users are ‘peers’ for data they have downloaded unless they choose to remove that data and others then download the data from them and become a peer for it once it is completed. | The first concept to implement is that the only data to be hosted on a user’s data node, is the data that the user of the node viewed or follows. A data node user who views a website or anything hosted on a data namespace will become a ‘peer’ for that data (hosting a copy of it on their data node as well). This system functions very similarly to that of the ‘torrent’ network, wherein users are ‘peers’ for data they have downloaded unless they choose to remove that data and others then download the data from them and become a peer for it once it is completed. | ||
| Line 34: | Line 33: | ||
| Data storage on Qortal is not only meant to provide redundant copies of the data, improve speeds of the downloads, and decentralize the content. Qortal data will also utilize blockchain technology to SECURE the content beyond any security methods that exist on the traditional Internet. To a degree that the files are literally only able to be modified by the account that put them there. Making websites hosted on Qortal ‘unhackable’ in the traditional sense. There is literally no way for any user other than the creator who holds the private keys for the account that owns the namespace to modify the data. | Data storage on Qortal is not only meant to provide redundant copies of the data, improve speeds of the downloads, and decentralize the content. Qortal data will also utilize blockchain technology to SECURE the content beyond any security methods that exist on the traditional Internet. To a degree that the files are literally only able to be modified by the account that put them there. Making websites hosted on Qortal ‘unhackable’ in the traditional sense. There is literally no way for any user other than the creator who holds the private keys for the account that owns the namespace to modify the data. | ||
| - | Every bit of data on Qortal’s data network will be ‘hashed’ (using a cryptographic hashing algorithm to obtain a unique string that identifies the data hasn’t been tampered with) and stored on the ‘data chain’. What this means is that the data chain will be able to keep track of every file’s hash (unique identifier) to verify the file itself without needing the entire file ON the blockchain. The project that Qortal | + | Every bit of data on Qortal’s data network will be ‘hashed’ (using a cryptographic hashing algorithm to obtain a unique string that identifies the data hasn’t been tampered with) and stored on the ‘data chain’. What this means is that the data chain will be able to keep track of every file’s hash (unique identifier) to verify the file itself without needing the entire file ON the blockchain. The project that Qortal started from back in 2014 called QORA utilized a data storage method that required the data itself to be put up onto the blockchain. When writing Qortal from scratch, the Qortal development team modified this concept to remove the data from the blockchain itself. There are multiple reasons that the data being on the blockchain is a bad idea. If the data itself is on the blockchain, then every user must hold all of the data in order to synchronize the chain. Not only that, but it simply isn’t scalable to the size that Qortal aims to be if every user has to hold the data for every website in existence. Therefore the decision was made to completely revamp the idea of QORA by removing the data from the blockchain, while allowing only the data’s hash to remain so that the chain can SECURE and VERIFY the data, but does not actually HOLD the data. This opens up a plethora of other potential use cases for data storage in Qortal that QORA did not have. |
| A future development in regard to data storage will be the ability for public data users to browse a ‘data market’ where data nodes with algorithmically defined ‘reputation’ scores are available to choose (and pay a fee for) hosting another redundant copy of their data. The initial iteration will not have this and will be a ‘merit only’ model, wherein users will choose to become a peer for the data they believe has more merit, and will not do so simply for monetary reward. | A future development in regard to data storage will be the ability for public data users to browse a ‘data market’ where data nodes with algorithmically defined ‘reputation’ scores are available to choose (and pay a fee for) hosting another redundant copy of their data. The initial iteration will not have this and will be a ‘merit only’ model, wherein users will choose to become a peer for the data they believe has more merit, and will not do so simply for monetary reward. | ||
| Another future development will be ‘private data’ (for things like documents, pictures, and data that will never be shared publicly as well as 100% encrypted to the account that put it up). Each user will use the ‘data market’ to define which nodes and how many copies of their data they would like to have, and pay a fee for that data. There are literally countless end use cases for Qortal’s data storage concepts. | Another future development will be ‘private data’ (for things like documents, pictures, and data that will never be shared publicly as well as 100% encrypted to the account that put it up). Each user will use the ‘data market’ to define which nodes and how many copies of their data they would like to have, and pay a fee for that data. There are literally countless end use cases for Qortal’s data storage concepts. | ||
node_types.txt · Last modified: 01/17/2024 21:18 by crowetic