The Scuba Network Features

The Scuba Network has the following characteristics:

• Simplified design to avoid the cost of maintaining and operating a chain

• No difficulty in building an independent chain ecosystem

• Can be deployed and serve for any EVM-compatible chain

• Inherits the security assumptions of the Host Network it is connected to, avoiding complex security and trust issues

• Can serve as a scaling solution for the Host Network while providing privacy services

• Low gas fees

• Better user experience (similar to AA wallet experience for users and a simplified SDK for developers)

• Allows for the freedom to create different tokenomics to incentivize Scuba Node, Challenger, and Bundler

Compared to traditional Optimistic Rollup, Scuba Network does not require a long Challenge Period for the following reasons:

Scuba Network，as a Layer 2, adopts a similar approach to Op Rollup, so it has most of the Op Rollup's features. The difference is that since Scuba carries only Zk proofs, there is no need to consider the waiting period for fraud proofs when executing transactions on Scuba. Users can verify transactions related to themselves in advance of the Challengers and send their new transactions based on the local verification results.

Conflict Resolution: When users or Challengers have objections to the verification results of an Observer (Scuba Node), they can submit a Failed Proof to the ScubaArbitratror in Scuba Contracts. ScubaArbitratror can then resolve the conflict. Exemplar conflict resolution logics includes:

• Stake-based Conflict Resolve: Challenger can stake a certain amount of tokens in ScubaArbiter to become a Super Challenger. When ScubaArbiter collects more than 67% of the same voting results from Super Challengers, it will execute according to the results. Otherwise, the Scuba transaction will be rolled back. Active Super Challenger can get rewards, while the Scuba Node who produced the faulty block will be punished.

Conversion of Transparent Asset

Users can convert their assets on the Host Network from transparent asset to anonymous asset simply by the Scuba Wallet client. On the Wallet, users can directly deposit their assets to the Scuba contracts on the Host Network. The assets will be locked in the Scuba contracts. Then the Scuba Nodes who are monitoring the Scuba contract will verify the transaction and update Merkle Tree in the Scuba contract. When the transaction is finalized, the user's asset becomes the anonymous asset and eligible for anonymous transfer.

Anonymous Transfer

One of the most important features provided by the Scuba Protocol is the anonymous transfer. Any assets can be anonymously transferred after entering Scuba Network. Users can initiate an anonymous transfer from the Scuba Wallet. The Scuba Bundler collects users' anonymous transactions, packs them in a compatible transaction body, and submits them to the Scuba Nodes. The Scuba Nodes verifies all transactions and submit the Merkle Updates to the Scuba Contracts on the Host Network. After the challenge period, the anonymous transaction will be finalized.

Conversion of Anonymous Asset

The users’ anonymous asset can be also converted back to the transparent assets on the Host Network. The Scuba wallet will submit the token release operation to the Scuba Bundler. The Bundler processes this operation and submits it to the Contract. The Scuba Nodes verifies the operations from Contract and updates the Merkle Tree in the Scuba contracts. The Scuba contracts hosted on the Host network will release (withdrawal) user’s tokens on the Host network after the transaction is finalized.