> 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/faq.md).

# FAQ

<details>

<summary><strong>What is City Protocol?</strong></summary>

City Protocol is a one-stop infrastructure stack for neofinance. It helps yield providers, vault curators, applications, and developers launch tokenized yield products and integrate financial services onchain.

The core stack is TaaS, VaaS, and NaaS: tokenization infrastructure, vault infrastructure, and modular neofinance APIs/SDKs.

</details>

<details>

<summary><strong>What is neofinance?</strong></summary>

Neofinance is the convergence of traditional financial products, onchain infrastructure, and consumer-grade fintech experience.

In practice, it means users can access yield, swaps, payments, cards, on/off-ramps, lending, and rewards through simple interfaces, while the underlying products remain programmable, composable, verifiable, and global.

</details>

<details>

<summary><strong>What problem does City Protocol solve?</strong></summary>

High-quality yield assets and onchain users are separated by infrastructure gaps.

Yield providers often lack tokenization, compliance, oracle, reporting, and distribution infrastructure. Vault operators often need audited contracts, NAV accounting, governance controls, proof systems, and redemption flows. Consumer apps often want neofinance features, but integrating vaults, KYC, payments, swaps, and ramps separately is slow and expensive.

City Protocol packages these requirements into reusable infrastructure.

</details>

<details>

<summary><strong>What is Tokenization as a Service (TaaS)?</strong></summary>

TaaS is City Protocol's infrastructure for transforming yield sources into onchain products.

It supports yield asset tokenization, NAV monitoring oracles, investor management, attestations, multichain distribution, subscription, redemption, and product lifecycle operations.

TaaS is not only a token minting tool. It defines what the token represents, who can hold it, how value is calculated, how claims are verified, and how the product can be distributed.

</details>

<details>

<summary><strong>What is Vault as a Service (VaaS)?</strong></summary>

VaaS is City Protocol's infrastructure for launching and operating verified yield vaults.

It provides pre-audited vault contracts, configurable parameters, NAV-driven accounting, strategy whitelisting, role-based permissions, monitoring dashboards, subgraph-level indexing, security governance, and redemption logic.

VaaS is the operating layer that controls how capital enters a vault, how it can be deployed, how performance is reported, and how users redeem.

</details>

<details>

<summary><strong>What is Neofinance as a Service (NaaS)?</strong></summary>

NaaS is City Protocol's modular API/SDK layer for integrating neofinance features into applications.

Supported modules can include vaults, yield, swaps, on/off-ramps, KYC/AML, payments, cards, lending and borrowing, rewards, and agentic payment infrastructure. Instead of building each module from scratch, partners can integrate the stack through City Protocol.

</details>

<details>

<summary><strong>How do TaaS, VaaS, and NaaS work together?</strong></summary>

TaaS turns yield sources into tokenized products. VaaS operates the vaults and controls the capital flow behind those products. NaaS lets applications expose those products and related financial services to users.

</details>

<details>

<summary><strong>Who is City Protocol built for?</strong></summary>

City Protocol is built for multiple participants:

* yield providers and strategy managers that want to tokenize and distribute yield products;
* vault creators and curators that want to launch secure, monitored vaults;
* neofinance platforms, exchanges, wallets, and protocols that want to embed yield and financial services;
* developers that want APIs and SDKs for neofinance features;
* LPs and users who access products through City Protocol or partner interfaces.

</details>

<details>

<summary><strong>What kinds of yield products can City Protocol support?</strong></summary>

City Protocol can support multiple product templates, including RWA-backed lending, private credit, tokenized treasury or cash-management products, market-neutral trading strategies, statistical arbitrage strategies, DeFi yield vaults, and managed-account style products.

Each product has its own risk profile, eligibility rules, liquidity terms, verification requirements, and redemption process.

</details>

<details>

<summary><strong>How does City Protocol handle NAV and verification?</strong></summary>

City Protocol uses NAV monitoring, Oracle controls, attestations, and third-party verification where applicable.

Depending on the vault or tokenized product, verification can include proof of reserves, collateralization levels, service-provider confirmations, NAV report history, strategy debt tracking, settlement records, and permission change logs.

The goal is to make the product state observable and verifiable for users, integrators, and monitoring systems.

</details>

<details>

<summary><strong>How do redemptions work?</strong></summary>

Redemption depends on the product's liquidity profile.

Liquid vaults may support faster redemption. Less liquid strategies, private credit, or structured yield products may use epoch-based redemption, where withdrawal requests accumulate during a window, NAV is locked at epoch close, required liquidity is calculated, settlement assets are verified, and users claim after liquidity is available.

</details>

<details>

<summary><strong>Is City Protocol a bank?</strong></summary>

No. City Protocol is onchain infrastructure for tokenized yield products, vault operations, and neofinance services. Products built on or distributed through City Protocol may involve smart contract risk, market risk, liquidity risk, counterparty risk, oracle risk, operational risk, and legal or regulatory risk.

City Protocol infrastructure is designed to make those risks more transparent, constrained, and monitorable. It does not make yield risk-free or equivalent to a bank deposit.

</details>

<details>

<summary><strong>Where do Viral City and rewards fit now?</strong></summary>

Viral City and rewards can support distribution, participation, and user acquisition, but the main City Protocol narrative is now the neofinance infrastructure stack.

The primary product focus is TaaS, VaaS, and NaaS.

</details>

<br>