Dappy is a first of its kind ultra-secure web browser and name system. It is a no-DNS system that has been built with a decentralized and zero-trust approach from the start.
The DNS is a service in which you send a request to a given corporation or association (also called DNS service provider), the request contains the domain name, if found, the answer will include the IP address corresponding to this domain name.
Either the corporation you query tells you that example.com corresponds to an address in its database, either it sends back a not found error. DNS is centralized, a DNS lookup request is atomic/unique, you put 100% of your trust in the corporation you query, you have no way of questioning the answer, or asking another service if he has the same data regarding a domain name. This is called a single source of truth.
The system is neither bad or good, it just works that way. In some case you'll be happy that DNS service providers, registrars, lawyers and human employees constitute a chain that successfully turns your obscure IP address into a cool domain name. In some case, often when a registrar is hacked, or lawyers decide to take your domain name and give it to amazon, you may desire a more trustless, decentralized system.
Dappy is a service that, among other things, resolves domain names to IP addresses (we call them "names" and not "domain names" because they have no extensions). The system works in such a way that there are no single source of truth anymore, the mechanism is called multi-request. You basically ask many "DNS service providers" (5, 10, 20 etc.) for a given name, instead of a single one, and then perform a reconciliation at the browser level.
The accuracy, and trust one may put into this system is potentially superior to that of the DNS by one or two orders of magnitude. There is no magic, we simply apply the basic principle of decentralization, or distributed trust to a name system.
This is nice, but who decides that bob owns name bob, mike owns mike, and amazon owns amazon ?
Good question, this is where the blockchain thing comes in. It is all handled into a smart contract, either a name is available and you can purchase it, either it's not, meaning that someone already controls it and can set the IP address (and TLS certificate) to point to his server. No one owns this smart contract, once it's deployed it's basically here to stay, the underlying blockchain infrastructure keeps it alive. The corporations that get requested by browsers for DNS lookups just have to look into this smart contract to resolve, or not resolve a name to an IP address.
This basically is the dappy system.
This article was meant to stay short if you want to know more feel free to visit the website https://dappy.tech and join the discord community to ask question https://discord.gg/8Cu5UFV
The dappy team is not only developping a web browser and a name system, we are also developing a unified token interface and smart contracts for RChain platform. Here we'd like to share thoughts and experience on the need we have to monitor onchain data, and how we did it.
Hey everyone, there hasn't been any newsletters in a while, let's give an update on the project. RChain token, one of the main components of the dappy ecosystem is constantly improved and worked on. We are now at release 12.0.1, the NFT expiration is 100% coded and tested. This means that it's ready to receive the dappy name system
Dappy's goal is to build an ultra-trustworthy name system, and to expand the security features of current browsers in order to allow for critical industries to safely and easily distribute public web applications.