Introduction

In recent years many projects have been initiated with the intent of offering complete decentralized applications. The best example of a decentralized application is the blockchain with its distributed ledger and the ability to perform transactions without the need of a central authority.

However, even considering the complexity of managing transactions in a decentralized way, the blockchain and the cryptocurrencies remain a very specific kind of application, with very simple requirements regarding the storage of transaction-related data.

With the introduction of smart contracts, blockchain projects have introduced new functionalities, without really introducing additional complexity and volume regarding structured data.

The challenge

The expectation of creating completely decentralized applications changes abruptly the situation.

A team that wants to develop a decentralized application has the choice of using current blockchain technologies for managing monetization or maybe user identity but must rely on centralized backend solutions to store the “real” application data.

With real “application data” it is meant the terabytes or petabytes of information, typically organized in table and documents, which make the application work.

The most common backend solutions are based on several database technologies like:

Relational database management systems

NoSQL (key/value) databases

Document oriented databases

There are several competitors in the structured data storage world, most of them can master the management of petabytes or even exabytes of data.

However, none of them is decentralized. All of the existing solutions can be corrupted or even shut down by a government, a central authority or a malicious organization.

Does it make sense to build an application where only the monetization and smart contract part is decentralized if the application data itself is centralized?

The obvious answer is: no!

The solution

Ties.DB is the solution to this kind of problems. Ties.DB is the first distributed and decentralized database management system.

The Ties.DB public database instance consists of a network of nodes of different size that contributes to the storage and management of database tables. Everybody running a node will be able to insert, manipulate and query structured data in the Ties.DB public instance. This will be as easy as it is to enter data in common relational or NoSQL database management systems, with the advantage of not needing to care about redundancy, backup or high availability.

Data is stored in Ties.DB in an inherently redundant way. Data owners will not need to take care of backups and high availability like with on premise solutions and will not have to worry about a central authority, ownership of data itself or eventual access by government organizations like secret services like when hosting own data on cloud platforms. In addition to that, Ties.DB is censorship resistant, as data is encrypted using private keys controlled by the data owner.

A revolution in the way data is exchanged

Despite the huge advantages in security and privacy, Ties.DB offers indeed an extremely straight forward way of sharing data with other users or organizations.

As there is only a huge public instance of Ties.DB, all users and organizations are managing their data in the same database. Unencrypted data belonging to an organization is readable by any other user in the database network, but users and organizations can encrypt their valuable data. To make their own valuable data available to other organizations using Ties.DB, it is sufficient to give it the ability to decrypt the data, and the partner organizations need only to run a query on the granted data.

As a possible use case, imagine a company MyIM that offers a decentralized instant messaging and payment service and an E-Commerce company MyBazaar that sells items online using a decentralized e-commerce application. Both companies use Ties.DB as a backend for their applications. If MyBazaar wants to offer MyIM as a payment service to its customers, it just needs to buy the ability to decrypt the required data from MyIM.

Once the trade is completed, MyBazaar will access needed database objects without the need of complex data exchange procedures like using FTP servers or complicated ETL processes.

The same procedure could be used by insurance companies to access weather or traffic information from external services, or any company that wants to outsource its data science tasks to trusted specialized consulting companies.

For example, a company closes a deal with an analytics consultancy for some analysis on its data. Both the committer and the consultancy owns Ties.DB nodes. The company could just grant access to own raw data stored in Ties.DB to the analytics consultancy. The consultancy would elaborate complex analysis, store the results on Ties.DB and grant access to them to its customer.

Many examples like these are possible with Ties.DB.

A new economy of structured data

The economy of Ties.DB will be based on a system of rewards for users and organizations that hosts the nodes in the distributed database network. Organizations that simply want to store or query data without running a node will need to pay the network for the service. The currency used to buy and sell Ties.DB services is the TIE tokens.

However, another usage of the TIE token is the ability to stipulate trade deals over data usage through the Ties.Network.

Ties.Network is a professional social network for managing business transactions between organizations and IT professionals. Business transactions can concern work performed in a project or a team but also data usage in Ties.DB.

In the above examples concerning the right to access data owned by the different parties of the business deals, Ties.Network would act as the settlement platform for such deals.

In this way, a completely new economy would arise around structured data stored in Ties.DB.

Website & BitcoinTalk:

https://ties.network

https://bitcointalk.org/index.php?topic=2071592

Follow us:

https://blog.ties.network

https://twitter.com/tiesnetwork

https://reddit.com/r/tiesnetwork

https://facebook.com/tiesdb

Communication:

https://t.me/tiesnetwork

https://slack.ties.network

Questions:

info@ties.network