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

Ethos

Rating

AA

Score84.00

Services

Sec. Infrastructure Overview

Current Bug Bounty: Own
Bug Bounty Max Payout: 150.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

3

Number of Vul. Found

12

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

40

External Integrations

0

Code Summery

Ethos is a platform designed to measure credibility and reputation in the cryptocurrency space, addressing issues like fraud and misaligned financial incentives. It offers a credibility score similar to a credit report, utilizing open protocols and on-chain records to foster trust. By implementing a decentralized consensus mechanism called social Proof of Stake, Ethos incentivizes ethical behavior and allows users to vouch for one another. The platform integrates with existing crypto infrastructure, enabling participants to build a reputation through reviews and social network attestations. Ultimately, Ethos aims to enhance trust and transparency in the crypto economy, promoting a more credible environment for all users.

Show Dependency Graph

Code Structure & Dependency

Show Codefile metrics

Centralization

Decentralization Score

18 out of 20

Contract Upgradability

No upgradability

Frontend

Go to Dapp

Maintenance Score

2.00

Poor

Excellent

Admin / Governance Functions

Timelocks

Uses Timelocks

Pauseability

Can be paused

Admin Wallet

0xB4a9bc5fb037eBd805a405F2b53cFadF4bCB4774

Admins cannot remove all market configs (must keep at least 1)

No Pause Mechanism

No timelocks

Recommendations

We use arrays for invitations as they are limited by admin action. That will increase gas cost or lead to inability to add/remove invites, should traversal reach gas limits. That is acceptable and requires admins to avoid making that mistake.

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