# FAQ

<details>

<summary><strong>Does City Protocol take custody of user funds?</strong></summary>

No. City Protocol is entirely non-custodial. Assets are held in smart contracts governed by explicit, audited risk parameters. No single entity, including City Protocol itself, can unilaterally access or move user funds.

</details>

<details>

<summary><strong>Can a user cancel a redemption request?</strong></summary>

No. Unlike deposit requests, redemption requests cannot be canceled once submitted. This prevents users from forcing curators to unwind positions unnecessarily and protects the vault's strategy integrity.

</details>

<details>

<summary><strong>What networks does City Protocol support?</strong></summary>

City Protocol is chain-agnostic and natively supports EVM-compatible networks, with a strong focus on the **Base ecosystem**. Through chain abstraction, users can deposit from any supported network while strategy execution occurs on the optimal chain.

</details>

<details>

<summary><strong>How are vault shares priced?</strong></summary>

Vault shares are priced based on the **Net Asset Value (NAV)** submitted by an independent valuation provider and approved by the curator at the time of settlement. This ensures objective, tamper-proof pricing.

</details>

<details>

<summary><strong>What is the difference between withdraw and cooldownAssets?</strong></summary>

`withdraw` works only when cooldown is disabled in the vault contract and executes immediately. `cooldownAssets` works when cooldown is enabled and starts a vesting period; after maturity, users call `claimFromAp` to receive their assets.

</details>

<details>

<summary><strong>How does Viral City measure mindshare?</strong></summary>

Viral City uses the City ID reputation layer to measure and rank user contributions based on historical interactions, UGC quality, and overall engagement scores. This provides a smarter, fairer, and more accurate ranking system compared to simple follower counts.

</details>

<br>


---

# Agent Instructions: 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:

```
GET https://city-protocol.gitbook.io/docs/introduction/faq.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.