Loading...
Pitch or more infos?contact@dnp.technology
This page is under construction. More coming soon.

Our Vision

Short Term (3-5 Years)

Decentral Ecosystem for IoT devices and p2p-Applications

By creating a DNP Background-Service that abstracts the framework in a single instance for common desktop and mobile operating systems, we provide the necessary functionality for application developers to choose to develop their applications in a peer-to-peer design instead of using server/client models.

By providing the framework as an open standard with open source tools, device manufacturers can benefit from a single standardised approach to interoperability in a world of ever increasing complexity. The “Internet of Things” is largely incompatible and despite its nature of distributed devices, relies heavily on centralised systems with incompatible communication protocols. With DNP, IoT becomes IoT 2.0.

Applications or devices using the DNP network may facilitate communication between people, between devices, or between devices and people. DNP doesn’t distinguish between people and devices fundamentally - it is simply a matter of presentation and semantic purpose.

This is achieved by DNP acting as an abstraction layer not only for communication but also for purpose and meaning of communication. This allows applications to be developed more generally and with human purposes in mind. “Client applications” no longer need to be created for specific “server applications”. Now, they can simply submit requests to the network for information and get meaningful answers without needing to know anything about the technology behind the source of those answers. As more application developers and device manufacturers build on the DNP framework, we position DNP as the single ecosystem for a world of interoperable self-sovereign systems.

Mid Term (5-10 Years)

Decentral Ecosystem for Operatively Autonomous Devices


Operatively autonomous devices are devices that interact with one another autonomously for all of their typical daily functions, no longer requiring human facilitation for routine operative tasks. For example, a machine that requires solely periodic cleaning is “operatively autonomous” if it cleans itself or itself organises for someone/something else to clean it. A machine that requires both periodic cleaning and supply refilling however is only partially autonomous if it has a self cleaning function. Thus to be fully autonomous, a machine must - in the vast majority of cases - have an autonomous method of external communication.

This can be viewed as having a certain level of autonomy, from “fully manual” through to “completely autonomous”. To use a car as an example, a basic car is fully manual. A more advanced car has driver assistant technology such as maintaining distance, self-parking, and partial self-driving in specific conditions (e.g. highway). This is our current level of technology. The next step is clearly cars that are completely self-driving. Finally, we come to fully operationally autonomous cars that not only drive themselves, but also organise their own service, maintenance, and refuelling.

We aim to provide this operational autonomy by adding to the emerging field of artificially intelligent devices the DNP framework as the communication layer that these devices use to exchange information about their requirements and offers. This can in some ways be thought of as a virtual “automated services marketplace”. The aforementioned machine may send a message advertising its requirements for cleaning, and various offers are made from services that provide cleaning (maybe some human, maybe some not). The machine uses algorithms - potentially augmented with machine learning - to choose the offer that suits it best based on the various factors involved such as cost, time, and reputation/quality of the service provider.

Hereby, we become a key part of the underlying ecosystem infrastructure for the emerging world of operatively autonomous devices. The device manufacturers are responsible for building the devices and creating algorithms and AI to make them fit for the task, but without any need to organise the communication layer.

Long Term (>10 Years)

Base-layer for the "Future Internet"



The internet is already a decentralised system. It was designed this way from the start and all of the core fundamental protocols built on it are agnostic to the position of the system. A home computer connected via DSL has an IP address that is fundamentally the same kind of thing as the IP address of a server run by a giant multinational company. Anyone can start a web server or file server on their home computer without asking permission from a centralised authority.

This is all true for the basic design of the internet, but it becomes less true when we look at the typical internet services now being offered. The majority of internet services built for the last 30 years have been centralised. Tim Berners-Lee - the creator of the World Wide Web - has publicly stated that the internet has become fundamentally broken and cites this centralisation as a primary cause.

DNP has the ability to reverse this trend of centralisation, bringing the internet back to a true internet of peers with self-sovereign data. As the world becomes comfortable with peer to peer technology through the successful realisation of our short term and mid term visions, the protocol becomes as fundamental to the internet as HTTP is today.

In this “Future Internet”, the landscape is no longer dominated by large central service providers. While these companies will continue to play a role, much of their control and power has been dissolved amongst individual users who can now provide their information and services directly to their peers as they choose.

Some service providers that act solely as data middle-men or in facilitative roles will disappear entirely, as their function is replaced by simple application logic on top of the DNP network.
Top