> For the complete documentation index, see [llms.txt](https://polarischain-1.gitbook.io/polarischain/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polarischain-1.gitbook.io/polarischain/10.-real-world-asset-tokenization/10.3-supported-asset-classes-and-native-workflows.md).

# 10.3 - Supported Asset Classes & Native Workflows

Polarischain’s protocol natively supports the structural requirements of major institutional asset classes:

**10.3.1 Equity Tokens (Stocks)**

Represent fractional or whole ownership in public or private entities:

* **Fractional Precision:** Configurable decimal places for retail and institutional allocation.
* **Dividend Distribution:** Executed via native batch-transfer transactions, automatically routed to eligible holders based on snapshot timestamps.
* **Corporate Actions:** Protocol-native support for stock splits, reverse splits, mergers, and tender offers. All adjustments update the cap table deterministically.
* **Real-Time Cap Table:** On-chain shareholder registry with instantaneous reconciliation, eliminating T+2 settlement delays and manual audit overhead.
* **Transfer Restrictions:** Enforced lock-up periods, insider trading blackout windows, and jurisdiction-specific compliance gates.

**10.3.2 Debt Tokens (Bonds)**

Fixed-income instruments with embedded payout logic:

* **Maturity & Coupon Metadata:** Interest rate, payment frequency, and maturity date stored natively in the asset registry.
* **Automated Coupon Distribution:** Scheduled interest payments executed as deterministic batch transfers, validated against compliance and balance constraints.
* **Principal Redemption:** Atomic settlement at maturity, retiring the token and returning principal to holders.
* **Secondary Market Trading:** Fully compliant peer-to-peer transfers with real-time ERC-3643 validation.
* **Credit Rating Integration:** Updateable metadata fields allow trusted rating agencies to publish and refresh credit assessments on-chain.

**10.3.3 Real Estate Tokens**

Fractional ownership of property-backed assets:

* **Rental Income Distribution:** Dividend mechanism routes proportional yields to token holders based on verified lease/revenue data.
* **Property Metadata Chain:** Immutable references to location, valuation reports, holding entity, and deed documentation (stored off-chain, anchored via `BLAKE2b` hash).
* **Accredited Investor Enforcement:** Compliance module automatically validates KYC/AML status and jurisdictional eligibility before permitting transfers.
* **Title & Custody Mapping:** Legal ownership trails are cryptographically linked to on-chain token registries, enabling court-recognizable asset provenance.

**10.3.4 Fund Tokens**

Managed investment vehicles and NAV-tracked units:

* **NAV-Based Pricing:** Net Asset Value updated by authorized oracle or fund administrator via native state transactions.
* **Subscription/Redemption Windows:** Time-bound transfer restrictions enforce open/closed fund periods directly at the consensus layer.
* **Minimum Investment Thresholds:** Protocol-enforced entry limits prevent sub-threshold allocations.
* **Fee Deduction Logic:** Management and performance fees are automatically calculated and deducted during NAV update cycles, ensuring transparent, audit-ready expense tracking.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://polarischain-1.gitbook.io/polarischain/10.-real-world-asset-tokenization/10.3-supported-asset-classes-and-native-workflows.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.