This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| node_types [05/22/2023 18:47] – quickmythril | node_types [03/21/2026 14:52] (current) – ironfixxxer | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| ===== Full Nodes===== | ===== Full Nodes===== | ||
| - | There will be multiple ‘types’ of nodes on the Qortal Network | + | There are multiple ‘types’ of nodes on the Qortal Network. The first and ‘main’ node type is called a ‘full node’. A full node is a node that stores the entire blockchain database. A full node is the recommended node type for Minters, as they are meant to be the nodes that ‘power and support’ network, and a full node is the best type of node to accomplish that. However, given that Qortal is meant to be able to be run by anyone and that not everyone has a substantial amount of storage space on which to hold the entirety of the blockchain forever, there is another node type in development called ‘lite nodes’. |
| The concern over scalability in regard to the size of the Qortal blockchain is what spurred the development of the lite node type, but it also spurred the development of a new method for blockchain storage on full nodes. | The concern over scalability in regard to the size of the Qortal blockchain is what spurred the development of the lite node type, but it also spurred the development of a new method for blockchain storage on full nodes. | ||
| Line 10: | Line 10: | ||
| Full nodes in archive version 2.0 will have the option of ‘flat file offloading’ for their blockchain database files. What this means is that a full node can choose to store the majority of their ‘older data’ in the blockchain in ‘flat files’ and reduce the size of their full node database considerably. This type of database storage does not impact the full node in regard to retaining all of the data from every block since Genesis. It will still allow calls for older data to be made without the need for the entire database to be in its default SQL-compatible format. | Full nodes in archive version 2.0 will have the option of ‘flat file offloading’ for their blockchain database files. What this means is that a full node can choose to store the majority of their ‘older data’ in the blockchain in ‘flat files’ and reduce the size of their full node database considerably. This type of database storage does not impact the full node in regard to retaining all of the data from every block since Genesis. It will still allow calls for older data to be made without the need for the entire database to be in its default SQL-compatible format. | ||
| - | With the release of version 2.0, Qortal | + | With the release of version 2.0, Qortal |
| ===== Lite Nodes ===== | ===== Lite Nodes ===== | ||
| Line 18: | Line 18: | ||
| ===== Data Nodes ===== | ===== Data Nodes ===== | ||
| - | Data nodes in Qortal | + | (*This information is outdated as of June 2025, and will be updated further over time.) |
| + | |||
| + | Every Node on Qortal | ||
| NOTE: By default, all nodes are also data nodes, and they have relay mode enabled. Users can change their settings to disable relay mode, or set qdnEnabled to false to disable Qortal Data Network hosting completely. There is also a setting to change the storage policy to host ALL data, instead of just content that was viewed or followed, as detailed below. For information on changing those settings, please see the [[How To Edit Qortal Core Settings]] page. | NOTE: By default, all nodes are also data nodes, and they have relay mode enabled. Users can change their settings to disable relay mode, or set qdnEnabled to false to disable Qortal Data Network hosting completely. There is also a setting to change the storage policy to host ALL data, instead of just content that was viewed or followed, as detailed below. For information on changing those settings, please see the [[How To Edit Qortal Core Settings]] page. | ||
| Line 24: | Line 26: | ||
| 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. | ||
| - | Data nodes only the data they choose to have on their node. If the data node views a website, then after viewing it decides they do NOT want to be a peer for that website (they don’t want to host a redundant copy of that website for the website creator), they can subsequently delete the website from their data node, and will no longer hold the data nor continue being a peer for others to download that data. Full individual control over every bit of the data on a user’s node is absolutely essential to Qortal’s functionality. Individual sovereignty over EVERYTHING in Qortal is the end goal. Therefore full control over the data that is stored on the user’s data node is required. There is no data on any user’s node that the user is not aware of. | + | Data nodes share only the data they choose to have on their node. If the data node views a website, then after viewing it decides they do NOT want to be a peer for that website (they don’t want to host a redundant copy of that website for the website creator), they can subsequently delete the website from their data node, and will no longer hold the data nor continue being a peer for others to download that data. Full individual control over every bit of the data on a user’s node is absolutely essential to Qortal’s functionality. Individual sovereignty over EVERYTHING in Qortal is the end goal. Therefore full control over the data that is stored on the user’s data node is required. There is no data on any user’s node that the user is not aware of. Use the Q-App, **Host Monitor Plus** to view and manage your shared data. |
| - | The concept of ‘following’ has been used in many social media platforms for years. This concept is that of essentially ‘paying attention’ to a certain user and what they do. Following in terms of Qortal data storage will be similar, but slightly different. In Qortal, a data node will have the option to ‘follow’ a content creator’s namespace. If the data node chooses to become a follower of that namespace, they will subsequently automatically become a peer for the data that namespace puts up. If a data node likes the content of a certain website, following that website would bolster the availability of the website to others automatically. Becoming another redundant copy of that website’s data for the creator is a substantial way to support the creator. | + | The concept of ‘following’ has been used in many social media platforms for years. This concept is that of essentially ‘paying attention’ to a certain user and what they do. Following in terms of Qortal data storage will be similar, but slightly different. In Qortal, a data node will have the option to ‘follow’ a content creator’s namespace. If the data node chooses to become a follower of that namespace, they will subsequently automatically become a peer for the data that namespace puts up. If a data node likes the content of a certain website, following that website would bolster the availability of the website to others automatically. Becoming another redundant copy of that website’s data for the creator is a substantial way to support the creator. Use the Q-App, **Q-Follow** to follow and block names/ |
| Following also opens up many other unique opportunities, | Following also opens up many other unique opportunities, | ||
| Line 36: | Line 38: | ||
| 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. | + | |