One position, many venues
The depositor manages one share token instead of several protocol positions, approvals and dashboards.
Concrete’s latest integrations suggest an evolution from individual vaults toward a programmable allocation layer across specialized DeFi infrastructure.
Concrete lists a Morpho USD vault that automates USDC deposits across multiple Morpho vaults, and a Concrete × Morph vault set that supports nine assets and allocates to Morph-ecosystem protocols.
Taken together, these products place Concrete one layer above individual protocols. It selects, sizes and rebalances exposure to other venues instead of being the venue.
No new event after September 28, 2026 is asserted. Allocation weights, live TVL per venue and several launch-asset details were not independently verified. They are labeled where they appear.
For most of DeFi’s history, a “vault” meant access to one strategy: deposit here, earn from that protocol. Concrete’s product architecture increasingly sits one layer above individual DeFi opportunities. Instead of exposing a depositor to a single protocol, a Concrete vault can hold capital across several strategies and underlying venues, and move it between them under a defined allocation process.
Two integrations show this most clearly. Concrete × Morpho is a Concrete vault whose underlying positions are themselves Morpho vaults run by independent curators, so it allocates across allocators. Concrete × Morph is a set of vaults on the Morph network that deploy deposits into multiple partner protocols in that ecosystem. In both cases the depositor holds one position, and the multi-venue work happens underneath it.
This issue presents that as an observable direction in Concrete’s product architecture, not as proof that Concrete is, or will become, a general allocator for DeFi. The architecture has advantages, and it also adds dependencies. Both are covered below.
The deposit experience looks the same in both models. What differs is what sits between the vault and the market.
The vault is a wrapper around one opportunity. Yield, risk and liquidity are mostly those of that one venue. Changing venue usually means the user withdraws and redeposits somewhere else.
The vault is a portfolio. An allocator, which Concrete’s documentation describes as an automated operational role, decides how capital is spread across approved venues and when to move it. The user keeps one share token while the underlying mix can change.
In the older model, choosing a venue is the user’s job. In the newer model it becomes the vault’s job, which means the vault’s allocation logic, permissions and risk limits become part of what the depositor is exposed to.
Morpho provides lending infrastructure: isolated lending markets, and Morpho Vaults in which independent curators allocate across those markets. Concrete’s Morpho products add another layer that allocates across Morpho vaults.
Morpho curators already make market-level allocation decisions. A Concrete vault on top turns curator selection into a programmable decision. It chooses which curated vaults to hold and rebalances among them. That is a portfolio-construction layer, not a new lending market.
The trade-off is that depositors take on Concrete’s logic, each curator’s logic and Morpho’s contracts together. Diversifying across curators does not diversify away shared market exposure if those curators lend against similar collateral.
| Asset | Status in this review | Evidence |
|---|---|---|
| USDC | Verified | Morpho USD Vault page: USDC across multiple Morpho vaults. |
| WETH | Not independently verified | Listed as a launch asset in the brief for this issue; no primary Concrete × Morpho WETH vault page located as of Sep 28, 2026. |
| WBTC | Not independently verified | Listed as a launch asset in the brief for this issue. The Morpho Bitcoin Vault page located references LBTC, not WBTC. |
Morph is a separate Layer-2 network. The Concrete × Morph vaults take deposits on Morph and deploy them through partner protocols inside the Morph ecosystem, so the allocation happens within one ecosystem rather than across a single lending primitive.
Nine supported assets does not mean nine copies of one strategy. A BGB vault, a stablecoin vault and a restaked-ETH vault face different venues, liquidity depth and risk. Concrete also groups some assets, as in a “Majors” vault for ETH, WBTC, USDT and USDC. Per-asset strategy composition was not verified for this issue.
The Morph integration dates from early 2025, which predates this reporting week. It appears here as architectural evidence, not as news.
Select any layer to see what it does and what it adds. The diagram is conceptual. A given vault may use only some of these branches.
The depositor manages one share token instead of several protocol positions, approvals and dashboards.
Capital can shift between venues inside the vault without each depositor withdrawing and redepositing.
Exposure can span several venues and curators, which may reduce dependence on any single one.
ct[asset] shares are ERC-20 tokens, so other protocols can integrate them where they choose to.
Each layer (vault, allocator, curator vault, protocol) is code that can fail.
Allocation decisions can be wrong, slow or poorly parameterized.
A vault is no safer than the venues it allocates to.
A simple interface can obscure how many moving parts sit behind it.
Withdrawals depend on unwinding positions across several venues.
The architecture redistributes risk. It does not eliminate it. Advantages 1–4 are potential benefits whose value depends on execution, and the five costs apply however well the system is run.
Traditional finance separates exchanges, lenders, fund managers, allocators and distribution. On-chain finance is starting to show a similar stratification.
Analysis: Concrete appears at more than one layer. It runs its own strategy vaults, and it runs vaults whose holdings are other people’s vaults. The second role is the one this issue tracks. Being present at a layer is not the same as leading it, and this map makes no claim about market share.
If the allocation layer is the machine, ct[asset] shares are what the depositor actually holds. Concrete’s materials position these shares as the foundation for further products. Each stage below is labeled by what is live today and what is described as direction.
These are the properties institutional allocators usually look for. They are not claims that institutions are using these specific vaults, and no such adoption was verified for this issue.
A single ERC-4626-style share replaces separate integrations with each protocol.
Concrete documents role separation, bounded accounting, monitoring and pause authority. Whether these meet a given mandate requires diligence.
Exposure is expressed as one holding with an underlying mix, which is closer to how funds are reported.
The decision moves from picking markets to picking an allocation framework and its constraints.
Share value tied to vault NAV fits fund-style reporting, subject to the transparency of underlying positions.
Rebalancing inside a vault can reduce transactions, approvals and monitoring load for the holder.
An allocation layer is only as strong as the weakest thing it allocates to and the logic that decides where to allocate. These five questions are the ones worth asking of any multi-venue vault.
Losses in one venue flow through to vault NAV in proportion to exposure. An allocator can limit position sizes, but it cannot reverse a loss that has already happened. The share token carries the loss to every holder.
Diligence: per-venue caps, exposure disclosure, loss-socialization rules.
Withdrawals rely on unwinding positions. If lending utilization spikes or pools thin out, redemptions may queue. Some Concrete vaults already document withdrawal queues or lockups.
Diligence: queue mechanics, liquid buffer size, worst-case exit timing.
Three curated vaults can all lend against the same collateral or depend on the same oracle or stablecoin. Diversification by venue name is not diversification by risk factor.
Diligence: look-through collateral, oracle and asset exposure across venues.
Models tuned on calm markets can chase yield into crowded venues, rebalance too late, or churn and pay costs. Automation executes the model faithfully, including its blind spots.
Diligence: allocation constraints, human override, historical behavior in stress.
Composability risk grows with depth. An upgrade, pause or accounting edge case at one layer can behave unexpectedly at another. Audits are typically scoped per contract, not per stack.
Diligence: audit scope across integrations, upgrade authority, pause propagation.
These are observations to track. No outcome is predicted.
Whether the set of venues Concrete allocates to expands, and where.
How many underlying strategies each vault holds, and how different their risk factors are.
Whether integrations using shares as collateral, LP or derivatives become observable and live.
Disclosure of allocation logic, constraints, roles and rebalancing behavior.
Whether custody-connected or institutional integrations appear in verifiable live usage.
Concrete announces the Concrete × Morph vaults on X, listing nine supported assets.
Concrete Morpho USD and Morpho Bitcoin vault pages available on app.concrete.xyz; launch date not confirmed in reviewed sources.
Prior issue (Vol. 1 · Issue 7) publication timestamp; vault roles and Allocator described from Concrete documentation.
No major public update identified in the reviewed primary sources.
Research timestamp for this issue. Concrete, Morpho and Morph materials reviewed.
Future dates within the reporting period; no event is asserted.
The vault may be the visible product. The allocation layer may be the deeper infrastructure.
Concrete’s Morpho and Morph products show a vault design in which the core work is choosing, sizing and moving exposure across other venues, not providing a single yield source. If that direction continues, Concrete’s longer-term differentiation may depend on how effectively it coordinates capital across an expanding set of on-chain strategies while keeping risk, liquidity and transparency manageable for the people holding the share token.
That is a framework for evaluation, not a forecast. Each additional venue adds opportunity and dependency at the same time. The questions in Section 10 will matter more than the number of integrations.
Morpho USD Vault (USDC across multiple Morpho vaults; Gauntlet, MEV Capital, RE7 Labs named) and Morpho Bitcoin Vault (LBTC).
Morpho USD Vault ↗Search-index excerpt reviewed Sep 28, 2026Supported-asset list (nine assets) from Concrete’s announcement thread; Morph Majors vault page.
Concrete on X ↗ · Morph Majors ↗Posted Jan 31, 2025 · reviewed Sep 28, 2026Partner protocols (BulbaSwap, Quokka Lend), initial allocation, ct[ASSET] utility and withdrawal timing.
How Concrete Simplifies DeFi for Morph ↗Search-index excerpt reviewed Sep 28, 2026ct[asset] ERC-20 shares, exchange-rate accrual, vault roles including the Allocator, controls and risk disclosures.
docs.concrete.xyz ↗Search-index excerpt reviewed Sep 28, 2026Morpho Vaults, curator and allocator roles, and reallocation mechanics.
docs.morpho.org ↗Search-index excerpt reviewed Sep 28, 2026“Vault Flywheel” framing of ct[asset] secondary utility and derivative products (described direction).
Concrete on X ↗Posted Oct 20, 2025Every statement is tagged as documented fact, analysis or roadmap. Allocation weights, per-venue TVL, live APY and institutional usage were not verified and are not estimated. No event after the September 28, 2026 research timestamp is asserted. Older integrations are dated to their original announcements, not presented as this week’s news. Several primary pages could not be opened directly from the research environment, so their content was reviewed through search-index excerpts on September 28, 2026. Readers should confirm against the live pages.