Centrifuge V3

Protocol identification — Centrifuge (CFG)

• Name / website / docs: Centrifuge; centrifuge.io; docs.centrifuge.io. The selected entity matches the official centrifuge/protocol repository, contract documentation, and CFG token address—not the unrelated “Centrifugal” software projects.
• Category: RWA/tokenized-asset infrastructure and DeFi asset-management protocol. It tokenizes, distributes, and manages financial products across multiple chains using hub-and-spoke architecture.
• Launch date: Centrifuge Chain mainnet and Tinlake launched in May 2020. The Polkadot parachain launched in April 2022; V3 is the current EVM-native generation.
• Chains: Current documented deployments include Ethereum, Base, Arbitrum, Avalanche, Plume, BNB Smart Chain, Optimism, HyperEVM, Monad, Pharos, and X Layer; documented network IDs also include Solana, Stellar, and Arc. The documentation’s chain count and list are internally inconsistent, so the exact active set is Not verifiable as of October 19, 2026.
• Native token: CFG. The current Ethereum-native ERC-20 is 0xcccCCCcCCC33D538DBC2EE4fEab0a7A1FF4e8A94; it consolidated legacy CFG and WCFG at 1:1 under CP149.
• Core addresses published by Centrifuge: Hub 0xA4A7Bb3831958463b3FE3E27A6a160F764341953; Hub Registry 0x19f46D8130e610C6C0f0116EA40Fb781dEFaDE93; Accounting 0x050206c38f06e4710C4a37D39F75Ddc5c16a7396; Holdings 0x3f0c8D8d2637881c3f6d8531F51a47c2094C918d.
• Cross-check / verification: CFG is explorer-labelled and source-code verified on Etherscan; the listed core addresses were not independently explorer-verified here. A Dune raw-on-chain cross-check is Not verifiable as of October 19, 2026 because Dune MCP is unavailable. Fork lineage Centrifuge V3 is not evidenced as a direct fork of another protocol. Legacy Tinlake was inspired by MakerDAO and reused/adapted selected patterns/components, including the auth pattern and DAI-derived ERC-20 implementation, but added RWA securitization pools, tranche mechanics, and Centrifuge-specific infrastructure. V3’s changes received multiple security reviews; the deployment documentation cites four independent reviews and Sherlock verification. A documented history of malicious modifications in similar Centrifuge forks is Not verifiable as of October 19, 2026.

Centrifuge appears to have a real, functional product rather than a pure marketing landing page: the live app is publicly reachable, and the docs describe a working investment flow with pool pages, deposits, redemptions, and claim/withdraw steps. The documentation also exposes a public read-only API endpoint, with GraphQL access and no authentication required, so an open API does exist. Product maturity looks reasonably high for a DeFi protocol: the app and docs support synchronous vault deposits as well as asynchronous request/claim workflows, and the GitHub materials describe multi-chain protocol data, vault standards, and investor transaction tracking.

The app page and docs indicate an operational user interface rather than a placeholder, but the available sources do not verify the current success rate of live deposits/withdrawals or whether all links are working cleanly today. No clear evidence of fake metrics or template-site behavior was found in the retrieved sources, but that is not fully verifiable from web results alone. Not verifiable as of 2026-10-19 for broken links, current UX defects, or real-time transaction success rates.

Centrifuge has an active bug bounty program hosted on Cantina. Public reporting indicates the program was launched on 2025-07-17 and later expanded to cover V3.1; Centrifuge’s docs still describe it as a live $250,000 bug bounty program. The disclosed reward structure is up to $250,000 for critical findings, $50,000 for high severity, and $5,000 for medium severity.

The program also notes reduced payouts for some issues involving specific pool managers or cross-chain functionality. Publicly visible reporting says the program had recorded 480 findings by mid-2026, but no independently verifiable exploit-payout breakdown was found in the available sources.

Assessment — Dependencies & Counterparty Risk Centrifuge is an infrastructure layer, so the principal counterparty risk sits at the pool/product level rather than uniformly at protocol level. Each offering depends on an independent issuer/asset manager, the legal SPV or fund vehicle, trustees/administrators, banks and custodians, and the enforceability of investor claims. Centrifuge documentation explicitly states that products are offered by independent issuers; therefore issuer insolvency, fraud, servicing failure, valuation disputes, or SPV/legal-enforcement failure can impair recovery even if the smart contracts operate correctly. Oracle/NAV risk: Pool NAV is calculated on the hub and propagated to spoke chains.

The architecture supports both identity pricing and oracle-based valuation, creating reliance on issuer/manager inputs, valuation agents, and privileged update paths. A stale, manipulated, delayed, or erroneous NAV can cause mispriced subscriptions/redemptions and cross-chain contagion. Bridge and messaging risk: Cross-chain functionality uses adapters/integrations including LayerZero, Wormhole, Chainlink and Axelar; share-token transfers use native mint-and-burn mechanics. A compromised bridge, adapter, relayer, destination-chain halt, or message-ordering failure could freeze or create inconsistent representations of shares. DeFi/stablecoin exposure: Approved portfolio workflows can deploy pool assets into Aave or Morpho, bridge across chains, and use Circle CCTP or USDT0.

This introduces lending-protocol, stablecoin issuer/reserve, chain, liquidity and liquidation risk. Sky/Aave/Morpho/Pendle integrations are documented, but pool-specific allocations are not established here. CEX/MM exposure: Not verifiable as of October 19, 2026. Current dependency failure: Not verifiable as of October 19, 2026; no verified incident was identified in the reviewed sources. Maximum exposure percentage: Not verifiable as of October 19, 2026 because Dune/on-chain verification is unavailable and exposure is pool-specific. Key stress cases are issuer/SPV insolvency, custodian or bank failure, NAV error, bridge compromise, stablecoin depeg, DeFi liquidation, and redemption gates/queues.

Centrifuge V3’s custody is organized as a hub-and-spoke, pool-based system rather than a single omnibus wallet. Each pool selects one hub chain as its source of truth, while spoke chains host the tokenization layer; the protocol’s codebase describes separate escrows for pending-request assets and pool liquid assets, indicating assets are held in distinct onchain custody buckets at the protocol layer. For the specific Ethereum deployment, the available sources do not provide a verifiable, chain-specific custody diagram or evidence that custody is fully segregated at the wallet/address level for every investor; therefore segregated_assets = null.

The protocol and docs do state that pools, vaults, and escrows are deployed per pool/per chain, which is consistent with segregated operational custody, but the exact legal and address-level segregation on Ethereum is Not verifiable as of 2026-10-19 from the provided sources. There is also no source in the provided set showing a platform-wide withdrawal pause on Ethereum, so withdrawal_paused = null. In short, custody appears to be structured around per-pool vaults and escrows under a hub-and-spoke architecture, with offchain asset management common in Centrifuge’s institutional products, but the precise custody status for Ethereum is not independently verifiable from these results.

Centrifuge uses a layered, role-separated key-management model rather than one universal administrator:

• Protocol-wide control: An immutable Root contract holds administrative authority. It is accessed indirectly through two guardian contracts, each controlled by a separate Safe multisig: the Protocol Safe controls emergency response, protocol-level changes, upgrades, pausing, and cross-chain operations; the Ops Safe handles operational tasks such as adapter initialization, network wiring, and pool creation. The Ops Guardian reportedly has no pause authority.
• Delay and emergency controls: Privilege escalation through Root is subject to a 48-hour timelock. The protocol guardian can pause cross-chain messaging rapidly, while full resumption requires multisig consensus.
• Pool-level administration: Each pool has separate, non-hierarchical roles. The hub manager controls configuration, pricing, accounting, share classes, and cross-chain deployment; the balance-sheet manager controls asset movement and issuance; the request manager handles request routing; and the gateway manager can halt that pool’s cross-chain messaging. Roles can be assigned per chain and may be held by multiple addresses. Centrifuge recommends multisigs or institutional MPC wallets for high-impact roles and discourages a single EOA for production pools.
• Operational credentials: Centrifuge states that administrative accounts use hardware-based 2FA, credentials are managed with password managers and cloud KMS, access follows least privilege, and no single person holds all keys to a critical system. Sensitive deployments and configuration changes reportedly require multisignature authorization. These are protocol/operator disclosures, not independently on-chain verified findings.
• Automation: Lower-risk operational functions may use hot keys or bots where destinations and permissions are constrained on-chain—for example, offramp relayers and monitoring/response tooling. Risk conclusion: The architecture reduces single-key compromise risk through Safe separation, timelocks, scoped pool roles, and emergency pause authority. However, the public material reviewed does not disclose the exact Safe signer sets, signer independence, or m-of-n thresholds. Not verifiable as of October 19, 2026. On-chain verification is unavailable in this run.

Scope/addresses. Current v3.1–v3.3 deployments list Hub 0xA4A7Bb3831958463b3FE3E27A6a160F764341953, Hub Registry 0x19f46D8130e610C6C0f0116EA40Fb781dEFaDE93, Accounting 0x050206c38f06e4710C4a37D39F75Ddc5c16a7396, Holdings 0x3f0c8D8d2637881c3f6d8531F51a47c2094C918d; ProtocolGuardian 0xCEb7eD5d5B3bAD3088f6A1697738B60d829635c6; OpsGuardian 0x055589229506Ee89645EF08ebE9B9a863486d0dE. The guardian addresses are documented across supported EVM networks. Architecture. No proxy-admin architecture is documented for the current core: contracts are described as immutable/monolithic, with modular extensions and contract migrations rather than upgradeable proxies. Root is immutable, holds ward/admin authority over protocol contracts, and is reachable only through guardian contracts. The hub controls accounting/pricing; spoke chains host vaults/share tokens; cross-chain messages connect them. Protocol Safe → ProtocolGuardian → Root (wards) → Hub/Accounting/Holdings/vaults Ops Safe → OpsGuardian → operational setup/pool creation Hub ↔ GMP adapters/routers ↔ Spokes Privileges/risk. ProtocolGuardian handles emergency response, pausing, upgrades and cross-chain operations; OpsGuardian has no pause authority.

Global pause blocks cross-chain messaging but reportedly does not stop local deposit/redeem/withdraw operations. Root-mediated privilege escalation is documented with a 48-hour delay; emergency pause is immediate. A compromised guardian quorum could freeze cross-chain activity and, subject to the authorized message/extension paths, potentially redirect assets or install malicious behavior.

Historical audit context also identified escrow-transfer risk from a malicious router, while UserEscrow destinations were constrained. Verification gaps. Proxy-admin type via Dune decoded events: Not verifiable as of October 19, 2026. On-chain measured timelock delay, current Safe threshold/signers, role renouncements, and chain-by-chain exit liveness: Not verifiable as of October 19, 2026. Therefore, “users can always exit without admin” is not established; local withdrawals may remain available during a cross-chain pause, but asynchronous settlement and pool liquidity can still constrain exits.

Audited deployment is supported by published Sherlock deployment verification and multiple reviews, but unresolved issue counts are not independently consolidated here.

LonelySloth — V3.1–V3.3; Jan–Sep 2026; bug-bounty review.

Centrifuge was founded in 2017 and is publicly associated with repeat fintech founders rather than an anonymous team. The most consistently named founders across independent sources are Lucas Vogelsang, Maex Ament, Martin Quensel, Philip Stehlik, and Jeroen Offerijns, though some sources list slightly different co-founder sets. Lucas Vogelsang is described as CEO/co-founder; before Centrifuge he co-founded DeinDeal and worked at Taulia, while other co-founders are tied to Taulia and earlier supply-chain-finance work.

Philip Stehlik says he previously built fintech companies including Taulia, and the team’s background is repeatedly described as “silicon valley veterans” or seasoned repeat founders. The team’s credibility is materially strengthened by prior outcomes: Taulia is described as a successful supply-chain-finance company later acquired by SAP, and DeinDeal is described as an acquired e-commerce startup. I found no evidence in the provided sources that the team is anonymous or pseudonymous.

Centrifuge has a generally positive but cautious reputation in DeFi: it is widely described as an early RWA/private-credit pioneer with institutional integrations, long-running mainnet history, and multiple security reviews, but it also carries structural concerns around off-chain credit opacity, redemption liquidity, and regulatory complexity. The strongest negative event in the public record is a 2023 borrower/originator default that some analysts describe as a roughly $6 million unpaid-debt incident; later commentary says the team improved originator vetting and recovery processes, but the event remains a live reputational blemish. Independent risk writeups also stress that users cannot independently verify loan quality on-chain and must rely on issuers for asset performance and NAV reporting.

On security, Centrifuge’s own documentation says the protocol launched in 2019, has had 0 exploits, maintains a $250,000 bug bounty, and has undergone 24 security reviews, including Spearbit and Blackthorn. Third-party assessments are broadly consistent on “low exploit history” but emphasize that RWA systems have unique off-chain risks rather than classic smart-contract-only failure modes. Founders/investors: the provided results do not contain a reliable founder list or a verifiable cap table.

One media item notes Centrifuge was founded in 2017, and the protocol’s docs mention institutional use by Apollo, Janus Henderson, and S&P Dow Jones Indices, but those are not the same as investors. Legal/regulatory: the main concern is *regulatory complexity* around tokenized securities and off-chain credit enforcement across jurisdictions, not any clearly documented enforcement action or sanction in the retrieved results. I found no credible evidence in the results of sanctions, fraud charges, or insolvency proceedings against the protocol itself.

Unresolved concerns remain centered on counterparty default risk, liquidity during stress, bridge/multi-chain complexity, and the fact that off-chain assets are not fully transparent on-chain.

Economic model. Centrifuge is an RWA tokenization and distribution infrastructure protocol. Capital enters through pool-specific vaults into tokenized funds, private credit, corporate bonds/AAA CLOs, treasuries and other off-chain assets; proceeds and repayments exit through manager-controlled redemptions. Legacy Tinlake used NFT-collateralized loans and senior DROP/junior TIN tranches, while newer pools use share classes and pool balance sheets.

Yield is primarily asset-level interest, distributions and mark-to-NAV appreciation—not a protocol-wide liquidity-mining strategy. DefiLlama currently tracks 25–26 pools with average supply APY reported between 2.5% and 5.3% across its different pages; APY is pool-specific and history/volatility is not independently verifiable here. Current DefiLlama data reports zero incentives, supporting a predominantly organic-yield profile, but the organic percentage cannot be reliably decomposed across all products.

Risk is not market-neutral in the institutional sense: crypto-beta is limited, but investors retain credit/default, duration, liquidity, valuation, legal-enforcement, originator, custodian and concentration exposure. Leverage, looping and restaking are not core protocol mechanics; leverage may exist inside individual underlying funds or borrower structures and is product-specific. Redemptions are generally asynchronous: investors submit requests, managers approve or partially fulfill them, and assets are claimed after settlement.

Instant deposits may be available, but redemptions remain request-based. Deposit capacities, minimums, investor whitelists, jurisdiction rules, holder limits and configurable lockups/gates can apply. Fees are primarily manager/asset-management fees; DefiLlama reports approximately $5.83m fees and $478k protocol revenue over the latest 30-day period. TVL / contradiction. DefiLlama reports $1.505bn TVL: Ethereum $1.146bn (76.1%), Avalanche $262.3m (17.4%), Base $55.0m (3.7%), Plume $21.3m (1.4%), Monad $15.1m (1.0%), with smaller balances elsewhere.

Its RWA dashboard separately reports $953m active AUM, $1.076bn on-chain AUM and $453.6m DeFi-active TVL; this is a metric-definition discrepancy, not a confirmed economic loss. Dune comparison, product-level TVL, APY time series, and protocol-wide leverage are Not verifiable as of October 19, 2026.

Scope: Centrifuge protocol/DAO treasury, not investor assets held in Centrifuge-issued RWA funds. Treasury size and composition: No independently verified current USD treasury balance, asset-by-asset composition, or liabilities figure was found. Centrifuge’s tokenomics documentation states that the ecosystem allocation includes the Centrifuge Treasury, that locked incentive CFG vests into the Treasury through April 2029, and that 3% annual CFG inflation accrues to the Treasury. These are issuance/allocation policies, not proof of current liquid assets. Addresses and on-chain balances: A dedicated treasury address, wallet set, chain-by-chain balances, and custody allocation were not identified in the reviewed authoritative sources.

Dune MCP was unavailable for this run; therefore on-chain balances and valuation are Not verifiable as of October 19, 2026. No Dune query ID or execution ID exists for this assessment. Control and custody: Following CP171, approved November 3, 2025, active DAO governance is paused. The Centrifuge Network Foundation (CNF) has board-led oversight and “manages treasury”; CFG holders retain a process to reinstate DAO governance.

The protocol’s operational control layer is separate: Root permissions are mediated through Protocol and Ops guardian contracts controlled by separate Safe multisigs, with a 48-hour timelock for privilege escalation. The documented guardian addresses are 0xCEb7eD5d5B3bAD3088f6A1697738B60d829635c6 and 0x055589229506Ee89645EF08ebE9B9a863486d0dE; these should not be treated as treasury addresses without proof. Reserve policy and attestations: CP130 describes treasury spending objectives and funding sources historically including block rewards, transaction fees, and pool fees, with spending aligned to protocol-growth themes. A current formal reserve policy, third-party proof-of-reserves, financial statement, or treasury attestation was not found: Not verifiable as of October 19, 2026. Risk conclusion: Governance/control disclosures exist, but treasury transparency is insufficient to independently quantify liquidity, custody concentration, or liabilities.

CFG tokenomics (review date: October 19, 2026)

• Token/contract: Centrifuge (CFG), Ethereum ERC-20: 0xcccCCCcCCC33D538DBC2EE4fEab0a7A1FF4e8A94. The 2025 migration consolidated legacy CFG and WCFG 1:1 into this token.
• Supply/valuation: Official documentation reports 697,164,473 CFG total supply as of June 2026. CoinGecko currently reports 380.384M circulating, $45.9M market cap and $82.1M FDV, but also reports 680M total supply. This is a material contradiction; Etherscan’s accessible explorer snapshot supports approximately 697.164M total supply, while its market-data fields are stale.
• Utility/governance: CFG pays gas on Centrifuge’s EVM environment and historically supports on-chain governance. However, under CP171, approved November 3, 2025, active DAO governance is paused; the Centrifuge Network Foundation currently oversees execution, while the DAO can reassume governance.
• Value accrual: The current framework specifies 3% annual inflation, directed to the treasury. No revenue share, dividends, buybacks or buy-and-burn are currently implemented; Centrifuge explicitly stated there will be no buyback and no near-term dividends. Current staking-reward terms are Not verifiable as of October 19, 2026.
• Emissions/unlocks: CP149 added 115M CFG: 15M unlocked in May 2025 and 100M linearly vesting through April 2029. Team allocation is 12%, vesting through May 2030; ecosystem allocation is 14.3%; 10.5% remains locked as incentives, vesting to April 2029; other stakeholder vesting runs through March 2028. Whether announced unlocks actually occurred on-chain is Not verifiable as of October 19, 2026 (Dune unavailable).
• Allocations: Investor/community sub-allocations under the current post-migration supply are Not verifiable as of October 19, 2026. Historical documentation reported backers 17.1%, core contributors 27.0%, community sale 9.5%, grants/endowment categories, but these are legacy figures.
• Concentration/insiders: A current aggregator reports top-10 concentration of about 43.66%; largest wallets include 0xd052…93cb (15.15%) and 0x40d3…2201 (7.41%). Wallet ownership and insider attribution are Not verifiable as of October 19, 2026.
• Admin controls: Mint, blacklist, pause and fee-switch authority, and controlling addresses, are Not verifiable as of October 19, 2026 without raw contract analysis.
• Liquidity/listings: Main listings include Binance, Bybit, OKX and Coinbase. DEX liquidity is fragmented: DefiLlama reports an ETH-CFG Uniswap V4 pool near $1.2M TVL, while a separate CFG/USDT pool is reported near $220; depth is therefore venue- and pool-specific.

For Centrifuge, a Bitcoin move below $10,000 would be a severe stress event, but the protocol-specific impact is not verifiable as of 2026-10-19 because no on-chain pool, vault, or collateral exposure data was available in the provided results. The best-supported interpretation is therefore scenario-based: the damage would depend on whether Centrifuge has material BTC-linked collateral, or whether its borrowers rely on BTC-correlated assets or market-wide liquidity conditions. From the market evidence provided, the $10,000 BTC case is generally framed as an extreme downside scenario, not a base case.

Bloomberg strategist Mike McGlone’s call is conditional on a roughly 20% U.S. equity correction plus tighter liquidity conditions, and multiple sources say a move that deep would likely require a broader global liquidity shock or forced deleveraging. For a yield/credit protocol like Centrifuge, the practical stress channels would be:

• Collateral impairment if any real-world or crypto exposures are directly or indirectly tied to BTC.
• Borrower stress if portfolio companies, funds, or market participants financing through Centrifuge face balance-sheet pressure from falling crypto prices.
• Liquidity contraction if risk-off conditions reduce refinancing capacity, secondary-market demand, or new originations.
• NAV/mark-to-market pressure on any BTC-sensitive structured credit positions. However, whether any of these channels are material for Centrifuge specifically is Not verifiable as of 2026-10-19 from the supplied sources. The only defensible conclusion is that a BTC sub-$10k shock would likely be a high-severity macro stress test for Centrifuge, but the protocol’s actual loss exposure cannot be quantified here without chain-level and portfolio-level data.

Not verifiable as of 2026-10-19. The provided results do not identify Centrifuge’s current collateral basket, the largest collateral position, or on-chain exposure by chain, so a 20% depeg stress cannot be quantified from the supplied material. The only usable evidence here is generic stress-testing guidance on depeg contagion and liquidation spirals, not Centrifuge-specific holdings or balances.

For a stress scenario, the correct institutional framing is: if the largest collateral asset in a Centrifuge pool depegs by 20%, model whether the resulting haircut breaches pool-specific overcollateralization or liquidation thresholds, then estimate any shortfall after liquidation costs and oracle lag. If the protocol uses multi-chain deployments, each chain must be assessed separately and weighted by its share of total exposure; that chain-by-chain breakdown is not verifiable from the supplied sources. Key risk channels to test are:

• Direct impairment of the depegged collateral’s market value.
• Liquidation cascade if the depeg pushes borrow positions below threshold.
• Oracle latency / circuit-breaker failure that delays revaluation.
• Secondary market illiquidity that increases realized losses during unwind. Given the evidence available, the only defensible answer is that the impact is Not verifiable as of 2026-10-19 without protocol-specific on-chain positions, collateral composition, and liquidation parameters.

Scope limitation: The identity and exposure of Centrifuge’s largest counterparty are Not verifiable as of October 19, 2026. Centrifuge pools are independently structured, so the precise waterfall depends on the pool’s share classes and legal documents. Stress scenario — top borrower/counterparty becomes insolvent

• Expected loss path: Gross exposure is written down by the amount not recovered from collateral, guarantees, insurance, or bankruptcy proceedings: loss = exposure − recoveries. Recovery is normally delayed and uncertain because enforcement is off-chain. Centrifuge supports on-chain write-offs of impaired assets, including predefined overdue schedules or manual write-offs.
• Who absorbs it: In a conventional Centrifuge structure, the junior/first-loss share class absorbs losses first; mezzanine absorbs losses next if present; senior investors absorb residual losses once subordination is exhausted. In legacy Tinlake, this is explicit: TIN protects DROP, with senior value capped by total pool value.
• Compensation/recovery: There is no identified protocol-wide automatic insurance, CFG backstop, or guaranteed investor compensation. Investors’ economic recovery is limited to cash recovered from the underlying asset, collateral, guarantors, insurance, or legal claims. Any sponsor support or reserve is pool-specific. Not verifiable as of October 19, 2026 whether the relevant pool has such additional protection.
• Smart-contract impact path: 1. The pool manager or configured valuation mechanism records a lower asset value/write-off on the Hub balance sheet. 2. NAV and pricePoolPerShare fall; losses are allocated through the pool’s share-class waterfall. 3. Pending/new redemptions are settled at the lower approved price, while liquidity constraints can delay withdrawals through request-based vaults and batch processing. 4. Updated share prices and settlement instructions propagate from the Hub to spoke chains via the protocol’s messaging layer; the contracts do not create value or make investors whole. Bottom line: The primary absorber is the pool’s subordinated capital—not Centrifuge itself. A concentrated top-counterparty default can therefore impair junior, mezzanine, and eventually senior token holders, with recovery depending mainly on off-chain enforcement and collateral realization.

For the specific stress scenario of committed fraud by the DAO or owners, I found no filed lawsuit, SEC action, regulatory investigation, or similar fraud allegation naming Centrifuge, Anemoy, or the listed co-founders in the available results, so this scenario is not verified as of 2026-10-19. The strongest directly relevant material instead points to governance and credit-risk events, not proven fraud: Centrifuge’s governance has been paused under a streamlined model supervised by the Centrifuge Network Foundation, and historical pool distress included unpaid or at-risk loans in Centrifuge-originated credit pools. Those events indicate underwriting / asset-quality risk and counterparty default risk, not evidence of fraud by the DAO or owners.

What can be said cautiously is that Centrifuge’s model relies on issuer-provided information and on-chain/real-world asset structures, which can create room for misrepresentation if originators are dishonest; however, the search results do not show a Centrifuge-specific fraud finding. Centrifuge’s own materials also acknowledge governance centralization changes and tokenholder limitations, but that is a governance structure issue, not proof of fraud. So, for risk classification: fraud by DAO/owners = Not verifiable as of 2026-10-19; operational/credit risk = evidenced.

Centrifuge’s primary yield source is not verifiable as negative over the last 30 days from the provided results. The search results do not contain protocol-specific yield data, TVL, or revenue/fee metrics for Centrifuge; they mostly refer to laboratory centrifuges or unrelated “yield” content, so they cannot support a protocol stress assessment. For this protocol, the correct risk answer is therefore: Not verifiable as of 2026-10-19.

There is insufficient evidence in the provided sources to confirm that the main yield stream turned negative on a 30-day basis, or even to identify the protocol’s current primary yield source. From a risk-analytics perspective, this means the stress scenario cannot be completed without independent protocol data such as on-chain fee/revenue flows, vault performance, or audited reporting. The current evidence set is too noisy and largely non-relevant to Centrifuge as a DeFi protocol.

Assessment — as of October 19, 2026 Centrifuge is currently foundation/company-controlled, not DAO-controlled. Under CP171, approved November 3, 2025, active DAO governance was paused. Centrifuge Network Foundation (CNF) controls treasury and board-level oversight; Centrifuge Labs is the CNF service provider responsible for operations, development, growth, and adoption.

The frontend operator is not separately disclosed: Not verifiable as of October 19, 2026. Contracts and emergency powers. The immutable Root contract controls protocol permissions through two guardian contracts. The Protocol Guardian handles upgrades, cross-chain operations, and emergency pausing; the Ops Guardian handles operational tasks such as pool creation and network wiring. Privilege escalation through Root has a 48-hour timelock, but emergency response/pause can occur immediately.

Pool-level hub managers and balance-sheet managers can configure pools, settle requests, and move assets in or out of pool escrow without a DAO vote; this is a material centralization/drain risk, scoped to each pool. DAO and proposals. DAO governance is presently symbolic/inactive; dao_governance=false. Token holders may seek reinstatement through a CP0-style forum RFC, 14-day discussion, GitHub submission, 7-day Snapshot vote, and at least 4,000,000 CFG quorum. Whether a future vote would regain every contract, treasury, or operational power is not fully specified. Voting concentration / top holders. Dune was unavailable in this run. Not verifiable as of October 19, 2026. Company-controlled entity. Current controlling entity: Centrifuge Network Foundation, Inc., a Cayman Islands foundation company; registration number: Not verifiable as of October 19, 2026. Publicly identified board members are Bhaji Illuminati, Lucas Vogelsang, Kevin Chan, Jürgen Blumberg, Nick Cherney, Glenn Kennedy, and Laura Birrell.

The website Terms of Use provide broad disclaimers and state that neither Centrifuge nor affiliates are licensed in the user’s jurisdiction. The forum ToS names “Centrifuge Inc.”, applies Delaware law, and provides for San Francisco arbitration.

Centrifuge’s disclosed legal anchor is Centrifuge Network Foundation, Inc., a Cayman Islands foundation company; its imprint lists Grand Cayman, Cayman Islands. Centrifuge states that Centrifuge Labs operates as the Foundation’s wholly owned operating subsidiary. The protocol itself is open-source/decentralized infrastructure, so legal exposure is likely concentrated at the foundation, Labs, and individual product/issuer level rather than in a standalone “protocol company.” Terms/restrictions and classification: Website terms state that Centrifuge and affiliates are not licensed in the user’s jurisdiction, do not market where prohibited, and that virtual assets and pools may be high-risk and unregulated.

Access may be restricted by jurisdiction or investor status. This is a risk disclosure, not evidence of a regulatory classification or authorization. KYC/AML and sanctions controls: Compliance is product-specific. Centrifuge documentation says managers perform KYC/AML and eligibility checks, with approved wallets enforced through on-chain memberlists; jurisdictional and investor restrictions can be embedded in token/vault rules.

This does not establish that the base CFG token or every protocol interaction is KYC-gated. Data protection: The published privacy policy references GDPR concepts, confidentiality, data-subject rights, and supervisory-authority complaints. The policy is broad and does not, by itself, establish comprehensive jurisdiction-specific compliance. Warnings, enforcement, litigation, sanctions: No regulator enforcement action or sanctions designation against Centrifuge Network Foundation, Centrifuge Labs, or the Centrifuge protocol was identified in the reviewed sources. Court-case status and any non-public investigations: Not verifiable as of October 19, 2026.

Product-level defaults or disputes should not automatically be treated as regulatory enforcement against Centrifuge. Actual-risk conclusion: The structure provides a recognizable Cayman legal entity and board oversight, but does not eliminate regulatory perimeter risk. Tokenized pools may constitute separate securities, fund, AML, sanctions, or investor-protection exposures depending on issuer, asset, manager, jurisdiction, and distribution channel.

No exact GLEIF LEI record for 'Centrifuge Network Foundation Inc', 'Centrifuge V3'. OFAC SDN screening of 'Centrifuge Network Foundation Inc', 'Centrifuge V3': no match. SEC litigation and administrative release feeds: no mention.

Centrifuge does not appear to issue its own stablecoin; the sources found describe it as tokenization infrastructure that uses external stablecoins such as USDC for subscriptions and redemptions, and historical references also mention DAI in its early loan/pool design. Because no verified evidence was found that Centrifuge-issued stablecoins themselves existed or depegged, the stablecoin depeg question is not verifiable from the gathered sources as of 2026-10-19. The structured fields are therefore: own_stablecoin = false, stable = null, depeg_count = null, max_depeg_pct = null, last_depeg_date = null, stablecoin_ids = null.

Centrifuge’s principal risks are the performance and enforceability of underlying real-world assets, manager-controlled valuation and liquidity, cross-chain coordination, and concentrated operational authority. The protocol documents substantial controls, but several risks remain pool-specific and depend on issuers, managers, legal structures, and off-chain processes; no on-chain verification was performed in this run.

Centrifuge’s top five strengths are: (1) institutional-grade tokenization infrastructure for asset managers and investors, (2) multi-chain architecture that supports deployment across multiple blockchain networks, (3) strong DeFi composability and liquidity access through integrations with the broader DeFi ecosystem, (4) modular and extensible design that lets builders customize vaults, compliance logic, pricing, and allocation workflows, and (5) onchain automation and chain abstraction that centralize accounting and operations while enabling cross-chain synchronization and unified management from a hub chain. More specifically, Centrifuge describes itself as a real-world asset tokenization platform with automated infrastructure for origination, reporting, and lifecycle management. Its GitHub repository states that the protocol is an open-source, decentralized system for tokenizing and distributing financial products across multiple chains, with a hub-and-spoke model and burn-and-mint cross-chain transfers for 1:1 movement between chains.

The same repository also emphasizes seamless DeFi integration via ERC-20 share tokens and vault implementations, while governance materials highlight EVM compatibility, robust developer tooling, and access to larger onchain liquidity as strategic advantages.