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

Tokemak

Rating

AAA

Score93.00

CrosschainLiquidity

Sec. Infrastructure Overview

Current Bug Bounty: Own
Bug Bounty Max Payout: 250.0K $
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

6

Number of Vul. Found

68

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

399

External Integrations

0

Code Summery

The main purpose of Tokemak' Autopilot is to simplify and optimize the liquidity provision process for liquidity providers (LPs) in decentralized finance (DeFi). The application addresses the complexities LPs face when trying to rebalance their positions by offering a fully autonomous and transparent solution. It takes into account various factors such as yield variance, fee structures, and the costs associated with gas and trading fees, which are crucial for effective liquidity management. By streamlining the decision-making process and reducing the time spent on research and protocol interactions, Tokemak' Autopilot enhances the overall efficiency and accessibility of liquidity provision for a broader range of ecosystem participants.

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

Uses Timelocks

Pauseability

Can be paused

Admin Wallet

0x8b4334d4812c530574bd4f2763fcd22de94a969b

Uses Timelocks on Upgrades

Recommendations

Off-chain mechanisms listed in subsequent section are expected to be online and execute within their expected frequency The LMPStrategy.verifyRebalance() referenced in the LMPVault, and in the LMPDebt lib used by the vault, is expected to only return true when the rebalance is favorable for the vault/users.

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