K3 Capital

K3 Capital appears to have a real, functional web app rather than only a static landing page: the site exposes an Earn tab, wallet connect flow, vault browsing, deposit/withdraw actions, and a Portfolio tab, with browsing available before wallet connection. The public FAQ says deposits and withdrawals are performed directly through on-chain contracts and that users can withdraw subject to underlying protocol liquidity; it also says the interface can be bypassed via Etherscan or another DeFi interface if the front end is down. That said, the presence of multiple domains and dated material means some branding surfaces look inconsistent, so the maturity signal is moderate rather than fully polished. On live functionality, the site claims “most vaults” allow instant withdrawals, while some strategies may use a short queue during high utilisation; these are platform claims, not independently verified here. I could not verify live deposits/withdrawals on-chain in this run, so the state of actual executed flows is Not verifiable as of 2026-08-29. Docs/UX are present via a GitBook-style documentation page and a FAQ page, which indicates more than a pure marketing splash page. The site also shows chain-specific support text for Ethereum and Plasma on the main app, while a third-party listing mentions broader chain exposure; that inconsistency should be treated cautiously. I did not find strong evidence of broken links or fake metrics in the surfaced pages, but the totals and APY figures shown on the site are self-reported and remain unverified without on-chain cross-checks. An open API was not evidenced; the available pages describe wallet-based app interactions and direct contract access, but no public API documentation or developer endpoint was found.

Identified ChainSecurity audit of K3 Capital’s sBOLD smart contracts (Liquity-based ERC‑4626 vault). The report is hosted on ChainSecurity’s domain and clearly labeled for K3Capital / sBOLD. The scope focuses on accounting correctness, reentrancy risks, interactions with Liquity Stability Pools, price conversions, fees, and ERC‑4626 compliance. A secondary independent aggregator (DefiCare) summarizes this audit as covering sBOLD Version 3, not the full K3 Capital platform. Date (as-of): DefiCare lists the ChainSecurity audit date as 19‑05‑2025. This is off-chain, aggregator-sourced data. Findings and severities:

• DefiCare summary: 2 Critical, 3 High, 8 Medium, 11 Low, 3 Informational initially identified.
• It states that all Critical, High, and Medium findings were resolved, with 2 Low-severity issues remaining open ("SP cannot be emptied" and "slippage tolerance extraction"), both described as unlikely to materialize or mitigated by Liquity’s design. Fix status: According to DefiCare, all Critical, High, Medium issues were fixed; two Low issues remain by design/mitigation rationale. This is not on-chain verified; status depends on the audit report and aggregator interpretation. Not verifiable as of 2026‑08‑29. Bytecode / deployed-code coverage:
• The ChainSecurity PDF itself is a source-level review; none of the retrieved content explicitly confirms a formal bytecode match check against deployed contracts.
• No explorer-based confirmation (contract verification plus matching commit hash) was retrieved in this run.
• Therefore whether this audit fully covers the currently deployed sBOLD bytecode across Monad, Ethereum, Optimism, Plasma, Arbitrum, Binance, Unichain, BOB is Not verifiable as of 2026‑08‑29. Scope vs. protocol: All evidence points to this audit covering sBOLD, a specific yield strategy vault using Liquity/BOLD, not the entire K3 Capital protocol on all chains.

Identified Dedaub smart contract audit of sBOLD, commissioned by K3 Capital. The report describes sBOLD as an ERC‑4626 implementation aggregating yield from interest accrual and liquidation penalties in Liquity. Date (as-of): DefiCare lists the Dedaub audit date as 19‑05‑2025. Dedaub’s own page is consistent with a 2025 report but the exact calendar date is taken from the aggregator, not from the PDF itself. Scope:

• Dedaub states the audit covers contracts in the then-private GitHub repository https://github.com/K3Capital/sBOLD at commit 3630c7f6247b8fc8a709a9cfd036a90028fe0064.
• Scope is limited to core sBOLD vault contracts, including ERC‑4626 behavior and interactions with Liquity (oracle pricing and BOLD liquidity are highlighted as design-level risks). Findings and severities:
• DefiCare summary: 0 Critical, 0 High, 0 Medium, 1 Low, 0 Informational issues identified.
• The single low‑severity issue was acknowledged by the team; the summary states the contract appears safe for deployment from a smart-contract perspective, while emphasizing remaining protocol-level risks (liquidity, oracles). Fix status:
• DefiCare notes the low-severity issue was acknowledged; it does not clearly confirm if it was fully remediated in code.
• Dedaub’s own narrative emphasizes that the audit cannot guarantee correctness and focuses on remaining design risks.
• Specific fix status and post-audit code changes are Not verifiable as of 2026‑08‑29. Bytecode / deployed-code coverage:
• Dedaub explicitly ties the audit to a source-code commit hash in the private repository.
• There is no publicly retrieved evidence in this run that the deployed contracts on any chain were verified to match that commit byte-for-byte (e.g., via explorer verification or separate "bytecode match" section in the report).
• Multi-chain deployment status (Monad, Ethereum, Optimism, Plasma, Arbitrum, Binance, Unichain, BOB) and whether all instances match the audited commit is Not verifiable as of 2026‑08‑29. Scope vs. protocol: Like ChainSecurity, Dedaub’s audit appears strategy-specific (sBOLD) and does not constitute a full-platform audit of all K3 Capital vaults and integrations.

Not verifiable as of 2026-08-29. The available web results did not confirm a K3 Capital bug bounty program; the only bounty result found was for an unrelated company, Capital.com, which is a namesake collision and cannot be used for this protocol. No reliable source in the gathered material established an active program, start date, scope/parameters, or any disclosed results for K3 Capital. If a program exists, it remains unverified from the current evidence.

K3 Capital’s externally visible dependency profile is only partially verifiable from web sources, so the main conclusion is that counterparty risk is material and several key dependencies are not fully verifiable as of 2026-08-29. The protocol appears to deploy across multiple chains, with public aggregators showing meaningful exposure on Monad, Ethereum, Optimism, Plasma, Arbitrum, Binance Chain, Unichain, and BOB, but chain-by-chain exposure should be treated as an aggregated market view rather than on-chain verified evidence. The clearest *documented* dependency is on external money markets and yield venues: third-party coverage states K3 routes capital through Euler v2, Morpho, IPOR, and Liquity v2, and another source describes vaults interacting with Euler, Morpho, Pendle, Balancer, and Gearbox. That means K3’s solvency and yield can be affected by the failure, exploit, pause, or parameter change of any underlying venue. For oracle / manipulation risk, one independent risk report claims K3 markets use Chainlink, Pyth, and Redstone across multiple chains, but this is not directly corroborated by protocol-independent on-chain evidence here, so oracle design and manipulation resistance are not verifiable as of 2026-08-29. For stablecoin / LST / restaking exposure, public materials and third-party listings indicate exposure to USDT0, sBOLD (a yield-bearing stablecoin tied to Liquity v2 Stability Pools), and rsUSDe (described as a liquid restaking token backed by stablecoin collateral). These structures add depeg, redemption, and underlying-protocol contagion risk; however, the exact portfolio weights and whether these are live exposures across every chain are not verifiable as of 2026-08-29. For custody / bridge / CEX-MM risk, no reliable source found here confirms a trusted custodian, bridge architecture, or centralized exchange / market-maker dependency. Those items are not verifiable as of 2026-08-29. Failure scenarios most relevant to K3: underlying lending-market exploit, oracle failure, stablecoin depeg, restaking-token unwind, or a cross-chain deployment issue could impair NAV, block withdrawals, or force deleveraging. Any claim that K3 is “fully audited” or “safe” should be treated as unverified marketing claim unless supported by independent audit and live on-chain checks.

K3 Capital’s custody model appears to be non-custodial: users keep their private keys, and assets stay in on-chain vault contracts rather than being held in an off-chain account by K3. The protocol says deposits are standard ERC-20/vault interactions, that users receive vault share tokens, and that the platform is a convenience/risk-management layer rather than a custodian. Operationally, custody is organized through smart contracts: users deposit into vaults, the contracts route capital into underlying lending or yield venues, and users later redeem their shares from the vault. K3’s role is to manage allocations, parameters, and strategy selection, while the on-chain contracts execute the transfers. K3 also states that if its website/front end is unavailable, users can still interact directly with the underlying contracts, which is consistent with assets remaining under the control of the on-chain vault system rather than a centralized custody stack. Important caveat: these custody descriptions come mainly from K3’s own materials and related commentary, so the non-custodial structure is not independently verified here from on-chain data. Not verifiable as of 2026-08-29.

Not verifiable as of 2026-08-29. I found no independently confirmed incident report for K3 Capital in the available web results. The only K3 Capital-specific source located is the project’s own page, which claims the platform does not hold custody of assets in any off-chain system and that material parameters, fee recipients, strategy allocations, and pause-guardian addresses are publicly readable on-chain; it also says the team will publish incident post-mortems within 72 hours if something goes wrong. These are unverified marketing claims because they come from the protocol itself. No external evidence of an exploit, loss, reimbursement, or fix was verifiable from the gathered sources.

K3 Capital’s key management, as described in the available sources, is organized around shared operational control rather than a single opaque custodian. The protocol says it does not hold assets in off-chain custody, keeps material parameters such as fee recipients, strategy allocations, and pause-guardian addresses readable on-chain, and states that it avoids “admin keys with no public disclosure.” It also says clients have full visibility over the on-chain addresses being managed via an investor portal. At the protocol level, key-related control appears to be split across publicly disclosed roles and on-chain configuration. The available material indicates that pause-guardian addresses are disclosed, and that risk limits are set at both protocol and network levels for portfolio management. In other words, operational authority is organized through transparent smart-contract parameters and monitored execution, not through hidden off-chain key custody. What is not verifiable as of 2026-08-29 from the provided sources is the exact signing setup for treasury wallets, who holds the private keys, whether keys are multisig/MPC/EOA, and what specific rotation or emergency-recovery procedures are used. The sources confirm transparency claims, but they do not disclose the full key-operations model in technical detail.

K3 Capital is not verifiable as a DeFi protocol team/founders case from the evidence gathered. The web results mostly identify separate, non-crypto entities named K3 Capital / K3 Capital Group / K3 Ventures / K3 Capital Solutions, so name-collision risk is high. For the best-matching non-crypto entity, K3 Capital Group, public records show it was incorporated in England and Wales in 2007 and that Tony Ford founded it, with John Rigby as CEO and a Bolton, UK headquarters; those facts indicate a real operating business, but they do not establish anything about the yield protocol itself. There is also a Singapore-based K3 Ventures team page listing named personnel and an office in Singapore, again a different entity. No reliable source in the gathered material proves the yield protocol’s founders, prior projects, hack history, office, or onshore/offshore structure, so those items are Not verifiable as of 2026-08-29. The main reality-check finding is that the available web evidence points to legitimate businesses sharing the K3 name, but not to a verifiable public founder/team profile for the DeFi protocol under review.

K3 Capital appears to be a real, long-running UK professional-services group rather than a DeFi protocol, and the web results do not surface any credible evidence of fraud, rug-pull, insolvency, sanctions, or regulator action tied to the entity matched here. Public materials identify it as a business advisory group founded in 1998/2007-era corporate structure, later acquired by Sun European Partners in 2023; those are investor/ownership signals, not a DeFi audit trail. On reputation, the available sources are mostly neutral-to-positive corporate and transaction announcements. Sun European’s acquisition notice frames K3 as a “defensible business” with performance-improvement opportunities, and K3-related pages describe the group as a multi-disciplinary SME advisory platform. A separate corporate record shows named auditors/advisers in earlier filings, including BDO LLP, but I could not verify any current blockchain-security auditor because this is not evidenced as a DeFi protocol. Criticisms or adverse sentiment were not materially present in the retrieved results. The only clear negative signal is that this search set exposes a possible name collision: the matched entity is K3 Capital Group/K3 Capital Partners in traditional finance, while your prompt describes a yield DeFi protocol on multiple chains. Because I could not verify that the web results correspond to an on-chain protocol, protocol-level reputation claims are Not verifiable as of 2026-08-29. Legal/regulatory: the results show a 2023 UK High Court-sanctioned scheme of arrangement for the acquisition, which is a corporate transaction event, not a fraud or enforcement case. No sanctions, criminal proceedings, or insolvency allegations were found in the retrieved material. Unresolved concern: the protocol identity itself remains unconfirmed, so any founders/investors/auditors specific to the DeFi project are Not verifiable as of 2026-08-29.

K3 Capital appears to be a relatively new / niche protocol with very limited independent coverage; most information comes from its own site and social channels, so nearly all economic-model details are unverified marketing claims as of 2026-08-29. Where data is missing, I explicitly state it. High-level strategy & assets

• K3 Capital presents itself as a yield / structured products protocol aggregating DeFi strategies across multiple chains.
• Exact product set, per-product mandates (market-neutral vs directional), and target assets (stablecoins vs majors vs LSTs/LRTs) are not independently documented. Yield sources & risk profile
• The site and docs suggest yields are generated via DeFi strategies on external protocols (e.g., lending, liquidity provision, possibly restaking-type strategies), but no independent breakdown of:
• share of yield from organic sources (trading fees, borrow interest) vs subsidized incentives (token rewards),
• allocation by venue or chain,
• use of leverage / looping. These are therefore unverified marketing claims.
• No third‑party analytics (DefiLlama, Token Terminal, etc.) provide a clear classification of K3 strategies as market-neutral vs directional. Not verifiable as of 2026-08-29. Lock-ups, withdrawals, gates
• Public docs indicate products may have epoch-based or notice-period withdrawals, with potential cooldowns and capacity limits; exact mechanics per product (e.g., T+X redemption, exit fees, or gate thresholds) are not independently confirmed. These details are unverified marketing claims.
• No evidence of formal hard lock-ups (e.g., >30–90 days) in independent sources. Not verifiable as of 2026-08-29. Fees & protocol revenue
• K3 claims to charge management / performance fees on products; schedules and split between protocol vs managers are not externally validated.
• No public financials or revenue dashboards on analytics platforms. Not verifiable as of 2026-08-29. Collateral, TVL, chain split
• Chains listed by the project include Monad, Ethereum, Optimism, Plasma, Arbitrum, BNB Chain, Unichain, BOB.
• I could not find a DeFiLlama or similar listing with consistent TVL figures for K3 Capital, nor an independent dashboard breaking TVL down by product or chain. Not verifiable as of 2026-08-29. APY history, volatility, sustainability
• There is no independent APY history (time series) from aggregators or dashboards.
• Any APY figures on k3.capital or marketing materials are point-in-time, self-reported, and unverified. Given the absence of independent on-chain or analytics coverage, the economic model of K3 Capital cannot be rigorously characterized at this time. Any institutional allocation would require direct data-room access and chain-by-chain contract review.

Not verifiable as of 2026-08-29. The web results only confirm that K3 Capital’s site exists and that it says clients can see on-chain addresses in an investor portal, but they do not provide a treasury size, specific reserve wallets, asset composition, custody setup, reserve policy, or third-party attestations for the protocol’s treasury. The only related on-chain-adjacent clue is a social post claiming monthly reserve reporting and third-party attestations for stablecoin issuers, but that is not a verifiable K3 Capital treasury disclosure and should be treated as unverified marketing unless independently documented. The requested chain-by-chain reserve balance breakdown is also not verifiable here.

Not verifiable as of 2026-08-29: I could not confirm K3 Capital’s actual on-chain positions, collateral composition, or chain-by-chain exposure with the available evidence. In a BTC < $10,000 stress scenario, the plausible risk channels for a yield protocol are: direct losses on any BTC-denominated treasury/LP exposure, liquidation risk on BTC-backed borrow positions, contagion from correlated collateral depegging, and sharp TVL outflows if users de-risk. The external evidence available here only shows that some market commentators have discussed BTC targets near $10,000, while others argue BTC’s bear-market floor is much higher; that disagreement means the stress case is a tail scenario rather than a consensus base case. If K3 Capital has no direct BTC exposure, the main impact would likely be second-order: reduced user confidence, lower incentive yield, and possible liquidity fragmentation across Ethereum, Optimism, Arbitrum, Binance, Unichain, BOB, Monad, and Plasma. If you want, I can next produce a protocol-specific stress checklist covering reserves, oracle dependencies, liquidation thresholds, and cross-chain liquidity concentration.

Not verifiable as of 2026-08-29. The provided sources do not disclose K3 Capital’s live collateral inventory, per-chain exposure, or the exact collateral factors / liquidation thresholds needed to compute the impact of a 20% depeg on the largest collateral asset. What can be stated from the available material is only that K3 Capital uses collateral-specific risk parameters such as minimum collateralization ratios, debt ceilings, and stability fees, and that its Unichain vault lends USDC against volatile crypto collateral including WBTC, WETH, wstETH, weETH, and UNI. Without on-chain positions or a current risk snapshot, the loss / liquidation impact of a 20% depeg on the largest collateral cannot be calculated reliably. A conservative risk interpretation is that a 20% decline in the largest collateral’s price would reduce its mark-to-market value by 20%, but whether that causes undercollateralization, liquidation, or no loss depends on the vault’s actual leverage and buffers, which are not verifiable here.

Top-level: K3 Capital is a risk curator / vault manager that routes depositor funds into underlying lending / yield protocols (Euler, Morpho, IPOR, Liquity, Term Finance, etc.). In a stress where the largest underlying counterparty becomes insolvent, losses propagate mainly through those underlying protocols into K3-managed vaults, and then to depositors. Below I treat “top counterparty” as the largest underlying protocol or borrower exposure per vault. Exact on-chain positions are *Not verifiable as of 2026-08-29*. ### 1. Insolvent underlying lending protocol (e.g., Euler / Morpho) Expected loss path

• Borrowers on the affected market fail to repay; collateral is insufficient or liquidations fail.
• The lending protocol records bad debt; interest stops accruing; claims on collateral are impaired.
• K3 vaults holding LP / cTokens / morpho positions in that market see their asset price fall toward recovery value. Who absorbs it
• Economic loss is borne by vault depositors (holders of vault share tokens like tsvk3USDT or similar).
• K3 Capital as curator suffers reputational and fee revenue impact but does not automatically cover principal; no native insurance is documented. Compensation
• Any compensation would depend on:
• The failed protocol’s own recovery / bailout, governance decisions, or legal action.
• Off-chain fund agreements between K3 and specific institutional clients.
• There is no evidence of an on-chain automatic indemnity mechanism. *Not verifiable as of 2026-08-29*. Smart-contract impact path
• Underlying lending tokens depeg or freeze (e.g., markets paused).
• K3 vault smart contracts still function, but redemptions return devalued assets, reflecting loss.
• If the protocol’s tokens become non-transferable, vaults may be stuck with illiquid positions, causing prolonged withdrawal restrictions de facto. ### 2. Insolvent structured product / stablecoin counterparty (e.g., sBOLD, rsUSDe, Elixir-like case) Expected loss path
• Stablecoin/structured token loses peg or is revealed fraudulent; collateral cannot be reclaimed.
• Vaults holding that token mark it down; share price drops accordingly. Who absorbs it & compensation
• Again, vault depositors take the economic hit; K3 may pursue off-chain legal remedies (as in the Elixir dispute).
• Any recovered funds via courts would be off-chain and discretionary; no deterministic smart-contract payout path is visible. *Not verifiable as of 2026-08-29*. Smart-contract impact path
• Peg loss → price oracle updates → vault share value reprices downward.
• If the token contract is frozen or rug-pulled, vault assets become non-redeemable, locking loss into the vault. ### 3. Cross-chain / multi-chain propagation
• K3 operates across multiple chains (Ethereum, Plasma, Avalanche, Arbitrum, Unichain, Binance, BOB, Monad, Optimism).
• Insolvency on one chain primarily impacts vaults on that chain; cross-chain bridges used in strategies can transmit losses if bridged representations depeg or are frozen. *Exact per-chain TVL splits Not verifiable as of 2026-08-29*. Overall: in a top-counterparty insolvency, losses travel from the failed protocol → K3 vault asset value → vault share price → depositors; smart contracts generally remain operational but reflect impaired asset valuations, and compensation—if any—is off-chain and non-deterministic.

For K3 Capital, I could not verify any public evidence of committed fraud by the DAO or its owners from the provided sources. The only protocol-specific source is a LinkedIn page that describes K3 Capital as a DeFi-native fund manager since 2021, but that is an *unverified marketing claim* and does not establish misconduct. In a stress scenario, the appropriate risk judgment is Not verifiable as of 2026-08-29. I did not find a regulator action, audit finding, governance record, or independent media report in the supplied results alleging fraud, theft, rug pull, or owner misconduct by K3 Capital itself. Important distinction: the search results contain general material about DAO fraud mechanisms and unrelated examples such as The DAO and Kelp DAO, but those do not implicate K3 Capital and should not be treated as evidence against this protocol. If you need a harder risk screen, the next step would be to verify the exact K3 Capital contracts and wallets on-chain and check whether they map to the entity described on the website/LinkedIn; that could not be completed here.

K3 Capital’s primary yield source negative over the last 30 days is not verifiable as of 2026-08-29 from the provided web results. The search results only include generic stress-testing references from central banks and policy sources, not protocol-specific data for K3 Capital, its strategy mix, or 30-day yield performance. For an institutional stress view, the correct treatment is to assume negative primary yield contribution until independently verified chain data or a reputable third-party dashboard confirms otherwise. Because on-chain verification is unavailable in this run, I cannot attribute the negative performance to any specific chain among Monad, Ethereum, Optimism, Plasma, Arbitrum, Binance, Unichain, or BOB. What can be stated from the available sources is only the general stress-testing principle: severe adverse scenarios are designed to test resilience under sharp market deterioration, lower risk appetite, and volatile rates, but these sources do not provide K3 Capital’s realized yield, TVL, or chain-level exposure.

Not verifiable as of 2026-08-29. The only clearly relevant result found is a 2025-11-07 report about K3 Capital threatening legal action against Elixir over the deUSD depeg, which mentions deUSD trading at about $0.04 during that event. That establishes at least one depeg of a stablecoin used in K3-related activity, but it does not verify whether K3 itself used deUSD in production, how many times any such stablecoin depegged, or the exact last depeg and percentage for K3’s own selected yield protocol. A separate K3 page mentions stablecoin vaults such as USDT, USDC, USDe, sUSDe, USR, USDT0, AUSD, NUSD, and BOLD, but it does not provide any depeg history.

K3 Capital’s top risks are: (1) curator/judgment risk—depositors rely on a private team to choose collateral, parameters, and rebalancing, so a bad allocation can create losses; (2) smart-contract/oracle risk—the Dedaub audit notes that an oracle malfunction could enable a bad swap and that the owner can change the oracle registry or swap adapter, widening attack surface; (3) multi-protocol interaction risk—K3 routes capital through several external DeFi protocols, so a failure in any underlying leg can cascade into the vault; (4) concentration/liquidity risk—third-party risk reports flag large exposure to a single strategy such as sBOLD/Liquity v2 Stability Pool, which can amplify losses in stress; (5) centralization/governance risk—K3 is a private firm with no governance token, so users have limited recourse if risk management deteriorates. A notable contradiction is that third-party analytics/risk reports cite different TVL and risk scores for the same protocol, which suggests fast-moving exposure and/or methodological differences; the more defensible issue for users is that K3’s risk profile is driven less by on-chain transparency and more by curator discretion and external-protocol dependence. Not verifiable as of 2026-08-29: precise on-chain exposure by chain (Monad, Ethereum, Optimism, Plasma, Arbitrum, Binance, Unichain, BOB), because on-chain verification was not available in this run.

K3 Capital’s top strengths appear to be: non-custodial design (users keep control of assets in wallet until they sign), multi-protocol routing (capital can be deployed across Euler v2, Morpho, IPOR, and Liquity v2 to target better rates), institutional risk curation (it presents itself as a professional asset/risk manager rather than a generic vault app), multi-chain support (public materials show Ethereum and Plasma today, with additional chains being evaluated), and transparent on-chain parameters (fee recipients, allocations, and pause-guardian addresses are described as publicly readable). These strengths are supported by K3’s own site and third-party summaries that describe it as a DeFi yield and lending platform focused on curated vaults and cross-protocol yield aggregation. A few details are worth treating carefully: claims such as “largest crypto-native asset managers,” “leading institutional asset and risk management,” and specific TVL figures are marketing or aggregator claims rather than raw on-chain verification in this run. Based on the available sources, the clearest differentiated strengths are the custody model, routing breadth, risk-curation focus, chain expansion, and transparency of protocol parameters.