# Set Up The Project and Token

*To set up the project and the token, you submit the tokenization framework, where Phases 1–6 establish the legal and structural foundation. The seventh phase relates to the offering and becomes available after the token is minted; this is when the offering goes live. We'll describe it in due course.*

> *All our clients receive a detailed list of questions, requirements, and available options to help them prepare their answers before the first kickoff meeting with the tokenization team.*

*We recommend working with legal, financial, and compliance advisors throughout the process, whether through your own trusted advisors and in-house teams, or through our partners, who have 8+ years of experience in tokenization projects.*

{% hint style="warning" %}
At any point while working on the tokenization framework, you can open the **Summary** in the sidebar to see what is missing or needs updating. From there, you can jump directly to the relevant phase and item — no need to navigate through each phase manually.
{% endhint %}

***

#### Phase 1: Tokenization Planning

{% hint style="info" %}
You have most likely already submitted it to create and activate your Business Space, but you can update your information if needed.
{% endhint %}

**What's required:** Your high-level strategy — what you're tokenizing, why you're doing it, and who your investors will be. This includes asset type, approximate value, jurisdiction, eligible investor categories, and target markets.

**Why it matters:** This is the foundation of your entire offering. It determines which legal frameworks apply, which investor types can participate, and how the token structure should be designed. Getting this right upfront prevents costly redesigns later.

***

<figure><img src="/files/wKawZzwDLWrZB32BRGPO" alt=""><figcaption></figcaption></figure>

#### Phase 2: Asset Structuring and Legal Readiness

**What's required:** Financial details (asset value, fundraising target, tokenized portion), a valuation report from a recognized provider, proof of ownership, insurance documentation, and proof of reserves if applicable.

**Why it matters:** Investors and regulators need independent evidence that your asset is real, correctly valued, and legally yours to tokenize. Without verified ownership and a credible valuation, the offering lacks the legal and commercial credibility required to attract capital.

***

#### Phase 3: Define the Tokenization Model

**What's required:** A single selection from eight fundraising models (e.g., Full Asset Sale, Revenue Sharing, Loan-Based, Development Model, etc.).

**Why it matters:** The model defines the economic relationship between you and your investors — who owns what, how returns are generated, and what happens at exit. It directly shapes the token structure, smart contract logic, and legal documentation in every subsequent phase.

***

#### Phase 4: Token Economics & Smart Contract Configuration

**What's required:** Token category and type, yield type and rate, economic/capital/governance rights, total and initial supply, token price, name, symbol, decimals, and the blockchain network (Arbitrum).

{% hint style="warning" %}
Please note that the initial supply defines how many tokens you can issue immediately at the token minting stage.
{% endhint %}

**Why it matters:** This phase encodes your investor rights and financial terms into an immutable smart contract. Every detail — from yield rate to voting rights — becomes a binding, on-chain commitment. Precision here is critical, as errors cannot be easily corrected after deployment.

***

#### Phase 5: Define an Issuing Framework

**What's required:** The legal entity that will issue the tokens (your holding company, an SPV, SPC, or fund), its jurisdiction, company type, verification documents, and any applicable regulatory licenses.

**Why it matters:** Tokens must be issued by a recognized legal entity to be enforceable. The issuing company is the legal counterparty to every investor. Its jurisdiction determines tax treatment, investor protections, and regulatory oversight. Licensing requirements must be met before any public offering.

***

#### Phase 6: Legal Documentation

**What's required:** A comprehensive package of legal and compliance documents, including the link between the asset and the issuing entity, pitch deck, business plan, financials, corporate authorization, AML/KYC policy, privacy policy, terms of use, legal opinion, and, optionally, tax advice and audit reports.

**Why it matters:** This phase is the compliance backbone of your offering. Regulators, institutional investors, and legal advisors will scrutinize these documents. They prove you have the authority to issue tokens, that investors are protected, and that the offering meets anti-money laundering and data protection standards. After submission here, Stobox validates your tokenization before smart contract deployment.

***

#### Next Step: Send the tokenization framework to our Compliance team for validation

{% hint style="info" %}
**Note that validation may take up to two business days.**

* Once approved, you can move forward.
* If the framework requires revision, you will receive comments from the Compliance team. You can revise and resubmit: you have three attempts.
  {% endhint %}

{% hint style="danger" %}
**Important:** Once the tokenization framework is approved, it cannot be changed. Make sure all project and token details are final and accurate before submitting for validation.
{% endhint %}

***


---

# 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/helpcentre/help-centre/business-space/launch-your-project/set-up-the-project-and-token.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.
