• Sec. Infra Overview
  • Past Audits
  • Code Structure
  • Centralization
  • Exposure to other Defi
  • Recommendation
  • User Rating
  • Back
protocol logo

Aloe II

Rating

AA

Score85.00

YieldAggregator

Sec. Infrastructure Overview

Current Bug Bounty:

No Bug Bounty

Bug Bounty Max Payout: 0 $
Has paid White Hats before:
Date of Last Audit: 1 Jan 1

Recent Security Incidents

  • Incident

    Amount Lost

    Date

Secured By

The Protocol is secured by

  • Name

    Type

    Website

  • logo of list item
    0

Past Audits

Number of Audits

2

Number of Vul. Found

20

Date of Last Audit

1 Jan 1

Past Audit Reports

Last codebase change was on: 1 Jan 1

Show Code Locations
Show all Vulnerabilities

Vulnerabilities reported in past audits

Code Structure

Lines of Code

0

Amount of Contracts

37

External Integrations

0

Code Summery

Aloe II is a supercharged money market application that enables borrowers to manage Uniswap V3 positions on margin, enhancing capital access for market makers and increasing yields for lenders. The platform features two user types: passive investors, who earn yields by providing assets to lending markets, and sophisticated market makers, who utilize up to 20x leverage to execute liquidity provider strategies. Each lending market is isolated to specific Uniswap V3 pairs, allowing users to assess risks based on the quality of the associated TWAP oracle. Margin accounts facilitate capital access for market makers, enabling them to create and manage leveraged positions while ensuring that the notional value of their Uniswap positions can exceed their margin assets.

Show Dependency Graph

Code Structure & Dependency

Show Codefile metrics

Centralization

Decentralization Score

20 out of 20

Contract Upgradability

No upgradability

Frontend

Go to Dapp

Maintenance Score

1.00

Poor

Excellent

Admin / Governance Functions

Timelocks

No Timelocks

Pauseability

No pause

Admin Wallet

0x

Recommendations

After a Borrower has been warned, but before it'liquidated, there'an opportunity to make it healthy and avoid liquidation. If this is done via a call to Borrower.modify, the warning will be cleared, and further interactions are normal. However, if it'done by a 3rd-party via Lender.repay (with the borrower set as the beneficiary), the warning will not be cleared.

User Rating

Avg. User Rating

No ratings

No ratings yet

Submit your review

Protocols on SCAS can't offer incentives to hide reviews

Disclaimer:

SCAS conducts security assessments on the provided source code exclusively. Conduct your own due diligence before deciding to use any info listed at this page.

In case you find any information on this report is incorrect, please fill out following form:Feedback