Links table
Abstract and 1 introduction
2 background and relevant work and 2.1 from Bitcoin to Blockchains
2.2 Blockchains open and permission
2.3 Blocchains
3 series of inquiries across the series and 3.1 Integrated data form
3.2 Engineering processing and inquiries
4 Evaluation of the feasibility of implementation and 4.1 programs and devices
4.2 Treatment of the query
4.3 Discussion
5 Conclusion and expectations, approval, and references
2.3 Blocchains
The inter -employment is widely recognized for transactions that extend to multiple groups, established in the crosses of the crossed chain and similar concepts that are practically implemented in the so -called “bridges”. Moreover, the efforts made towards unifying heterogeneous data began not only the inquiry languages.
Blusies of the crossed chain. Blossoms are usually started via a protocol on the original Blockchain, where the symbols or arbitrary data are locked to prevent further transportation at the beginning. Then mutual transaction is issued on a secondary Blockchain for the initial replacement of the crossed chain, which means that another party often compensates for the different origins in the second series. This deal includes an encryption guide with a secret that makes symbols on the initial chain. Finally, the opposite end recovers the symbols from the original series. A wide range of protocols and variables has been developed on this founding principle [20,25]. For the exhibitions of the atomic chain [13,30]Atomicity is guaranteed for all transfers involved in the cross -chain swap. However, practical applications in bridges may appear different properties and assurances, not necessarily providing corn or other guarantees to complete the stock exchange. Bridges are used primarily to exchange encoded currency. For example, Multichain[11]Executing[12]And others[13] Facilitate the bares across the series between Ethereum, Avalanche and others. However, the bodies and bridges across the chain lack uniformity and do not provide uniforms or inquiries.
Heterogeneous data. The evaluation efforts are ongoing to deal with the issue of heterogeneous data, with the previously dispersed work that addresses the uniform access. For ethereum, one study [19] The conceptual plan derived from the initial data structures in Blockchain. in [5]The query language is proposed to the content of the blocs and transactions. This language design tends to build a SQL phrase and supports concepts such as projection and choice within Ethereum. For data analysis, a framework was proposed and implemented on the basis of Scala [2]Employ SQL or Nosql along with assembly functions and similar analysis methods.
Another approach [7] Data warehouse details and ETL process to analyze ETHEREUM data using the SQL standard with a multi -dimensional data form for the Detament Dimensions and support data collection. Although these studies and similar studies may communicate with multiple groups, they fail to provide access to homogeneous data, queries, or simultaneous access to data across multiple groups.
An additional work on the basis of SQL includes [17],, A study that uses multiple groups to fill a standard MySQL database with a third -party Google Begkorier service. However, relying on third -party services as data sources presents another common problem in previous research, as verification of the validity of Blockchain data is impossible or strongly restricted. Other methods include general connectors between Blockchains and Blockchains that combine with others and hybrid curricula [3].
Betical operation restrictions in previous research. Current solutions face Blockchains in parallel, and (L4.) Lost in verification of Blockchain data. The current focus is on the crosses of the crossed chain and the analysis of isolated data instead of data integration. The proposed inquiry language here seeks to reduce these restrictions by proposing an integrated data model for unified access (L1), building a total of grammar and conclusion for uniform access It is locally multiple to verify transactions (L4.).
author:
(1) Felix Herner[0000 −0002 −2768 −2342]Digital and Information Systems Group, University of Friborg, Switzerland ([email protected]).
[11] 2023-06-30
[12] 2023-06-30
[13] 2023-06-30
