bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 4쪽 중 2쪽
4660-8d43-b755e42171ed" alt=""><figcaption></figcaption></figure></div>
#### Utility
[$BANK](https://coinmarketcap.com/currencies/lorenzo-protocol/) unlocks three core functions in the Lorenzo ecosystem:
* Staking: As an access token, users may stake $BANK to access exclusive privileges on the Lorenzo protocol, for example ability to access voting, certain features, and to influence incentive gauges.
* Governance: $BANK functions as the native governance token which would grant holders governance voting rights to vote on proposals on key matters relating to the protocol, for example protocol adjustments (product changes, fee changes), use of ecosystem growth funds for the benefit of the ecosystem, and future emission adjustments.
* User engagement rewards: $BANK will be allocated to reward active users which participate on the protocol (with a sustainable reward pool comprising a portion of ongoing Protocol Revenue). Users which utilise the platform or engage in other community-based activities such as voting or campaigns will be able to receive $BANK incentives.
#### veToken
[$BANK](https://coinmarketcap.com/currencies/lorenzo-protocol/) utilities will be activated via veBANK — a vote-escrowed token received by locking [$BANK](https://coinmarketcap.com/currencies/lorenzo-protocol/).
veBANK is non-transferable and time-weighted:
* The longer the lock, the greater the influence
* Vote on incentive gauges
* Earn boosted user engagement rewards for your long term committed participation
Earn boosted user engagement rewards for your long term committed participation
veBANK ensures governance is shaped by committed stakeholders.
# Financial Abstraction Layer
## Building the On-chain Asset Administration Infrastructure $BANK
According to [Mordor Intelligence](https://www.mordorintelligence.com/industry-reports/global-payments-market), the global payments market is projected to grow substantially from $3.16 trillion in 2025 to $5.3 trillion by 2030. In traditional finance, a wide range of ETFs have been developed to offer access to various trading strategies—such as covered call writing, volatility harvesting, and risk-managed equity overlays—enabling users to gain exposure to structured yield generation with ease and scalability. For instance, the JPMorgan Equity Premium Income ETF (JEPI) has delivered an annualized return of approximately 8–9% since launch through a covered call strategy; the Simplify Volatility Premium ETF (SVOL) has generated 10–12% returns annually by shorting VIX futures with hedges; and the Cambria Shareholder Yield ETF (SYLD) has achieved over 11% annualized by targeting companies with strong capital return policies.
However, within the Web3 ecosystem, tokenized access to such structured trading strategies remains limited. While products like Ethena’s USDe have demonstrated how delta-neutral funding rate strategies can be successfully tokenized, the broader spectrum of on-chain yield products is still underdeveloped. There is a significant opportunity to tokenize a diverse range of trading strategies—across volatility, risk parity, hedged equity, and managed futures—and make them accessible to both retail and institutional users seeking differentiated and sustainable on-chain yield solutions.
### **Financial Abstraction Layer (FAL)**
The **Financial Abstraction Layer (FAL)** is the core technical infrastructure developed by Lorenzo to enable the tokenization, execution, and distribution of trading strategies across DeFi and CeFi. It abstracts complex financial operations into modular, programmable components, allowing seamless access to sophisticated strategies through simple on-chain interfaces.
FAL powers the creation and management of **On-chain Traded Funds (OTFs)** and provides all necessary backend services, including capital routing, NAV accounting, and multi-format yield distribution.
***
#### **Three-Step Operational Model**
FAL is designed around a robust three-step execution cycle:
1. **On-Chain Fundraising**
* Capital is raised directly on-chain via smart contracts (subscriptions, vault deposits, etc.)
* Users receive tokenized shares representing their claim on the underlying fund or strategy
2. **Off-Chain Trading Execution**
* Capital is deployed into off-chain strategies (e.g., CeFi arbitrage, delta-neutral trading, volatility harvesting)
* Strategies are executed by whitelisted managers or automated systems with transparent mandates
3. **On-Chain Settlement & Distribution**
* Trading P\&L is settled periodically on-chain
* FAL handles performance reporting, NAV updates, and yield distribution through various payout mechanisms (e.g., rebasing tokens, claimable rewards, fixed maturity yield tokens)
### **On-Chain Traded Fund (OTF)**
**On-Chain Traded Funds (OTFs)** are tokenized fund structures (issued by third party issuers and managers utilising Lorenzo infrastructure) that mirror traditional ETFs, but are fully integrated into blockchain infrastructure. Issued and settled on-chain, each OTF represents a basket of trading strategies or yield sources.
Unlike traditional ETFs, OTFs:
* Use smart contracts for real-time NAV tracking and issuance/redemption
* Plug directly into wallets, DeFi protocols, and dApps
* Enable granular strategy exposure for both retail and institutional participants
<figure><img src="https://3057728637-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftbitm06J0ATMxDbw8njN%2Fuploads%2FwvbBsXkKHwbtLzDxtnjW%2Fotf_compare.jpeg?alt=media&token=aef6868d-8f4a-4190-9ac9-cc9f3f3a0740" alt=""><figcaption></figcaption></figure>
***
#### **Supported Trading Strategies**
Each OTF can be backed by a single strategy or diversified blend, including:
* Delta-neutral arbitrage (CEX/DEX)
* Covered call income strategies
* Volatility harvesting (short VIX, long puts)
* Risk-parity portfolios
* Macro trend-following via managed futures
* Funding rate optimization in perp markets
* Tokenized CeFi lending or RWA income
#### **FAL + OTF = Modular, Scalable, and Composable Finance**
The synergy between FAL and OTF introduces a **new financial primitive**:
> "Tokenized access to actively managed trading strategies, with modular yield structures and fully on-chain control."
By standardizing this across protocols, FAL and OTFs unlock:
* Institutional-grade yield for DeFi users
* Transparent, permissionless access to active strategies
* Customizable exposure based on user risk/yield preferences
<figure><img src="https://3057728637-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftbitm06J0ATMxDbw8njN%2Fuploads%2FzGqNrpumTXaSXdrje8Zo%2Fimage.png?alt=media&token=6a68834f-1227-4ba9-ba84-80e362432ede" alt=""><figcaption><p>Lorenzo Financial Abstraction Layer</p></figcaption></figure>
# Technical Design
Lorenzo **Financial Abstraction Layer (FAL)** supports two vault types:
* **Simple vault:** A basic, single-strategy vault managing one off-chain yield strategy.
* **Composed vault (Fund):** a portfolio vault aggregating multiple simple vaults under a delegated third-party fund manager (could be a person, an institution, or an AI agent), who rebalances capital across the corresponding simple vaults.
<figure><img src="https://3057728637-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftbitm06J0ATMxDbw8njN%2Fuploads%2FAs3kMDgiDUFKDtnAd3rk%2Fsimple_v_composed.jpeg?alt=media&token=6dbf9d6c-4596-4811-823d-3b01718eff90" alt=""><figcaption></figcaption></figure>
Lorenzo highlights ***CeFi*** trading strategy vaults. Here, the return of a vault comes from the financial returns of centralized exchanges (CEXs). Assets are received in custody wallets and are mapped to CEX sub-accounts at a 1:1 ratio. Trading teams can operate these exchange sub-accounts on behalf of Lorenzo via dedicated account APIs with fine-grained permission control.
Therefore, the followings are required to instantiate and operate a Lorenzo *CeFi* trading strategy vault:
* **Sub-accounts:** Multiple sub-accounts need to be created on CEXs, each managing an underlying asset to obtain trading strategy income.
* **Custody wallets:** Registered custody wallets are 1:1 mapped to exchange sub-accounts.
* **Simple vault configuration:** When creating a vault, it is necessary to specify the yield source and APY of its portfolios. It is also required to specify the proportion of capital for each portfolio, and bind it to the corresponding custody wallet. Upon receiving user deposits, the underlying assets will be automatically allocated to the corresponding custody wallets according to the configured proportion of each portfolio.
* **Composed vault configuration:** When creating a composed vault, it is necessary to specify the composition and capital proportion across the involved simple vaults. Upon receiving a user's deposit, the fund is first automatically allocated to the involved simple vaults according to the configured proportion, and then each simple vault is dispatched to the correspinding custody wallets according to the configured portfolios.
* **Withdraw:** Upon expiration of the requested withdrawal cycle, the yield is collected and settled by Lorenzo and its financial partners. The underlying assets corresponding to the yield amount are then divided from the relevant custody wallets into a dedicated multi-signature payment wallet and transferred to the vault contract. The user receives the withdrawal asset through the vault contract.
* **LP tokens:** When depositing into/withdrawing from a vault, corresponding amount of LP tokens (ERC20) are minted/burnt.
# Data Flow
<figure><img src="https://3057728637-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftbitm06J0ATMxDbw8njN%2Fuploads%2FjDjqHDfO35qiJVaPexeQ%2Fdata_flow.jpeg?alt=media&token=d6b5351e-204c-4839-81b0-19b5daf06b21" alt=""><figcaption></figcaption></figure>
* **Vault Contracts** emit events for deposit, NAV updates, and withdrawals.
* **Backend API** aggregates on-chain data and CEX trading reports to compute unit NAV and performance metrics.
* **Lorenzo Frontend and Exchange Partners** query the API for real-time vault status and user PnL.
# LP Tokens and Unit NAV Calculation
When a user deposits assets into a Lorenzo vault, the vault issues LP tokens to represent the shares of capital in the vault that belong to the user. ***The LP tokens could be used as underlying assets for OTF tokens.*** The value of an LP token is represented by the $$UnitNAV$$ of the yield vault. During the operation of the vault system, due to user activities (i.e., deposit and withdrawal) and fluctuations in financial incomes (i.e., trading yields), the vault's $$NAV$$, $$UnitNAV$$, and amount of LP tokens will be calculated according to the following formulas, where: 
$$NAV =\text{Vault Total Assets} - \text{Vault Total Liabilities}$$
$$LP$$ is the total outstanding vault shares during the current settlement cycle, and
$$UnivNAV$$ is the networth per share during the current settlement cycle.
## Net Worth Per Share
When a vault is initialized, the exchange ratio between the LP tokens and the underlying asset is 1:1. As the operation of the vault progresses, the exchange ratio is updated each time the vault settles, represented by
$$
UnitNAV = \frac{NAV}{LP}
$$
## 1. LP Token Shares to Obtain After Deposit
Assume at the $$n^{th}$$ vault settlement, a user deposits $$\Delta{T}$$ tokens. The amount of LP token shares to claim is
$$
\Delta{LP}=\frac{\Delta{T}\times{LP\_n}}{{NAV\_n}}=\frac{\Delta{T}}{{UnitNAV\_n}}
$$
## 2. UnitNAV Update After Settlement
After the $$n^{th}$$ vault settlement cycle expires and finalizes, the PnL of the cycle is obtained ($$\Delta{r}$$). The vault manager will then update the vault $$UnitNAV\_{n}$$ in the contract as
$$
NAV^{settle}*{n}=NAV*{n} + \Delta{r}
$$
$$
UnitNAV^{settle}*{n} = \frac{NAV^{settle}*{n}}{LP\_{n}}
$$
## **3. NAV Update After Withdrawal**:
Users can opt to withdraw shares at their will once a vault is settled for the cycle. After users withdraw, the $${(n+1)}^{th}$$ cycle's $${NAV\_{n+1}}$$ is finalized as
$$
{NAV\_{n+1}} = NAV^{settle}\_{n} + \Delta{T}-R
$$
Where $$R$$ is the amount of withdrawn underlying asset
$$
R=\Delta{LP^{withdraw}}\times{UnitNAV^{settle}\_{n}}
$$
## 4. UnitNAV for the Next Cycle
Summarizing step 1 - 3, for the $${(n+1)}^{th}$$ cycle, we have
$$
NAV\_{n+1}=NAV\_n + \Delta{T}
* \Delta{r} - R
$$
$$
LP\_{n+1}=LP\_n + \Delta{LP}
$$
And therefore,
$$
UnitNAV\_{n+1} = \frac{NAV\_{n+1}}{LP\_{n+1}}
$$
# Integration Workflows
Before engaging with Lorenzo *Financial Abstraction Layer (FAL)*, new participants must complete a streamlined integration process to ensure security, compliance, and smooth operations. The following workflows outline the key steps for both trading teams and DeFi partners to onboard, configure, and interact with Lorenzo *Financial Abstraction Layer (FAL).*
# Trading Team Onboarding
A trading team could apply to create yield vaults on Lorenzo *Financial Abstraction Layer (FAL)* for a specific trading strategy to raise liquidity.
## Process of Integration
The trading team needs to complete the following steps before integrating with the platform:
1. **Due Diligence**:
* Work with Lorenzo BD team for onboarding.
* Complete due diligence on team credentials and trading strategy.
* Discuss details for the collaboration.
2. **Configuration**:
* The trading team provides the trading pairs they intend to operate.
* The trading team provides a list of IP addresses for the servers running the trading strategy.
3. **Fund Mirroring**: Lorenzo team mirrors capital raised from the vaults to a sub-account delegated to the trading team.
4. **API Keys:** Lorenzo team provides the trading team with an API Key configured based on the information from steps 2.
5. The trading team uses the trading platform's API for asset administration. Please refer to the specific trading platform's API documentation (e.g., [Binance](https://developers.binance.com/docs/)).
## Settlement
1. The trading team needs to settle the operational status every 7 days to determine the profit and loss for the current trading team.
2. Lorenzo team needs to provide the quantity of positions to be closed 3 days before the settlement date.
3. The trading team must transfer the principal and the profits generated from the closed positions to the vault contract address.
## Withdrawal
1. Lorenzo team calculates and submits the amount of capital to be withdrawn from the vault.
2. Lorenzo team confirms with the trading team on the actual amount of capital that could be settled after closing all of the requested positions. This information is then relayed to the liquidity providers of the vault.
3. After the trading team closes the positions, Lorenzo team and vault managers return the capital requested for withdrawal through the vault contract.
# DeFi Partners Onboarding
A liquidity provider of a vault could be a person or an institution. Currently Lorenzo is primarily working with leading yield-generating DeFi protocols. Such DeFi protocols seek yield opportunities and hence operate as liquidity providers of the vaults.
## Process of Integration
A liquidity provider needs to complete the following steps to integrate with the platform:
1. **Due Dilignce:**
* Work with Lorenzo BD team for onboarding.
* Complete due dilignce on the team and its product.
* Discuss details for the collaboration.
2. **Product design:** The DeFi partner specifies the features and yield strategies desired in the yield vault. Lorenzo team customizes the vault to meet the demands of the DeFi partner.
3. **Development:** Lorenzo team implements and integrates with the DeFi partner's system, and grants necessary permissions.
4. **Delivery:** Lorenzo team and the DeFi partner work together for final testnet and mainnet deployment.
# Smart Contract
Lorenzo's vault system includes two key parts: `CeDeFiManger` and `Vault`, shown in the diagram below:
<figure><img src="https://3057728637-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftbitm06J0ATMxDbw8njN%2Fuploads%2Fec0QheJ2tF0ZTG0s5gQS%2Fsmart_contract.jpeg?alt=media&token=914626e8-77c5-40b1-9243-43778387b806" alt=""><figcaption></figcaption></figure>
* The `CeDeFiManager` contract is managed by Lorenzo. It has the following functions:
* `createVault()`: Create a vault.
* `executeCommand()`: Manage the vault, such as adding or removing addresses from the blacklist, freezing or unfreezing LP tokens, updating the $$UnitNAV$$, upgrading contracts, etc.
* The management permissions of the `Vault` contract are controlled by `CeDeFiManager`. Apart from management functions, the `Vault` contract primarily handles deposit, withdrawal requests, and withdrawal settlements:
* `deposit()` : Deposit underlying assets to the vault.
* `requestWithdraw()`: Request withdrawals using LP tokens.
* `withdraw()` : Complete the withdrawal process.
Please use the following ABI file to interact with the contracts:
{% file src="/files/iJdz9tKxzj0tuE2Ey9Ke" %}
{% file src="/files/vIrfXkBY8Q7xSuBkEHVb" %}
# Operational Details
## Security Arbitrage
When in collaboration, Lorenzo grants the DeFi partner the following permissions:
* Co-management permission of the on-chain vaults
* Co-management permission of the custody account(s)
* Co-management permission of the CEX account(s) or sub-account(s)
LP tokens are made non-transferable by default. If there is any fund from the DeFi partner flagged by the CEX as suspicious, Lorenzo will take the following actions for risk management:
* Coordinate with the CEX to detain the flagged suspicious fund
* Freeze the LP tokens issued for the suspicious fund
* Notify the DeFi partner about the frozen fund and LP tokens
## Query Information About the Vault
A DeFi partner can query various types of real-time information about the vault, including the yield strategy, $$NAV$$, $$UnitNAV$$, user PnL, and historical performance, through Lorenzo-provided APIs. More details are provided in the [API Documentation](/docs/financial-abstraction-layer/api-documentation) section.
## Deposit
1. The DeFi partner prepares the capital to be deposited into the target vault.
2. The DeFi partner calls the `approve()` method on the underlying assets, authorizing the vault to collect the proper amount of the underlying assets.
3. The DeFi partner calls the `deposit()` method on the vault to deposit the underlying assets into the vault and get cprresponding LP tokens in return.
## Request Withdrawal
1. The DeFi partner can request to redeem all or part of its shares.
2. The DeFi partner submits a withdrawal request for the desired amount of shares through the `requestWithdraw()` method of the target vault contract.
3. The DeFi partner waits for the current settlement cycle to end and the vault's $$NAV$$ to be finalized.
4. The DeFi partner can check the withdrawal status via the Lorenzo-provided API.
## Settle Withdrawal
1. Once all withdrawal requests are confirmed, the final $$NAV$$of the vault for the current settlement cycle can be determined. The $$UnitNAV$$ of each withdrawal cycle can be checked using the contract method `periodUnitNav()`.
2. The DeFi partner can redeem their principal and profits to its original wallet address by calling the `withdraw()` method of the vault contract.
# Security
To ensure the security of assets, the following measures are implemented:
1. **Custody:** The underlying assets allocated towards in the vault will be directly transferred to the custodial wallet / exchange prime wallet during the deposit transactions, depending on the CEX setup.
2. **Multi-signature control:** Assets in the custodial wallet are managed by a multi-signature mechanism involving Lorenzo, DeFi Partners, and security curators.
3. **Freeze mechanism**: If Lorenzo is notified by the trading platform that프로젝트로 돌아가기