Robby

The narratives in crypto are always changing and as a marketer it's extremely hard to keep up. Working at @chaoslabs, I interface with 20+ protocols on a typical day across verticals like lending, derivatives, and infra. Tbh it's a struggle to context switch across these niche protocols (with very exciting tech) while staying on top of our core products across the risk management stack. Not to mention the daily information overload from crypto newsletters, tech newsletters, CT, podcasts, macro, Trump, and everything else.... It gets overwhelming and scary really quick. But not anymore 💪 Since using Chaos AI, I've cut my research time by over 60% and can respond to technical questions way faster than before. I no longer need to stay on top of every protocol update and can simply prompt Chaos AI while I focus on execution and other higher-impact initiatives. Here's how I use Chaos AI. • Go direct with my questions. Rather than searching numerous sites or platforms for metrics, I ask questions directly to the Chaos AI agent. I no longer need to bug our data scientist (🤣 @whale_hunter_) or query @Dune to get metrics on @aave, @GMX_IO, or @VenusProtocol. • No more reading 100+ page technical docs (unless I want to ofc). I can upload whitepapers and research and use this as a framework to understand protocol mechanics. I'm not an engineer so this puts me on equal footing with my more technical colleagues. • Power up my market intelligence: This is by far the most context-aware onchain intelligence platform in the market. I can easily analyze token performance, protocol metrics, and feed in market info to identify trends and opportunities before they become mainstream narratives. Very useful. With Chaos AI, marketers and non-technical folks like myself can go direct with questions and get precise, actionable insights in seconds!

The last mile curve in financial AI. > The dashed line assumes output scales with model capability. > The solid line reflects reality: output quality steepens when the agent operates on live state, enforces constraints, and executes. Read more:

After what happened with USR, i'm running custom alerts on my stablecoin exposure through Chaos AI. > pick the asset > describe the alert or use a template > choose where you get notified (i've set mine to email & tg) Could have been helpful to some teams last week

Is DeFi's Risk Infrastructure Actually Broken? w/ Omer Goldberg | Uneasy Money x.com/i/broadcasts/1…

Financial AI, built on live market state. Chaos AI powers oracles, analytics, and vault strategies for @krakenfx, @Aave, @pendle_fi, @etherealdex, and more. → Trained on $5T+ in proprietary market data → Real-time risk modeling → From research to execution in one prompt

Damn it took 1 prompt and a few seconds for Chaos AI to piece together the $USR contagion across vaults

Chaos AI analyzed the vaults impacted by the USR exploit. A ton of interesting weekend transactions. Here, we build a knowledge graph, filtering for the Gauntlet USD Alpha Vault and the Gauntlet Resolv USDC vault: Pre-exploit: • USD Alpha had allocated ~438,440 USDC to the Gauntlet Resolv USDC vault • That vault was deposited into the impacted Morpho Resolv markets via the Gauntlet Resolv USDC vault. app.morpho.org/ethereum/vault… • USD Alpha held receipt tokens representing this exposure Post-exploit, March 23: • 00:30 UTC, Gauntlet USD Alpha sends ~438,440 USDC worth of resolvUSDC receipt tokens (~405,439 shares) to a Safe. • 00:35 UTC, Gauntlet USD Alpha receives USDC ($438,401) from Coinbase. Receipt tokens out, USDC in, 5 min apart, w/ roughly the same notional. etherscan.io/tx/0x7db422e95… #eventlog#541" target="_blank" rel="nofollow noopener">etherscan.io/tx/0x35ce2a750… A ton more to dig into. Analyzing and contrasting vault curator operations and allocation patterns in real time is one of the use cases we’re building Chaos AI for.

@burstingbagel @yieldsandmore thanks for this banger tweet btw. got an honorary mention in this article x.com/chaoslabs/stat…

Members of @yieldsandmore were on top of usr exploit within 5 minutes meanwhile most risk curators, whose job is to manage risk, took around an hour to take action. In fact yam members were the ones alerting the risk curators to what was happening 🥀

Editors note: Previously, @MidasRWA was presented as a separate category. This has been revised to reflect individual markets with their respective risk curators. → Direct and indirect exposures may be included → Values may not reflect current positions

"You can't be pleased about this if you're a DeFi bull." Andy walks through Omer Goldberg's thread documenting how millions in bad debt were created across Gauntlet's Morpho vaults after the Resolv USR exploit.

@alphaleaked or when risk cursors become the risk

Risk Curators renamed in Risk Creators.

@Yannimoto we (@chaoslabs) covered this issue here:

Good as time as any to bring this tweet back I guess. Also feels like DeFi maybe needs a better label than "curator"? Given that pure selection is maybe 20% of the actual job. The rest is upfront due diligence followed by live risk management, spotting when leverage is building up, and making the call to pull back and give up yield before things get ugly. I think the distinction will matter more as the next wave of capital comes onchain.

@takehisamuto Thought it was just me lol

X acting up again? 😩 "This page is down" screen popped up with the classic ice cream joke: "I scream. You scream. We all scream... for us to fix this page" 😂 How many times is this now? Everyone else seeing it too? #XDown #XOutage #TwitterDown #ElonMusk

per the article: "Due diligence. Every protocol, asset, parameter, and oracle is reviewed before deployment. Each dependency is mapped as an exposure vector, analyzed for how it could affect solvency, liquidity, and yield, and constrained with explicit limits. This is not a one-time onboarding exercise and is the baseline that all subsequent automation enforces."

@0xGeeGee I agree with everything, but I didn’t like Omer’s accusation that Stakehouse was superficial in its risk analysis, especially after this (image). By putting its treasury in its own vault, Stakehouse lets users exit first, effectively taking any potential losses. Wich is good imho

If we don't improve things for lenders, we will soon have only yield bearing token holders and no-one willing to sign up to be the counter party

@sberex @ResolvLabs and counting smh

Total estimated @ResolvLabs contagion (known amounts): ~$54.8M+

This recent issue reflects a broader design bias visible in teams like .... where capital allocation is fast and automated, risk management is slow and over-reliant on human intervention".

@emilylai we (@chaoslabs) wrote about this issue months ago -- link to one of many pieces: x.com/chaoslabs/stat…

it feels safer to just earn 3% on your stables via kyc and fdic insured venues like coinbase or kraken …in which case you might as well just buy t-bills on treasury direct i had some funds deposited into a yield aggregator and it took some digging to know how exposed they were to RLP/USR there’s multiple fall points between smart contract, key management, and curator risk that doesn’t really make 6-8%+ yield ready for masses we’d need some forms of tranching, protocol safety modules, or external insurance, all which would eat into yields or require rates large enough for first loss positions to assume risk curious who is building here

@shimon_newman @gauntlet_xyz @chaoslabs @omeragoldberg 😂😂😅

The beef between @gauntlet_xyz + @chaoslabs has always been entertaining. I just KNOW @omeragoldberg was writing this report like

1/ Millions in bad debt, at the time of writing, were created across Gauntlet's Morpho vaults from the Resolv USR exploit. Almost all of it was supplied ** after ** the exploit. So why would curators supply millions in USDC to a broken market? Let’s dive in.

1/ Resolv's USR stablecoin was exploited for $25M. There’s significant contagion across Morpho vaults, lending markets, and protocols. USR was collateral across multiple lending markets /vaults. Many used hardcoded pricing without risk guardrails. - written with Chaos AI