> For the complete documentation index, see [llms.txt](https://city-protocol.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://city-protocol.gitbook.io/docs/introduction/welcome-to-city-protocol/bridging-the-gap.md).
# Bridging the Gap
### The gap between liquidity and yield assets
More money and assets are moving onchain, but the infrastructure to connect that liquidity to sustainable yield remains incomplete.
* Stablecoins have made onchain settlement global and 24/7.
* Real-world assets, private credit, tokenized treasuries, and institutional trading strategies are becoming credible sources of onchain yield.
* Neobanks and fintech apps have shown that users will adopt financial products when the experience is simple, mobile, and integrated into daily life.
**The opportunity is clear: bring high-quality yield assets onchain and make them usable through Neofinance platforms.**
**The challenge is that every part of the stack is still fragmented.**
***
### 1. Yield providers need more than token issuance
For a yield provider, tokenization is not only about deploying a token contract.
A real product needs:
* investor eligibility and access controls;
* subscription and redemption workflows;
* NAV calculation and reporting;
* Oracle publication and deviation checks;
* proof of reserves or proof of deployment;
* third-party verification;
* strategy and collateral monitoring;
* multichain distribution;
* dashboards and lifecycle operations.
Without this infrastructure, high-quality yield sources remain trapped in private channels or one-off integrations.
***
### 2. Vault operators need secure, observable operating systems
Vaults are the main interface between user capital and yield strategies. They must do more than receive deposits.
A production-grade yield vault needs audited contracts, configurable parameters, role-based permissions, strategy whitelisting, allocation limits, NAV accounting, signer quorum, monitoring, emergency pauses, redemption queues, and settlement records.
When each vault team builds these systems independently, the result is slow launch cycles, duplicated security work, inconsistent reporting, and limited trust for users and integrators.
***
### 3. Neofinance apps need a modular infrastructure
Consumer finance products are moving toward an embedded model. A project, exchange, wallet, creator platform, AI agent, or fintech app may want to offer yield, swaps, on- and off-ramps, payments, cards, KYC/AML, lending, and rewards within a single user journey.
Today, every feature usually requires a separate vendor, integration, compliance path, dashboard, settlement process, and user experience.
This makes Neofinance slow to launch and hard to maintain.
***
### 4. Users need simplicity without losing transparency
Mainstream users do not want to manage bridges, gas tokens, strategy contracts, custody details, pricing reports, and redemption mechanics across multiple interfaces.
At the same time, yield products cannot hide the underlying risks. Users and partners need to understand what the product represents, who manages it, how NAV is calculated, what controls are in place, when redemptions occur, and what can cause a pause.
The winning experience must be simple on the surface and verifiable underneath.
***
### 5. The missing layer is the neofinance infrastructure
City Protocol exists to fill this gap.
It provides the infrastructure that allows:
* yield assets to become tokenized products;
* tokenized products to operate through secure vaults;
* vaults to expose NAV, proof, permissions, and redemption state;
* applications to embed neofinance modules through APIs and SDKs;
* users to access yield and financial services through simpler interfaces.
This is the foundation for City Protocol's TaaS, VaaS, and NaaS stack.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://city-protocol.gitbook.io/docs/introduction/welcome-to-city-protocol/bridging-the-gap.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.