Key Information

Tokens Database

Currently, these are the tokens than an user can choose from when deciding which asset to receive in L2:

• USDT

• WBTC

• USDC

• MIM

• FRAX

The updated group can be queried with queryTokenDatabase() from StorageBeacon in L1 and queryTokenDatabase() from ozLoupeFacet in L2.

Ozel Index

Changing value used -among other variables- to calculate the OZL balance of each user, and to keep the peg of the OZL token's total supply at 100.

It is calculated internally by a call to _updateIndex() and can be queried with getOzelIndex() from ozLoupeFacet in L2.

Regulator Counter

Variable that gets increased by 1 and acts as a release valve for each balancing iteration of the Ozel Index.

It can be queried with getRegulatorCounter() from ozLoupeFacet in L2.

Protocol Fee

Currently at 0.1% per ETH transfer or 10 bps.

It can be queried with getProtocolFee() from ozLoupeFacet in L2.

Default Slippage

Slippage used by the protocol on non-user swaps, such as the calculations for revenue distribution to the owner. Currently set at 1% or 100 bps.

It can be queried with getDefaultSlippage() from ozLoupeFacet in L2.

AUM

Assets Under Management.

The total amount of fees the protocol has charged plus the generated yield from investing these fees in DeFi.

It can be queried with getAUM() from ozLoupeFacet in L2.

Total volume

The total amount of ETH transfers received by all Accounts.

It can be queried with getTotalVolumeInETH() from ozLoupeFacet in L2.

Non-Revenue contracts

These implementations from the L2 subsystem don't trigger a check on the owner's revenue tiers (the check to determine if part of AUM would belong to the Diamond owner):

• ozCutFacet

• ozLoupeFacet (and its upgrades v1.1 and v1.2)

• OwnershipFacet

• RevenueFacet

Cost of usage for L1 transfers

In the current state, the cost of using the protocol (PayMe since it's the only finalized section) derives in its majority from actions in L1 since these are not subject of data compression like in L2.

Example:

This L1 transaction sent 1.9271 ETH and received 1.9206 in L2 (L2 transaction here), resulting in a difference of 0.0065 ETH, which, if we add up the current protocol fee of 0.1% (0.00192 ETH), we have 0.00842 ETH (or $12.77 - at an ETH price of $1,515.42 -when the transaction was sent) as the total cost of using the protocol this time.

This can be divided as (with a gasPrice of 16.49 gwei):

0.006395 ETH (L1 gas cost) - 75.95 %

- The transaction fee on the L1 receipt (0.0003473 ETH) is for only sending ETH to the Account.

Since we're using Gelato to continue the execution, in order for Accounts to be able to received ETH with a gasLimit of a standard transfer (21,000), the ETH that's being sent will be used to pay the gas consumption on the rest of the bridging execution on the L1 side. This process pertains to Gelato and more info can be found here.

Cost in gwei: 274,291 (from ozPayMe to Arbitrum's Delayed Inbox contract) + 21,055 (to receive the ETH in the Account) = 295,346

0.0001041 ETH (L2 gas cost) - 1.23 %

- The transaction fee in the L2 receipt is accurate.

Cost in arbGas: 1,041,216 (full L2 execution)

0.00192 ETH (protocol fee) - 22.8 %

- The current fee of 0.1% charged by the protocol.

As we can see, the vast majority of costs for using the protocol (75%+) goes in L1 gas fees, so by getting rid of the bridging mechanism and having all ETH transfers done exclusively in L2, the protocol would be extremely cheap to use, on top of removing the risks associated to cross-chain transactions.

This would also mean that the Akash deployments would be terminated since there wouldn't be a need of checking transactions for manual redeems, getting the protocol closer to fulfill its vision, detailed in the VISION tab.