Components and Base Services of the Bitbon System

1. The terms used in this Appendix shall be interpreted in accordance with the definitions given in the Appendix to the Bitbon System Public Contract Terms and Definitions in the Bitbon System SocialNetwork.

1. The subject of this Appendix is relations between Bitbon System Users[i] (hereinafter — User) that arise when using the functionalities of the Bitbon System components (hereinafter — component) and the Bitbon System base services (hereinafter — base service).

2. This Appendix establishes the list of the main components and base services.

1. This Appendix consists of the preamble, sections, chapters, which consist of articles that include parts and paragraphs. The structure of the Appendix includes links and references to the Provisions of the Bitbon System Public Contract, as well as to separate Appendices, which are an integral part of the Bitbon System Public Contract.

1. Component is an application or a group of applications being architecture elements of the Bitbon System infrastructure[i], which interact with each other ensuring the operation of base services and services of Users[i].

2. Access of the User to components is provided through a Bitbon System personal account (hereinafter — personal account).

1. The main components of the Bitbon System include:

• personal account;
• corporate account;
• Assetbox;
• capitalization fund of the Bitbon System (hereinafter — capitalization fund);
• providing fund of the Bitbon System (hereinafter — providing fund);
• meta-asset protocol form;
• infrastructure fee fund of the Bitbon System (hereinafter — infrastructure fee fund);
• account certificates;
• digital asset unit transformation;
• User advertisements;
• Safebox;
• escrow;
• tokenization of assets;
• contributing;
• obventing;
• documents and document workflow;
• Bitbon System Integration.

2. The list of the main components is not exhaustive and will be supplemented as new components and their functionalities are implemented in accordance with the Bitbon System Roadmap.

3. The Bitbon System has other components, which the User does not directly interact with, but which are an integral part of the Bitbon System infrastructure.

1. “Personal account” component is created as a result of the registration of an entity in the Bitbon System in order to get the rights of the User.

2. The “Personal account” component functioning and special aspects of its use by the User are regulated by the Appendix Bitbon System Account.

1. “Corporate account” component allows the User to represent the interests of a commercial or non-profit organization in the Bitbon System.

2. The “Corporate account” component functioning and special aspects of its use by the User are regulated by the Appendix Bitbon System Account.

1. “Assetbox” component is intended for registration of Bitbon units[i] in the Bitbon System and provides access to the storage address of distributed ledger token accounting units[i] in the distributed ledger token accounting system[i].

2. The functionalities of Assetboxes allow Users to interact during circulation of Bitbon units[i] in the Bitbon System[i].

3. The User can additionally assign the following to his/her Assetbox:

3.1. Alias as a unique name to make it easier for other Users to identify the Assetbox.

3.2. Icon for visual identification.

3.3. Info as additional information (comment) for an Assetbox.

4. When an Assetbox is created, a hash[i] allowing the User to identify such Assetbox in the Bitbon System is assigned.

1. “Bitbon System capitalization fund” component provides a mechanism that allows Bitbon System Participants[i] to develop the Bitbon System in the interests of all its Users.

2. The capitalization fund is managed by Bitbon System Participants.

3. The terms of the “Bitbon System capitalization fund” component functioning are established by this Appendix, the Appendix Funds of the Bitbon System and the Bitbon System Public Contract.

1. “Providing fund of the Bitbon System” component accumulates Bitbon units[i] received from the Bitbon System infrastructure fee fund[i] and Bitbon units that may also be received from the Bitbon System capitalization fund[i], and distributes them among Bitbon System Providers[i] based on the role of a Provider: Registrator[i] and/or Partitioner[i].

2. The terms of the “Providing fund of the Bitbon System” component functioning are established by this Appendix, the Appendix “Funds of the Bitbon System” and the Bitbon System Public Contract.

1. “Meta-asset protocol form” component is a special form for creating a meta-asset[i] that contains standardized parameters for each type of a meta-asset, determining which the User establishes the terms and conditions for using the meta-asset as well as its attributes and properties during tokenization of an initial asset[i].

2. The “Meta-asset protocol form” component and its functionalities are implemented in accordance with the Bitbon System Roadmap.

1. “Infrastructure fee fund of the Bitbon System” component accumulates Bitbon units received from infrastructure fees for the purpose of their further distribution according to the procedure established by the Appendix to the Bitbon System Public Contract Service Fees in the Bitbon System: the Procedure for Their Deduction and Distribution.

2. The terms of the “Infrastructure fee fund of the Bitbon System” component functioning are established by this Appendix, the Appendix “Funds of the Bitbon System” and the Bitbon System Public Contract.

1. “Account certificates” component allows automating registration of the User’s account certificates[i] required to provide such a User with access to certain functionalities of the Bitbon System infrastructure as well as allows managing the User’s account certificates.

2. The terms of the “Account certificates” component functioning are established by this Appendix and the Appendix Bitbon System Account.

1. “Digital asset unit transformation” component allows implementing the process of direct and reverse transformation of digital asset units into other types of tokenized assets[i] (monoassets[i] or polyassets[i]) outside the Bitbon System.

2. The terms of the “Digital asset unit transformation” component functioning and its functionalities are implemented in accordance with the Bitbon System Roadmap.

1. “User advertisements” component allows Users to create and publish advertisements for exchange of tokenized asset units.

2. The terms of the “User advertisements” component functioning and its functionalities are implemented in accordance with the Bitbon System Roadmap.

1. “Safebox” component allows storing and managing tokenized asset units units with advanced access authentication capabilities.

2. The terms of the “Safebox” component functioning and its functionalities are implemented in accordance with the Bitbon System Roadmap.

1. “Escrow” component ensures accounting for deferred payment in transactions by means of tokenized assets[i].

2. The “Escrow” component and its functionalities are implemented in accordance with the Bitbon System Roadmap.

1. “Asset tokenization” component provides access to tokenization of an initial asset[i] in order to implement methods for accounting of property or personal non-property rights to an initial asset[i] for tokenized assets.

2. The “Asset tokenization” component and its functionalities are implemented in accordance with the Bitbon System Roadmap.

1. “Contributing” component provides implementation of crowdfunding options and commercial projects using the functionalities of the Bitbon System infrastructure.

2. The “Contributing” component and its functionalities are implemented in accordance with the Bitbon System Roadmap.

1. “Obventing” component provides access to the distribution of obvents[i] through tokenized asset units, the protocol[i] of which envisions obvents.

2. The “Obventing” component and its functionalities are implemented in accordance with the Bitbon System Roadmap.

1. “Documents and document workflow” component allows Users to create an information resource[i] for conducting commercial and non-commercial activities outside or in the Bitbon System, including for creation of a meta-asset[i].

2. The “Documents and document workflow” component as well as its functionalities are implemented in accordance with the Bitbon System Roadmap.

1. “Bitbon System Integration (BSI)” component enables information platforms, applications and digital systems of Users to integrate and interact with the Bitbon System infrastructure.

2. The “Bitbon System Integration” component and its functionalities are implemented in accordance with the Bitbon System Roadmap.

1. Base service is a software complex that is an architecture element of the Bitbon System infrastructure and provides Users with access to certain functionalities of this infrastructure in order for Users to realize property and personal non-property relations using tokenized assets.

1. Base services of the Bitbon System include:

• One Space service;
• Meta-asset segregation service;
• Bonpay service;
• User profile data service;
• channel service;
• Bon Transfer service;
• providing service;
• Exchange Request for Bitbon (ERBB) service;
• Bitbon System Authentication service.

2. The list of base services is not exhaustive and will be supplemented as new base services and their functionalities are implemented in accordance with the Bitbon System Roadmap.

1. The One Space service is part of the Bitbon System infrastructure and ensures interaction between Users.

2. The functionalities of the One Space service are regulated by the Appendix to the Bitbon System Public Contract One Space Base Service.

1. The meta-asset segregation[i] service allows managing usage of meta-assets based on the terms and conditions established in the meta-asset protocols and services of the Bitbon System.

2. The meta-asset segregation service and its functionalities are implemented in accordance with the Bitbon System Roadmap.

1. The Bonpay service allows the User to make purchases in retail outlets or on the Internet using tokenized asset units, generate invoices for deferred payment, as well as keep financial records of commercial activities.

2. The Bonpay service and its functionalities are implemented in accordance with the Bitbon System Roadmap.

1. The User profile data service allows the User to manage access to his/her personal data using the Bitbon System infrastructure, namely to determine the amount of personal data to which such a User is ready to provide access, the range of entities to whom he/she is ready to provide such data and the possibility of further use of personal data.

2. The User profile data service and its functionalities are implemented in accordance with the Bitbon System Roadmap.

1. The channel service provides tokenized asset owners with tools for publishing news about events related to the use of a particular tokenized asset in order to inform the owners of tokenized asset units, manage the news and communicate with other Users.

2. The channel service and its functionalities are implemented in accordance with the Bitbon System Roadmap.

1. The Bon Transfer service ensures the transfer of Bitbon units[i] owned by Users as a way to conclude and make deals using Bitbon units.

2. The Bon Transfer service and its functionalities are implemented in accordance with the Bitbon System Roadmap.

1. The providing service allows ensuring the economic, legal and technological decentralization of the Bitbon System by providing a certain number of Bitbon units owned by the User being a Registrator[i] and/or resources of proper quality being a Partitioner[i].

2. The providing service and its functionalities are implemented in accordance with the Bitbon System Roadmap.

1. The Exchange Request for Bitbon (ERBB) service allows transforming Bitbon units into ERBB units (distributed ledger token of the ERC20 standard in the Ethereum blockchain network) as well as transforming ERBB units into Bitbon units.

2. The functionalities of the Exchange Request for Bitbon (ERBB) service are regulated by the Appendix to the Bitbon System Public Contract The ERBB Service.

1. The Bitbon System Authentication service is intended to authenticate the Bitbon System User in other services of the Bitbon System using an account of this User.

2. The Bitbon System Authentication service and its functionalities are implemented in accordance with the Bitbon System Roadmap.

1. Amendments and/or additions to this Appendix may be made solely under the rules stipulated by the Appendix to the Bitbon System Public Contract MakingAmendments and/or Additions to the Bitbon System PublicContract.

2. If there is any discrepancy between various forms (printed, electronic, etc.) of this Appendix, its electronic version published on the official information resources of the Bitbon System[i] shall be deemed official.

3. This Appendix is translated into other languages only for convenience of Users. In case of differences in understanding and/or interpretation of this Appendix, the Russian version shall prevail.

4. Only the Bitbon System Operators[i] are entitled to give an official explanation of this Appendix.

5. In accordance with Provision 2 of the Bitbon System Public Contract, this Appendix is an integral part of the Bitbon System Public Contract and comes into force after its publication on the official information resources of the Bitbon System.

6. In accordance with paragraph 3 of Provision 2 of the Bitbon System Public Contract, amendments and/or additions may be made to this Appendix only if such amendments and/or additions do not contradict the Provisions of the Bitbon System Public Contract and Appendices, which are an integral part of the Bitbon System Public Contract. Amendments and/or additions made to this Appendix shall be published on the official information resources of the Bitbon System and come into force in accordance with the Appendix to the Bitbon System Public Contract “Making Amendments and/or Additions to the Bitbon System Public Contract”.

1. The Bitbon System Operators strive to maintain uninterrupted operation of the components and base services. By using the Bitbon System infrastructure, the User agrees that there is a possibility of disruptions in the operation of the Bitbon System infrastructure, which may lead to a temporary interruption of the operation and limitation of access to the functionalities of the components and/or base services in whole or in any part.

2. The User shall not use the components and base services if he/she does not accept the terms and conditions established by the Bitbon System Public Contract in whole or in any part.

3. The use of the Bitbon System infrastructure shall mean agreement of the User with the terms and conditions established by the Bitbon System Public Contract.