Post

@0xngmi this makes better sense than a single figure... because with a single figure everyone just avoids anyone with bad rating but with this both protocol and users can know where the single point of failure lies. Great one ser

@0xngmi bro the transparency here is wild. most people ignore the risk side totally honestly this is needed

@0xngmi APY is useless without knowing what can break.

@0xngmi This is how you track losses. Not by looking at some dumb vault rating.

@0xngmi when you pull a historical balance Of to flag token exposure, what sanity check stops it from being some dead chain's block number? lol imo

@0xngmi @llama the top risky defi vaults plbs

@0xngmi Our kind of simulations 🤯

@0xngmi exposing every hidden loss vector so users cant blame someone else later actually refreshing risk communication

@0xngmi listing every exploit path makes more sense than a score. people ape into 90-rated vaults without reading that the rating ignores oracle risk or token concentration. your format forces them to see the actual failure modes instead of outsourcing judgment to a letter grad

@0xngmi can non-Morpho vaults list?

@0xngmi yeah this is the right framing. vault APY is useless if the blast radius is hidden

@0xngmi this is the right direction imo. users dont lose to “a vault”, they lose to the dependency nobody drew

@0xngmi Goated as always

@0xngmi users don't want a rating, they want to see what breaks when the curve pool gets drained or the timelock is 6 hours. show me the liquidation cascade not a score

@0xngmi imo this is the right direction. users dont need a rating, they need to see every weird way the vault can die

@0xngmi this is honestly a much healthier approach than pretending risk can ever fully disappear

@0xngmi Love it! This is a big need! @0xngmi let's chat

@0xngmi Knowledge is power, especially curated knowledge (as opposed to noise).

@0xngmi this is the right direction imo. users dont need a score as much as a map of what can actually break under them

@0xngmi Definitely agree with this approach; a rating is meant to be a summary term that allows people to make a cursory decision but can often obfuscate nuanced tail event. Being very transparent about imbedded risks allows users to curate their own risk profile.

@0xngmi this is the sane direction imo. vault APY without dependency-risk maps is just a prettier roulette table

@0xngmi Finally, someone did this.

@0xngmi Clear loss paths matter more than another score.

@0xngmi surfacing every path to loss instead of scoring it is the right instinct. what these maps underweight: the deps aren't independent. an oracle blowup and a sequencer halt correlate toward 1 in the window you need liquidity. a flat list reads additive; the real risk's joint.

@0xngmi This is the right direction for risk UX. Vault labels are useful, but users need to see the failure paths: oracle, bridge, collateral, admin role, sequencer, liquidity exit. Risk gets easier to price when the dependency graph is visible.

@0xngmi That makes total sense! It’s all about empowering users to make informed choices and understand their risks better.

@0xngmi This approach seems more effective to me. A simple "risk" number rarely offers a complete picture. Understanding the reasons behind possible financial losses is usually much more valuable than relying only on a score.