Storing data on a public blockchain is very different from storing data on a traditional database. One of the main differences is access to the data. Thread #BlockBase #EOS #EOSIO (1/7)

Whereas when storing data on a database there is the assumption that that data is private and will remain private, storing data on a public blockchain should have the assumption that that data is public and will remain public. (2/7)

While on the first case private data may become public, something that happens every time there is a leak of information, on the second case public data will never become private again. When it gets public, it stays public. The genie is out of the bottle. (3/7)

Data privacy concerns might not seem that important when storing data on a private database. At least until the data is leaked…and the damage is done. Blockchain adoption thus presents a great opportunity for data privacy and for regaining ownership over one's data. (4/7)

Surprisingly, few blockchains worry about privacy at all. For most cases, all data stored there is public for everyone to read. Smart contract based blockchains have the same issue since any arbitrary data may be stored there and no encryption mechanisms are provided. (5/7)

This lack of privacy should be a deal breaker for many businesses considering adopting smart contract technologies. This is why BlockBase was designed from the ground up to deal with data privacy. (6/7)

All data stored on BlockBase is encrypted by default and can be queried without revealing its contents to the network providers. This functionality is unique, and it's opensource, ready to use, and a gift to our community. (7/7)

#EOS #EOSIO