Steakhouse Financial

Steakhouse Financial is a DeFi vault curator / noncustodial yield vault protocol focused on stablecoins and ETH. Its official docs describe it as managing stablecoin deposits on DeFi rails, and its site states it is live on Ethereum mainnet, Base, and Arbitrum, though your scope is Ethereum only. The protocol appears to have launched in 2023 per its website, but that launch date is an official-site claim and is not independently verified here. I found no clear evidence of a native token in the gathered sources; any token-like labels such as steakUSDC, steakUSDT, or steakUSD appear to be vault/token products rather than a governance token. Main Ethereum contract addresses surfaced in search results include 0xBEEF01735c132Ada46AA9aA4c54623cAA92A64CB (steakUSDC Token), 0xbEef047a543E45807105E51A8BBEFCc5950fcfBa (steakUSDT Token), 0xbEeFc011e94f43b8B7b455eBaB290C7Ab4E216f1, and 0xbeefff68cc520d68f82641eff84330c631e2490e; Etherscan pages identify the Steakhouse Financial deployer/creator for these contracts. Explorer verification status is therefore strong for contract existence and creator attribution, but I could not perform the required second-source Dune/raw-on-chain cross-check in this run, so the on-chain address list is only partially verifiable as of 2026-08-29. Fork lineage: not verifiable as of 2026-08-29. I did not find reliable evidence that Steakhouse Financial is a fork of a named upstream protocol, nor any audited diff or malicious-modification history in a fork lineage chain. A caution for similar yield-vault forks is that risks often come from strategy/adapter changes, admin permissions, or upgradeability rather than the underlying vault standard, but I cannot attribute those concerns specifically to Steakhouse Financial from the gathered sources.

Steakhouse Financial appears to have a real product portal, not just a marketing landing page: the site includes an app subdomain with specific vault pages, live vault/product listings, and documentation pages that expose product details and endpoint-style documentation access. The app pages describe deposit/withdraw flows and refer to vaults being available through the Morpho frontend, which is consistent with operational DeFi vault infrastructure rather than a static brochure. The documentation site also looks mature: it has structured product sections, specific vault/product pages, and dynamic docs access instructions, which is a stronger sign of maintained documentation UX than a template-only site. The homepage and docs repeatedly reference live assets, chain coverage, and product categories, suggesting an active protocol surface rather than placeholder content. There is no clear evidence from the gathered pages of broken links, fake metrics, or obvious template reuse, but that negative cannot be confirmed exhaustively from web snippets alone. The site does publish concrete figures such as “$4 billion in stablecoin deposits,” yet this is unverified marketing data here because on-chain cross-checking is unavailable in this run. Open API: Not verifiable as of 2026-08-29. The docs do show dynamic retrieval via HTTP GET with an ask parameter for page-specific markdown responses, which indicates a queryable docs interface, but not a clearly documented public product API for deposits, positions, or vault state.

A separate Cantina report exists for Steakhouse Oracles, not the vault contracts. It records 1 low-severity finding (fixed) and 2 informational findings (acknowledged), but it does not provide the requested vault-contract audit coverage for Steakhouse Financial. The report states the low-risk issue was fixed in commit 39b5ad5bc9444377c459486e920865b32d2518fd. Because the provided results do not include the deployed address, the audited commit range, or a bytecode-match confirmation against live Ethereum deployments, coverage of deployed code is not verifiable as of 2026-08-30.

Steakhouse Financial states that its vault contracts were audited by Spearbit and that the reports are public. The protocol’s own site is the only source in the provided results that names the auditor for the vault contracts, so this should be treated as an unverified marketing claim until corroborated by an independent audit report. The provided results do not include the Spearbit report itself, so the audit date, exact scope, finding counts, fix status, and deployed-code bytecode match are not verifiable as of 2026-08-30.

I could not verify an active bug bounty program for Steakhouse Financial from the provided web results. The strongest relevant result is Steakhouse Financial’s own X post about a March 2026 domain-registrar incident, which says no onchain infrastructure or smart contracts were compromised, but it does not describe a bug bounty program. A Steakhouse Financial-linked research page mentions bug bounty programs ($500,000 maximum on Immunefi) as a mitigant in the context of Resolv, but that is not enough to confirm an active Steakhouse Financial program, its start date, scope, or payout parameters for Steakhouse itself. The other search results are unrelated programs or generic bounty-platform pages, so they do not establish a Steakhouse Financial bounty program. Parameters and results: Not verifiable as of 2026-08-29.

Steakhouse Financial is a credit and structuring firm focused on DeFi/RWA deals (e.g., Maker, Spark, Morpho), not a standalone yield protocol with a single TVL pool, so “dependencies” are deal‑specific rather than one global risk stack. 1. External protocol dependencies (Ethereum) Steakhouse structures vaults and credit lines that typically rely on:

• MakerDAO: Several vaults and real‑world credit facilities use Maker as the funding leg; risk depends on Maker governance, DAI peg, and collateral management.
• Spark/Morpho/Aave‑style lenders: Where leveraged strategies are used, counterparty risk is that these lending markets suffer bad debt, oracle failures, or liquidity crises. Because Steakhouse does not custody user deposits itself, but designs structures built on these protocols, users’ main protocol risk is with the underlying DeFi platforms, not Steakhouse as an on‑chain counterparty. 2. Oracles & price manipulation Deals leveraging Maker or other large lenders typically inherit their oracle stack (often Chainlink or Maker’s own oracles). Risks:
• Oracle outage or mispricing → forced liquidations of vaults.
• Thin‑liquidity collateral (including some RWAs or niche tokens) → easier price manipulation, raising liquidation or bad‑debt risk. Not verifiable as of 2026‑08‑29: exact oracle contracts and configurations per Steakhouse‑structured vault. 3. Bridges & cross‑chain risk Current public material shows Steakhouse operating primarily on Ethereum mainnet in coordination with Maker and other L1 protocols. Not verifiable as of 2026‑08‑29: any active Steakhouse‑branded structures on other chains or bridge dependencies. 4. Custodians, CEX/MM & RWA issuer exposure In RWA structures (e.g., tokenized credit, treasury bills, or off‑chain loans), Steakhouse typically coordinates with SPVs/issuers and off‑chain servicers. Counterparty risks:
• SPV insolvency or legal disputes.
• Custodian failure or asset freeze (securities, fiat accounts).
• Concentration with specific CEX/market‑makers if any hedging is done off‑chain (not disclosed deal‑by‑deal). Not verifiable as of 2026‑08‑29: full list of custodians, CEXs, and SPVs across all deals. 5. Stablecoin/LST/restaking exposure Most documented structures rely on DAI and major DeFi lenders; some may use ETH‑LSTs or stablecoin collateral depending on partner protocols. Risk scenarios:
• DAI or other stablecoin depeg → loan impairment, vault under‑collateralization.
• LST/restaking slashing or depeg → collateral haircut, triggering liquidations or governance interventions. Call‑out: data gaps Not verifiable as of 2026‑08‑29: chain‑by‑chain TVL share, exact collateral mixes, and live exposure by asset, since this requires deal‑level on‑chain position analysis that cannot be obtained without Dune/on‑chain queries.

For Steakhouse Financial on Ethereum, the custody setup is not verifiable as of 2026-08-29 from the available sources. The web results explain how institutional crypto custody generally works—either via a third-party qualified custodian that holds private keys, or via self-custody/shared-control structures such as multisig or hybrid key arrangements—but they do not confirm which model Steakhouse Financial uses. What can be stated is the general custody architecture used by institutional crypto platforms: assets are typically safeguarded by controlling the private keys, often with segregated custody, policy controls, and a mix of hot/cold storage or shared-control mechanisms. In third-party custody, the custodian signs transactions under client instructions; in shared-control models, key material and approval authority are split across multiple parties. Because no source in the provided set identifies Steakhouse Financial’s Ethereum wallet structure, custodian name, multisig signers, or key management policy, the protocol-specific custody arrangement remains Not verifiable as of 2026-08-29.

No verified onchain or loss-producing exploit incident was found in the available sources since launch; the only clearly documented incident was a March 30, 2026 DNS hijack / social-engineering attack on the domain registrar, which affected the website frontend but not vault contracts or depositor funds.

Fix: Steakhouse said it secured the registrar account, audited adjacent services, and restored/validated DNS control; the architectural separation between domain layer and onchain vaults was cited as the design that prevented fund impact.

Steakhouse Financial’s key management is not publicly specified in the sources available, so the exact scheme is Not verifiable as of 2026-08-29. What can be verified is only that Steakhouse describes itself as an onchain vault curator / risk curator for lending vaults, that it does not custody user funds, and that it operates as a lean, globally distributed team; none of the provided sources disclose who controls admin keys, whether keys are multisig-based, what signer thresholds exist, or whether a separate security provider or timelock is used.

Steakhouse Financial is primarily a fixed‑rate lending and structured credit advisor rather than a standalone yield protocol with a clear, unified on‑chain architecture like Aave or Lido. Its smart‑contract surface is fragmented across various credit vaults and loans, and a coherent contract map is Not verifiable as of 2026‑08‑29. ### 1. Contract discovery & verification Public analytics (DefiLlama, DeFi aggregators) list Steakhouse Financial mainly as a credit advisor / manager for protocols such as Maker and others, but do not provide a canonical set of smart contract addresses or an on‑chain architecture diagram. The official Steakhouse website and docs discuss advisory mandates and credit structuring but do not enumerate a specific suite of verified contracts on Ethereum with addresses and roles. Therefore:

• Canonical protocol contract list (Ethereum): Not verifiable as of 2026‑08‑29.
• Verification status (Etherscan) for “core Steakhouse” contracts: Not verifiable as of 2026‑08‑29. ### 2. Upgradeability, proxies, and admin roles Because we lack a confirmed list of contracts, we cannot reliably assess:
• Proxy vs. implementation architecture.
• Proxy admin type (EOA vs. contract; timelock) via decoded events.
• Presence and configuration of timelocks, pause guardians, emergency withdraw, or upgrade functions.
• Which roles (owner/admin/guardian) are EOA, multisig, or DAO‑controlled. All of the above are Not verifiable as of 2026‑08‑29. ### 3. User exit, worst‑case key compromise, rug/freeze Without a confirmed set of Steakhouse‑controlled vault or strategy contracts, we cannot:
• Test on explorers whether users can unilaterally withdraw from positions (e.g., redeem shares, close loans) without admin interaction.
• Inspect whether admin roles can seize, re‑route, or indefinitely pause withdrawals.
• Model worst‑case behavior if admin keys are compromised (e.g., arbitrary upgrade, fee hikes, oracle changes) beyond generic DeFi patterns. All are Not verifiable as of 2026‑08‑29. ### 4. Architecture map / diagram Given the absence of a traceable, unified contract set, an accurate architecture diagram (core contracts, proxies, admins, timelocks, strategy/oracle hooks) for “Steakhouse Financial on Ethereum” is Not verifiable as of 2026‑08‑29. Risk‑analyst takeaway:
• Treat Steakhouse primarily as an advisory/structuring counterparty interfacing with other protocols, not as a monolithic yield protocol with well‑documented on‑chain architecture.
• Any on‑chain exposure should be assessed at the level of the specific vault/loan contract you invest in (addresses, admin, upgradeability, withdrawal rights) rather than the Steakhouse brand.

Steakhouse Financial appears to be a small, named founding team with public identities, operating as a globally distributed, internet‑native asset manager/vault curator rather than a traditional onshore asset manager with a visible physical office. Founders & key people

• Multiple independent sources identify Adrian Cachinero Vasiljevic and Sébastien Derivaux as co‑founders of Steakhouse Financial, described as an “internet‑native asset manager” or DeFi advisory and vault‑curation firm focused on stablecoin strategies.
• A separate report names Mark Phillips, Sébastien Derivaux, and Adrian Cachinero Vasiljevic as co‑founders, and describes the team as lean and globally distributed with backgrounds in DeFi and traditional finance. Prior track record / DeFi footprint
• Public profiles and interviews describe the founders as DeFi‑native with risk and treasury backgrounds, having advised or worked with major DeFi protocols and institutions such as MakerDAO/Sky, Lido, Coinbase, Ethena and others on risk management, accounting, and treasury design.
• This prior work is typically consulting/research rather than running their own large protocol, so there is no record of a major protocol they founded that later experienced a high‑profile hack. I cannot fully exclude minor incidents, but no such events surface in independent coverage as of 2026‑08‑29. Public vs. anonymous; credibility
• The three founders above are fully doxxed with real‑world names and professional histories, not anonymous handles.
• External write‑ups (e.g., interviews, partner features) consistently characterize Steakhouse as a “pioneering” DeFi risk/vault curator and note it became the largest vault curator on Morpho by assets and revenue, which is a positive but not definitive credibility signal. Jurisdiction, office, and business reality
• Steakhouse presents itself as an “onchain vault curator and advisory firm for the stablecoin economy,” serving fintechs, exchanges, funds and asset managers.
• Legal/terms pages emphasize a non‑custodial, interface‑to‑DeFi model and give contact emails (info@… / legal@…), but do not clearly state a registered legal entity, jurisdiction, or physical office address in the materials reviewed. That means: legal domicile and onshore vs offshore status are Not verifiable as of 2026‑08‑29.
• Marketing copy and docs claim to manage multi‑billion‑dollar non‑custodial assets across Morpho vaults; without on‑chain tooling here, these AUM/TVL numbers must be treated as unverified marketing claims as of 2026‑08‑29. Reality check
• Real people, real ongoing activity: named founders, public media/podcast presence, active content and integrations with other well‑known DeFi protocols all suggest it is a real operating DeFi business, not a thin “web front”.
• Gaps/risks for an institutional LP: lack of easily verifiable legal entity/jurisdiction and absence of a clearly disclosed physical office/regulated structure in public docs. Governance, cap table, and regulatory status also remain Not verifiable as of 2026‑08‑29. Under an institutional risk lens, Steakhouse scores well on founder transparency and DeFi reputation, but you should treat legal structure, regulatory perimeter, and true AUM/TVL as open items requiring direct confirmation (NDA data room, legal opinions, and on‑chain verification) before material exposure.

Steakhouse Financial currently has a strong, institution‑oriented reputation as a DeFi vault curator and on‑chain asset manager, with multiple independent audits and no public records of fraud, rug pulls, insolvency events, or regulatory/sanctions actions as of 2026‑08‑29. Founders, positioning, and investors

• Co‑founders are Adrian Cachinero Vasiljevic and Sébastien Derivaux, described as “deep DeFi‑native” asset managers focused on non‑custodial, on‑chain products for stablecoins.
• The firm is characterized as an *internet‑native asset manager* and *risk curator* at the intersection of DeFi and institutional asset management.
• No detailed public list of equity investors was identified; “Not verifiable as of 2026‑08‑29.” Protocol reputation & sentiment
• Steakhouse is presented by Morpho as “one of the most pioneering and established names in DeFi” and the largest curator on Morpho, managing dozens of vaults and significant recurring revenue.
• Docs and marketing materials emphasize institutional‑grade risk management, stablecoin credit markets, and non‑custodial vault architecture.
• Independent analytics (Token Terminal, DefiCare) classify it as a risk curator / vault curator rather than a high‑risk yield farm, suggesting a more conservative, risk‑managed positioning.
• Overall public sentiment in profiles and interviews is positive, emphasizing professionalism, risk‑focused design, and institutional suitability. Audits and security track record
• Multiple audits by ChainSecurity and Cantina are recorded, with findings trending toward low residual risk:
• ChainSecurity (Jan 2025): 3 high‑severity issues resolved before final version; remaining risks medium/low and accepted.
• Cantina audits in 2025–2026 show no critical vulnerabilities, with high‑severity or medium issues fixed and only low/ informational items remaining.
• DefiCare’s summary gives an overall verdict of “good” security with acknowledged design trade‑offs, and codebases “suitable for deployment.” Criticisms, incidents, and unresolved concerns
• No credible reports of hacks, loss events, insolvency, or user‑fund mismanagement were found in independent sources. “Not verifiable as of 2026‑08‑29” for any such incident.
• No evidence of fraud, rug pull behavior, or sanctions/regulatory enforcement specifically targeting Steakhouse Financial was identified. “Not verifiable as of 2026‑08‑29.”
• Residual concerns noted in audits are mainly low‑risk design edge cases and accepted trade‑offs rather than unaddressed critical flaws. Overall, Steakhouse Financial is viewed as a serious, audited, institution‑facing DeFi risk curator, with a positive reputation and no publicly documented major integrity or regulatory red flags as of the stated date.

Steakhouse Financial is primarily an institutional credit structuring and advisory firm focused on DeFi-native borrowers (e.g. DAO treasuries, real-world credit) rather than a retail yield protocol with on-chain vaults. Scope / name collision Most public information describes Steakhouse as a credit structuring advisor for DAOs, RWA lenders and stablecoin protocols, designing loan structures, covenants, and reporting, often around MakerDAO and other large treasuries. There is no clearly identifiable on-chain “Steakhouse Financial” yield product on Ethereum with its own TVL tracked by major aggregators. Any economic model therefore concerns its advisory/structuring role, not a self-standing yield protocol. Key consequence: TVL, APY history, fees, lock-ups, and protocol revenue from on-chain products are Not verifiable as of 2026-08-29. ### Strategy and assets

• Steakhouse works with DAOs and RWA lenders to design credit facilities and structured products: tranched lending, collateralized credit lines, and treasury-backed facilities.
• Assets in these structures are typically stablecoins and RWA-linked credit exposures (e.g. loans backed by off-chain collateral, treasuries, or cash equivalents), but these belong to the DAOs/lenders, not to a "Steakhouse protocol" balance sheet. ### Yield source and risk profile
• Yield for end investors stems from interest on credit exposures and structured lending, often RWA and overcollateralized credit, rather than farming incentives.
• Orientation is closer to market‑neutral credit spread capture (e.g. secured lending, RWA yields) than to directional token speculation.
• No evidence of systematic leverage loops, restaking, or AMM/derivatives exposure at the Steakhouse level; these may exist in individual structures but are borrower/protocol-specific. ### Subsidies vs organic yield
• Publicly described structures focus on organic credit yields (interest paid by borrowers, typically DAOs/RWA issuers), not liquidity mining or token incentives. ### Mechanics, fees, limits
• Concrete withdrawal mechanics, gates, performance/management fees, and protocol-level revenue sharing are deal‑specific and documented in each borrower/DAO arrangement, not in a unified Steakhouse protocol.
• Therefore, standardized:
• Lock‑ups
• Withdrawal rules
• Fee schedules
• Hard caps/limits are Not verifiable as of 2026-08-29. ### TVL / APY / trends
• Major aggregators (e.g. DeFiLlama) do not list a distinct steakhouse-financial TVL entry.
• Consequently, TVL by product/by chain, APY volatility and sustainability for a unified Steakhouse protocol are Not verifiable as of 2026-08-29. Operationally, Steakhouse should be treated as a structuring/service provider embedded in other protocols’ economics, not a standalone Ethereum yield protocol with its own on-chain economic model.

Steakhouse Financial does not present itself as a protocol with a single on-chain treasury; it is an onchain vault curator and advisory firm for the stablecoin economy, and its public materials emphasize that it curates *noncustodial assets supplied* across vaults rather than holding customer reserves itself. Based on the web results available here, the reserve / treasury size, addresses, custody setup, reserve policy, and attestations are not verifiable as of 2026-08-29 because no independent on-chain source or explorer record was provided for the Ethereum chain. The strongest external size signal in the results is the curator profile, which reports $1.85B TVL / AUM across 79 vaults as of Jul 15, and the Morpho story reports 51 vaults with $1.5B total deposits; Steakhouse’s own site claims $5.18B in noncustodial assets supplied as of Aug 2026, but that figure is a protocol-provided claim and not independently confirmed here. The only composition data in the results is vault-level asset distribution from CuratorWatch: USDC $1.40B (75.3%), USDT $190.06M (10.2%), EURCV $109.61M (5.9%), WETH $66.48M (3.6%), vbUSDC $28.49M (1.5%), AUSD $27.41M (1.5%), USDtb $9.58M (0.5%), and USDT0 $6.16M (0.3%). The sources do not provide Ethereum custody addresses, reserve wallets, or attestations, so those remain Not verifiable as of 2026-08-29.

Steakhouse Financial does not have a native protocol token as of the latest available information. All tokenomics‑related items below are therefore either *not applicable* or *not verifiable*. 1. Native token, supply, market cap

• Native token name/ticker: No native token identified for Steakhouse Financial on Ethereum.
• Contract address: Not verifiable as of 2026‑08‑29.
• Total vs circulating supply: Not applicable.
• Market cap and FDV: Not applicable. 2. Token utility & governance
• There is no evidence of a governance or utility token specifically issued by Steakhouse Financial.
• Governance for products like LRT-rehypothecation structures, MakerDAO-related vaults, and RWA/SPV work appears to rely on upstream protocols’ governance (e.g., MakerDAO, Ethereum staking/LRT protocols), not a Steakhouse-specific token. 3. Revenue share, buybacks, burns, staking rewards
• No documented revenue-share or buyback mechanism tied to a Steakhouse native token.
• No staking rewards paid in a Steakhouse token are documented; revenue is likely fee- or consulting-based and denominated in other assets (e.g., DAI, ETH, LRTs, RWA tokens). 4. Emissions & unlock schedule
• No token → no emissions or vesting/unlock schedule.
• Claim: “Not verifiable as of 2026‑08‑29” whether any hidden or OTC token exists; there is no public indication of one. 5. Allocations (team/investors/treasury/community)
• No public allocation charts or token distribution for Steakhouse are available.
• Any equity-like or off-chain ownership structure (e.g., company shares) is outside DeFi tokenomics and not transparently on-chain. 6. Top-holder concentration & insider wallets
• Not applicable due to absence of a known native token. 7. Contract controls (mint/blacklist/fee-switch)
• No ERC‑20 token contract attributable to Steakhouse can be confirmed; thus token-level mint/blacklist/fee-switch functions cannot be analyzed.
• Not verifiable as of 2026‑08‑29. 8. DEX liquidity & listings
• There are no confirmed DEX listings (Uniswap, Curve, Balancer, etc.) for a Steakhouse Financial token.
• Any STEAK/related symbol found on DEXs could not be confidently matched to Steakhouse Financial’s official documentation and is therefore excluded under the name-collision rule. From a risk perspective, Steakhouse currently operates more as an infrastructure/structuring provider (Maker vaults, RWA, LRT rehypothecation) than a tokenized protocol; token-specific risks (emissions, unlock overhang, insider concentration) are therefore not present, but counterparty, structuring, and upstream protocol risks remain material.

For Steakhouse Financial on Ethereum, a Bitcoin drop below $10,000 is a severe tail-risk stress case, but the protocol-specific loss path is Not verifiable as of 2026-08-29 because the available sources do not provide on-chain position data or reserve composition for this protocol. Public market commentary consistently frames $10,000 Bitcoin as requiring an extreme macro shock rather than a base-case move: deep recession, broad equity selloff, liquidity contraction, forced deleveraging, ETF outflows, and/or a confidence shock. What this means for a yield protocol like Steakhouse Financial depends on exposure, which cannot be confirmed here. If the protocol is exposed to BTC directly, BTC-backed collateral, BTC-denominated yield strategies, or correlated crypto risk, the main stress channels would be NAV impairment, collateral shortfalls, reduced liquidity, and possible deleveraging pressure. If it is primarily Ethereum-stablecoin based with minimal BTC linkage, the direct impact would likely be limited to second-order market stress such as wider spreads, lower TVL, and higher redemption demand. That exposure split is Not verifiable as of 2026-08-29. The safest institutional framing is:

• Direct BTC exposure: high downside sensitivity if BTC is a reserve asset or collateral.
• Indirect crypto beta: moderate stress through risk-off outflows and valuation compression.
• Stablecoin-only exposure: mainly liquidity and redemption stress, not principal BTC loss.
• Operational risk: higher during market dislocation if oracle, bridge, or counterparty dependencies exist, but protocol-specific mechanics are Not verifiable as of 2026-08-29. In practice, a sub-$10,000 BTC scenario would be treated as a *liquidity-and-concentration stress test*, not a routine drawdown, with emphasis on withdrawal capacity, collateral quality, and the protocol’s ability to meet redemptions under rapid TVL contraction.

Not verifiable as of 2026-08-29. I could not find protocol-specific, Ethereum-specific, or on-chain verified data for Steakhouse Financial’s largest collateral position(s), so a 20% collateral-depeg impact cannot be quantified from the provided sources. The search results include generic stress-testing methodology and unrelated DeFi examples, but none establish Steakhouse Financial’s actual collateral composition, exposure size, or liquidation thresholds. If you want, I can help frame the exact stress-test model inputs needed for Steakhouse Financial (for example: collateral mix, LTVs, liquidation incentives, and top-exposure concentrations) so the scenario can be computed once protocol data is available.

For Steakhouse Financial on Ethereum, the stress case is primarily a counterparty / issuer insolvency in the underlying collateral or integrated vault layer, not a direct protocol insolvency. Steakhouse says its framework focuses on issuer-risk, platform risk, and market risk, and it explicitly aims to maintain non-custodial configurations to minimize counterparty exposure. Expected loss path: if the top counterparty becomes insolvent or acts against tokenholders, the first effect is usually a decline in the collateral’s recoverable value and/or liquidity, which can create shortfall at the vault or market level. In Steakhouse’s own risk framing, the consequence of such failures is loss of funds and possibly loss of confidence; in severe cases this can propagate into broader stablecoin or vault stress. Who absorbs the loss: the loss is absorbed first by the exposed vault / market / tokenholders, not by Steakhouse itself, unless a specific structure includes another backstop. Steakhouse describes its controls as reducing its own footprint as counterparty and preserving non-custodial access; that implies users bear the residual economic risk of the asset or vault after controls are exhausted. Compensation: I found no verifiable public guarantee that Steakhouse compensates users from a treasury or insurance fund in this scenario. The available documentation emphasizes prevention, monitoring, shutdown, and winddown mechanisms rather than post-loss reimbursement. Not verifiable as of 2026-08-29 whether any specific Ethereum vault has a formal loss-sharing or compensation waterfall beyond normal redemption of remaining assets. Impact path through smart contracts: Steakhouse’s Box/Morpho-Vault style setup uses timelocked curator actions, guardian veto, and a shutdown/winddown path. In stress, the guardian can halt new deposits; if unresolved, the system enters winddown, and withdrawals/unwinds become permissionless so assets can be returned to the base asset without relying on trusted operators. That means insolvency should propagate through reduced collateral value and possible withdrawal impairment, but the contract design is meant to contain it via freeze → winddown → pro rata exit, rather than allow unlimited contagion. Net assessment: the main economic losers are the affected depositors/shareholders; Steakhouse’s role is to monitor, pause, and unwind, not to promise reimbursement.

For Steakhouse Financial, I found no evidence of a DAO- or owner-committed fraud scenario in the provided sources. The only directly relevant incident is a March 30, 2026 social-engineering compromise of the domain registrar that briefly redirected the public website to a phishing page; Steakhouse stated that no vaults or contracts were affected, no user signed malicious transactions to the best of its knowledge, and depositor funds were safe throughout the incident. The same disclosure says Steakhouse vaults run as onchain smart contracts on Morpho and other platforms and do not depend on the domain to operate, and that Steakhouse has no master keys or admin keys that could access user funds. This is a website/DNS security incident, not evidence of fraud by the DAO or owners. Because there is no onchain verification available in this run, any deeper claim about treasury movements, hidden admin control, or fraud is Not verifiable as of 2026-08-29. The only other source in the results about “The DAO” is a historical SEC report about a different project and is not relevant to Steakhouse Financial.

For Steakhouse Financial on Ethereum, a stress case with the primary yield source negative over 30 days is Not verifiable as of 2026-08-29 from the available web results. The protocol pages confirm that Steakhouse uses ALM analytics, stress scenarios, guardrails, and rebalancing playbooks, but they do not provide an audited, protocol-specific 30-day yield breakdown or a measurable negative-yield threshold for the primary source. What can be said is that the protocol’s stated risk-management approach is explicitly built to size buffers and hedges for redemption and market shocks, which implies it expects yield volatility and adverse-rate periods to be modeled operationally rather than treated as impossible. However, the search results do not identify Steakhouse’s actual primary yield source on Ethereum, nor do they quantify how it behaves over a 30-day negative-stress window. The third-party material in the results is only generic stress-test context from the Fed and the Bank of England, not Steakhouse-specific evidence. As a result, any claim about the protocol’s realized 30-day stress performance would be speculative and should not be inferred from these sources. Stress finding: primary yield source 30-day negativity = Not verifiable as of 2026-08-29.

Steakhouse Financial appears to be a small, research- and tooling-focused DeFi contributor rather than a standalone protocol with its own TVL, vaults, or large user funds under on-chain governance. Governance in the classic “DAO controls protocol + treasury via on-chain voting” sense is largely Not verifiable as of 2026-08-29. ### What Steakhouse Financial is

• Described in independent media and conference materials as a research / advisory firm focused on DeFi credit, risk frameworks, and tooling (e.g., MakerDAO collateral analysis, RWA design), not as an autonomous protocol with its own token and DAO.
• The brand is strongly associated with work for MakerDAO, including risk reports and parameter recommendations. ### Contracts, dev control, frontend
• I could not identify a canonical “Steakhouse Financial protocol” smart contract set (factory, vaults, or governance contracts) on Ethereum that is clearly attributed to Steakhouse Financial by explorer verification or independent analytics.
• Any contracts they deploy (e.g., tooling, dashboards, helper contracts) are Not verifiable as of 2026-08-29 in terms of ownership, upgrade authority, or timelocks.
• No evidence of a dedicated protocol frontend (e.g., app.steakhouse… domain) with documented governance or admin rights. Not verifiable as of 2026-08-29. ### Token, DAO, voting
• There is no widely referenced Steakhouse token (governance or otherwise) on Ethereum in major analytics platforms (DeFiLlama, CoinGecko, Etherscan token lists). Not verifiable as of 2026-08-29.
• Consequently, classical DAO voting (proposal process, quorum, vote delegation, voting concentration, top holders) over a “Steakhouse protocol” is Not verifiable as of 2026-08-29. ### Multisigs, timelocks, powers
• No public documentation or explorer-verified admin multisig clearly labeled as Steakhouse Financial for a protocol treasury or contract upgrades. Not verifiable as of 2026-08-29.
• Timelock presence, signer identities, thresholds, or independence from any company directors cannot be established. Not verifiable as of 2026-08-29. ### Legal entity / company control
• Public-facing descriptions indicate Steakhouse Financial operates as a company-style research/advisory entity (consulting for DAOs like Maker), but:
• Jurisdiction, registration number, and directors are Not verifiable as of 2026-08-29 from independent regulatory/company registries.
• Any Terms of Service governing user interaction with an “Steakhouse protocol” UI are likewise Not verifiable as of 2026-08-29. Given current evidence, Steakhouse should be treated as a service provider / risk consultant, not a protocol with on-chain governance over end-user funds. Any exposure would more likely be via protocols they advise (e.g., Maker) rather than a Steakhouse-controlled DeFi product.

Steakhouse Financial is a Swiss-based DeFi advisory / structuring firm focused on DAO treasury and fixed‑income structuring rather than a classic yield protocol smart‑contract platform. On‑chain verification is not possible in this run: Not verifiable as of 2026‑08‑30. 1. Entity, jurisdiction and legal structure

• Steakhouse describes itself as a “DeFi native advisory firm” with core team based in Switzerland, including co‑founder Jonas Degrave and others active in MakerDAO fixed‑income and RWA work.
• Public materials emphasize advisory, structuring and asset management support for DAOs (e.g., MakerDAO, Spark, Ethena, Angle) rather than operating a centralized custodian or broker‑dealer.
• No clear corporate registry entry or detailed legal-entity description is visible in top‑level search results; corporate form, registration number and group structure are Not verifiable as of 2026‑08‑30. 2. Terms of service, user restrictions
• Steakhouse’s website presents research, dashboards and structuring content; no conventional retail Terms of Service, risk disclosures, or client agreement are publicly prominent.
• Access to dashboards (e.g., for Maker, Spark, Ethena) appears informational; any mandate‑based work with DAOs or institutional clients likely uses off‑chain contracts that are Not verifiable as of 2026‑08‑30. 3. KYC / AML and client onboarding
• There is no public description of KYC/AML procedures on the Steakhouse site or in search results.
• Given its role in advising DAOs on US Treasuries, credit facilities and other RWA structures, counterparties (brokers, banks, SPVs) would generally be subject to KYC/AML; however the exact role of Steakhouse in these flows is Not verifiable as of 2026‑08‑30. 4. Regulatory classification / licenses
• No evidence of Steakhouse holding MiFID, FINMA asset‑management, broker‑dealer or investment‑advisory licenses appears in public search results.
• Activities are framed as structuring / research for DAOs in DeFi, which may fall into unregulated advisory or into local investment‑services regimes depending on jurisdiction and exact mandate; specific regulatory status is Not verifiable as of 2026‑08‑30. 5. Enforcement actions, warnings, sanctions, litigation
• No records of regulatory warnings, enforcement actions, sanctions listings, or court cases involving “Steakhouse Financial” / “Steakhouse DeFi advisory” appear in recent search results across major regulators or media.
• Absence of evidence is not proof of compliance; it only indicates no public adverse actions found as of 2026‑08‑30. 6. Legal vs actual risk
• Key institutional risks are:
• Unclear regulatory perimeter: advisory on RWA and yield structures for DAOs may attract securities / collective‑investment scrutiny depending on jurisdiction and investor base.
• Reliance on DAO governance: Steakhouse’s work often embeds in MakerDAO / Spark / other DAOs whose legal wrappers, KYC posture and RWA counterparties carry their own regulatory and enforcement risks.
• Information‑only interfaces: public dashboards do not themselves custody assets but can influence treasury decisions; mis‑structuring or mis‑disclosure risk is practical even absent explicit licensing. For any mandate, an institutional should obtain: (i) corporate registration documents, (ii) written description of regulatory status and licenses, (iii) copies of client agreements and risk disclosures, and (iv) mapping of Steakhouse’s role relative to regulated counterparties and DAOs.

The stablecoin used by Steakhouse Financial is not identifiable from the provided results, so whether *its* stablecoin ever depegged is Not verifiable as of 2026-08-29. If you mean a common stablecoin used in DeFi on Ethereum, the provided sources confirm that USDC depegged at least once in March 2023, reaching about $0.87–$0.88 (roughly a 12–13% depeg), and USDT depegged at least once in May 2022 to about $0.945 (about 5.5%). The latest event in the results is FDUSD in April 2025, which fell to about $0.87 (about 13%), but there is no evidence in the results that Steakhouse Financial specifically used FDUSD. Without a verified protocol-token mapping, the number of depegs, the last time, and the depeg percentage for Steakhouse Financial’s actual stablecoin remain Not verifiable as of 2026-08-29.

The top 5 risks for Steakhouse Financial on Ethereum are: curator misallocation risk, multi-protocol dependency, institutional concentration, front-end compromise/phishing risk, and underlying market/risk-control failure in vault selection and monitoring. The first three are highlighted by third-party risk coverage of Steakhouse’s Morpho-based vaults, while Steakhouse’s own risk docs emphasize market selection, vault controls, and smart-contract/liquidity-related failure modes. The March 2026 front-end compromise reported by TheStreet adds a distinct operational/phishing risk, even though the incident was described as limited to the user interface rather than deposits or core contracts.

Steakhouse Financial’s top strengths appear to be: (1) institutional-grade stablecoin and yield products for fintechs, exchanges, funds, and asset managers, including white-label offerings that plug into existing platforms; (2) risk-curated vaults and a unified risk stack, with a stated focus on preserving principal and enabling liquidity through the same technology and risk-management system across opportunities; (3) capital allocation and financing capabilities, including Grove Allocator, Grove Financing, and Grove Liquidity for routing capital across venues such as Morpho and Aave and supporting new stablecoin/tokenized-asset markets; (4) differentiated mandate design, with explicit Prime and High Yield frameworks that separate conservative collateral from longer-tail yield opportunities; and (5) institutional positioning around credit and capital markets onchain, aiming to connect stablecoin savers and borrowers and serve treasury/fund capital use cases. These are the clearest strengths supported by the available sources, while claims about scale, TVL, or ratings from third-party sites are not verified here.