1. These Regulations set out the regulations of providing the Service of making the platform

available for storing, sending and receiving specified tokens, but not only limited to those

functionalities, as described in details below by users via the Wallet available at

https://mrbob.io/whitelist/public/, as well as the rights and obligations of the Provider and the User

using the Service, and also define the principles of liability and the course of the complaint

process.

2. The entity providing the Service to the User is MRBOB  IT SERVICES L.L.C. with its registered

office in Bur Dubai, Dubai Investment Park 1, 00-000 Dubai, United Arab Emirates, entered

into the Commercial Register kept by Ministry of Economy (Dubai Economy and Tourism)

under the registry number: 1695648.

3. A prerequisite for using the Services provided via the Wallet is reading the Regulations,

accepting them, and following the rules specified therein. The User is also obliged to observe

the Privacy Policy published on https://mrbob.io/whitelist/public/sign-up.

4. The Wallet Operator reserves the right to update or amend the Regulations at any time. The

User is obliged to keep up to date with the content of the Regulations published on the website

available at https://mrbob.io/whitelist/public/sign-up .

-2-

1. The following terms are defined in these Regulations:

a. Service - the Service concerning offering a safe storage and trading space for MR BOB COINS,

and other tokens selected by the Operator but limited to those based on the ERC20 standard.

available at https://mrbob.io/whitelist/public/, on Regulations specified in the Regulations, provided

after registration of the User's account by means of a form available at,

https://mrbob.io/whitelist/public/sign-up which is considered the moment of agreeing with the User

and the Wallet Operator for the provision of a free of charge service provided via the Wallet;

b. User - a user who has registered an account at https://mrbob.io/whitelist/public/sign-up the mobile

application made available by the Wallet Operator, being a natural person with the full legal

capacity to perform acts in law, a legal person or an organisational unit without legal

personality, but granted a legal capacity under the law;

d. Wallet Operator/Provider - MRBOB  IT SERVICES L.L.C. with its registered office in Bur Dubai,

Dubai Investment Park 1, 00-000 Dubai, United Arab Emirates, entered into the Commercial

Register kept by Ministry of Economy (Dubai Economy and Tourism) under the registry

number: 1695648;

e. Wallet - the platform made available to the User by the Wallet Operator at

https://mrbob.io/whitelist/public/.

-3-

1. The User wishing to use the Wallet functionalities is obliged to register via the registration form

available at https://mrbob.io/whitelist/public/sign-in. Completion of the registration form requires:

a. Providing the User's e-mail address;

b. Create a password to access the User's account;

c. Confirmation of the e-mail address provided during the User’s registration process by

entering the authorization code received to the e-mail address provided;

d. To be entitled to use our Services you must guarantee - and by using our services you

warrant and represent – that you:

da. are at least 18 years old or of other legal age, according to your relevant jurisdiction;

db. will not use our Services or will immediately cease using those if any applicable law

in your country prohibits or will prohibit you at any time from doing so; it is your

responsibility to follow the rules and laws in your country of residence and/or country

from which you access our Services;

dc. will not use our Services or will immediately cease using those if you are a resident or

become a resident at any time of the state or region, where the crypto assets

transactions you are going to execute are prohibited or require special approval, permit

and/or authorization of any kind, which Wallet or you have not obtained in this state or

region;

dd. have not previously been suspended or removed from our Services.

2. To log into Wallet, the User must enter the following information:

a. E-mail address provided during registration process;

b. Password created during registration process;

c. Authorization code received to the e-mail address provided.

3. Wallet has three core functionalities: (i) storing selected tokens based on the ERC20 standard, (ii)

sending stored tokens, (iii) receiving tokens currently accepted by the Operator for trading within the

infrastructure.

4. Aside from the aforementioned functionalities, Wallet also provides other features, which are (i)

Premium Holder Program; (ii) voting and (iii) launchpads.

5. Storage. Wallet User has the ability to store selected tokens based on the ERC20 standard.

a. Now, Wallet can store tokens purchased from Wallet Operator's launchpads. There are plans to

expand the selection of tokens available for trading within the Wallet in the future.

b. Wallet supports only tokens specified by the Operator. Transferring other types of tokens to

the Wallet will result in loss of transferred assets.

c. Tokens stored in the Wallet are in no way insured by the Wallet Operator, who is not

responsible for their eventual destruction, loss or misplacement.

6. Sending. Wallet User can send, swap or withdraw stored tokens.

a. Transmission of User's Wallet tokens is done using the Ethereum network, so the only

acceptable addresses to which a User can send their funds have to be on the Ethereum

network.

b. To make a withdrawal, a Wallet User must provide the following details: (i) a valid Ethereum

address; (ii) the number of tokens that User wishes to withdraw from the Wallet; and in some

specific cases, as detailed later, also (iii) the 2FA verification code sent to him via email.

c. Since transferring funds within the Ethereum network has a cost, the Wallet Operator is

entitled to charge a certain fee for each transfer transaction carried out.

d. The aforementioned fee is set by the Wallet Operator prior to each transaction. The fee

charged is not refundable under any circumstances.

e. The Wallet Operator stipulates that fund will be transferred within a maximum of 72 hours.

f. The Wallet Operator does not take any responsibility for tokens transferred to the wrong

address due to the User's fault. In addition, the Wallet Operator is not responsible for the

outcome of funds sent directly to cryptocurrency exchanges, which is expressed by a warning

against making such transactions, displayed each time during the transfer process.

g. The minimum amount withdrawn must be greater than the fee charged by the Operator and

must exceed the amount of 1000 MR BOB COINS.

h. The Wallet Operator cautions that all major transactions taking place within the infrastructure

operated by the Wallet Operator are manually authorised, which may or may not extend

transaction processing time beyond the aforementioned 72 hours period. In case the

transaction does not pass the verification stage, the funds shall be returned to the User's

account.

i. As for the previously mentioned case in which 2FA verification would be required, the

transaction will be processed only after the User enters the appropriate code. In case the

transaction fails, the funds will be returned to the User's account. If the verification is

successful, the transaction will take place without any obstacles and shall be considered

completed.

j. Wallet User can at any time access the history of transactions carried out within his wallet.

7. Receive. Wallet User can receive tokens via his Wallet, but only if the token has been implemented

into the Wallet by the Operator.

a. To successfully transfer funds to the Wallet, the User must first generate a deposit address.

Only the token added by the Operator to the Wallet platform can be successfully transferred to

this address.

b. Tokens sent by User that have not yet been implemented by the Operator, and therefore are not

functional, shall be lost. The Operator will not be liable for assets lost by the User as a result

of such actions.

c. If the User attempts to deposit funds worth less than the value of the operative fee charged,

such transaction will not be booked and therefore shall not take place.

d. Wallet User can at any time access the history of transactions carried out within his wallet.

8. Premium Holder Program. Wallet User can freeze a certain amount of his MR BOB COINS, in order

to receive a reward proportional to the amount of frozen assets.

a. The bonuses rate applied to this feature will be variable and dynamic. It has the potential to

change at any time, so the User shall be able to check the current value of the bonuses rate

through their Wallet at any time.

b. The User who had locked tokens at the time of Snapshot is entitled to receive an Airdrop of

new tokens. The amount of the Airdrop that the user can expect, heavily depends on the

number of tokens and the time for which the tokens were locked. The precise number of

tokens granted is calculated at the moment they are transferred to the User.

c. The minimum value of tokens that can be locked is 1,000 MR BOB COINS. The User cannot

spend for this purpose any less than the value indicated above.

d. If the User decides to unfreeze all or part of his frozen funds, the User must select the

appropriate option in his Wallet and specify the exact amount of funds the User would like to

withdraw from the Premium Holder Program. The withdrawal process takes 14 days, after

which the requested amount of funds return to the User's Wallet. Tokens deposited to the

Premium Holder Program are subjected to a 14-day-lockup. To receive them back, User need

to manually unlock them. During the unlocking period, User won’t receive any reward or

airdrops.

e. The Operator cannot guarantee that the User will obtain the expected benefits from the

Premium Holder Program due to the high dynamics and volatility of both bonuses rates and

token values.

f. Wallet Users can access the history of transactions carried out within their Wallet at any time.

9. KYC process. A Wallet User holding considerable funds on his Wallet is subject to the KYC

procedure.

a. Once initiated, all funds at User’s disposal are frozen until its completion.

b. The User is informed about the initiation of the procedure by displaying an appropriate

message in the form of a pop-up after logging into the Wallet.

c. Procedure is carried out automatically via the website www.veriff.com. Through it, the User is

required to confirm identity by showing an appropriate document and sending a face photo.

d. After successfully verifying the User's identity, all Wallet functionalities are immediately

restored.

e. In case of unsuccessful verification, the User should immediately contact www.veriff.com

support and make another attempt to verify identity. Data security is guaranteed by

www.veriff.com.

10. Voting. The Wallet User, who has adequate assets, is entitled to participate in the decision-making

process regarding operation of the community gathered around MR BOB COINS, through the possibility

of taking part in votes organised by the Operator regarding further development of the project.

Participation in voting is mandatory if the User wants to participate in the Premium Holder Program.

a. Total vote weight depends on the number of tokens gathered in the wallet during the vote and

their status. Both locked at the Premium Holder Program and deposited coins have the same

voting weight.

b. Tokens withdrawn from the Premium Holder Program are subjected to a 14-day lockup.

During this period, tokens may not be used for voting. Only after 14 days and correct crediting

to the user's account, the tokens can be used for voting again. Tokens remaining in the wallet

or locked at PHP can be used to vote.

c. If MR BOB COINS would be withdrawn from the Wallet during an active vote, vote weight

would be reduced only to the tokens remaining in the user's wallet.

d. Voting is free, and does not result in reduction of User’s assets.

e. The voting results are not binding in any way for the Wallet Operator and can be treated only

as community proposals. Therefore, while such proposals can eventually be implemented,

there is no obligation to do so on the Operator side.

11. Launchpads. The Wallet User can join active Launchpads via Wallet.

a. Informational pages about both active and inactive Launchpads are available for both logged

in and non-logged Users.

b. To participate in an active Launchpad, the User must possess an active account through which

the User must log into the Wallet.

c. Each Launchpad has a specified duration and a Hard Cap, which is to be understood as the

maximum sum of money after the collection of which the Launchpad is terminated.

d. Each Launchpad is divided into a certain number of phases. After the completion of each

phase, a subsequent phase is initiated. In each following phase, the price of the tokens emitted

is raised upward.

e. The User can submit payment to participate in an ongoing Launchpad in any of three different

methods: (i) direct deposit of funds based on the ERC20 standard. The previously stated rules

for making standard deposits to Wallet apply; (ii) transfer funds using a service offered by a

third-party provider, in this instance Coinbase Commerce. The only funds accepted are those

based on the ERC20 standard and approved for trading by the service provider; (iii) a payment

made using a credit card, through a service offered by a third-party provider, in this case

Advcash.

f. The User utilizing services offered by third-party providers in order to participate in

Launchpad, declares that he has carefully read the terms of use of these services and will not

claim any liability to the Wallet Operator for the possible inconvenience caused by their use.

g. The binding price for the tokens purchased during the Launchpad is the price in effect at the

time the transaction is successfully booked.

h. If a phase shift occurs before the transaction has been successfully booked, the User is bound

by the new, higher price of the token.

i. The User shall receive a confirmation of the executed transaction via email.

j. Tokens purchased by the User during the Launchpad are granted only after the official end of

the Launchpad. The exact deadline for Users to receive the purchased tokens is determined

individually for each Launchpad.

-4-

1. The User is obliged to provide correct data when using the Wallet. If the Wallet Operator suspects

that the data provided by the User is false, it has the right to block the User's account until the

doubts are clarified.

2. While using the Services provided by the Wallet, the User is obliged not to undertake any actions to

the detriment of the Wallet, its other users or the Wallet Operator. The User shall be obliged to act

in accordance with the provisions of generally applicable law and the Regulations and to exercise

due diligence while using the Services provided by the Wallet.

3. The User shall be obliged to use the Wallet in accordance with its intended purpose, for purposes

and undertakings that are consistent with generally applicable laws and exclusively in their name

and on their account.

4. The Wallet Operator shall be entitled to temporarily block the User's access to the Wallet due to

ongoing modernization work, in case of a suspected critical error in the IT system executing the

Service provided via the Wallet or in systems linked to the Wallet IT system.

5. The Wallet Operator shall be entitled to temporarily or permanently block access of a given User to

the Wallet if it suspects or learns that such User is using the services provided via the Wallet in a

manner contrary to its intended use or violation of generally applicable laws or the Regulations.

6. The Wallet Operator shall verify the User's identity at the stage when the User creates an account

on the website available under the address https://mrbob.io/whitelist/public, which it also operates.

7. The Wallet Operator shall at any time be entitled to request the User to confirm the data provided

while filling out the User registration form in the domain https://mrbob.io/whitelist/public. The Wallet

Operator shall be entitled to demand confirmation of identity by sending documents proving the

User's identity. Until the User's identity is confirmed, the Wallet Operator can block the User's

access to the Wallet. In the case of verification of a negative identity of the User, the Wallet

Operator is entitled to delete the User account under the domains https://mrbob.io/whitelist/public.

8. The Wallet Operator shall be obliged to exercise due diligence to ensure proper provision of

services via the Wallet to the User.

9. The User is obliged to update the software used by them at any stage to use the Wallet Services.

This obligation shall also always apply to anti-virus software and software designed to protect the

User's data.

-5-

1. The Wallet Operator shall not be liable for the failure to perform or improper performance of the

Service due to circumstances beyond the Wallet Operator's control, random causes, hacking attacks

on the Wallet , the Service provided via Wallet or other services required for the proper

provision of the Service or the Wallet , or on the server infrastructure of the Wallet or of the

Wallet Operator. In particular, the Wallet Operator is not responsible for circumstances, elements or

parameters of the Service that depend on the Ethereum network, or other third parties and service

providers that affect the way the Wallet operates.

2. The Wallet Operator shall not be liable for failure to perform or improper performance of the

Service due to circumstances for which the User is responsible. These circumstances will include,

among others, providing incorrect data by the User during registration for the domain

https://mrbob.io/whitelist/public.

3. The Wallet Operator shall not be liable for any loss or failure to achieve the intended purpose by

the User, resulting from the User's use of the instructions generated by the Wallet, voluntarily

accepted by the User.

4. The Wallet Operator shall not be liable for failure to notify the Client of the fact and reasons for

failure to perform or improper performance of the Service due to circumstances beyond its control,

in particular, if the Wallet Operator does not have the User's contact details or if the User provided

a false or incorrect e-mail address in the registration form.

5. Subject to generally applicable provisions of law, the Wallet Operator shall not be liable for any

damage incurred by third parties directly or indirectly related to the User's use of the Service

provided by the Wallet.

6. Subject to generally applicable laws, the Wallet Operator shall not be liable for any damages

incurred by the User that result from malfunctioning or non-functioning of the User's

cryptocurrency wallet, independent of the domain https://mrbob.io/whitelist/public.

7. The Wallet Operator shall not be liable for any damage suffered by the User caused by improper or

illegal use of the Wallet.

8. The Wallet Operator shall not be liable for failure by the User to achieve planned objectives or

benefits that were intended to be completed by using the Service provided via the Wallet.

9. The Wallet Operator shall not be liable for any damage incurred by the User due to using the Wallet

Services in a manner not provided for by the Wallet website interface, resulting from manual

interference with the scripts, source code, or parameters https://mrbob.io/whitelist/public.

10.The Wallet Operator shall not be liable for temporary inability to use the services provided via the

Wallet due to modernisation works or circumstances attributable to force majeure.

-6-

1. The User has the right to lodge a complaint if the Wallet Service is not performed in compliance

with the provisions of these Regulations.

2. The User should submit a complaint by regular mail, sending it to the address of the Wallet

Operator's registered office as specified in the Regulations.

3. A complaint submitted by the User should include:

a. user data, allowing the User to be identified;

b. a description of the irregularities which are the subject of the complaint.

4. The complaint shall be submitted in English within a maximum of 14 days from the date of

occurrence of the irregularity which is the subject of the complaint.

5. The Wallet Operator shall examine the complaint within 30 days of receiving the complaint,

responding to it in the manner in which the complaint was received unless the User specified the

e-mail address in the complaint. The deadline for handling a complaint may be extended in justified

cases, of which the Wallet Operator will inform the User.

-7-

1. The Wallet Operator is entitled to process personal data of the User who is a natural person,

necessary to provide the Service or to conduct a complaint procedure.

2. Suppose the Wallet Operator becomes aware of the User's use of the Service in a manner contrary

to generally applicable laws or regulations. In that case, the Wallet Operator may process the User's

personal data for the purpose and to the extent necessary to determine its liability.

3. The precise storage method and the scope of the data stored are specified in the Privacy Policy

published on https://mrbob.io/whitelist/public.

4. The Wallet Operator cares about the security of personal data provided by the User. These data are

protected against unauthorised access.

-8-

1. All notifications and User statements related to the use of the Service provided via the Wallet

should be delivered via:

a. snail mail: MRBOB  IT SERVICES L.L.C. with its registered office in Bur Dubai, Dubai

Investment Park 1, 00-000 Dubai, United Arab Emirates;

b. e-mail address: office@mrbob.io.

2. Any disputes related to the performance of the Wallet Service shall be resolved amicably by the

Parties. If an amicable resolution of the dispute is ineffective, the court of competent jurisdiction

shall be the court having jurisdiction over the registered office of the Wallet Operator.

3. If at any time one or more of the provisions of these Regulations becomes invalid or ineffective for

any reason by operation of law, final court judgement, or final administrative decision of a public

administration body, all the remaining provisions of these Regulations shall remain in full force and

effect. The invalid or ineffective provisions referred to in the preceding sentence shall be replaced

by provisions arising from the relevant legal provisions and producing legal effects as close as

possible to those being replaced.