ваше сообщение коммита
This commit is contained in:
113
legal-en/ATTRIBUTION_REQUIREMENTS.md
Normal file
113
legal-en/ATTRIBUTION_REQUIREMENTS.md
Normal file
@@ -0,0 +1,113 @@
|
||||
# Attribution Requirements
|
||||
|
||||
## Mandatory Attribution
|
||||
|
||||
When using any code from the DLE (Digital Legal Entity) project, including individual functions, modules, or algorithms, you must indicate the source.
|
||||
|
||||
## Attribution Formats
|
||||
|
||||
### In code comments
|
||||
```javascript
|
||||
/**
|
||||
* Source: DLE (Digital Legal Entity)
|
||||
* Author: Tarabanov Alexander Viktorovich
|
||||
* License: Proprietary
|
||||
* Link: https://github.com/VC-HB3-Accelerator/DLE
|
||||
*/
|
||||
```
|
||||
|
||||
### In documentation
|
||||
```markdown
|
||||
## Used Components
|
||||
|
||||
- **DLE Authentication Module** - Tarabanov Alexander Viktorovich
|
||||
- License: Proprietary
|
||||
- Source: https://github.com/VC-HB3-Accelerator/DLE
|
||||
```
|
||||
|
||||
### In configuration files
|
||||
```json
|
||||
{
|
||||
"attributions": {
|
||||
"DLE": {
|
||||
"author": "Tarabanov Alexander Viktorovich",
|
||||
"license": "Proprietary",
|
||||
"source": "https://github.com/VC-HB3-Accelerator/DLE",
|
||||
"contact": "info@hb3-accelerator.com"
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
## What Requires Attribution
|
||||
|
||||
### Must indicate source:
|
||||
- Any functions or methods
|
||||
- Algorithms and logic
|
||||
- Data structures
|
||||
- Configuration files
|
||||
- Styles and UI components
|
||||
- Documentation and comments
|
||||
|
||||
### Does not require attribution:
|
||||
- Standard libraries and frameworks
|
||||
- Well-known algorithms
|
||||
- Basic programming patterns
|
||||
|
||||
## Attribution Violations
|
||||
|
||||
### Considered a violation:
|
||||
- Using code without indicating source
|
||||
- Removing or modifying attribution
|
||||
- Incorrect author indication
|
||||
|
||||
### Consequences:
|
||||
- Automatic license termination
|
||||
- Possibility of legal action
|
||||
- Requirement to immediately cease use
|
||||
|
||||
## Examples of Proper Attribution
|
||||
|
||||
### In JavaScript file
|
||||
```javascript
|
||||
// Document validation function
|
||||
// Source: DLE (Digital Legal Entity) - Tarabanov Alexander Viktorovich
|
||||
// License: Proprietary
|
||||
function validateDocument(doc) {
|
||||
// implementation
|
||||
}
|
||||
```
|
||||
|
||||
### In Python file
|
||||
```python
|
||||
# Blockchain transaction processing module
|
||||
# Source: DLE (Digital Legal Entity) - Tarabanov Alexander Viktorovich
|
||||
# License: Proprietary
|
||||
class BlockchainProcessor:
|
||||
# implementation
|
||||
```
|
||||
|
||||
### In README file
|
||||
```markdown
|
||||
## Used Components
|
||||
|
||||
This project uses components from DLE (Digital Legal Entity):
|
||||
|
||||
- **Authentication System** - Tarabanov Alexander Viktorovich
|
||||
- **Document Processing** - Tarabanov Alexander Viktorovich
|
||||
- **Blockchain Integration** - Tarabanov Alexander Viktorovich
|
||||
|
||||
**License:** Proprietary
|
||||
**Contacts:** info@hb3-accelerator.com
|
||||
```
|
||||
|
||||
## Contacts for Questions
|
||||
|
||||
**Tarabanov Alexander Viktorovich**
|
||||
Email: info@hb3-accelerator.com
|
||||
Website: https://hb3-accelerator.com
|
||||
|
||||
---
|
||||
|
||||
**© 2024-2025 Tarabanov Alexander Viktorovich. All rights reserved.**
|
||||
|
||||
35
legal-en/AUTHORS.md
Normal file
35
legal-en/AUTHORS.md
Normal file
@@ -0,0 +1,35 @@
|
||||
# DLE Project Authors (Digital Legal Entity)
|
||||
|
||||
## Main Developer
|
||||
|
||||
**Tarabanov Alexander Viktorovich**
|
||||
- **GitHub:** [@VC-HB3-Accelerator](https://github.com/VC-HB3-Accelerator)
|
||||
- **Organization:** HB3 Accelerator
|
||||
- **Email:** info@hb3-accelerator.com
|
||||
- **Website:** [hb3-accelerator.com](https://hb3-accelerator.com)
|
||||
|
||||
## Contributors
|
||||
|
||||
- **Limited Liability Company "ERAITI" (LLC "ERAITI")**
|
||||
- **Role:** Official seller and licensing partner for clients from the Russian Federation
|
||||
- **Contacts:** 18900@эрайти.рф, +7 (968) 269-92-64
|
||||
|
||||
## Contact Information
|
||||
|
||||
### For copyright and licensing questions:
|
||||
- **Email:** info@hb3-accelerator.com
|
||||
- **GitHub Issues:** [Create issue](https://github.com/VC-HB3-Accelerator/DLE/issues)
|
||||
- **Website:** [hb3-accelerator.com](https://hb3-accelerator.com)
|
||||
|
||||
|
||||
## Project History
|
||||
|
||||
- **2024-2025:** Development and release of the first version of DLE
|
||||
- **Author:** Tarabanov Alexander Viktorovich
|
||||
- **License:** Proprietary Software License
|
||||
- **Status:** Active development
|
||||
|
||||
---
|
||||
|
||||
**All rights reserved.** See the [LICENSE.md](LICENSE.md) file for details.
|
||||
|
||||
76
legal-en/CONTRIBUTING.md
Normal file
76
legal-en/CONTRIBUTING.md
Normal file
@@ -0,0 +1,76 @@
|
||||
# Contributor Guide
|
||||
|
||||
## Licensing
|
||||
|
||||
When contributing to the DLE (Digital Legal Entity) project, you agree that your code will be distributed under the **Proprietary Software License**.
|
||||
|
||||
## Copyright
|
||||
|
||||
All contributors must:
|
||||
- Indicate their name in commits
|
||||
- Agree to transfer code rights to the project author
|
||||
- Not violate third-party copyrights
|
||||
|
||||
## Contribution Process
|
||||
|
||||
### 1. Preparation
|
||||
- Fork the repository
|
||||
- Clone your fork locally
|
||||
- Create a feature branch for your changes
|
||||
|
||||
### 2. Development
|
||||
- Follow the project's coding standards
|
||||
- Add code comments in English
|
||||
- Test your changes
|
||||
|
||||
### 3. Commits
|
||||
- Use clear commit messages
|
||||
- Indicate your name in commits
|
||||
- Break large changes into logical parts
|
||||
|
||||
### 4. Pull Request
|
||||
- Create a Pull Request with a description of changes
|
||||
- Indicate what problems your code solves
|
||||
- Wait for review from the project author
|
||||
|
||||
## Code Standards
|
||||
|
||||
### Naming
|
||||
- Files and folders: kebab-case
|
||||
- Variables and functions: camelCase
|
||||
- Constants: UPPER_SNAKE_CASE
|
||||
- Classes: PascalCase
|
||||
|
||||
### Comments
|
||||
```javascript
|
||||
/**
|
||||
* @copyright 2024-2025 Tarabanov Alexander Viktorovich
|
||||
* @license Proprietary
|
||||
* @author [Your name] <your-email@example.com>
|
||||
*/
|
||||
```
|
||||
|
||||
### Git Messages
|
||||
```
|
||||
feat: add new authentication function
|
||||
fix: fix data validation error
|
||||
docs: update API documentation
|
||||
style: code formatting
|
||||
refactor: refactor user module
|
||||
test: add tests for new functionality
|
||||
```
|
||||
|
||||
## Contacts
|
||||
|
||||
### For questions about project participation:
|
||||
- **Email:** info@hb3-accelerator.com
|
||||
- **GitHub Issues:** [Create issue](https://github.com/VC-HB3-Accelerator/DLE/issues)
|
||||
|
||||
### Project Author:
|
||||
**Tarabanov Alexander Viktorovich**
|
||||
Email: info@hb3-accelerator.com
|
||||
|
||||
---
|
||||
|
||||
**Thank you for your contribution to the DLE project development!**
|
||||
|
||||
101
legal-en/COPYRIGHT_NOTICE.md
Normal file
101
legal-en/COPYRIGHT_NOTICE.md
Normal file
@@ -0,0 +1,101 @@
|
||||
# Copyright Notice
|
||||
|
||||
## For use in code file headers
|
||||
|
||||
Add the following header to the beginning of each source code file:
|
||||
|
||||
```javascript
|
||||
/**
|
||||
* @copyright 2024-2025 Tarabanov Alexander Viktorovich
|
||||
* @license Proprietary
|
||||
* @author Tarabanov Alexander Viktorovich <info@hb3-accelerator.com>
|
||||
* @see https://github.com/VC-HB3-Accelerator
|
||||
* @see https://hb3-accelerator.com
|
||||
*/
|
||||
```
|
||||
|
||||
## For Python files
|
||||
|
||||
```python
|
||||
"""
|
||||
@copyright 2024-2025 Tarabanov Alexander Viktorovich
|
||||
@license Proprietary
|
||||
@author Tarabanov Alexander Viktorovich <info@hb3-accelerator.com>
|
||||
@see https://github.com/VC-HB3-Accelerator
|
||||
@see https://hb3-accelerator.com
|
||||
"""
|
||||
```
|
||||
|
||||
## For Vue files
|
||||
|
||||
```vue
|
||||
<!--
|
||||
@copyright 2024-2025 Tarabanov Alexander Viktorovich
|
||||
@license Proprietary
|
||||
@author Tarabanov Alexander Viktorovich <info@hb3-accelerator.com>
|
||||
@see https://github.com/VC-HB3-Accelerator
|
||||
@see https://hb3-accelerator.com
|
||||
-->
|
||||
```
|
||||
|
||||
## For CSS/SCSS files
|
||||
|
||||
```css
|
||||
/*
|
||||
@copyright 2024-2025 Tarabanov Alexander Viktorovich
|
||||
@license Proprietary
|
||||
@author Tarabanov Alexander Viktorovich <info@hb3-accelerator.com>
|
||||
@see https://github.com/VC-HB3-Accelerator
|
||||
@see https://hb3-accelerator.com
|
||||
*/
|
||||
```
|
||||
|
||||
## For HTML files
|
||||
|
||||
```html
|
||||
<!--
|
||||
@copyright 2024-2025 Tarabanov Alexander Viktorovich
|
||||
@license Proprietary
|
||||
@author Tarabanov Alexander Viktorovich <info@hb3-accelerator.com>
|
||||
@see https://github.com/VC-HB3-Accelerator
|
||||
@see https://hb3-accelerator.com
|
||||
-->
|
||||
```
|
||||
|
||||
## For configuration files
|
||||
|
||||
```json
|
||||
{
|
||||
"_copyright": "2024-2025 Tarabanov Alexander Viktorovich",
|
||||
"_license": "Proprietary",
|
||||
"_author": "Tarabanov Alexander Viktorovich <info@hb3-accelerator.com>",
|
||||
"_website": "https://hb3-accelerator.com",
|
||||
"_github": "https://github.com/VC-HB3-Accelerator"
|
||||
}
|
||||
```
|
||||
|
||||
## Important files for adding headers
|
||||
|
||||
### Frontend
|
||||
- `frontend/src/main.js`
|
||||
- `frontend/src/App.vue`
|
||||
- All Vue components
|
||||
- All CSS/SCSS styles
|
||||
|
||||
### Backend
|
||||
- `backend/src/index.js`
|
||||
- All modules and controllers
|
||||
- Configuration files
|
||||
|
||||
### Documentation
|
||||
- `README.md`
|
||||
- `docs/` - all documentation files
|
||||
|
||||
## Automation
|
||||
|
||||
It is recommended to set up pre-commit hooks for automatically adding copyright headers to new files.
|
||||
|
||||
---
|
||||
|
||||
**All rights reserved.** See the [LICENSE.md](LICENSE.md) file for details.
|
||||
|
||||
141
legal-en/README.md
Normal file
141
legal-en/README.md
Normal file
@@ -0,0 +1,141 @@
|
||||
# DLE LEGAL DOCUMENTATION
|
||||
## Intellectual Property Protection
|
||||
|
||||
**🌐 Language / Язык:** [🇷🇺 Русский](../legal/README.md) | [🇬🇧 English](README.md)
|
||||
|
||||
### 📋 **DOCUMENT OVERVIEW**
|
||||
|
||||
This section contains all legal documentation for protecting the intellectual property of the DLE (Digital Legal Entity) project.
|
||||
|
||||
### 🔒 **CONFIDENTIAL DOCUMENTS**
|
||||
|
||||
#### **Patent documents (DO NOT PUBLISH):**
|
||||
- [patents/](patents/) - Patent applications and innovative processes
|
||||
- Russian Federation patent applications
|
||||
- Technical specifications
|
||||
- Innovative processes
|
||||
- Strategic plans
|
||||
|
||||
**⚠️ IMPORTANT:** Patent documents contain confidential information and MUST NOT be published in public repositories.
|
||||
|
||||
### ✅ **PUBLIC DOCUMENTS**
|
||||
|
||||
#### **Copyright and licenses:**
|
||||
- [AUTHORS.md](AUTHORS.md) - Author information
|
||||
- [CONTRIBUTING.md](CONTRIBUTING.md) - Contributor guidelines
|
||||
- [COPYRIGHT_NOTICE.md](COPYRIGHT_NOTICE.md) - Copyright templates
|
||||
|
||||
#### **Licensing and terms:**
|
||||
- [service-terms.md](service-terms.md) - Terms of use and licensing
|
||||
- [ATTRIBUTION_REQUIREMENTS.md](ATTRIBUTION_REQUIREMENTS.md) - Attribution requirements
|
||||
- [USAGE_NOTIFICATION.md](USAGE_NOTIFICATION.md) - Usage notifications
|
||||
|
||||
#### 📑 **File Overview**
|
||||
|
||||
| File | Purpose |
|
||||
| --- | --- |
|
||||
| [AUTHORS.md](AUTHORS.md) | Author information and contact details. |
|
||||
| [CONTRIBUTING.md](CONTRIBUTING.md) | Participation rules for project contributors. |
|
||||
| [COPYRIGHT_NOTICE.md](COPYRIGHT_NOTICE.md) | Copyright notice templates for source files. |
|
||||
| [service-terms.md](service-terms.md) | Detailed licensing and maintenance terms. |
|
||||
| [ATTRIBUTION_REQUIREMENTS.md](ATTRIBUTION_REQUIREMENTS.md) | Formats and examples of mandatory attribution. |
|
||||
| [USAGE_NOTIFICATION.md](USAGE_NOTIFICATION.md) | Instructions and template for usage notification. |
|
||||
|
||||
#### **Complete service terms:**
|
||||
- 📖 [../docs-en/service-terms.md](../docs-en/service-terms.md) - **Detailed purchase and maintenance terms**
|
||||
- Licensing model (Perpetual License)
|
||||
- Service term types (Standard & Priority)
|
||||
- Smart contract voting system
|
||||
- 70% refund program
|
||||
- Technical support via https://hb3-accelerator.com/
|
||||
|
||||
---
|
||||
|
||||
## 📜 **LICENSING MODEL**
|
||||
|
||||
### Perpetual License
|
||||
|
||||
- **💰 Price:** $1,000 USDT (Standard) or $10,000 USDT (Priority)
|
||||
- **⏳ Term:** Lifetime (no time limit)
|
||||
- **🔄 Updates:** Free for 5 years for license token holders (see [service-terms](./service-terms.md))
|
||||
- **🗳️ Voting:** Blockchain voting for new feature development
|
||||
|
||||
### Management via DLE Smart Contract
|
||||
|
||||
Application development is managed through a blockchain smart contract (tokenized joint-stock company):
|
||||
|
||||
- **1 token = 1 vote** regardless of quantity
|
||||
- **51%+ for approval** majority decision
|
||||
- **Multi-chain** support for voting and execution
|
||||
- **Transparency** - all decisions on blockchain
|
||||
|
||||
### Portal for Licensees
|
||||
|
||||
- 🗳️ **Voting portal**: https://hb3-accelerator.com/
|
||||
- 📥 **Download updates**: https://hb3-accelerator.com/
|
||||
- 💬 **Support**: https://hb3-accelerator.com/
|
||||
|
||||
### 📁 **PROTECTION STRUCTURE**
|
||||
|
||||
```
|
||||
legal-en/
|
||||
├── AUTHORS.md # ✅ PUBLISH - Project authors
|
||||
├── CONTRIBUTING.md # ✅ PUBLISH - Contribution guidelines
|
||||
├── COPYRIGHT_NOTICE.md # ✅ PUBLISH - Copyright templates
|
||||
├── service-terms.md # ✅ PUBLISH - Terms of use
|
||||
├── ATTRIBUTION_REQUIREMENTS.md # ✅ PUBLISH - Attribution requirements
|
||||
├── USAGE_NOTIFICATION.md # ✅ PUBLISH - Usage notifications
|
||||
└── README.md # ✅ PUBLISH - This file
|
||||
```
|
||||
|
||||
### 🛡️ **PROTECTION MECHANISMS**
|
||||
|
||||
#### **1. Copyright:**
|
||||
- All files contain copyright by Tarabanov A.V.
|
||||
- Proprietary license used
|
||||
- Copying without permission prohibited
|
||||
|
||||
#### **2. Patent protection:**
|
||||
- Confidential documents in `patents/` folder
|
||||
- Folder added to `.gitignore`
|
||||
- Documents not published in repositories
|
||||
|
||||
#### **3. Licensing:**
|
||||
- Strict proprietary license
|
||||
- Mandatory attribution when using
|
||||
|
||||
#### **4. Monitoring:**
|
||||
- Code usage notifications
|
||||
- Attribution requirements
|
||||
|
||||
### 🎯 **USAGE RECOMMENDATIONS**
|
||||
|
||||
#### **For developers:**
|
||||
1. Review the main [LICENSE](../LICENSE) before use
|
||||
2. Follow [ATTRIBUTION_REQUIREMENTS.md](ATTRIBUTION_REQUIREMENTS.md)
|
||||
3. Notify the author according to [USAGE_NOTIFICATION.md](USAGE_NOTIFICATION.md)
|
||||
|
||||
#### **For use:**
|
||||
1. Respect copyright
|
||||
2. Indicate source when using
|
||||
3. Do not transfer to third parties
|
||||
|
||||
### 📞 **CONTACTS**
|
||||
|
||||
**Author:** Tarabanov Alexander Viktorovich
|
||||
**Email:** info@hb3-accelerator.com
|
||||
**Website:** https://hb3-accelerator.com
|
||||
**GitHub:** https://github.com/VC-HB3-Accelerator
|
||||
|
||||
### ⚖️ **LEGAL INFORMATION**
|
||||
|
||||
All documents in this section are protected by copyright. Unauthorized use, copying, or distribution is prohibited.
|
||||
|
||||
For usage permissions, contact the author at the provided contacts.
|
||||
|
||||
---
|
||||
|
||||
**Creation date:** 2024-2025
|
||||
**Last update:** 2024-2025
|
||||
**Status:** Actively maintained
|
||||
|
||||
131
legal-en/USAGE_NOTIFICATION.md
Normal file
131
legal-en/USAGE_NOTIFICATION.md
Normal file
@@ -0,0 +1,131 @@
|
||||
# Usage Notification Requirements
|
||||
|
||||
## Mandatory Notifications
|
||||
|
||||
When using code from the DLE (Digital Legal Entity) project in any form, including private repositories, you must notify the author.
|
||||
|
||||
## When Notification is Required
|
||||
|
||||
### Must notify:
|
||||
- Use in private repositories
|
||||
- Integration into existing systems
|
||||
- Creation of derivative works
|
||||
- Use for educational purposes
|
||||
|
||||
### Does not require notification:
|
||||
- Personal code study
|
||||
- Functionality testing
|
||||
- Capability demonstration
|
||||
|
||||
## Notification Form
|
||||
|
||||
### Email notification
|
||||
```
|
||||
Subject: DLE Usage Notification
|
||||
|
||||
Dear Tarabanov Alexander Viktorovich,
|
||||
|
||||
We notify you of the use of code from the DLE (Digital Legal Entity) project:
|
||||
|
||||
## Project Information:
|
||||
- Project name: [NAME]
|
||||
- Description: [DESCRIPTION]
|
||||
- Type of use: [EDUCATIONAL/PERSONAL]
|
||||
|
||||
## Used Components:
|
||||
- [LIST OF USED MODULES/FUNCTIONS]
|
||||
|
||||
## Contact Information:
|
||||
- Name: [FULL NAME]
|
||||
- Email: [EMAIL]
|
||||
- Organization: [ORGANIZATION]
|
||||
|
||||
## Usage Plans:
|
||||
- [DESCRIPTION OF PLANS]
|
||||
|
||||
Best regards,
|
||||
[FULL NAME]
|
||||
[EMAIL]
|
||||
```
|
||||
|
||||
### GitHub Issue
|
||||
Create an issue in the repository with the `usage-notification` tag:
|
||||
- Project description
|
||||
- List of used components
|
||||
- Contact information
|
||||
- Usage plans
|
||||
|
||||
## Notification Deadlines
|
||||
|
||||
- **Before starting use** - for commercial projects
|
||||
- **Within 30 days** - for educational projects
|
||||
- **Within 90 days** - for personal projects
|
||||
|
||||
## Consequences of Missing Notification
|
||||
|
||||
### License violation:
|
||||
- Automatic termination of usage rights
|
||||
- Possibility of requiring cessation of use
|
||||
- Potential legal consequences
|
||||
|
||||
### Exceptions:
|
||||
- Use for demonstration purposes
|
||||
- Short-term testing
|
||||
- Study of architecture and algorithms
|
||||
|
||||
## Usage Monitoring
|
||||
|
||||
### Automatic monitoring:
|
||||
- Tracking repository forks
|
||||
- Monitoring code mentions
|
||||
- Analysis of dependencies in npm/pip
|
||||
|
||||
### Manual monitoring:
|
||||
- Search on GitHub/GitLab
|
||||
- Monitoring technical blogs
|
||||
- Tracking conferences and presentations
|
||||
|
||||
## Contacts for Notifications
|
||||
|
||||
**Tarabanov Alexander Viktorovich**
|
||||
- **Email:** info@hb3-accelerator.com
|
||||
- **GitHub Issues:** [Create issue](https://github.com/VC-HB3-Accelerator/DLE/issues)
|
||||
- **Subject:** "DLE Usage Notification"
|
||||
|
||||
## Notification Templates
|
||||
|
||||
### For commercial use
|
||||
```
|
||||
Subject: Commercial DLE Usage Notification
|
||||
|
||||
We notify you of commercial use of DLE in the project [NAME].
|
||||
Licensing is required to continue use.
|
||||
|
||||
Project details are attached.
|
||||
```
|
||||
|
||||
### For educational use
|
||||
```
|
||||
Subject: Educational DLE Usage Notification
|
||||
|
||||
We notify you of the use of DLE for educational purposes.
|
||||
Project: [NAME]
|
||||
Educational institution: [NAME]
|
||||
|
||||
Permission is required for use in courses.
|
||||
```
|
||||
|
||||
### For personal use
|
||||
```
|
||||
Subject: Personal DLE Usage Notification
|
||||
|
||||
We notify you of personal use of DLE in the project [NAME].
|
||||
Usage: [DESCRIPTION]
|
||||
|
||||
Thank you for creating an excellent tool!
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
**© 2024-2025 Tarabanov Alexander Viktorovich. All rights reserved.**
|
||||
|
||||
625
legal-en/service-terms.md
Normal file
625
legal-en/service-terms.md
Normal file
@@ -0,0 +1,625 @@
|
||||
# Digital Legal Entity Purchase and Service Terms
|
||||
|
||||
## 1. Licensing Model
|
||||
|
||||
### 1.1. Basic Principles
|
||||
|
||||
- **📜 License Type**: Single type - **Perpetual License**
|
||||
- **⏳ Term**: Lifetime (no time limit)
|
||||
- **💰 Price**: Depends on **number of tokens** in the license (see section 2)
|
||||
- **🔄 Updates**: FREE for 5 years for license token holders
|
||||
- **🚫 Cancellation**: License cannot be canceled by the company
|
||||
- **⚖️ Service Terms**: Same for all licenses (difference only in number of votes)
|
||||
|
||||
### 1.2. Connection: Tokens ↔ Licenses
|
||||
|
||||
Each Digital Legal Entity license is linked to a **blockchain governance token**.
|
||||
|
||||
#### 📊 Token and Rights Ratio
|
||||
|
||||
| Parameter | For 1 token | For 10 tokens |
|
||||
|----------|-----------|--------------|
|
||||
| **Number of licenses** | 1 | 1 |
|
||||
| **Types of activity** | 1 | 1 |
|
||||
| **Votes in voting** | 1 | 10 |
|
||||
| **Service terms** | Same | Same |
|
||||
| **Influence on development** | 1 vote | 10 votes |
|
||||
|
||||
#### 🗳️ Community Voting
|
||||
|
||||
- **Vote = 1 token** (regardless of number of tokens per owner)
|
||||
- Voting occurs on **blockchain** (governance smart contract)
|
||||
- Tokens give voting rights for **new features and development priorities**
|
||||
- **Democracy**: Decisions are made by majority vote (51%+)
|
||||
|
||||
### 1.3. Type of Activity and Usage
|
||||
|
||||
- Each license is tied to **one type of activity/business**
|
||||
- Owner can redefine the type of activity, but can only maintain one at a time
|
||||
- For multiple types of activity, separate licenses and tokens are needed
|
||||
|
||||
---
|
||||
|
||||
## 2. License Types
|
||||
|
||||
### 2.1. License with 1 Token
|
||||
|
||||
- **💰 License price**: **$1,000 USDT** (one-time, perpetual, excluding taxes)
|
||||
- **🪙 Number of tokens**: **1 token** = **1 vote** in voting
|
||||
- **🗳️ Development influence**: Basic (1 vote for new features)
|
||||
|
||||
### 2.2. License with 10 Tokens
|
||||
|
||||
- **💰 License price**: **$10,000 USDT** (one-time, perpetual, excluding taxes)
|
||||
- **🪙 Number of tokens**: **10 tokens** = **10 votes** in voting
|
||||
- **🗳️ Development influence**: Enhanced (10 votes for new features)
|
||||
|
||||
### 2.3. Service Terms (same for all licenses)
|
||||
|
||||
**📧 All license token holders receive (within 5 years from on-chain transfer date):**
|
||||
|
||||
- ✅ All web application updates (free, 5 years)
|
||||
- ✅ Access to documentation and knowledge base
|
||||
- ✅ Technical support through the application: https://hb3-accelerator.com/
|
||||
- ✅ Response time: according to problem priority (see section 6.3)
|
||||
- ✅ 🤖 **24/7 AI Assistant** - built-in assistant for consultations
|
||||
- ✅ All integrations and deployment capabilities
|
||||
- ✅ Participation in voting for new features (by number of tokens)
|
||||
- ✅ Early access to beta features (if desired)
|
||||
- ✅ 99% uptime SLA guarantee
|
||||
- ✅ 🎓 **Online training and implementation sessions**:
|
||||
- Group online sessions (quarterly - 4 times per year)
|
||||
- Individual online sessions (on request)
|
||||
- Application setup training
|
||||
- Business integration strategies
|
||||
- ROI maximization consultations
|
||||
- Access to library of all session recordings
|
||||
|
||||
**⚖️ The only difference between licenses:**
|
||||
- Number of governance tokens (1 vs 10)
|
||||
- Number of votes in voting (1 vs 10)
|
||||
- Influence on prioritization of new feature development
|
||||
|
||||
---
|
||||
|
||||
## 3. Voting System and Product Development
|
||||
|
||||
### 3.1. How Voting Works
|
||||
|
||||
1. **Feature proposal**: Community proposes new features
|
||||
2. **Blockchain registration**: Voting is created in smart contract
|
||||
3. **Token holder voting**: Each token = 1 vote
|
||||
4. **Implementation**: If 51%+ tokens vote - feature goes into development
|
||||
|
||||
### 3.2. Voting Frequency
|
||||
|
||||
- **Voting window**: Open continuously (asynchronous voting)
|
||||
- **Quarterly analysis**: Each quarter votes are summed, decisions analyzed
|
||||
- **Prioritization**: Development follows priority (number of votes)
|
||||
|
||||
### 3.3. "Non-compliance Complaint" Mechanism
|
||||
|
||||
⚠️ **Refund mechanism (see section 4.2)**
|
||||
|
||||
### 3.4. 🌐 Web Application for Voting
|
||||
|
||||
**Address**: https://hb3-accelerator.com/
|
||||
|
||||
Token holders can:
|
||||
- 📋 Create proposals for new features and prioritization
|
||||
- 🗳️ Vote for or against proposals
|
||||
- 📊 View voting results
|
||||
- 📈 Track development status of approved features
|
||||
- ⏱️ See history of all blockchain votes
|
||||
|
||||
**Requirements:**
|
||||
- Wallet connection with tokens (MetaMask, WalletConnect, etc.)
|
||||
- Your number of tokens = number of votes
|
||||
|
||||
---
|
||||
|
||||
## 4. Refunds and Guarantees
|
||||
|
||||
### 4.1. General Terms
|
||||
|
||||
- **🔒 Principle**: License is perpetual - no refund (except exceptional cases)
|
||||
- **📋 Exception**: Special refund program (see section 4.2)
|
||||
|
||||
### 4.2. 70% Refund Program
|
||||
|
||||
**Refund Conditions:**
|
||||
|
||||
You can request a refund of **70% of the license cost** within **5 years** from purchase date, if:
|
||||
|
||||
1. ✋ **Complaint threshold**: Accumulated more than **51% negative votes**
|
||||
2. 📋 **Reason**: Complaints concern **lack of update releases**
|
||||
3. 🗳️ **Voting**: Complaints were **accepted through token holder voting mechanism on blockchain**
|
||||
4. ⏱️ **Deadline**: Request submitted within **5 years** from licensing date
|
||||
|
||||
**Refund Process:**
|
||||
|
||||
1. Request submitted to hb3-accelerator.com with blockchain proof attached
|
||||
2. Condition confirmation on smart contract (51%+ votes for refund)
|
||||
3. Refund of **70% of purchase amount** within 30 days
|
||||
|
||||
**Example:**
|
||||
- License with 10 tokens purchased for $10,000 USDT
|
||||
- Refund: $10,000 × 70% = $7,000 USDT
|
||||
- Valid until: 5 years from purchase date
|
||||
|
||||
### 4.3. Liability Limitations
|
||||
|
||||
✅ **What is guaranteed:**
|
||||
- License is perpetual (usage right not limited by term)
|
||||
- Updates and basic maintenance provided free for 5 years
|
||||
- Basic functionality remains available
|
||||
- Ability to vote for product development
|
||||
|
||||
❌ **NOT guaranteed:**
|
||||
- Specific new features (depends on voting)
|
||||
- Specific release schedule (depends on votes)
|
||||
- Support when modifying source code
|
||||
- Performance when exceeding limits
|
||||
|
||||
### 4.4. What the Author is NOT Liable For
|
||||
|
||||
❌ **Author is exempt from liability for:**
|
||||
|
||||
- **Lost profits** - income losses due to application failures
|
||||
- **Indirect damages** - secondary consequences of use
|
||||
- **Data loss** - user is responsible for backups
|
||||
- **Business interruption** - downtime and service disruptions
|
||||
- **Reputation loss** - reputational damage to business
|
||||
- **Special damages** - fines, penalties, sanctions, punitive payments
|
||||
- **Educational use** - without permission
|
||||
- **Use in accordance with terms** - if terms are violated
|
||||
|
||||
### 4.5. Maximum Liability
|
||||
|
||||
- **Liability limit**: Size of paid license (no more)
|
||||
- **Example**: If license cost $1,000 USDT, maximum refund $1,000 USDT
|
||||
- **Direct damages**: Only for direct contract violation
|
||||
- **Exceptions**: Indirect, special, or punitive damages not covered
|
||||
|
||||
### 4.6. User Responsibility
|
||||
|
||||
✅ **User is responsible for:**
|
||||
- Backing up own data (weekly minimum)
|
||||
- Use in accordance with license terms
|
||||
- Protecting wallet private keys and access
|
||||
- Compliance with all applicable laws and regulations
|
||||
- Updating application within reasonable timeframes
|
||||
- Checking compatibility with environment before updating
|
||||
|
||||
---
|
||||
|
||||
## 5. Updates and Maintenance
|
||||
|
||||
### 5.1. Free Updates and Basic Maintenance (5 years)
|
||||
|
||||
🎁 **Updates and basic maintenance are FREE for 5 years for license token holders (from on-chain token transfer date):**
|
||||
- Bug fixes
|
||||
- Performance improvements
|
||||
- New features (approved by voting)
|
||||
- Security updates
|
||||
|
||||
**Frequency:**
|
||||
- Security Patches: Immediately (upon discovery)
|
||||
- Regular Updates: Weekly (on Wednesdays) within 5-year period
|
||||
- Major Features: Based on voting results
|
||||
|
||||
### 5.2. 📥 Update Download Platform
|
||||
|
||||
**Address**: https://hb3-accelerator.com/
|
||||
|
||||
All license holders can:
|
||||
- ✅ Download all released application versions
|
||||
- 📝 Read detailed release notes
|
||||
- 📅 View scheduled update calendar
|
||||
- 🔄 Receive automatic notifications about new versions
|
||||
- 📚 Study migration documentation between versions
|
||||
- 🪵 See change logs
|
||||
|
||||
**Access Requirements:**
|
||||
- Wallet connection with license token on address
|
||||
- License token must be on address at time of update request
|
||||
|
||||
## 6. Technical Support
|
||||
|
||||
### 6.1. Unified Support Portal
|
||||
|
||||
**All types of support available ONLY through the application:**
|
||||
|
||||
🌐 **https://hb3-accelerator.com/**
|
||||
|
||||
- 📝 Creating and tracking support tickets
|
||||
- 💬 Direct chat with support team
|
||||
- 📊 History of all requests
|
||||
- 📅 Response time tracking
|
||||
|
||||
### 6.2. Available Support Channels
|
||||
|
||||
**All license holders have access to:**
|
||||
|
||||
| Function | Availability |
|
||||
|--------|-------------|
|
||||
| 🌐 Support portal | ✅ All licenses |
|
||||
| 💬 Chat with support team | ✅ All licenses |
|
||||
| 🤖 24/7 AI assistant | ✅ All licenses |
|
||||
| 🎓 Online training sessions | ✅ Group + individual (all licenses) |
|
||||
| 📚 Recording library | ✅ All licenses |
|
||||
| 📧 Email support | ✅ All licenses |
|
||||
|
||||
### 6.3. Problem Classification and SLA
|
||||
|
||||
**Response time depends on problem priority, not license type:**
|
||||
|
||||
| Priority | Description | SLA (first response time) |
|
||||
|-----------|---------|-----|
|
||||
| 🔴 Critical | Service completely unavailable | 4 hours |
|
||||
| 🟠 High | Loss of main function | 8 hours |
|
||||
| 🟡 Medium | Performance degradation | 24 hours |
|
||||
| 🟢 Low | Questions, documentation | 48 hours |
|
||||
|
||||
### 6.4. Support Request Process
|
||||
|
||||
1. Log into application: https://hb3-accelerator.com/
|
||||
2. Go to "Proposals" section
|
||||
3. Create new ticket with problem description
|
||||
4. Indicate priority (system automatically classifies)
|
||||
5. Attach logs, screenshots, and reproduction steps
|
||||
6. Receive ticket number for tracking
|
||||
7. Wait for response according to SLA (by problem priority)
|
||||
|
||||
### 6.5. 🎓 Online Training and Implementation Sessions
|
||||
|
||||
**All license holders** (regardless of type) receive access to **online training sessions**, where experts help maximize the effective use of Digital Legal Entity.
|
||||
|
||||
#### Group Online Sessions
|
||||
|
||||
**📅 Frequency**: Quarterly (4 times per year)
|
||||
|
||||
**📚 Training Topics:**
|
||||
- 🔧 **Application Setup** - step-by-step guide for initial configuration
|
||||
- 🏢 **Business Integration** - how to integrate DLE into existing business processes
|
||||
- 💰 **ROI Maximization** - best practices for using features
|
||||
- 📊 **Analytics and Reporting** - how to use data for decision-making
|
||||
- 🔐 **Security and Compliance** - security setup and regulatory compliance
|
||||
- 🗳️ **Voting and Governance** - how to effectively use your tokens
|
||||
|
||||
**⏱️ Format:**
|
||||
- Duration: 1-2 hours
|
||||
- Webinar with presentation and demonstration
|
||||
- Q&A session at end (30-40 minutes)
|
||||
- Recording available after session
|
||||
|
||||
**👥 Participation Format:**
|
||||
- Online meetings
|
||||
- Chat for questions during session
|
||||
- Ability to ask questions in advance
|
||||
|
||||
#### Individual Online Sessions
|
||||
|
||||
**Available for all licenses**
|
||||
|
||||
**📅 Frequency**: (on request)
|
||||
|
||||
**🎯 Personalized Topics:**
|
||||
- 🏗️ **Individual Architecture** - setup for your business specifics
|
||||
- 📈 **Integration Strategy** - step-by-step DLE integration plan
|
||||
- 💡 **ROI Optimization** - how to get maximum return on investment
|
||||
- 🔄 **Data Migration** - transfer from existing systems
|
||||
- 🛠️ **Customization and Integrations** - setup for your requirements
|
||||
- 📊 **Efficiency Analysis** - metrics and improvements overview
|
||||
- 🗳️ **Voting Strategy** - how to use your tokens to influence development
|
||||
|
||||
**⏱️ Format:**
|
||||
- Duration: 1-2 hours (as needed)
|
||||
- Individual video meeting
|
||||
- Personal expert familiar with your case
|
||||
- Session recording for your team
|
||||
- Materials and documentation after session
|
||||
- Ability to invite your team (up to 10 people)
|
||||
|
||||
#### Registration for Online Sessions
|
||||
|
||||
**How to register:**
|
||||
1. Log into application: https://hb3-accelerator.com/
|
||||
2. Go to group
|
||||
3. Select available session from calendar (group or individual)
|
||||
4. Click "Register" and receive connection link
|
||||
|
||||
#### Recording Library
|
||||
|
||||
All past online sessions are available in the library for all license holders:
|
||||
|
||||
**📚 Address**: https://hb3-accelerator.com/
|
||||
|
||||
- 🎥 Video recordings of all group sessions
|
||||
- 📄 Presentations and materials
|
||||
- 💬 Q&A session transcripts
|
||||
- 🔍 Search by topics and keywords
|
||||
- 📥 Download materials for offline viewing
|
||||
|
||||
---
|
||||
|
||||
## 7. Terms of Use
|
||||
|
||||
### 7.1. Permissible Use
|
||||
|
||||
✅ **Permitted:**
|
||||
- Use for managing own business
|
||||
- Deployment on own infrastructure
|
||||
- Use of selected type of activity (1 type per license)
|
||||
- Data backup
|
||||
- Local configuration modification
|
||||
- Voting for new feature development
|
||||
- License transfer to heirs (for perpetual license)
|
||||
|
||||
❌ **Prohibited:**
|
||||
- Resale or sublicensing
|
||||
- Use of more than one type of activity with one license
|
||||
- Reverse engineering and source code modification
|
||||
- Removal of copyright and license notices
|
||||
- Shared use between independent organizations
|
||||
- Educational use without permission
|
||||
- SaaS deployment based on application
|
||||
---
|
||||
|
||||
## 8. Security and Privacy
|
||||
|
||||
### 8.1. Data Encryption
|
||||
|
||||
- **TLS 1.3**: For all connections
|
||||
- **AES-256**: For critical data in storage
|
||||
- **Key Management**: User controls encryption keys
|
||||
|
||||
### 8.2. Standards Compliance
|
||||
|
||||
- **GDPR**: Compliance (with DPA)
|
||||
- **SOC 2 Type II**: Certification obtained
|
||||
- **ISO 27001**: Planned
|
||||
---
|
||||
|
||||
## 9. License Management Smart Contract
|
||||
|
||||
### 9.1. Management System Architecture
|
||||
|
||||
DLE uses a **smart contract** on blockchain for license management and voting:
|
||||
|
||||
- **ERC20 tokens**: Each license is represented by governance tokens (1 or 10)
|
||||
- **ERC20Votes**: Built-in voting system through smart contract
|
||||
- **ERC20Permit**: Signatures for token transfers without gas fees (meta-transactions)
|
||||
- **Multi-chain architecture**: Support for voting and execution in multiple networks simultaneously
|
||||
|
||||
### 9.2. Proposal and Voting System
|
||||
|
||||
**Creating a proposal:**
|
||||
- Only token holders (licenses) can create proposals
|
||||
- Description: Text of proposal for new feature
|
||||
- Voting duration: From 1 hour to 30 days
|
||||
- Target networks: Can be executed in one or multiple networks simultaneously
|
||||
|
||||
**Voting Process:**
|
||||
1. Proposal is created and receives unique ID
|
||||
2. Token holders vote "For" or "Against"
|
||||
3. Each token = 1 vote (regardless of holder)
|
||||
4. Quorum is checked at deadline or when 51%+ is reached
|
||||
|
||||
**Proposal Execution:**
|
||||
- If "For" > "Against" AND quorum reached → proposal accepted
|
||||
- Execution can be through:
|
||||
- Direct call (in voting chain)
|
||||
- Through signatures (in other networks)
|
||||
|
||||
|
||||
### 9.3. Security and Limitations
|
||||
|
||||
✅ **Reentrancy Protection** - ReentrancyGuard in all critical operations
|
||||
✅ **Direct Transfer Blocking** - tokens transferred only through governance
|
||||
✅ **Vote Snapshots** - past values used to protect against flash-loans
|
||||
✅ **EIP-712 Signatures** - support for contract wallets and meta-transactions
|
||||
✅ **Operation Validation** - all parameters checked before execution
|
||||
|
||||
### 9.4. License Transfer
|
||||
|
||||
- License = governance tokens tied to wallet address
|
||||
- Transfer: Simply transfer tokens to new address (possible through governance)
|
||||
- Rights: New owner automatically receives voting rights
|
||||
|
||||
---
|
||||
|
||||
## 10. Contact Information and Support
|
||||
|
||||
### 📞 Support Service
|
||||
|
||||
🌐 **ONLY through application**: https://hb3-accelerator.com/
|
||||
- **GitHub**: https://github.com/VC-HB3-Accelerator/DLE
|
||||
|
||||
### ⚖️ Legal Information
|
||||
- **Legal Status**: Proprietary Software (see [LICENSE](../LICENSE))
|
||||
- **Full Documentation**: [legal-en/README.md](README.md)
|
||||
|
||||
---
|
||||
|
||||
## 11. Terms Change Policy
|
||||
|
||||
### 11.1. Changes for New Licenses
|
||||
|
||||
- We may change service terms **for new purchases**
|
||||
- Notification: 60 days before taking effect
|
||||
- Application: Only for new licenses purchased after change date
|
||||
|
||||
### 11.2. Protection of Existing Licenses
|
||||
|
||||
- **Guarantee**: Your license terms **DO NOT change** after purchase
|
||||
- **Fixed Rights**: Remain forever with current terms
|
||||
- **Backward Compatibility**: Old terms are supported
|
||||
---
|
||||
|
||||
**© 2024-2025 Tarabanov Alexander Viktorovich. All rights reserved.**
|
||||
|
||||
**Last update**: October 2025
|
||||
|
||||
### 🔐 Blockchain Note
|
||||
|
||||
This license management model uses blockchain to ensure **transparency**, **democracy**, and **immutability** of the product development voting process. All token holders have equal votes and control over the future development of Digital Legal Entity.
|
||||
|
||||
## 5. Pricing and Payment Terms
|
||||
|
||||
### 5.1. Payment Methods
|
||||
|
||||
- 💵 **Cryptocurrency (USDT)**: Directly to addresses of authorized partner companies
|
||||
- 💳 **Local Currency Transfer**: Equivalent in buyer's country local currency
|
||||
- 🏦 **Bank Transfer**: Through authorized dealers
|
||||
- 💳 **Credit Cards**: Through partner payment systems
|
||||
|
||||
### 5.2. Prices and Taxes
|
||||
|
||||
#### ⚠️ IMPORTANT: All prices are EXCLUDING TAXES
|
||||
|
||||
**Prices in USDT:**
|
||||
- **License with 1 token**: $1,000 USDT (excluding taxes)
|
||||
- **License with 10 tokens**: $10,000 USDT (excluding taxes)
|
||||
|
||||
**Equivalent in other currencies (examples, depends on exchange rate):**
|
||||
- EUR: €899 (1 token) or €8,991 (10 tokens)
|
||||
- RUB: ₽99,000 (1 token) or ₽990,000 (10 tokens)
|
||||
- Other currencies at current exchange rate at time of payment
|
||||
|
||||
#### Taxes - Buyer's Responsibility
|
||||
|
||||
Buyer is independently responsible for paying all applicable taxes:
|
||||
- **VAT** - in EU countries and others (usually 15-25%)
|
||||
- **Sales Tax** - in USA and other countries
|
||||
- **Income Tax** - depends on tax status
|
||||
- **Customs Duties** - when importing to certain countries
|
||||
- **Any other taxes** - depending on local jurisdiction
|
||||
|
||||
**Tax rate is determined by:**
|
||||
- Buyer's jurisdiction (country, city, region)
|
||||
- Tax status (individual, sole proprietor, LLC, JSC, etc.)
|
||||
- International trade specifics
|
||||
|
||||
#### 💸 Payment Fees - FULLY ON BUYER
|
||||
|
||||
All fees for transfers, conversion, and payment processing are borne by the **BUYER**:
|
||||
|
||||
**🌍 Currency Conversion Fees:**
|
||||
- Bank/payment system commission: 1-5% of amount
|
||||
- Inter-market spread commission (rate): +1-2% above market
|
||||
- Hidden conversion fees: often 2-3%
|
||||
|
||||
**🏦 Bank Transfer Fees:**
|
||||
- **SWIFT transfers** (international): $10-50+ per transaction
|
||||
- **SEPA transfers** (within EU): €0-3 or free
|
||||
- **Other systems** (Wise, Payoneer): 1-2.5% + fixed fee
|
||||
- **Recipient side commission**: additional $0-50 (may be)
|
||||
|
||||
**⛓️ Blockchain Fees (cryptocurrency - USDT):**
|
||||
- **Gas fees (network commission)**:
|
||||
- Ethereum: $1-50+ depending on load
|
||||
- Polygon: $0.01-1
|
||||
- BSC: $0.10-5
|
||||
- Other networks: varies
|
||||
- **Wallet commission**: 0-2% (if payment provider used)
|
||||
- **Exchange/platform commission**: 1-3% for fiat to USDT exchange
|
||||
|
||||
**💳 Payment System Fees (credit cards):**
|
||||
- **Processing commission**: 2-5% of amount
|
||||
- **Currency conversion commission**: 1-3% (if payment in other currency)
|
||||
- **Issuing bank commission**: 0-2% (rare, but may be)
|
||||
- **Dynamic Currency Conversion (DCC) commission**: 2-4% (if available)
|
||||
|
||||
**Real Examples of Total Costs:**
|
||||
|
||||
| Option | Stated Price | Fees | Total to Pay |
|
||||
|---------|-----------------|----------|-----------------|
|
||||
| USDT directly | $1,000 | $15-80 (gas + fees) | $1,015-1,080 |
|
||||
| SWIFT transfer USD | $1,000 | $25-80 (bank fees) | $1,025-1,080 |
|
||||
| Card in EUR | €899 | €30-45 (conversion + fees) | €929-944 |
|
||||
| Crypto exchange | $1,000 | $30-150 (all fees) | $1,030-1,150 |
|
||||
|
||||
**💡 Tip:** Choose payment method with minimum fees!
|
||||
|
||||
**⚠️ Total Amount = License Price + Taxes + All Transfer and Conversion Fees**
|
||||
|
||||
### 5.3. Authorized Sellers and Dealers
|
||||
|
||||
#### Official Sales Terms
|
||||
|
||||
Licenses may be sold **ONLY through companies** that have **official written permission from the author**:
|
||||
|
||||
**Requirements for authorized seller:**
|
||||
- ✅ Legal entity (LLC, JSC, sole proprietor, corporation, etc.)
|
||||
- ✅ Signed contract/agreement for dealership with author
|
||||
- ✅ Inclusion in official list at https://hb3-accelerator.com/
|
||||
- ✅ Compliance with all licensing terms
|
||||
- ✅ Record keeping of all sales
|
||||
- ✅ Timely transfer of funds to author
|
||||
|
||||
**Payment Structure Through Dealer:**
|
||||
- 💰 Buyer pays → Authorized seller
|
||||
- 🤝 Seller receives commission (% determined by contract)
|
||||
- 📤 Remainder transferred to author within established terms
|
||||
- 📋 All payments documented officially and tracked
|
||||
|
||||
#### Official Seller for Clients from Russian Federation
|
||||
|
||||
For clients from the Russian Federation, the official seller of licenses is **Limited Liability Company "ERAITI" (LLC "ERAITI")** with the following details:
|
||||
- **OGRN:** 1222600014383
|
||||
- **INN:** 2636220809
|
||||
- **Address:** 355007, Stavropol Territory, Stavropol, Burmistrova St., 65B, room 2
|
||||
- **Contacts:** 18900@эрайти.рф, +7 (968) 269-92-64
|
||||
|
||||
LLC "ERAITI" has official rights to sell and support Digital Legal Entity licenses in the Russian Federation.
|
||||
|
||||
#### Direct Purchase from Author
|
||||
|
||||
Can be purchased directly from author without intermediaries:
|
||||
|
||||
- 📧 **Email**: info@hb3-accelerator.com
|
||||
- 🌐 **Website**: https://hb3-accelerator.com
|
||||
- 🐙 **GitHub**: https://github.com/VC-HB3-Accelerator
|
||||
|
||||
|
||||
### 5.4. Payment Process and Confirmation
|
||||
|
||||
1. **Seller Selection**: Authorized dealer or directly from author
|
||||
2. **Price Agreement**: In USDT or equivalent local currency
|
||||
3. **Receiving Details**: From seller or author
|
||||
4. **Sending Payment**: Cryptocurrency, bank transfer, or other method
|
||||
5. **Confirmation**: Receiving payment number and payment document
|
||||
6. **License Activation**: Receiving NFT token or portal access
|
||||
|
||||
### 5.5. Refund and Claims
|
||||
|
||||
- **Claim Period**: 30 days from payment date
|
||||
- **Process**: Contact seller or author with payment confirmation
|
||||
- **Refund**: Maximum 70% of amount in accordance with refund program
|
||||
- **Refund Reasons**:
|
||||
- Calculation error
|
||||
- Double payment
|
||||
- Other justified reasons
|
||||
|
||||
---
|
||||
|
||||
## 📚 Additional Documentation
|
||||
|
||||
### Explore DLE Capabilities
|
||||
- 🤖 **[AI Assistant](../docs-en/ai-assistant.md)** - second pilot for team, frees time for strategy
|
||||
- 💼 **[Blockchain for Business](../docs-en/blockchain-for-business.md)** - asset tokenization and business solutions
|
||||
- 🛡️ **[DLE Security](../docs-en/security.md)** - multi-level protection for your business
|
||||
|
||||
### Technical Documentation
|
||||
- 🔗 **[Blockchain Technical Documentation](../docs-en/blockchain-integration-technical.md)** - for developers
|
||||
- 🔧 **[Installation Instructions](../docs-en/setup-instruction.md)** - step-by-step setup
|
||||
- 📝 **[Application Description](../docs-en/application-description.md)** - functionality overview
|
||||
- 📋 **[FAQ](../docs-en/FAQ.md)** - frequently asked questions
|
||||
|
||||
### Contacts and Support
|
||||
- 📧 **Email**: info@hb3-accelerator.com
|
||||
- 🌐 **Website**: https://hb3-accelerator.com
|
||||
- 💬 **Support Chat**: https://hb3-accelerator.com/
|
||||
- 🐙 **GitHub**: https://github.com/VC-HB3-Accelerator
|
||||
|
||||
Reference in New Issue
Block a user