Get best of the week

Ontology Launches Layer 2, Contributing to More Integrated Public Chain Platform

image

Foreword


Imagine a scenario in which the blockchain platform is developing rapidly, and the number of users is growing rapidly, reaching tens of millions, which leads to a sharp increase in associated costs in a short time. What strategies are needed at this stage to maintain operational efficiency without compromising the pace of development due to complex reconciliation and validation processes? As many business ventures agree, scalability should be a priority.

As an off-chain scaling technology, Ontology Layer 2 offers higher performance and lower performance. Enterprises can safely store a large number of transaction records outside the chain, and then transfer them to the chain when they need to interact, reducing user transaction costs and dramatically improving productivity.

Introduction


As stated in the Aristotle 2020 roadmap, in combination with the Ontology, Wasm-JIT, Multi-VM cross-chain and other advanced core technologies, Ontology Layer 2 now shows better performance than other Tier 2 solutions. This is reflected in its low cost at storage, multilingual support and full compatibility of analysis and execution versions. Ensuring unhindered interaction of deployment contracts, for example, launching several virtual operating systems on one computer, which increases execution efficiency and reduces processing costs.

The working process


Ontology Tier 2 consists of 3 main parts: Ontology Tier 2 deposit, Ontology Tier 2 findings, Tier 2 transactions and security guarantee.

In a Level 2 trading center, users can complete transactions, fulfill contract requests, and sign contracts. This transaction may be the same as the Ontology main chain transaction format, or it may be different. Transactional collectors (called collectors, hereinafter referred to as the collector) are responsible for collecting user Level 2 transactions. There may be several collectors throughout the process. Users can also stream their Level 2 transactions to multiple collectors.

The collector periodically packs the collected Layer 2 transactions and runs them to create a new state. The collector is also responsible for transferring the root of the new state to the main Ontology chain. After the transactions packaged in the Level 2 block, the root of the new state becomes the state of the Level 2 block. The applicant is responsible for checking the status of the Level 2 block presented by the Collector in the main Ontology chain. This requires the Bidder to synchronize the Level 2 block through the Collector in order to maintain full global status.
ACKNOWLEDGMENT OF THE ACCOUNT STATUS INCLUDES INFORMATION ABOUT THE STATUS OF THE ACCOUNT AND ITS CONFIRMATION WHICH CAN BE OBTAINED FROM COLLECTOR AND CHALLENGER REQUESTS. ONLY THEY SUPPORT THE FULL GLOBAL STATE.

Deposit at Level 2


  1. «Deposit» Ontology. 2. «unreleased».
  2. , Ontology . 2 . 2. 2 Ontology, .
  3. «released».

Ontology


  1. 2 « » .
  2. Collector Withdraw Withdraw 2. 2 Ontology .
  3. , «not released».
  4. .
  5. , «released».

2


2


  1. The user creates a Level 2 transaction “Transfer” and transfers it to the Collector.
  2. The collector packs the transfer transaction and other transactions into a Level 2 block, executes transactions in the block, and transfers the status of this level 2 block to the main Ontology chain.
  3. Wait for status confirmation.

Safety guarantee


After the Operator sends the status of the Level 2 block to the main Ontology chain, the Bidder can also complete the Level 2 block transaction and check the correctness of the Level 2 block status. If something is not right, the Bidder will collect evidence of fraud and send a Level 2 smart contract. to challenge the Operator.

How to use


Ontology Level 2 is currently available on Ontology TestNet for developers to experiment with.

Link

Link to documentation

In the next article, we will present a detailed comparison of performance with Level 2 in other chains.

Appendix: terms


Level 2 Transactions


The user has made a request for the transfer or performance of the contract at Level 2 and has already signed it. This transaction may be the same as the Ontology main chain transaction format, or it may be different.

Collector


Collector is a Tier 2 transaction collector. It is responsible for collecting the user's Tier 2 transactions, validating and executing the transaction. Each time a Level 2 block is generated, the collector is responsible for executing transactions in the block, updating status and generating Level 2 contracts, which can be interpreted as confirmation of the status used to ensure security.

Level 2 Block


Collector periodically wraps collected Level 2 transactions, generates a block containing all Level 2 transactions, and generates a new Level 2 block.

Level 2 State


Collector performs batch transactions in a Level 2 block, updates the state, sorts all updated state data to create the Merkle tree, and computes the root hash of the Merkle tree. The root hash is the state of a Level 2 block.

Operator


The operator is responsible for Level 2 security and is responsible for monitoring whether a token is being transferred to Level 2 or a token transfer transaction from Level 2 to the main Ontology chain. The operator is also responsible for periodically sending confirmation of Level 2 status. As confirmation, you can go to the Ontology network.

Challenger


The Applicant is responsible for checking the status confirmation submitted by the Operator to the main Ontology chain. This requires the applicant to synchronize Level 2 transactions from the operator or chain to maintain full global status. After the Bidder synchronously executes the transaction and updates the status, he can check the validation of the status presented by the Operator on the network. If there are problems, the Bidder may create a fraud proof challenge, which a Level 2 contract can explain.

Account Status Verification


Achieved with Merkle proof, account status confirmation can be obtained from Operators and Bidders. They are the only parties that maintain a complete global state.

Fraud proof


Confirmation of fraud includes confirmation of the status of the account before the current update of the block of the 2nd level.

The previous Level 2 block status certificate and the submitted account status certificate confirm the legitimacy of the old state before the upgrade. Proof that the old state is legal can be obtained by running the current block.

Enterprise-oriented blockchain Ontology is ready to help enterprises transform and modernize their business. If you have problems with autonomous scalability, virtual machines or a full set of technical systems, please contact us at contact@ont.io.

Learn more about Ontology


Fresh, up-to-date information and pleasant communication in our Telegram chat - Telegram Russian

Also, subscribe and study our: Ontology website - GitHub - Discord - Twitter - Reddit

More articles:


All Articles