# Use Cases

Stobox DID is designed to power regulated financial ecosystems, acting as the identity and compliance foundation for tokenized real-world assets (RWAs).

It enables issuers, investors, institutions, regulators, and custodians to participate in blockchain-based markets while meeting legal and operational requirements.

This chapter outlines practical use cases for Stobox DID across industries, platforms, and business models, with a particular focus on **Stobox 4**, **STV3 programmable assets**, and **institutional RWA adoption**.

***

### **Use Cases in Stobox 4 (Enterprise Tokenization Platform)**

Stobox 4 uses DID as its core identity and compliance layer. DID powers several workflows inside the platform:

***

#### **Investor Onboarding & Verification**

Stobox 4 automatically generates a DID for each investor after KYC/KYB approval.\
Attributes reflect:

* jurisdiction
* investor type (accredited, retail, institutional)
* sanctions screening
* eligibility for specific offerings
* verification validity dates

This enables issuers to onboard investors globally with full compliance automation.

**Benefits:**

* No manual whitelisting
* Investors re-use their DID across offerings
* Compliance updates propagate instantly

***

#### **Access Control to STO / RWA Offerings**

Each project in Stobox 4 uses DID attributes to define investor access rules.

Examples:

* U.S. accredited investors permitted
* EU retail investors restricted
* Institutional-only share classes
* SPV access limited by jurisdiction

The DID validation occurs automatically when an investor attempts to subscribe to an offering.

**Benefits:**

* Automated investor gating
* Lower legal risk
* No need for human review

***

#### **Token Distribution & Whitelisting**

When issuers distribute STV3 tokens via Stobox 4, eligibility is enforced by DID:

* only active, compliant DIDs can receive allocations
* investors who fail renewal or sanctions checks lose eligibility
* vesting attributes prevent early transfers

**Benefits:**

* Fully compliant distribution
* No risk of sending tokens to unauthorized wallets

***

#### **Marketplace & Secondary Trading (Future)**

In forthcoming Stobox marketplace modules, DID enables:

* compliant secondary trading
* investor qualification screening
* jurisdiction-based liquidity segmentation
* prevention of illegal or restricted transfers

**Benefits:**

* A compliant, global secondary market for RWAs
* Full transparency for issuers and regulators

***

#### **Governance Participation for Tokenized Projects**

SPVs or tokenized companies running governance processes may restrict voting to:

* eligible token classes
* verified investors
* jurisdiction-appropriate participants

DID ensures governance integrity.

***

### **Use Cases for RWA Tokenization**

Real-world assets require strict identity and compliance controls. Stobox DID enables fully compliant lifecycle management across sectors.

***

#### **Security Tokens (Equity, Debt, SPVs)**

DID allows:

* accredited investor checks
* lockup enforcement
* voting rights assignment
* cap table transparency
* investor class restrictions

STV3 programmable securities rely on DID to ensure that all transfers, redemptions, and governance operations comply with securities laws.

***

#### **Tokenized Funds & NAV-Based Products**

Fund managers can use DID to:

* define investor categories
* assign eligibility for share classes
* restrict redemptions to verified entities
* manage lockups and subscription windows
* automate compliance for distributions

Combined with STV3 fund facets, DID makes fund tokenization fully compliant.

***

#### **Tokenized Real Estate (Commercial & Residential)**

DID supports:

* jurisdiction-based investor eligibility
* enforcement of foreign ownership restrictions
* lockup and resale restrictions
* governance eligibility for property SPVs

Real estate tokenization requires strict legal enforceability — DID provides the identity assurance layer needed.

***

#### **Commodity & Precious Metals Tokens**

Commodity-backed RWAs (gold, metals, energy) require:

* KYC/KYB compliance
* jurisdictional restrictions
* redemption rights limited to authorized custodians
* prevention of unauthorized minting/receiving

DID ensures only approved entities can participate in reserve-backed ecosystems.

***

#### **Tokenized Carbon Credits & ESG Assets**

For carbon markets, DID ensures:

* only accredited registries issue tokens
* corporate buyers meet environmental reporting requirements
* double counting is prevented via DID-bound identities
* retirement events are linked to verified organizations

DID supports transparent carbon markets aligned with ESG regulations.

***

#### **Infrastructure & Energy Assets**

DID enables:

* eligibility-based access for institutional investors
* compliance validation for revenue distribution
* jurisdictionally restricted ownership
* wallet-level permissioning for operations

Examples:

* solar farm tokens
* energy production credits
* infrastructure SPVs

***

#### **Intellectual Property & Royalties**

For IP tokenization, DID enforces:

* rights attribution to real creators
* distribution eligibility for verified beneficiaries
* transfer restrictions based on licensing agreements

***

### **Use Cases for Institutions & Compliance Teams**

#### **AML / KYC Integration**

DID allows compliance teams to automate:

* sanctions checks
* enhanced due diligence
* politically exposed person screening
* periodic KYC renewals

When attributes expire, the system automatically restricts permissions.

***

#### **Regulator-Friendly Audit Trails**

Regulators benefit from:

* immutable DID event logs
* transparent identity histories
* full traceability of compliance states over time

This strengthens the approval case for RWA tokenization programs.

***

#### **Custodial Platforms & Banks**

Custodians can:

* manage multiple wallets per client
* preserve regulatory identity binding
* rotate keys without re-verifying customers

Banks can use DID to automate controlled access to tokenized assets and deposits.

***

#### **Marketplaces, ATS, and Trading Venues**

Marketplace operators can use DID to:

* screen buyers and sellers
* enforce pre-trade eligibility
* restrict trading by geography
* enable institutional onboarding

This enables legally compliant liquidity for RWAs.

***

### **Advanced Use Cases**

#### **Enterprise Tokenized Balance Sheets**

Corporations can tokenize:

* debt instruments
* revenue streams
* internal assets

DID enforces internal rules for eligible holders.

***

#### **DAO Governance with Legal Compliance**

Hybrid organizations can:

* combine token voting with DID-based identity
* enforce member eligibility
* ensure compliance with corporate law

***

#### **Interoperable Identity Across Assets**

A DID created once can be reused across:

* multiple offerings
* different asset classes
* partner platforms
* liquidity venues

This reduces friction and increases market participation.

***

### **Summary**

Stobox DID unlocks a vast range of use cases across tokenized finance, corporate structures, and institutional asset management.\
By delivering programmable, secure, and privacy-preserving identity, DID enables compliant RWA issuance and trading across Stobox 4, STV3, and external enterprise systems.

DID ensures:

* compliant investor onboarding
* secure multi-wallet operations
* deterministic transfer validation
* scalable governance
* interoperable identity across asset ecosystems

This makes Stobox DID not just an identity tool — but the cornerstone of regulated digital asset infrastructure.

***


---

# 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.stobox.io/did/use-cases.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.
