> 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.2-security-token-issuance-and-lifecycle-management.md).

# 10.2 - Security Token Issuance & Lifecycle Management

Regulated assets are instantiated via the `IssueSecurityToken` native transaction type, which atomically registers the asset on-chain and binds its compliance envelope. Each issuance transaction defines:

* **Token Metadata:** Name, symbol, decimal precision, ISIN/CUSIP identifiers, and legal jurisdiction.
* **Compliance Configuration:** Required claim topics, authorized issuer registries, geographic allowlists/blocklists, and investor eligibility thresholds.
* **Agent Designation:** Cryptographically bound addresses for the issuer, transfer agent, registrar, and compliance officer.
* **Corporate Action Parameters:** Dividend schedules, voting rights configuration, split/consolidation rules, and redemption mechanisms.
* **Lifecycle State Machine:** Enforced transitions: `Issuance → Active → Paused → Redeemed`. State changes require authorized agent signatures and are validated by consensus before commitment.


---

# 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.2-security-token-issuance-and-lifecycle-management.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.