# Layered Architecture

1. **Layer 1 (Ethereum Mainnet):**
   * **Security and Settlement:** CarrChain inherits Ethereum's security through the Rollup or AnyTrust protocols of Arbitrum.
   * **Data Finality:** Ethereum acts as the ultimate settlement layer, ensuring the integrity and finality of transactions executed on CarrChain.
2. **Layer 2 (Arbitrum):**
   * **Scalability with Rollup Technology:** Arbitrum uses Rollup technology to batch transactions and compress data, reducing fees and improving throughput.
   * **Data Availability Models:**
     * **Rollup Mode:** Posts all transaction data on Ethereum, offering full decentralization and security.
     * **AnyTrust Mode:** Reduces costs by maintaining data availability off-chain with a trusted data committee.
3. **Layer 3 (CarrChain):**
   * **Custom Native Gas Token:** CarrChain uses its own token for paying transaction fees, allowing for specialized economic models and incentives within the ecosystem.
   * **EVM+ Compatibility:** Supports smart contracts written in Solidity as well as additional languages like Rust, C, and C++ through Arbitrum Stylus.
   * **Application-Specific Logic:** Optimized for automotive use cases, providing tailored features for vehicle identity management, marketplaces, and automotive financial products.


---

# 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://docs.carrchain.io/products/integrations/layered-architecture.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.
