User Tools
node_types
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| node_types [04/27/2023 18:26] – [Full Nodes vs Top-Only Nodes] gfactor | node_types [01/17/2024 21:18] (current) – crowetic | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| {{: | {{: | ||
| - | ===== Full Nodes vs Top-Only | + | ===== Full Nodes===== |
| - | There will be multiple ‘types’ of nodes on the Qortal Network in the near future. 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 has been another node type developed | + | There will be multiple ‘types’ of nodes on the Qortal Network in the near future. 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 |
| - | The concern over scalability in regard to the size of the Qortal blockchain is what spurred the development of the top-only | + | 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. |
| - | Full nodes in version 2.0 of Qortal | + | Full nodes in archive |
| With the release of version 2.0, Qortal will have essentially ‘unlimited’ scalability for its blockchain without users having to worry about needing more storage space to continue running their Qortal node. | With the release of version 2.0, Qortal will have essentially ‘unlimited’ scalability for its blockchain without users having to worry about needing more storage space to continue running their Qortal node. | ||
| - | 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 " | ||
| - | Also, I think the default behavior is for the node to auto bootstrap on the next launch if it can't find its archive folder. So best not to delete it - if you don't have the SSD space then use the topOnly setting instead. | ||
| ===== Lite Nodes ===== | ===== Lite Nodes ===== | ||
| - | Lite nodes will not store the blockchain at all, but instead, will utilize connected full or top-only | + | Lite nodes will not store the blockchain at all, but instead, will utilize connected full node peers to facilitate the calls to the blockchain they need to make. With this type of node, minting will not be possible. However, all of the other functionality within Qortal will be. This type of node would be perfect for something like a fully decentralized mobile app making use of any service on Qortal. It could be used to build a decentralized Trade Portal phone app, a full local multi-wallet cross-chain trading enabled app, or simply a fully featured Qortal app with multi-plugin capability (just like the existing Qortal UI). All of this can be done without the need to store the database at all, thus taking very minimal storage space and not requiring the user to synchronize the blockchain at all. Another use case for lite nodes would be bundling a lite node with the Qortal UI, so that users can simply install the UI and make use of everything on the Qortal Network with no need to synchronize the chain or store the blockchain database at all. In order for lite nodes to function as intended, it is essential that the base level of the Qortal Network consist of a majority of full nodes, which is why the development of lite nodes is planned for a good while after the release of the other node types. |
| ===== Data Nodes ===== | ===== Data Nodes ===== | ||
| - | Data nodes in Qortal are a Qortal node with an added ‘module’ (the ‘Data Module’) installed | + | Data nodes in Qortal are a Qortal node with an added feature |
| + | |||
| + | 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. | ||
| 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 37: | Line 36: | ||
| 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. | + | |
node_types.txt · Last modified: 01/17/2024 21:18 by crowetic