# [EXAIP-26] Launching Exactly Protocol on Base with KYC

- Space: [Exactly Protocol](https://snapshot.box/s:gov.exa.eth.md)
- Author: 0x997137e1c2A1A8A78CE2D17796b870eFbC7572D2
- State: Passed
- Voting type: Basic
- Start: 2025-11-03 01:38 UTC
- End: 2025-11-08 01:38 UTC
- Votes: 19
- Quorum: 100,000 voting power
- Discussion: https://exact.ly/discord
- Open in Snapshot: https://snapshot.box/#/s:gov.exa.eth/proposal/0xfaabd2a7ebaaaaea1b86a65b63c5c7cae2e1a9fa05d548aad4e07583c0967d51

## Results

- For: 1,903,250.18 voting power, 100.0%
- Against: 0 voting power, 0.0%
- Abstain: 0 voting power, 0.0%

## Proposal

Proposal ID: EXAIP-26
Proposer: Exa Labs
Date: November 01, 2025

---

## Summary

This proposal seeks governance approval to **deploy the Exactly Protocol on Base**, including a **KYC-enabled version** to meet institutional and regulatory requirements.

It also introduces:
- Support for **USDC, WETH, cbBTC, and cbXRP**
- **Asset-level collateral caps** to limit exposure per asset
- Deployment of the **EXA token on Base** via LayerZero
- Routing of **Base treasury fees** to the existing staking rewards program on Optimism

---

## Motivation

This proposal aims to expand Exactly’s reach by enabling compliant access to institutional users through KYC verification while maintaining decentralization and transparency.

Deploying on **Base (Coinbase’s Layer 2)** offers:
- Lower gas costs and faster UX
- Access to a large, verified user base
- Integration with Uphold and future partners requiring compliance

This deployment aligns with the roadmap defined in **EXAIP-21** and strengthens the DAO’s sustainability through multi-chain revenue distribution.

---

## Specification

### 1. Network Deployment
- **Chain:** Base 
- **Protocol Version:** Exactly Protocol (KYC-enabled)  
- **Compliance Layer:** Integrated KYC verification  

---

### 2. Supported Assets and Parameters

Risk Adjustment Factor per asset: 
USDC: 0.91 
WETH: 0.86 
cbBTC: 0.78 
cbXRP: 0.60 (with an initial Collateral Cap of $1,000,000)

> The *Risk Adjustment Factor* defines the maximum percentage of collateral value that can be borrowed against, following Exactly’s standard risk model.

---

### 3. Collateral Caps

To prevent concentration risk, each supported asset will have a **maximum aggregate collateral limit**.  Once a cap is reached, new deposits for that asset will no longer be considered as collateral. This cap can be increased by governance in the future. 

---

### 4. KYC Process

The KYC mechanism provides regulatory compliance while maintaining user privacy and self-custody.
Only pre-approved partners (allowers) will have the power to add users to the allowlist, and they will also have the power to revoke access to the protocol for the users they have allowed. 

0. **Partner approval for the role of allower**
Entities that wish to be included as allowers and have the authority to add users to the allowlist, thereby interacting with the protocol, must undergo a series of audits conducted by the existing allowers and then be approved by the DAO. 

1. **User Verification**  
The user completes a verification flow as set by an allower. Checks include identity verification, sanctions screening, and residency validation.
2. **Allowlisting**
Once the KYC process is approved, the allower will include the user in the allowlist, granting them the power to interact with the protocol.
3. **Access Control**  
The protocol verifies the presence of a valid KYC credential before allowing interaction with the KYC-enabled markets.
4. **Privacy & Compliance**  
   - No personal data is stored or visible on-chain.  
   - Verification data remains solely with the provider.  
   - Partners can integrate via an Exactly KYC endpoint for seamless onboarding.
5. **Removal of the allowlist**
The allower has the right to revoke the permissions granted to a user who they initially allowed to access. In the case that this happens:
The existing debt of the user will be repaid with their own assets without penalty. The liquidator can trigger this forced repayment and must also be allowlisted.
The assets that are not used to repay the debt will be locked. If the user is allowed to interact with the protocol again in the future, the assets will be unlocked.
This decision is not final and can be revoked by the allower.

This flow ensures **compliance, privacy, and interoperability** across institutional partners.

---

### 5. EXA Token on Base

- The **EXA token** will be bridged to **Base** via **LayerZero**.
- No new tokens are minted; total supply remains constant across chains.
- Governance rights remain unified across deployments.

---

### 6. Treasury Fees Distribution

All **treasury fees generated on Base** (interest spreads, liquidations, etc.) will be **transferred periodically to the Exactly DAO Treasury on Optimism**.

These funds will flow into the **existing staking rewards program (stEXA)**, ensuring unified incentives and alignment between users, stakers, and the DAO across chains.

---

### 7. Audit & Security

- **ABDK Report:** https://github.com/exactly/audits/blob/main/ABDK%20Protocol%20Update%20(Oct-25).pdf 
-**Commif Dif:**
https://github.com/exactly/protocol/compare/20405f7...beeafdd
- **Final Commit:**  
https://github.com/exactly/protocol/commit/beeafdd

---

## Next Steps

1. Deploy contracts on Base with KYC 
2. Configure supported assets and collateral caps  
3. Route Base treasury fees to the DAO Treasury  
4. Deploy LayerZero EXA bridge

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

