Skip to content
Crypto Almanac Daily
c
Lending

cap

Best for audited protocol with published methodology

Total value locked:$292m at this checkChains:1Audits recorded:2Audit report linked:YesRubric:v2.0 · verified 9 Aug 2026
Kayla PetersonKayla PetersonDeFi Research Analyst· Last verified August 9, 2026
Confidence ARubric v2.0Verified August 9, 2026
8.2
out of 10
Open account
Scorecard

How it rates

Counterparty & contract risk · 40%9.0
Cost transparency · 15%6.0
Market quality · 15%5.0
Transparency & track record · 20%10.0
Public documentation surface · 10%9.0
Pros
  • Audit report linked from a public dataset
  • Accounting methodology published
  • TVL of $292m recorded independently
Cons
  • Single-chain deployment
How this score was built

Each indicator scores 2, 1 or 0. A pillar is the points earned over the points available; the overall score is the weighted sum. Every source below is public — check any of them yourself.

Counterparty & contract risk · 40% weight9/10 points · 9.0/10
Cost transparency · 15% weight6/10 points · 6.0/10
  • Partial
    Application reachable without an account

    Published at a documented URL; automated retrieval blocked at this check.

    cap.app/
  • Met
    Protocol economics published independently

    TVL and change history published.

    defillama.com/protocol/cap
  • Met
    Accounting methodology published

    Methodology published.

    defillama.com/protocol/cap
  • Not met
    Fee or reward model documented publicly

    Not available at this check.

    cap.app/
  • Partial
    No account required to reach the application

    Published at a documented URL; automated retrieval blocked at this check.

    cap.app/
Market quality · 15% weight5/10 points · 5.0/10
Transparency & track record · 20% weight10/10 points · 10.0/10
Public documentation surface · 10% weight9/10 points · 9.0/10

A lending and yield protocol holding $292m, using restaked capital as economic backing for delegated yield strategies.

Our assessment

Cap holds $292m with two audits and reports linked. Its design uses restaked capital as economic backing for yield strategies — operators generate returns and stakers underwrite their performance, so a shortfall is covered by slashing rather than by depositors.

Insurance instead of emissions

Most yield in DeFi comes from token emissions or from lending demand. Cap's premise is that yield can come from operators running strategies, with restakers taking the downside risk in exchange for a share of the upside. If it works, depositors get yield backed by real economic collateral rather than by inflation. That is a genuinely different answer to where yield comes from.

The backing has to be sized correctly

The entire model depends on the slashable stake being large enough to cover realistic losses and on the slashing mechanism executing when it should. Both are new problems with limited history. If losses exceed the backing, depositors bear the remainder — which is the ordinary case in DeFi and the thing this design is trying to avoid.

Evidence and maturity

Two audits with linked reports is solid for a novel design, and novelty is the main risk here. There is no long record of behaviour under stress, which for a mechanism whose value appears precisely during stress is the open question.

Who it suits

Cap fits users who understand restaking and want yield with an explicit backstop, in size they can afford to lose while the model matures. Conservative lenders should use Aave or Compound.

Alternatives

How rivals compare

ServiceScoreBest for
Compound V39.9audited protocol with published methodologyRead →
Aave V39.9audited protocol with published methodologyRead →
Euler V29.6audited protocol with published methodologyRead →
Fluid Lending9.6audited protocol with published methodologyRead →
Reference

Frequently asked

Does this score mean cap is safe?

No. It measures what an outsider can verify: linked audits, published methodology and independently recorded market data. Contract risk is not tested by us.

Where do the TVL and audit figures come from?

A public analytics dataset queried at the verification date, plus the audit reports it links. Both are re-runnable by anyone.

Why do some protocols score zero on audits?

Because no audit report is linked in the public record. The indicator records what a user can reach, not a claim that no audit exists.