Vaults don't hold one asset in one place anymore.

A single vault may simultaneously hold lending positions, LP tokens, restaking assets, bridged collateral, and exchange balances across multiple chains and protocols. The reason is that real returns now require active strategies, run by curators who trade in the wallets, venues, and tools they already use.

For years, the trade-off was forced. Vaults could either build every strategy on-chain through bespoke adapters and scripts and expose LPs to smart contract risk, or let curators run freely and lose the ability to know, at any moment, what the vault was actually worth.

Concrete's asset-tracking system removes that trade-off.

Know exactly what the vault owns, where it is, and what it's worth at any moment in time — across every chain, every venue, every position type.

The Asset-Tracking Problem

Modern DeFi portfolios are fragmented by design.

Assets can exist across:

• Lending markets
• AMMs
• Restaking protocols
• Structured products
• Cross-chain bridges
• Centralized exchange accounts
• Perpetual venues

Each venue reports data differently, updates at different speeds, and lives on different infrastructure.

At institutional scale, manually reconstructing a vault’s positions becomes impossible.

The challenge isn’t identifying the assets.

It’s verifying:

• where they are,
• whether the data is fresh,
• and whether the reported value is trustworthy.

How Concrete Tracks Vault Assets

Concrete combines:

• independent off-chain data providers,
• direct on-chain reads,
• and custom indexers.

Primary Indexer: Debank

Debank provides the primary portfolio view across strategist wallets, protocols, and chains.

Concrete’s automation system continuously reads this data and computes vault value updates.

Direct On-Chain Reads

For integrated protocols like lending markets and AMMs, Concrete reads state directly from smart contracts rather than relying solely on third-party indexers.

Custom Indexers

For unsupported venues, perpetual exchanges, or newer protocols, Concrete builds custom indexers to maintain full portfolio visibility.

Turning Asset Data Into NAV

Tracking positions is only half the system.

Concrete also verifies every accounting update before it affects vault NAV. Tracking positions is half the system. Verifying every accounting update before it affects NAV is the other half

The process uses a three-party model:

• Transaction Proposer computes the portfolio update.
• Independent Signer cross-checks against separate data.
• Smart Contract Safeguards reject impossible accounting changes on-chain.

No single party can update vault accounting alone.

Time Travel: Vault History, Visible to the Whole Team

Running a vault takes coordination. The trader runs the strategy. The risk lead reviews it. The allocator audits it. The fund admin reports on it. The board asks about it three weeks later.

Every one of those roles needs to see the same thing: what the vault held, where, and what it was worth — at any moment, on demand, without filing a request.

Time Travel makes that visible.

Concrete stores a full snapshot of every vault every fifteen minutes. Total assets, protocol allocations, network exposure, APY, exchange rates — all of it, all the time, all the way back to the vault's first deposit.

Pick a timestamp. Watch the vault reassemble itself. No exporting, no reconciling, no asking the curator to explain what Tuesday looked like.

Why This Matters

Institutional capital requires operational transparency.

Allocators need to know:

• where capital is deployed,
• how NAV is verified,
• whether accounting is independently checked,
• and whether historical positions can be audited.

Concrete’s asset-tracking system was designed to answer those questions directly.

Frequently Asked Questions 

‍

How often are vault snapshots taken?

Every fifteen minutes. Each snapshot captures total assets, APY, exchange rate, and the full breakdown by asset, protocol, and network.

‍

Which protocols and chains does Concrete track?

Concrete tracks every venue the platform integrates with, on-chain and off-chain. On-chain protocols: Aave V3, Morpho, Euler, Compound, Curve, Uniswap V3, Balancer, Pendle V2. Exchanges: Binance (spot and USDS futures, balances, price feeds), Hyperliquid (perpetuals), Paradex (derivatives). Networks: Ethereum, Arbitrum, Stable. Additional integrations are added as they are deployed. Tracking: Debank, Binance, Hyperliquid, Paradex, CoinStats. As well as, Concrete is always integrating new sources to track. 

‍

What is Time Machine?

Time Machine is a tool in Concrete Enterprise that rewinds any vault to a past timestamp. It displays total assets, APY, exchange rate, and the full breakdown by asset, protocol, and network as of that moment. The data is queried from Concrete's internal snapshot store rather than re-indexed from external providers.

‍

How far back can Time Machine reach?

Time Machine reaches back to the start of each vault's recorded history on Concrete Enterprise.

‍

How does Concrete verify that reported NAV is accurate?

Every accounting update goes through three independent parties. The Transaction Proposer computes the proposed value from the primary data source. The Independent Signer cross-validates against a second source and refuses to sign on disagreement. The Smart Contract Safeguards reject any update outside hard-coded accounting bounds. No single party can update NAV alone.

‍

What happens when a data source returns bad data?

The Independent Signer refuses to sign updates that disagree across data sources beyond a configured tolerance. The vault holds the prior NAV until a fresh, verified update is available.

‍

Do curators need to install or configure anything?

No. Both the asset-tracking pipeline and Time Machine are enabled automatically for every Concrete curator with vault access.

‍

This article is for informational purposes only and does not constitute investment, legal, tax, or financial advice. References to Concrete’s architecture and controls are descriptive only and do not eliminate risks associated with smart contracts, DeFi protocols, market conditions, oracle failures, operational failures, or third-party infrastructure. 

‍