> 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/6.-transaction-model/6.1-native-transaction-types.md).

# 6.1 - Native Transaction Types

All network operations are implemented as typed transactions, compiled directly into the node binary and validated by every consensus participant. The transaction set is phased to align with network maturity and institutional onboarding:

| Transaction Type                              | Phase | Description                                                              |
| --------------------------------------------- | ----- | ------------------------------------------------------------------------ |
| `Transfer`                                    | 1     | Native `$POLA` transfer between accounts                                 |
| `MintNAA`                                     | 1     | Mint a new Native Attached Asset (token) into a collection               |
| `TransferNAA`                                 | 1     | Transfer ownership of a Native Attached Asset                            |
| `RegisterIdentity`                            | 3     | Register on-chain identity record (address ↔ identity-id ↔ jurisdiction) |
| `UpdateIdentity`                              | 3     | Modify identity metadata (e.g., re-verification, jurisdiction change)    |
| `RemoveIdentity`                              | 3     | Remove identity record (e.g., account closure)                           |
| `AddTrustedIssuer`                            | 3     | Authorize a claim issuer for an asset (per claim topic)                  |
| `RemoveTrustedIssuer`                         | 3     | Revoke an issuer's authorization                                         |
| `UpdateIssuerClaimTopics`                     | 3     | Modify authorized claim topics for an issuer                             |
| `IssueClaim`                                  | 3     | Trusted issuer issues a Dilithium2-signed compliance claim               |
| `RevokeClaim`                                 | 3     | Trusted issuer revokes a previously issued claim                         |
| `IssueSecurityToken`                          | 4     | Issue a regulated security token with full ERC-3643 compliance config    |
| `AgentMint`                                   | 4     | Mint additional units of a regulated security token                      |
| `AgentBurn`                                   | 4     | Burn units for redemption or settlement                                  |
| `AgentFreeze` / `AgentUnfreeze`               | 4     | Freeze or unfreeze wallet holdings of a specific asset                   |
| `AgentForceTransfer`                          | 4     | Court-ordered asset recovery (compliance-agent operation)                |
| `AgentWalletRecovery`                         | 4     | Migrate assets from a lost-key wallet to a new wallet                    |
| `BondStake` / `UnbondStake` / `WithdrawStake` | 5     | Validator/delegator staking lifecycle operations                         |
| `ProtocolUpgradeSignal`                       | 5     | Validator signals readiness for next protocol version (§8.6)             |
| `GovernanceProposal` / `GovernanceVote`       | 5     | Submit and cast stake-weighted votes on protocol parameters              |

Each transaction type is cryptographically signed, nonce-sequenced, and validated by every validator before DAG inclusion. State transitions are applied deterministically once blocks are linearized.


---

# 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/6.-transaction-model/6.1-native-transaction-types.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.