222 lines
9.9 KiB
Markdown
222 lines
9.9 KiB
Markdown
**Language:** [English](sandbox-description.md) | [Русский](../ru/sandbox-description.md)
|
||
|
||
---
|
||
|
||
# Regulatory Sandbox Description
|
||
|
||
## Version for Partners: IT Hubs and Regulators
|
||
|
||
---
|
||
|
||
## 1. Purpose of the Sandbox
|
||
|
||
Creating a controlled legal and technological environment for testing business models based on blockchain and smart contracts, with the possibility of scaling to the real market.
|
||
|
||
The sandbox addresses three objectives:
|
||
1. **For business:** A legal way to test blockchain solutions without the risk of violating legislation.
|
||
2. **For the regulator:** Ready-made supervisory tools and the ability to explore new technologies on live use cases.
|
||
3. **For the IT hub:** Attract new residents, strengthen expertise, and become part of a global sandbox network.
|
||
|
||
---
|
||
|
||
## 2. Territory and Jurisdiction
|
||
|
||
The sandbox is deployed **on the territory of an IT hub** that has accreditation or a special legal regime (special economic zone, international tech park, special administrative region).
|
||
|
||
**Legal mechanism:**
|
||
1. The IT hub (or authorized body) issues permission for pilot companies to open representative offices on its territory.
|
||
2. Each participating company receives a **legal address on the hub’s territory**.
|
||
3. The legal address is linked to the company’s smart contract on the DLE platform.
|
||
4. All operations within the pilot are recorded on the blockchain and available for regulator monitoring.
|
||
|
||
---
|
||
|
||
## 3. Sandbox Participants and Their Roles
|
||
|
||
The sandbox involves **three types of legal entities**, each with its own DLE platform:
|
||
|
||
### 3.1. IT Hub Company (Infrastructure Operator)
|
||
|
||
| Parameter | Value |
|
||
|-----------|--------|
|
||
| **Platform** | DLE purchased by the hub (Standard or Premium license) |
|
||
| **Role** | Provision of rental, consulting, and technical support services to new residents |
|
||
| **Funding source** | Hub’s own funds |
|
||
| **What the hub gets** | New service for residents, revenue from services, stronger capabilities |
|
||
|
||
### 3.2. Regulator’s Entity (Supervisory Authority)
|
||
|
||
| Parameter | Value |
|
||
|-----------|--------|
|
||
| **Platform** | DLE deployed for supervisory purposes |
|
||
| **Role** | Monitoring sandbox operations, data analysis, technology research |
|
||
| **Funding source** | State grant allocated to the fund (VC HB3 Accelerator) for opening a representative office and paying for computing equipment rental |
|
||
| **What the regulator gets** | Blockchain scanner, access to the operations ledger, analytics tools |
|
||
|
||
### 3.3. Fund’s Entity (VC HB3 Accelerator)
|
||
|
||
| Parameter | Value |
|
||
|-----------|--------|
|
||
| **Platform** | Fund’s DLE (deployed with grant funds) |
|
||
| **Role** | Running the accelerator program, registering and coordinating pilot companies |
|
||
| **Funding source** | Regulator grant + license revenue |
|
||
| **What the fund gets** | Official representation in the hub, access to the pool of pilot companies |
|
||
|
||
### 3.4. Pilot Companies (Accelerator Participants)
|
||
|
||
| Parameter | Value |
|
||
|-----------|--------|
|
||
| **Registration** | On the fund’s platform (VC HB3 Accelerator) |
|
||
| **Legal address** | On IT hub territory, linked to smart contract |
|
||
| **Groups** | By type of economic activity (70+ areas) |
|
||
| **Program** | Platform setup, testing, training, access to investment |
|
||
| **Participation term** | Within a cohort (up to 5 years) |
|
||
|
||
---
|
||
|
||
## 4. Technology Architecture
|
||
|
||
All three platforms (hub, regulator, fund) are deployed **independently** on servers located within the jurisdiction (on-premises).
|
||
|
||
**Shared infrastructure:**
|
||
1. **Blockchain ledger** — EVM-compatible, deployed locally.
|
||
2. **Smart contracts** — with support for identifiers (tax, banking, accounting).
|
||
3. **Blockchain scanner** — real-time access for the regulator.
|
||
4. **AI agents** — local models for analytics and reporting (data does not leave the server).
|
||
|
||
**Links between platforms:**
|
||
- Pilot companies register on the fund’s platform.
|
||
- The legal address issued by the hub is linked to the company’s smart contract.
|
||
- The regulator accesses operation monitoring through its own platform instance.
|
||
|
||
---
|
||
|
||
## 5. Mechanics for Pilot Companies
|
||
|
||
### 5.1. Selection and Registration
|
||
|
||
1. The fund (VC HB3 Accelerator) recruits pilot companies by type of economic activity.
|
||
2. The company applies on the fund’s platform: https://hb3-accelerator.com.
|
||
3. After approval, the company purchases a DLE license (Standard or Premium).
|
||
4. The company receives a legal address on the IT hub’s territory and registers a representative office.
|
||
5. The legal address is linked to the company’s smart contract.
|
||
|
||
### 5.2. Participation in the Accelerator
|
||
|
||
1. The company registers in a group by its type of activity (70+ areas).
|
||
2. Contractors (fund token holders) help configure the platform to the company’s business processes.
|
||
3. The company undergoes training and participates in online sessions and workshops.
|
||
4. After testing, the company receives recommendations for further development.
|
||
|
||
### 5.3. Access to Investment
|
||
|
||
1. Companies that meet target metrics receive an investment offer from the fund.
|
||
2. Investment range: from Pre-seed (50,000–200,000 USDT) to ICO (up to 4,000,000 USDT).
|
||
3. In exchange for investment, the fund receives governance tokens of the portfolio company.
|
||
|
||
---
|
||
|
||
## 6. Mechanics for the IT Hub
|
||
|
||
1. **Joining the project:** The hub signs a partnership agreement with the fund (VC HB3 Accelerator).
|
||
2. **Platform acquisition:** The hub purchases a DLE license (Standard or Premium) to provide services to residents.
|
||
3. **Venue accreditation:** The hub confirms readiness to provide legal addresses to pilot companies.
|
||
4. **Staff registration:** Hub staff register on the fund’s platform to participate in the accelerator as observers or consultants.
|
||
5. **Monitoring:** The hub tracks resident activity through its own platform (without access to regulator data).
|
||
|
||
**What the hub gets:**
|
||
- A new service to attract residents.
|
||
- Revenue from rental and consulting services.
|
||
- Participation in a global sandbox network (100+ countries).
|
||
- DLE platform governance tokens (voting rights in product development).
|
||
|
||
---
|
||
|
||
## 7. Mechanics for the Regulator
|
||
|
||
1. **Grant funding:** The regulator allocates a grant to the fund for opening a representative office in the IT hub, server equipment rental, and organizing pilot company recruitment.
|
||
2. **Provision of identifiers:** The regulator provides the fund with API access to reference data with codes for identification of legal entities, banking transactions, and tax reporting.
|
||
3. **Integration:** VC HB3 Accelerator embeds the identifiers into the DLE platform.
|
||
4. **Deployment:** Using grant funds, a platform instance is deployed for the regulator (blockchain scanner, analytics tools).
|
||
5. **Staff registration:** Regulator observers register on the fund’s platform for access to pilot company data.
|
||
6. **Monitoring:** The regulator tracks sandbox operations in real time through its own platform instance.
|
||
|
||
**What the regulator gets:**
|
||
- Ready supervisory tools (blockchain ledger, scanner, reporting).
|
||
- A research environment for new technologies.
|
||
- Data on pilot company operations for building the regulatory framework.
|
||
- Ability to integrate with ledgers of other jurisdictions (cross-border cooperation).
|
||
|
||
---
|
||
|
||
## 8. Mechanics for the Fund (VC HB3 Accelerator)
|
||
|
||
1. **Receiving the grant:** The fund secures funding from the regulator to open a representative office in the IT hub.
|
||
2. **Integration:** VC HB3 Accelerator embeds the identifiers into the DLE platform.
|
||
3. **Representative office registration:** The fund establishes a legal entity in the hub and deploys its DLE platform.
|
||
4. **Participant recruitment:** The fund runs marketing campaigns to attract pilot companies by type of economic activity.
|
||
5. **Accelerator operations:** The fund forms cohorts and groups and engages contractors to configure participants’ platforms.
|
||
6. **Investment:** The fund selects the best companies and invests treasury funds (70% of all inflows).
|
||
7. **Scaling:** The fund replicates the model in other countries (target: 100+ sandboxes in 3–12 months).
|
||
|
||
---
|
||
|
||
## 9. Scaling: 100 Sandboxes in 12 Months
|
||
|
||
Launching a single sandbox takes **3–4 months**. With parallel efforts, the fund team can deploy a network of 100 sandboxes within **one year**.
|
||
|
||
**Parallel processes:**
|
||
- Registration of fund representative offices.
|
||
- Integration of local identifiers.
|
||
- Recruitment of pilot companies by type of activity.
|
||
- Formation of cohorts and groups.
|
||
|
||
**Key metrics:**
|
||
- 100+ countries with representative offices.
|
||
- 21,000+ entrepreneurs in the accelerator (4 cohorts × 70 groups).
|
||
- 600+ portfolio companies over 5 years.
|
||
|
||
---
|
||
|
||
## 10. Risks and Mitigation
|
||
|
||
| Risk | Mitigation |
|
||
|------|-------------|
|
||
| Grant disbursement delays | Working with multiple regulators in parallel, phased funding |
|
||
| Hub refusal to cooperate | Prioritizing hubs with an existing sandbox (e.g. Astana Hub) |
|
||
| Technical failures | On-premises deployment, open source, independent audit |
|
||
| Shortage of pilot companies | Marketing via IT hubs, partnership programs, international networking |
|
||
| Regulatory changes | Flexible architecture, on-chain voting, data localization |
|
||
|
||
---
|
||
|
||
## 11. Conclusion
|
||
|
||
The proposed sandbox model is not only a technological solution but a ready-made ecosystem that aligns the interests of business, the regulator, and the infrastructure venue.
|
||
|
||
For the IT hub it offers:
|
||
- Becoming a node in a global network of regulatory sandboxes;
|
||
- Attracting new residents without budget expenditure (funding comes via the regulator’s grant);
|
||
- A practical tool for developing the blockchain segment.
|
||
|
||
---
|
||
|
||
## 12. Contacts
|
||
|
||
See [Contacts](CONTACTS.md).
|
||
|
||
---
|
||
|
||
## See also
|
||
|
||
- [Team](team.md) — founder, AI tools, token holders
|
||
- [IT hubs and regulators database](it-hubs-database.md) — target venues for sandboxes
|
||
- [Accelerator program](accelerator-program.md) — format, timelines, cohort structure
|
||
- [For regulators](for-regulators.md) — cooperation proposal, implementation steps
|
||
- [Glossary](GLOSSARY.md) — terms and definitions
|
||
- [Contacts](CONTACTS.md)
|
||
|
||
---
|
||
|
||
**Last updated:** 2026-02-27
|