# Why MVC in short

MVC has the following characteristic:

1\)    Layer 1 – [UTXO model](/mvc-dao/about-us/about-mvc/why-mvc-chose-utxo-model.md) – Same Structure as Bitcoin.

2\)    Technically speaking, MVC can offer the ideal Side-Chain service to Bitcoin.

3\)    Same wallet address as Bitcoin wallet address. (Optional by Bitcoin holder)

4\)    BTCfi narrative. (Enable to use BTC as asset, enable BTC as transaction unit)

5\)    Viable smart contract - No more theoretical stage

6\)    [TPS – 10,000](/mvc-dao/frequently-asked-question/mvc-tps.md)+

7\)    Proven Security Model - [POW](/mvc-dao/about-us/about-mvc/why-mvc-chose-pow.md)

8\)    [Zero-confirmation](/mvc-dao/about-us/technical-documentation/metacontract-technical-explanation.md) technology – FT & NFT transaction goes through instantly. (Low latency on-chain application user experience)

9\)    [Permissionless](/mvc-dao/frequently-asked-question/verification-process-for-project-onboard-mvc.md) development

10\)   POB – You build you earn mechanism. 

11\)   Community driven - DAO govern

11\)   Friendly cross chain Modular Infrastructures (MetaSo):

A)    Open – source application

B)    Enable highly customizable, out of the box feature application.

C)    Native [Cross-Chain DID](/mvc-dao/about-us/mvc-solution/metaid.md) protocol, currently enable user to transact Ethereum & Polygon’s NFT, payment under the same application platform. More protocol & public chain will be connected. Ex: (Ordinal protocol)


---

# 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://mvc-dao.gitbook.io/mvc-dao/about-us/about-mvc/why-mvc-in-short.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.