Overview
The Issuance & Operation Layer is City Protocol's product layer for launching and running tokenized financial products onchain.
It applies to products such as ETP-style products, index baskets, thematic portfolios, multi-vault income products, model portfolios, copy-allocation products, market-neutral strategy products, and tenor-based structured yield products.
In plain terms: if a partner wants to turn several tokenized assets, verified vaults, or approved strategies into one investable product with its own rules, NAV, subscriptions, redemptions, disclosures, and lifecycle, this is the layer that handles it.
A structured product or ETP-style product has concrete operating requirements: what components it can hold, how those components are weighted, when it can rebalance, how product-level NAV is calculated, who can subscribe or redeem, what fees apply, what disclosures must be shown, and what happens if a component becomes stale, paused, impaired, or ineligible.
Therefore, for the Issuance & Operation Layer, the key idea is product logic as infrastructure. Issuers define the mandate. City Protocol supplies the issuance and operating machinery that makes the mandate verifiable, governable, and distributable.
Relation with VaaS & TaaS
TaaS creates the tokenized yield product. VaaS operates the vault and capital controls behind it. The Issuance & Operation Layer sits above both as the framework for product issuance, product-level accounting, methodology enforcement, rebalancing, reporting, and ongoing operations.
Why This Layer Exists
Onchain yield is moving from single products to portfolios.
The first wave of tokenized finance focused on making individual exposures available onchain: private credit products, tokenized treasury products, managed accounts, market-neutral strategies, and DeFi yield vaults. That matters, but it is only one step. Users and platforms often want packaged outcomes: a stable-yield product, a tokenized income basket, a managed allocation, an ETP-style wrapper, or a strategy product with defined risk limits.
Today, every team that wants to launch these products tends to rebuild the same machinery:
component selection and validation;
product issuance and token or position records;
product methodology and weighting rules;
rebalancing logic and execution limits;
product-level NAV aggregation;
fee accrual and settlement accounting;
subscription, redemption, and claim workflows;
eligibility rules and transfer policy;
disclosure, reporting, and product status tracking.
The Issuance & Operation Layer standardizes this product infrastructure. It turns City Protocol's capital primitives into a product platform: tokenized assets from TaaS, verified vaults from VaaS, and integration surfaces from NaaS can be composed into products with clear rules and observable state.
The result is a repeatable path from product idea to live onchain product.
Last updated