The increase in the adoption of blockchain technology in different application domains e.g., healthcare systems, supplychain management, has raised the demand for a data query mechanism on blockchain. Since current blockchain systems lack the support for querying data with embedded security and privacy guarantees, there exists inherent security and privacy concerns on those systems. In particular, existing systems require users to submit queries to blockchain operators (e.g., a node validator) in plaintext. This directly jeopardizes users' privacy as the submitted queries may contain sensitive information, e.g., location or gender preferences, that the users may not be comfortable sharing. On the other hand, currently, the only way for users to ensure integrity of the query result is to maintain the entire blockchain database and perform the queries locally. Doing so incurs high storage and computational costs on the users, precluding this approach to be practically deployable on common light-weight devices (e.g., smartphones). To this end, this paper proposes $\pi$QLB, a query language for blockchain systems that ensures both confidentiality of query inputs and integrity of query results. Additionally, $\pi$QLB enables SQL-like queries over the blockchain data by introducing relational data semantics into the existing blockchain database. $\pi$QLB has applied the recent cryptography primitive, i.e., function secret sharing (FSS), to achieve confidentiality. To support integrity, we extend the traditional FSS setting in such a way that integrity of FSS results can be efficiently verified. Successful verification indicates absence of malicious behaviors on the servers, allowing the user to establish trust from the result. To the best of our knowledge, $\pi$QLB is the first query model designed for blockchain databases with support for confidentiality, integrity, and SQL-like queries.
翻译:在不同应用领域(例如,医疗保健系统、供应链管理等)采用链链技术的增加,提高了在不同应用领域(例如,医疗保健系统、供应链管理)采用链链技术的程度,提高了对条链上数据查询机制的需求。由于目前的链链系统缺乏对内嵌安全和隐私保障的查询数据支持,因此这些系统存在固有的安全和隐私问题。特别是,现有系统要求用户向条链操作员(例如,一个节点验证器)提交查询,这直接危及用户隐私,因为所提交的查询可能包含敏感信息,例如,传统内部系统、地点或性别偏好,用户可能不愿分享。另一方面,目前用户确保查询结果完整性的唯一办法是维护整个链链和隐私保障数据,因此,用户的存储和计算成本很高,无法将这一方法实际用于普通的轻量设备(例如,智能手机)。为此,本文件首先提议用“美元”、“美元”、“地点”、“地点”、“地点”、“地点”、“地点”、“地点”、“地点”、“地点”、“地点”、“地点”、“地点”、“地点”、“地点”、“地点”、“地点”、“地点”、“地点”、“地点”、“地点”、“地点”、“地点、“地点”、“地点”、“地点、“地点”、“地点”、“地点”、“地点”、“地点”、“地点”、“地点”、“地点、“地点”、“地点”、“地点”、“地点、“地点”、“地点”、“地点”、“地点”等”、“地点”等、“地点、“地点、“、“地点”、“地点”、“地点”等”、“地点”、“地点”、“地点、“地点、“等”等”、“地点”、“地点”、“地点”、“地点”等”。 等”、“地点、“地点”、“地点、“地点”等”等”、“地点”等”、“地点”、“地点、“地点、“地点、“地点、“地点”等”。 等”。 等”。 等”。 和“等”。 等”。 等”、“地点”、“地点”等”。 为此、“地点”。 等”、“地点”、“地点”等”。 为此、