Key takeaway: CeDeFi is credible only when centralized execution is wrapped in vault-first controls, creator-defined mandates, approved venue policies, continuous monitoring, and redemption logic. City Protocol turns that operating model into reusable VaaS infrastructure.
Onchain finance makes capital easier to move, settle, and compose. Centralized finance still provides execution depth, custody workflows, and liquidity that many institutional strategies use every day. CeDeFi sits between these two systems. It uses onchain infrastructure for access, accounting, monitoring, and redemption, while approved centralized venues or custody workflows handle the parts of execution that belong off-chain.
For City Protocol, CeDeFi is not a vague mix of centralized and decentralized finance. It is a controlled operating model. User capital enters a vault first. The vault applies policy checks. Approved capital becomes available for allocation through a strategy manager. The strategy then operates only through whitelisted accounts, adapters, venues, or custody paths defined by the vault mandate.
This article explains how CeDeFi works inside the City Protocol model, how curators define the vault, how assets are managed through approved centralized exchange paths, and how monitoring, net asset value reporting, creator-bound execution, and redemption controls keep the product governed.
Why CeDeFi Exists
DeFi is powerful because it gives users open access, transparent settlement, and composable assets. It is not the deepest execution layer for every strategy. Market-neutral trading, basis strategies, cross-exchange arbitrage, institutional lending, treasury execution, and managed-account products often depend on centralized order books, institutional accounts, professional custody, or active strategy management.
CeDeFi exists because useful strategy execution takes place across both environments. The onchain side gives users a transparent product interface and programmable accounting. The centralized side provides execution venues, liquidity, custody workflows, and market access. A production CeDeFi product needs a clear bridge between the two, not an informal promise that the centralized component is handled somewhere else.
City Protocol structures that bridge through vault infrastructure. The vault is the user-facing and accounting layer. The approved centralized venue, custody workflow, or managed account is the execution layer. The strategy manager operates between them, but only inside the mandate defined by the curator and enforced by vault policy.
The City Protocol CeDeFi Flow
The flow begins with a curator. The curator designs the vault mandate before user capital enters the product. The mandate defines the accepted assets, strategy type, eligible users, capacity, allocation limits, approved venues, reporting cadence, net asset value process, redemption window, and emergency controls.
A user then deposits through a City Protocol-powered interface or a partner application. The user does not send capital directly to a centralized exchange, borrower, trading operator, or offchain account. The deposit enters the vault. The vault checks the accepted asset, capacity, eligibility, pause status, and product rules. After the checks pass, the user receives a share, receipt, or claim record according to the product design.
Approved capital becomes available for allocation through the strategy manager. The strategy manager routes capital only to approved strategies, managed accounts, exchange adapters, custody workflows, or venues. For a centralized exchange strategy, execution happens through a whitelisted institutional account, subaccount, custody workflow, or exchange adapter. The user still enters and exits through the vault process.
Once the strategy is active, monitoring begins. The vault tracks deposits, withdrawals, allocation changes, strategy debt, fees, net asset value reports, permission changes, settlement records, and redemption status. The user sees a cleaner product experience. The operating layer underneath stays controlled and observable.
What Curators Control
The curator defines the product before execution begins. This is the first layer of risk management. In a CeDeFi vault, the curator does not simply choose a strategy name. The curator defines the policy envelope that governs how capital moves.
That policy envelope includes the strategy mandate, approved execution venues, allocation limits, eligible assets, liquidity terms, redemption mechanics, reporting requirements, and emergency controls. If the strategy involves centralized exchange execution, the curator defines which accounts, adapters, and venues are approved for that product.
The curator does not receive user funds directly. The vault receives user deposits. The strategy manager receives allocation authority only after the vault makes approved capital available inside the mandate. This distinction keeps the product aligned with the vault-first model and prevents the strategy from becoming a direct user-to-exchange transfer flow.
How Assets Are Managed on Centralized Venues
After the curator defines the mandate and users deposit into the vault, the strategy manager executes inside the approved setup. For a centralized exchange strategy, this setup uses whitelisted institutional accounts, subaccounts, custody workflows, or exchange adapters. These paths are part of the vault's approved strategy registry and venue policy.
The strategy manager uses those approved paths to trade, hedge, rebalance, or manage positions. The vault policy controls the boundaries of this activity. It defines where capital is allowed to move, how much exposure is allowed, which assets are accepted, which venues are approved, and which operational events trigger review or pause.
City Protocol's model separates execution flexibility from control authority. The strategy manager has room to operate the strategy. The manager does not control the base vault rules, does not bypass eligibility checks, does not change redemption logic, and does not deploy capital to arbitrary destinations. Execution is active, but it is bounded by the curator-defined mandate and the vault's security layer.
Security Model: Vault-First, Then Approved Execution
City Protocol treats security as an operating model rather than a single contract feature. In CeDeFi, this matters because the product touches both onchain infrastructure and centralized execution surfaces. The vault-first model gives the system a defined point of control before capital reaches any strategy path.
The security layer checks user eligibility, capacity, accepted assets, approved allocation rules, emergency pause state, venue permissions, net asset value controls, and reporting requirements. Strategy whitelisting restricts capital deployment to approved strategies, accounts, adapters, or venues. Role separation limits what curators, strategy managers, net asset value signers, guardians, operators, and governance can do.
Creator-bound execution is the key principle. The curator defines the mandate. The strategy manager executes inside that mandate. The vault enforces the rules that separate permitted strategy activity from unauthorized capital movement. This mirrors the risk management logic used in institutional strategies, where managers operate inside mandates, limits, reporting obligations, and oversight processes.
Monitoring, Net Asset Value, and Reporting
CeDeFi becomes credible when the centralized execution component remains observable. The system does not publish every trade or expose sensitive strategy logic. It does expose the product state that users, partners, operators, and risk teams need to understand.
Net asset value is the central reporting number. It affects subscriptions, redemptions, share value, performance reporting, and user balances. City Protocol's VaaS model uses net asset value-driven accounting, signer controls, deviation checks, report records, and indexed vault events where applicable. A net asset value update that breaches the product's policy does not pass silently. It routes into review, pause, resubmission, or governance action according to the vault design.
Monitoring also covers allocation changes, strategy debt, fees, permission updates, settlement records, proof records, and redemption status. This creates a product that is easier to supervise without turning every operational detail into public strategy leakage.
How Redemption Works
Redemption also returns through the vault. A user submits a redemption request according to the product's rules. The vault applies the relevant net asset value, checks liquidity, records the settlement state, and allows the user to claim when the required assets are available.
For liquid strategies, redemption follows a faster process because the vault has sufficient idle liquidity or highly liquid positions. For strategies using centralized venues, managed accounts, private credit, or scheduled liquidity, redemption follows a defined window. The strategy manager returns liquidity from the approved execution path back into the vault process. The user exits through the vault, not through the centralized venue.
This structure makes liquidity terms explicit. It does not describe every strategy as instantly liquid. It describes the redemption process as a rule-based product feature.
Why This Matters
CeDeFi is often misunderstood as a compromise between centralization and decentralization. In City Protocol's model, CeDeFi is a structured operating path. Centralized venues provide execution depth where they are useful. Onchain vault infrastructure provides access, accounting, policy enforcement, monitoring, and redemption.
This is the role of VaaS. Vault as a Service turns a strategy into a controlled vault experience. It defines how capital enters, how permissions are checked, how curators set mandates, how strategy managers execute inside approved boundaries, how net asset value is updated, how monitoring works, and how users redeem.
The result is not a black box. It is a product architecture for bringing centralized execution into neofinance through controlled, transparent, and partner-ready vault infrastructure.
Summary
CeDeFi connects centralized execution with onchain product infrastructure. It exists because some strategies require deep liquidity, institutional accounts, custody workflows, or active management that pure DeFi does not fully provide today.
City Protocol structures CeDeFi through a vault-first model. Curators define mandates. Users deposit into vaults. The vault verifies the product rules. Strategy managers allocate only through approved paths. Centralized execution happens through whitelisted accounts, custody workflows, or adapters. Monitoring, net asset value reporting, pause controls, and redemption workflows keep the product governed.
CeDeFi does not remove risk. It makes complex strategy access more structured, more observable, and easier to distribute through neofinance infrastructure.
