> For the complete documentation index, see [llms.txt](https://docs.allo.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allo.xyz/on-chain-funds/architecture.md).
# Architecture
#### **Workflow Description**
#### **Step 1: Connect Wallet**
* The **Fund Manager** initiates the process by connecting their wallet (either **MetaMask** for EVM-based chains or **Phantom** for Solana) to the platform through the **Connect** module.
#### **Step 2: Create Fund**
* Once the wallet is connected, the **Fund Manager** creates a new fund using the platform’s interface.
#### **Step 3: Investors Contribute**
* Investors contribute their assets (e.g., USDC, USDT, or ETH) to the fund by interacting with the fund through the platform’s front end.
#### **Step 4: Tokenization Execution**
* Once the fund reaches its required amount, it becomes **ready for tokenization**.
* The **Fund Manager** triggers the tokenization process via the **Tokenizer Module**, which handles the execution.
#### **Step 5: Chain Selection**
* The **Tokenizer Module** selects the appropriate blockchain based on the manager’s choice:
* **BNB Chain:** The process uses the **ERC20 Token Factory** to mint ERC20 tokens.
* **Solana:** The process uses the **TOKEN Program 2022** to mint Solana-compliant tokens.
#### **Step 6: Minting Tokens**
* The selected smart contract (either ERC20 Token Factory or Solana TOKEN Program) mints the tokens representing the fund.
* These tokens are sent to the **Fund Manager Wallet**, representing ownership or shares in the fund.
#### **Step 7: Token Distribution**
* The minted tokens are then distributed to the **Token Treasury**, which can be accessed by investors.
* This marks the completion of the fund’s tokenization, allowing investors to hold or trade the tokens representing their share in the fund.
---
# 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://docs.allo.xyz/on-chain-funds/architecture.md?ask=&goal=
```
`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.