How MaataData's Blockchain Database Is More Secure

Why current database technology is not secure

There are four basic data technology deficiency areas that must be solved before a general secure data technology could be presented.

· A distribution protocol for effective decentralization

· Encryption of the public ledger for privacy

· An integrated database for use cases

· And an integrated scalability for bandwidth

Although, current blockchains have present a public ledger to verify signatures and have some functionality to provide synchronized replication in a network of nodes, it has not a clear protocol for distribution for decentralization, encryption on the public ledger for privacy, bandwidth scalability for high volume enterprise applications, and nor a database setup for use cases.

The typical blockchain consensus protocol is by synchronizing a replication of multiple copies of the blockchain data of server nodes in a network.

Proof of work nor proof of stake protocols have an effective consensus mechanisms to point out the node that must produce the next block for the synchronize replication throughout the network of nodes.

A representative decentralization of nodes is nothing more eventually than a centralized group of nodes.

These consensus mechanisms are or lead to a centralization of nodes which pose eventually a security risk.

The first circle is the decentralized nodes that manage the network which must be as wide as possible, but the second circle of decentralization str the users or the owners of the value (recorded in the network) with its passive nodes.

Distribution

The distribution of a block through the network must be solved to inherently produce a decentralized network of nodes.

The distribution of a block to the next nodes must be exponentially effective (to form a wide circle) to fulfill the promise of the immutability of decentralization.

Encrypted for privacy

The data on the blockchain must be encrypted for privacy.

On current cryptocurrency blockchains, the transaction amount must be verified against the account balance therefore the blockchain data could not be encrypted.

But there are many other use cases where the signature can be verified but the blockchain data would need to be encrypted, like storage of sensitive documents, private chat app, etc.

The transaction payment use case where verification is necessary can only be implemented after other technologies is integrated with the blockchain setup.

Database needs to be integrated

To address the database integration to the blockchain setup, both the database construct and the blockchain construct need adjustment to be able to merge as a single technology, which we call a blockchain database.

· The database must handle the keys for its indexes, but it cannot store any data but only pointers to the data. The keys of the database can be hashed.

· The database cannot update or delete data or pointers

· The database creation or generation must depend on the immutability of the blockchain

· The database can only add data or pointers to its index keys

· The blockchain must separate the transaction signatures and data. The blockchain transaction points to its data through the storage engines

· The database data pointers point to the blockchain which in turns points to the data through the storage engine

MaataData's blockchain network is a secure database

We were able to integrate data security features of the blockchain with database functionality with the following features.

Our Blockchain's Security

Authentication

The signing of a transactions or records and verification by each node on the network

Cannot be edited

No updates nor deletes of any transaction are possible but secured by the hashes of the blockchain

Immutability

Immutability of independent nodes provides live backups in the network

Our Secure Database Functionality

Encryption

End-to-end encryption of all data in transition and at rest.

Distribution

Effectively distribute blocks exponentially in a network to 8 billion nodes under one second

Scalability

By adding parallel servers to a node, the speed and capacity tested could increase to 1 million+ transactions per second speed with ten 24 core servers

API

We have developed an API that looks at the data on the blockchain like records, fields, and indexes.

Write/Read

Normally, the write/read functions are private and can only be accessed by the user with password authentication. We can also make write/read public access for all users.

Multiple-Users

It is possible to transfer and have activity between databases of each user in applications like chats and money transfers.

Latency

Most data access is reading data. Node servers can globally be deployed with high read speed access. Write speed globally is under a second.