This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
qortal_data_network_qdn [12/07/2022 14:39] – gfactor | qortal_data_network_qdn [11/02/2023 14:31] – [Qortal Data Network (QDN)] crowetic | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Qortal Data Network (QDN) ====== | ====== Qortal Data Network (QDN) ====== | ||
{{: | {{: | ||
- | {{:: | ||
- | **Qortal Data Network (QDN) is LIVE! Although there is a data size limit of 500MB as we begin building this into a scalable solution to rebuild the Internet as we know it. Bear with us!** | ||
- | QDN is a 100% FREE solution to rebuilding the Internet in a decentralized fashion. Instead of paying third-parties for a domain name, simply register a name on Qortal | + | =====QDN - Qortal |
- | Now what if you come across ‘illicit’ content during your QDN browsing? Simply click the red x next to the website you’ve viewed and delete the data. Of course this raises a lot of concerns for the typical user and we completely understand. Please keep in mind that we are building a set of layers to Qortal’s infrastructure and perfecting this will take time. The plan is to develop | + | QDN (Qortal |
- | Data can be relayed through our nodes, in order for other nodes to communicate. All of this data is end-to-end encrypted, and is also chunked so the data is not relayed on a single node. The data being relayed is only on your node long enough to conduct the transfer, and is deleted afterwards automatically. Users can choose to opt out of relay mode if their lack of understanding with this matter raises too much concern. Getting data around the network is difficult and requires more fine tuning- even with relay mode enabled (which helps the network). To disable relay mode, add this setting to your json settings: | + | QDN is **unlike any other data network** in the world, and has many unique features |
- | < | + | The Qortal Data Network provides the ability to: |
- | QDN is accessible to everyone and does not cost anything. The only cost is registering a name (current name registration fee can be found on the [[Qortal Status Updates]] page. | + | * Host Websites |
+ | * Host Applications | ||
+ | * Communications | ||
+ | * Host Public Data | ||
+ | * Host Private Data | ||
+ | * Build nearly | ||
- | We came up with a method of data storage that could be better than using IPFS. 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. | + | The Qortal Data Network is completely **encrypted and chunked** - This means that the data transmitted from node-to-node is completely encrypted, and unable |
- | Here are two examples of sites hosted | + | An internet service provider wishes to ' |
- | http:// | + | On QDN, however, they would not be able to see any of this, the only information they would be able to obtain, would be that there is a connection from one computer to another, sending data (that has no meaning whatsoever) back and forth. They would be completely unable to determine what this data is, who published it, where it came from initially, etc. |
- | http:// | + | This makes it essentially completely unnecessary to run things like a ' |
- | Here is an example of a data node that acts as a gateway for traditional users - allowing them to access QDN sites without having | + | Ultimately, QDN is MUCH more secure than any other data network, and attempting |
- | These are older static copies of the Qortal website and wiki so they may not be up to date FYI. | ||
- | At first, it will be more simple, since we will only be doing simple static websites, and we can convert wordpress sites to be hosted on Qortal' | + | (this page is in process of being updated, and completely re-written, more information coming soon.) |
- | Data hosting will essentially be a clone of Qortal, without the synchronizer and a different chain that will keep track of the data hashes. The data transmission will be done like a torrent. The more peers you have the more redundant copies you will have. You will obtain peers by obtaining ' | ||
- | 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/ | ||
- | |||
- | Here’s the code being worked on so far for the data hosting: https:// | ||
- | |||
- | ===== Notes From CalDescent ===== | ||
- | |||
- | The Qortal data nodes currently work very similarly to an AWS S3 bucket (but in a decentralized way). They essentially give you an interface to add, retrieve and update static " | ||
- | |||
- | I am also in the process of building several " | ||
- | |||
- | -Static site serving (mostly finished) | ||
- | -Git repositories | ||
- | -Blog | ||
- | |||
- | The idea with these interfaces is they allow static file structures to be served and written to by the data nodes. For static sites, it's mostly just a case of serving them over a webserver, but for blogs it will be a custom plugin that renders the blog and backs the data off to JSON files - using it as the database essentially. | ||
- | |||
- | For git repositories, | ||
- | |||
- | I hadn't thought of doing a " | ||
- | |||
- | In terms of dynamic content, I haven' | ||
- | |||
- | Databases are even more difficult. I will probably start by making a MySQL interface that backs off its data to the static files. But I worry that it will be impractical for a lot of use cases, because each INSERT or UPDATE would require a new transaction to be published on chain. So it would only work for infrequent updates, such as a basic website. | ||
- | |||
- | We are limiting the amount of transactions / resource updates using a proof of work nonce, so that will stop someone from being able to spam the chain constantly, which will have the effect of limiting to only "low throughput" | ||
- | |||
- | Here's how " | ||
- | |||
- | -Add a MySQL resource and publish the initial database schema and data. This would create a transaction on chain and sync the associated data around the network. | ||
- | -Add a PHP resource and publish your initial PHP files. | ||
- | -Inside your PHP database class you would point it to the Qortal MySQL instance. This would essentially map to http:// | ||
- | -Deploy the PHP resource which would add a transaction and sync its data around the network. | ||
- | -Other users could then run the PHP app (and database) using by visiting `http:// | ||
- | -The MySQL resource would have permissions set so that it can be updated by all (or a certain group of people, or just the original creator - depending on the use case). | ||
- | -Everyone' | ||
- | |||
- | Obviously the approach above has major drawbacks for serious / high throughput use cases, and also ones that need to store sensitive data. But it would work in projects that update their data infrequently (e.g. WordPress), so it could be a fairly straightforward way to get started. Most of the foundations are in place for this already. | ||
- | |||
- | The current plan is to include a java-based version of httrack in the data nodes, so that it can automatically convert a URL and add the static copy to the data chain. After that, we'll have the ability to include a bot in the data nodes that watches a given URL for changes and then automatically creates a static copy and publishes any differences to the chain each time. I'm not sure whether this feature will make it into v1 of data nodes; it will most depend on whether there is a java-based static site downloader already available. If not we'll have to create our own, which will take a while. | ||
- | |||
- | 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 " | ||
- | |||
- | Name registration doubles as a “domain name” for websites and other data hosted by that account (in v3.0). Currently owned domain names will not be possible to transfer registration to your account on Qortal. They are completely separate and there won't be any way of linking them. Traditional domain names rely on " | ||
- | |||
- | You can absolutely access it via a separate browser. There are a couple of options: | ||
- | |||
- | 1. Using the API on a public/ | ||
- | |||
- | 2. Using the “domain mapping” feature with existing DNS - e.g http:// | ||
- | |||
- | When setting up domain mapping: you will need to add the domain name to your node(s) and then point the domain at them via DNS. You can have multiple nodes behind a single domain for better redundancy. | ||
- | |||
- | This “gateway” feature is now developed, so we can already support gateways to the Qortal network via an existing domain. E.g: < | ||
- | |||
- | or | ||
- | |||
- | < | ||
- | |||
- | etc. | ||
- | |||
- | Basically anyone who is willing to can provide access to the entire Qortal network of websites via a domain they own. They just have to enable the gateway service in their node’s settings (and point their domain at the node using DNS). You can always connect the traditional domain name to your Qortal site if you want to. It will just rely on centralised components, unlike using a registered name within Qortal. | ||
- | |||
- | ===== We Use PoW For Data Uploads ===== | ||
- | |||
- | We use PoW for data uploads to reduce the ability for people to spam the chain with data. For most transaction types in Qortal, we use a 0.001 QORT transaction fee. For QDN we decided to remove the fee and replace it with a " | ||
- | |||
- | The main reason for doing this for QDN was because we were planning on putting data hashes on a sidechain that wouldn' |