LogoLogo
  • Welcome To INERY
  • INERY WHITEPAPER
    • Abstract
    • 1.0 Overview
      • 1.1 Introduction
    • 2.0 What Is INERY?
      • Key Functionalities Of Inery
    • 3.0 Features Of Inery
      • 3.1 Decentralized and Unstoppable
      • 3.2 Immutability
      • 3.3 Security
      • 3.4 Database Owner Control
      • 3.5 Complex Queries
      • 3.6 High Throughput
      • 3.7 Affordable
      • 3.8 Byzantine Fault Tolerance (aBFT)
    • 4.0 Inery Ecosystem
    • 5.0 IneryDB
      • IneryDB Functionalities
      • Cross-chain data management
      • IneryDB Design Goals
      • IneryDB Use Cases
      • IneryDB as DBaaS
    • 6.0 Inery Blockchain
    • 7.0 Use Cases
    • 8.0 Inery Token Utility
    • 9.0 Tokenomics
    • 10.0 Vesting Schedules
    • 11.0 Roadmap
      • 2020
        • Q1 2020
        • Q2 2020
        • Q3 2020
        • Q4 2020
      • 2021
        • Q1 2021
        • Q2 2021
        • Q3 2021
        • Q4 2021
      • 2022
        • Q1 2022
        • Q2 2022
        • Q3 2022
        • Q4 2022
        • Future
      • 2023
        • Q1 2023
        • Q2 2023
        • Q3 2023
        • Q4 2023
      • 2024
        • Q1 2024
        • Q2 2024
        • Q3 2024
        • Q4 2024
    • 12.0 Inery Official Links
Powered by GitBook
On this page
  1. INERY WHITEPAPER
  2. 3.0 Features Of Inery

3.4 Database Owner Control

Conventional databases empower centralized entities such as tech monopolies that access users’ data and engage in unethical practices for their own personal gain. Inery’s solution gives the control of users’ data back in their hands.

With the implementation of value contracts, access to databases is allowed only to the owner (or owners) of the value contract. The database and actions upon the value contracts are pre-defined. Custom permissions to users for data additions have also been defined in the value contracts. This is managed through an authorization managed by a set of private key holders that can push actions in the value contract.

Blockchain manages and checks every transaction to make sure it is not a duplicate transaction and prevents double spending of the data by making sure that the transfer of an output (data) was not previously transferred or spent. This empowers users to activate the potential of their untapped data.

Previous3.3 SecurityNext3.5 Complex Queries

Last updated 3 years ago