249 lines
14 KiB
Markdown
249 lines
14 KiB
Markdown
# Business Presentation: DLE Implementation and Sandbox Participation
|
||
|
||
**Language:** [Русский](../../ru/presentations/business-sandbox-deck.md) | [English](business-sandbox-deck.md)
|
||
|
||
## Slide 1. Title
|
||
|
||
**To:** company executives, entrepreneurs
|
||
**From:** VC HB3 Accelerator / OOO “ERAYTI” (authorized seller in the Russian Federation)
|
||
**Topic:** Installation, configuration, and implementation of the Digital Legal Entity (DLE) operating system with the option to participate in a digital regulatory sandbox
|
||
**Format:** license-token purchase → platform registration → OS installation → sandbox stage with accelerator and fund governance
|
||
|
||
**Role of this presentation:** a detailed document for a company that is already interested in DLE and wants to understand the path of implementation and participation.
|
||
---
|
||
|
||
## Slide 2. What is happening in the market right now
|
||
|
||
Business and the state are moving toward digital identification and settlements via blockchain. This is no longer a forecast — these are current data:
|
||
|
||
| Fact | Value |
|
||
|------|---------|
|
||
| Asset tokenization market (2026) | $2.02 trillion, 37% annual growth |
|
||
| BlackRock + JPMorgan tokenized assets | $24 billion |
|
||
| Organizations with on-chain governance (DAO) | 13,000+, $24.5 billion in treasuries |
|
||
| Regulatory sandboxes worldwide | 199 in 92 countries |
|
||
| Digital ruble pilot (Bank of Russia) | 12 banks, smart contracts on a CBDC platform |
|
||
| McKinsey forecast for 2030 | $2–4 trillion of tokenized assets |
|
||
|
||
Major companies and regulators are already building infrastructure in which the smart contract is the basis of identification and settlements.
|
||
---
|
||
|
||
## Slide 3. Core idea: the smart contract as a digital record of your company
|
||
|
||
Today, a company’s legal identification is a record in a state registry (USRLE in the Russian Federation, analogues elsewhere): tax ID, registration number, region code, activity type, address.
|
||
|
||
**What we are building:** infrastructure in which these identifiers are written into a smart contract on a blockchain, and the regulator recognizes that record as legally significant.
|
||
|
||
| Today | In the digital sandbox |
|
||
|---------|---------------------|
|
||
| Identification — paper extract from the state registry | Identification — smart contract with regulator tagging |
|
||
| Settlements — bank account | Settlements — wallet bound to the smart contract (CBDC / stablecoins) |
|
||
| Reporting — manual preparation of declarations | Reporting — automatically formed from smart-contract operations |
|
||
| Control — desk audits | Control — blockchain scanner in real time |
|
||
|
||
**Why this matters for your company:**
|
||
- Automatic tax reporting without manual reconciliation
|
||
- Transparent operation history for partners and investors
|
||
- Settlements in digital currencies without traditional intermediaries
|
||
- Legally protected digital identification recognized by the state
|
||
- Reduced dependence on foreign corporate SaaS with paid subscriptions
|
||
|
||
---
|
||
|
||
## Slide 4. Where the sandbox fits and why it is needed
|
||
|
||
Writing state identifiers into a smart contract today has no legal force without regulator recognition. For this there is an **experimental legal regime (EPR)** — a mechanism that allows technologies to be tested with controlled departures from current norms.
|
||
|
||
**Sandbox goal:** the regulator provides identifier lists and tagging rules → these identifiers are written into participants’ smart contracts → under the EPR such a record is recognized as legally significant.
|
||
|
||
**What the EPR gives participants:**
|
||
- Your company’s smart contract receives state tagging
|
||
- Operations via the smart contract are accepted as legally significant within the experiment
|
||
- You gain first-mover advantage — when the regime becomes permanent, your infrastructure is already configured
|
||
|
||
**Important:** DLE’s baseline value appears already at the OS installation stage. The sandbox is the next contour for companies interested in regulatory tagging and a pilot regime.
|
||
|
||
---
|
||
|
||
## Slide 5. The DLE operating system — a ready tool, not a concept
|
||
|
||
**Digital Legal Entity (DLE)** — an operating system whose source code is available for review and audit by license-token holders. Installed on your server (on-premises).
|
||
|
||
### Key component: smart contracts with identifier support
|
||
|
||
The OS supports deployment of smart contracts into which regulator-set identifiers are written (country code, region, supervisory body, activity type). The smart contract’s governance tokens are used for access control, voting, and oversight.
|
||
|
||
### What else is included in the OS
|
||
|
||
| Component | Replaces | Savings over 5 years |
|
||
|-----------|-------------|-------------------|
|
||
| CRM and contact management | Bitrix24, AmoCRM, HubSpot | ~$12,000 |
|
||
| Omnichannel communications (Telegram, Email, chat, SMS) | SendPulse, Intercom, JivoSite | ~$9,000 |
|
||
| AI agents (local model, RAG, knowledge base) | ChatGPT API, Jasper | ~$12,000 |
|
||
| Spreadsheets and analytics | Google Sheets, Excel Online | ~$6,000 |
|
||
| Groups and workspaces | Slack, Notion, Confluence | included |
|
||
|
||
**Total:** instead of $39,000+ on SaaS subscriptions over 5 years — a one-time license of $1,000 or $10,000.
|
||
|
||
**Source code is available for review and audit by license-token holders.** A company can study the OS, documentation, and architecture before joining the program.
|
||
|
||
### Platforms already work
|
||
|
||
| Platform | Address | What it does |
|
||
|-----------|-------|------------|
|
||
| **Sandbox platform** | [hb3-accelerator.com](https://hb3-accelerator.com) | Participant registration, groups, acceleration, voting, support |
|
||
| **Contributor platform (RF)** | [эрайти.рф](https://xn--80aqc0am6d.xn--p1ai/) | License-token purchase, participation paperwork |
|
||
| **DLE repository** | [gitea/DLE](https://hb3-accelerator.com/gitea/VC-HB3-Accelerator/DLE) | OS source code, documentation, releases |
|
||
|
||
You can visit any of the platforms right now and see that this is a working product.
|
||
|
||
---
|
||
|
||
## Slide 6. How work is organized after entry
|
||
|
||
**VC HB3 Accelerator** — software provider and organizer of the support program. After a participant enters, the OS, contractors, and accelerator program operate as a single implementation contour:
|
||
|
||
### Mechanics
|
||
|
||
1. **Contributor** (local operator) handles entry, sells the license, and helps connect to the program.
|
||
2. **Participant company** installs DLE, deploys a smart contract, and connects to support.
|
||
3. **Contractors** configure the OS for the company’s processes and help bring it to a working state.
|
||
|
||
All tracks work as one contour: OS implementation, business configuration, participant support, and transition to the sandbox stage with the accelerator and fund governance.
|
||
|
||
### What the company gets after entry
|
||
|
||
After joining the program, the company receives:
|
||
|
||
- the DLE OS on its own server;
|
||
- configuration for real business processes;
|
||
- contractor support during implementation;
|
||
- access to the sandbox stage with the accelerator;
|
||
- connection to the next participation level via the fund governance contour.
|
||
|
||
### Cohorts
|
||
|
||
70 groups by activity type × 4 cohorts = 280 groups, 21,000+ participants. Experience exchange, joint work, and operation in the shared contour of the sandbox, acceleration, and fund ecosystem.
|
||
|
||
---
|
||
|
||
## Slide 7. What you get as a DLE user
|
||
|
||
| What you get | Details |
|
||
|---------------|--------|
|
||
| **DLE OS on your server** | Full source code, Docker containers, one-command install. Data stays with you |
|
||
| **Your company’s smart contract** | After EPR agreement — tagging with state identifiers, legally significant identification |
|
||
| **Configuration for your business** | Contractors adapt the OS to your activity type and processes |
|
||
| **Replacement of SaaS subscriptions** | CRM, communications, AI agents, analytics — in one contour. Savings from $30,000 over 5 years |
|
||
| **Connection to the next stage** | License purchase opens the sandbox stage with the accelerator and fund governance |
|
||
| **Accelerator program (5 years)** | Online sessions, training, technical support, updates |
|
||
| **Access to investment** | For some companies that pass the next development stage and reach required metrics |
|
||
| **First-mover advantage** | When the EPR becomes permanent, your infrastructure is already running |
|
||
|
||
---
|
||
|
||
## Slide 8. What the participant path looks like
|
||
|
||
```
|
||
1. Purchase a license token at эрайти.рф ($1,000 Standard / $10,000 Premium)
|
||
↓
|
||
2. Register at hb3-accelerator.com for repository and support-portal access
|
||
↓
|
||
3. Receive the license token and access to the OS template available for download in the DLE repository
|
||
↓
|
||
4. Install DLE on your server (Docker, one command)
|
||
↓
|
||
5. Deploy a smart contract with your company’s governance tokens
|
||
↓
|
||
6. Transfer the license token to the company smart-contract balance (the business now holds the license)
|
||
↓
|
||
7. Inclusion in the fund contour: the fund verifies the license on the contract balance and, if all conditions are met, credits fund governance tokens. This opens ecosystem participation (see [for-entrepreneurs.md](../for-entrepreneurs.md) and [service-terms.md in DLE](https://hb3-accelerator.com/gitea/VC-HB3-Accelerator/DLE/src/branch/main/legal.ru/service-terms.md)).
|
||
↓
|
||
8. Contractors configure the OS for your business
|
||
↓
|
||
9. Work in the program: training, support, experience exchange
|
||
↓
|
||
10. EPR agreement → tagging smart contracts with regulator identifiers
|
||
↓
|
||
11. Next stage: legally significant digital identification and settlements
|
||
```
|
||
|
||
---
|
||
|
||
## Slide 9. Refunds and protection in force majeure
|
||
|
||
| Guarantee | Details |
|
||
|----------|--------|
|
||
| **Perpetual license** | Right of use is not time-limited and cannot be revoked |
|
||
| **OS runs autonomously** | Even if the project ends — DLE keeps running on your server; data stays with you |
|
||
| **70% refund (no updates)** | Possible under contract terms: vote of license-token holders, confirmation of grounds, and request within the set term |
|
||
| **70% refund (regulator refusal)** | Possible with documented regulator refusal and compliance with contract terms |
|
||
| **Claim within 30 days** | For calculation error, double payment, or other justified reasons |
|
||
| **Terms are fixed** | Your license terms do not change after purchase; backward compatibility is maintained |
|
||
|
||
---
|
||
|
||
## Slide 10. Pricing
|
||
|
||
| Package | Price | Tokens | Votes |
|
||
|-------|------|--------|--------|
|
||
| **Standard** | $1,000 USDT (one-time) | 1 | 1 |
|
||
| **Premium** | $10,000 USDT (one-time) | 10 | 10 |
|
||
|
||
**Included in both packages:** perpetual license, full source code, 5 years of updates, technical support, access to the support program, document pack for the regulator.
|
||
|
||
**Payment:** cryptocurrency (USDT), bank transfer via an authorized seller, credit cards via partners.
|
||
|
||
**Seller in the RF:** OOO “ERAYTI” (OGRN: 1222600014383)
|
||
|
||
---
|
||
|
||
## Slide 11. Sandbox structure
|
||
|
||
| Level | What happens | Platform |
|
||
|---------|---------------|-----------|
|
||
| **Accelerator platform** | Shared groups, support, training, and program access | [hb3-accelerator.com](https://hb3-accelerator.com) |
|
||
| **Contributor platform** | License sales and participant onboarding in a specific jurisdiction | [эрайти.рф](https://xn--80aqc0am6d.xn--p1ai/) (RF) |
|
||
| **Participant operating systems** (on-premises) | Own DLE instance, own data, own smart contract with governance tokens | Installed on your server |
|
||
| **Pilot regulatory contour** | Used when agreeing and operating the sandbox under pilot rules | Connected per sandbox scenario |
|
||
|
||
**Start** — Russian Federation. Contributor in the RF — OOO “ERAYTI” ([эрайти.рф](https://xn--80aqc0am6d.xn--p1ai/)).
|
||
|
||
**For business this means:** after buying a license token, installing DLE, and submitting the smart-contract address, you get your OS on your side, go through implementation with contractors, and open the next stage — participation in the sandbox, accelerator, and fund governance contour when conditions are met (see for-entrepreneurs.md).
|
||
|
||
---
|
||
|
||
## Slide 12. Next step
|
||
|
||
| Step | Action | Link |
|
||
|-----|----------|--------|
|
||
| 1 | Purchase a license token from the contributor in the RF | [эрайти.рф](https://xn--80aqc0am6d.xn--p1ai/) |
|
||
| 2 | Register on the accelerator platform | [hb3-accelerator.com](https://hb3-accelerator.com) |
|
||
| 3 | Review OS source code and documentation | [gitea/DLE](https://hb3-accelerator.com/gitea/VC-HB3-Accelerator/DLE) |
|
||
|
||
**Contacts:**
|
||
- **Accelerator platform:** [hb3-accelerator.com](https://hb3-accelerator.com) — registration, groups, support
|
||
- **License purchase (RF):** [эрайти.рф](https://xn--80aqc0am6d.xn--p1ai/) — OOO “ERAYTI”, 18900@эрайти.рф, +7 (968) 269-92-64
|
||
- **Email:** info@hb3-accelerator.com
|
||
- **Telegram bot:** [@HB3_Accelerator_Bot](https://t.me/HB3_Accelerator_Bot)
|
||
|
||
---
|
||
|
||
## Slide 13. Additional materials
|
||
|
||
- [DLE product (README.md)](https://hb3-accelerator.com/gitea/VC-HB3-Accelerator/DLE/src/branch/main/README.md)
|
||
- [Purchase and service terms](https://hb3-accelerator.com/gitea/VC-HB3-Accelerator/DLE/src/branch/main/legal.ru/service-terms.md)
|
||
- [Accelerator program](../accelerator-program.md)
|
||
- [Fund business model](../business-model.md) — for a detailed study of ecosystem economics
|
||
- [For entrepreneurs](../for-entrepreneurs.md)
|
||
- [Presentation for regulators](fns-epr-dle-hb3-deck.md)
|
||
- [Sandbox description](../sandbox-description.md)
|
||
- [FAQ](../FAQ.md)
|
||
- [Disclaimers](../DISCLAIMERS.md)
|
||
|
||
---
|
||
|
||
## Note
|
||
|
||
Materials are provided for informational purposes and are not legal advice or an offer to deal. Participation terms are defined by the agreement with the authorized seller. All projections are a forward-looking vision, not a guarantee. More: [DISCLAIMERS.md](../DISCLAIMERS.md)
|