Alex
9fc4c62052
Root README files removed from Docs; navigation now points to the org profile page. Co-authored-by: Cursor <cursoragent@cursor.com>
3.6 KiB
Project Roles: VC HB3 Accelerator and Contributor
This document describes not the team composition, but the role distribution in the demonstration contour and in the pilot logic.
1. Current status
The project is currently at the demonstration prototype stage:
- the
DLEoperating system and smart contracts are used on a test network; - the OS supports smart contracts with identifiers set by the regulator;
- for a specific pilot, identifier lists and tagging rules approved by the regulator are not yet agreed or fixed in the pilot regulation;
- integration of regulator data sources is handled under separate agreement and a contractual model.
In other words, the current contour shows how the mechanics work, but is not yet an industrial regulatory contour.
2. Role of VC HB3 Accelerator
In this model, VC HB3 Accelerator acts as an organizing project that uses the Digital Legal Entity (DLE) operating system to organize commercial activity with sandbox participants.
In this role, VC HB3 Accelerator:
- runs the accelerator program for participants;
- organizes the interaction rules for participants in the pilot;
- receives participants’ smart-contract addresses to configure access rights to service and resources;
- forms a shared interaction contour among business, contractors, and the regulatory scenario.
3. Role of the contributor
A contributor is a local organization in a specific jurisdiction that provides the operator contour on its territory.
The contributor:
- enters contractual relations with the OS author-developer in the relevant state;
- initiates the pilot for business and the regulator;
- gathers participants and helps launch the demonstration contour;
- provides local installation, configuration, and support of
DLE; - may act as an authorized license seller on its territory.
The contributor’s main task at the demonstration stage is to bring the pilot to agreement with the regulator in order to later move to the industrial contour.
4. Contributor in the Russian Federation
In the Russian Federation, the contributor is OOO “ERAYTI”.
In the current contour, OOO “ERAYTI”:
- uses its own installation of the
Digital Legal Entity (DLE)operating system; - provides participant onboarding and configuration of access rights and service;
- acts as an authorized license seller in the Russian Federation under a contractual model with the rights holder.
This relates specifically to the demonstration contour used to prepare the pilot and negotiate the transition to the next stage.
5. What changes after agreement with the regulator
After receiving smart-contract tagging from the regulator, the demonstration contour can move to the industrial stage.
At that stage:
- contributors form an industrial smart contract with regulator tagging for their jurisdiction;
- the selected jurisdiction becomes the launch point for the industrial contour;
- the operating contour is built not as a mechanics demonstration, but as an agreed interaction model with the regulator.
What not to confuse
team.md— who builds the project and how work is organized.roles-hb3-contributor.md— who is responsible for what in the pilot and demonstration contour.
See also
Last updated: 2026-03-30