# Tokenization Security Measures

#### Core Framework <a href="#core-framework" id="core-framework"></a>

The Zodor Protocol enables real-world asset tokenization through a structured approach that mints **a fixed, auditable supply of Security Tokens at the point of asset tokenization**.

#### Key Security Mechanisms <a href="#key-security-mechanisms" id="key-security-mechanisms"></a>

**Asset Validation** Assets undergo rigorous due diligence and legal structuring to meet jurisdiction-specific regulatory standards before tokenization. Five mandatory document classes (Certificate of Incorporation, Legal Opinion, Financial Audit, AML Policy, Board Resolution) are verified, hashed, and anchored to IPFS through `ZodorProofRegistry`.

**Smart Contract Governance** Custom contracts manage critical functions including transfer restrictions, KYC/AML enforcement, wallet whitelisting/blacklisting, and automated yield distribution. Pausable + AccessControl is mandatory on every contract; ERC-7201 namespaced storage ensures upgrade safety.

**Fixed Token Supply** Rather than dynamic per-user issuance, the protocol establishes one immutable token supply held in a protocol-managed treasury and distributed to investors based on allocations. For Energy, the per-project minting cap is `totalCarbonTonnes × 1e18` and is enforced at the registry level.

**Real-Time Compliance** All token interactions are regulated by `ZodorComplianceModule`, ensuring automatic enforcement of jurisdictional restrictions and regulatory alignment throughout the asset lifecycle. This applies on every transfer primary purchase, secondary trade, bridge, vault deposit, AMM swap.

**Reserve Proof (Path C)** For private tokens like `ZodorReserveOracle` attests live token supply against the USDT/USDC inventory held in the treasury. Investors and auditors can independently verify reserve coverage even though individual balances are confidential.

#### Multi-Sector Application <a href="#multi-sector-application" id="multi-sector-application"></a>

The framework supports tokenization across green energy, real estate, commodities, mines, private businesses, and structured products each with its own compliance configuration but the same underlying security primitives.


---

# 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://whitepaper.zodor.io/security-and-privacy/tokenization-security-measures.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.