Security Token Acknowledgement

Preamble

The board of directors (Board) of CasperLabs Holdings AG (CHE-456.783.617) (Company) has established the following regulations, which (i) provide the information that the Company is required to provide under article 973i para. 1 of the Swiss Code of Obligations, (ii) set forth the tokenization terms (Registrierungsvereinbarung) in relation to those shares of the Company that have been or will be issued from time to time in the form of ledger-based securities (Registerwertrechte) within the meaning of articles 973d et seq. of the Swiss Code of Obligations (Tokenized Shares) and (iii) set forth the modalities pursuant to which acquirers of the Company’s shares can be recognized as shareholders of the Company and recorded in the Company’s share register, as contemplated by the Company’s articles of association.

1 Information Regarding the Tokenized Shares; The Distributed Ledger and the Smart Contract

1.1 Rights associated with the Tokenized Shares

1.1.1 The Board has resolved to tokenize and may in the future resolve to tokenize from time to time some or all of the Company’s ordinary registered shares pursuant to Articles 973d et seq. of the Swiss Code of Obligations and these regulations.

1.1.2 The rights associated with the Tokenized Shares are set forth in the articles of association of the Company and Swiss law, in particular Articles 620 et seq. of the Swiss Code of Obligations.

1.2 Functioning of the distributed ledger and smart contract

The Board has resolved that the Tokenized Shares will be associated with digital tokens created by means of the CasperLabs smart contract (see Section 1.2.3) and recorded on the Ethereum distributed ledger (see Section 1.2.2).

1.2.1 The distributed ledger technology

1.2.1.1 Ethereum is a distributed ledger. The distributed ledger technology is a technology that allows the operation of a distributed ledger, i.e. a ledger that is not kept by a trusted intermediary but by a community of independent participants.

1.2.1.2 The distributed ledger technology, as implemented on the Ethereum distributed ledger is based on complex mathematical and cryptography concepts, which are described in this document at a high level only. The technology makes it possible to keep records of data relating to persons whose identity is protected by asymmetric cryptographic methods. Such methods are based on the interplay between a public key and a private key, which are two numbers that are mathematically related. The public key (often referred to as the “distributed ledger address” is available to all ledger participants, while the private key must remain secret. The holder of the private key can generate “signature messages” that can be identified as authentic (i.e. as having been generated with the private key) by the ledger participants. Such signature messages can be used to initiate “transactions”, i.e. new entries in the ledger. In a distributed ledger that functions as a “blockchain”, the participants validate transactions in blocks, by adding a new set of data (or “block”) to a chain of pre-existing blocks.

1.2.1.3 Each ledger participant maintains its own copy of the ledger and updates such copy when a participant includes a new “block” in a manner consistent with the chain’s protocol. This regime aims to ensure the transparency and immutability of the transactions recorded in the ledger.

1.2.2 Functioning of the Ethereum distributed ledger

1.2.2.1 The Board has resolved that the tokens associated with the Tokenized Shares will be recorded in the Ethereum blockchain (the “distributed ledger”).

1.2.2.2 The distributed ledger has two functions.

1. The first is related to Ether (or ETH). Ether is a cryptocurrency (or digital currency) that is recorded and traded on the distributed ledger. Users of the distributed ledger can trade Ethers on the distributed ledger and use such Ethers as a means of payment.
2. The second is the use of “smart contracts”. The distributed ledger allows for the creation of computer codes called “smart contracts”, which can perform a large number of functions, including creating a record of digital tokens on distributed ledger addresses.

1.2.2.3 A “token” is an entry in a register that is maintained by means of the smart contract. Each token is attributed to a particular distributed ledger address. The fact that the register maintained through the smart contract contains a corresponding entry is evidence that a token is attributed to the relevant distributed ledger address.

1.2.2.4 Entries in the distributed ledger are validated by a large number of participants. Any person or entity may act as validator and validate transactions in the distributed ledger, subject to technical requirements unrelated to the identity of the person or entity (e.g. technical infrastructure requirements and/or minimum amount of Ethers “staked” (i.e. locked on a distributed ledger address for a certain period of time)).

1.2.3 The CasperLabs smart contract framework

1.2.3.1 The Tokenized Shares are created and managed by means of the CasperLabs smart contract (Smart Contract). The Smart Contract defines the manner in which the tokens are created, transferred and revoked. The Smart Contract also serves to record the ownership of the tokens

1.2.3.2 The Solidity source code and the distributed ledger address of the Smart Contract are published at https://etherscan.io/token/[•]].

1.2.3.3 The code of the Smart Contract is provided on an “as is” basis, without warranty of any kind including warranties that the code is free of defects, merchantable, fit for a particular purpose or non-infringing.

2 Tokenization Terms

2.1 Definitions

In these regulations:

1. “Hard Fork” means a disagreement among participants of the distributed ledger resulting in a split into two or more incompatible versions of such distributed ledger, and which results in the tokens recorded in the distributed ledger being duplicated (one version of the tokens remaining on each version of the distributed ledger).
2. “Token” means the account unit created by means of the smart contract.
3. “Token Holder” means any person with de facto control over the private key associated with the distributed ledger address on which one or more tokens are recorded.

2.2 Transactions in Tokenized Shares

2.2.1 Unless applicable law provides otherwise (e.g. in the event of universal succession further to the death or merger of the Token Holder, or if the transfer or encumberment is carried out pursuant to the Federal Act on Intermediated Securities), the transfer of legal title to a Tokenized Share, and the creation of a security or other interest on such Tokenized Share (such as a pledge or usufruct) (each such transfer or creation of interest a Transaction), requires the transfer of the relevant token to a distributed ledger address controlled by the acquirer, in accordance with the rules and procedures of the distributed ledger and the functions of the smart contract.

2.2.2 A transfer of a token will be deemed to have been recorded in the distributed ledger when 18 blocks or more have been validated after the one relating to the Transaction.

2.2.3 Once a Transaction has been recorded in the distributed ledger, the Transaction will remain valid if the agreement based on which the Transaction was carried out is invalidated, for example further to a material error of one of the parties or of a fraud. In such a case, unwinding the Transaction will require a return of the relevant token to a distributed ledger address controlled by the transferor.

2.3 Hard Forks

2.3.1 In the event of a Hard Fork or under similar circumstances that may endanger the reliability of the distributed ledger, the Company may activate the “pause” function of the smart contract to prevent Transactions on both versions of the distributed ledger pending its decision on which version it will support and the communication of such decision to the shareholders.

2.3.2 If the Company decides to support the version of the distributed ledger that follows the rules and protocols of such distributed ledger that were in force immediately prior to the occurrence of the Hard Fork (i.e. the “legacy” version of the relevant distributed ledger), all Transactions on “forked” versions of the distributed ledger will be invalid, and any token existing on a forked version of the distributed ledger will not be associated with Tokenized Shares.

2.3.3 If the Company decides to support a forked version of the distributed ledger, all Transactions on the “legacy” version of the relevant distributed ledger will be invalid, and any token existing on the “legacy” version of the distributed ledger will not be associated with Tokenized Shares.

2.4 Cancellation of lost or stolen tokens

2.4.1 If a Token Holder initiates proceedings to have one or more tokens canceled pursuant to Article 973h CO, the number of public notices required pursuant to Article 973h para. 2 will be one, and the deadline imposed on Token Holders to produce the relevant private keys will be one month.

2.4.2 The Company will revoke and reissue a token upon delivery of an enforceable (vollstreckbar) court decision ordering such revocation and re-issue.

2.5 Change in type of securitization of shares / intermediated securities (Bucheffekten)

2.5.1 The Board may change the type of securitization of the Company's shares at any time and switch between Tokenized Shares, registered securities, global securities and uncertificated securities.

2.5.2 The Board may register the Tokenized Shares, which are deposited with the Company or a custodian, as intermediated securities (Bucheffekten). The Board may withdraw shares registered as intermediated securities from the custodian system at any time.

3 Recognition of Acquirers of Shares as Shareholders

3.1 Share register

3.1.1 According to the Company’s articles of association, the Company recognizes as shareholders the persons who are recorded in the Company’s share register as the owners or usufructuaries of shares. Shareholders can only exercise or claim their shareholder rights (including their dividend and other financial shareholder rights) upon their registration in the Company’s share register. Rights to dividends and other financial shareholder rights that arise before the registration of a shareholder in the Company’s share register are forfeited to the Company. Persons having acquired shares of the Company will be recorded in the Company’s share register as shareholders only if they have followed the rules and procedures set forth in this Section 3.

3.1.2 These requirements apply to the acquirers and holders of the Company’s shares irrespective of whether such shares have been issued as ledger-based securities or otherwise.

3.1.3 The rules and procedures set forth in this Section 3 do not limit the powers and rights of the Company and its board of directors under applicable law and the Company’s articles of association.

3.2 Registration request

The Company will register in its share register acquirers of shares who have submitted a duly completed registration request in the manner contemplated in this Section 3. The Company may, at its discretion, register acquirers of shares in its share register if it has otherwise satisfied itself that such acquirer satisfies the relevant requirements of the Company’s articles of association and applicable law.

3.2.1 Form of the registration request

Registration requests must be made electronically, by email to investorrelations@casperlabs.io.

3.2.2 Content of the request – Shares acquired by the beneficial owner¹

3.2.2.1 All acquirers of shares must provide the following information:

1. first and last name (for individuals) or corporate name (for legal entities and unincorporated partnerships) of the applicant;
2. details of the applicant;
   1. place of residence (for individuals) or registered office (for legal entities and unincorporated partnerships) and valid postal address;
   2. date of birth (for individuals) or date of constitution (for legal entities and unincorporated partnerships);
   3. nationality(ies) (for individuals);
   4. email address;
   5. telephone number;
   6. copy of a document used to verify the identity;
3. confirmation that the applicant holds the shares for its own account and not as a fiduciary for a third party;
4. total number of shares acquired by the applicant, split by the form of the shares (ledger based securities, share certificates, etc.); and
5. IBAN of a bank account opened in the name of the shareholder with a bank established in Switzerland or in another member State of the Organization for Economic Co operation and Development (OECD).

3.2.2.2 Acquirers of Tokenized Shares who hold their Tokenized Shares on distributed ledger addresses that they control (e.g. through a wallet that they control) must provide the following additional information:

1. distributed ledger address(es) on which the Tokenized Shares are recorded;
2. confirmation that the applicant has sole control over the distributed ledger address(es) referred to under (f) above; and
3. total number of Tokenized Shares held on each distributed ledger address referred to under (f) above.

3.2.2.3 Acquirers of Tokenized Shares who hold their Tokenized Shares through professional custodians within the meaning of the Federal Act on Intermediated Securities (e.g. banks, securities firms or DLT-based trading facilities within the meaning of the Financial Market Infrastructure Act) must provide the following additional information:

1. name and address of the professional custodian; and
2. total number of shares acquired through the professional custodian, split by the form of the shares (ledger-based securities, share certificates, etc.)

3.2.3 Content of the request – Shares held through a fiduciary

All persons and entities who have acquired shares through a third party (fiduciary) must themselves or through the fiduciary provide the following information:

1. first and last name (for individuals) or corporate name (for legal entities and unincorporated partnerships) of the beneficial owner;
2. details of the applicant:
   1. place of residence (for individuals) or registered office (for legal entities and unincorporated partnerships) and valid postal address;
   2. date of birth (for individuals) or date of constitution (for legal entities and unincorporated partnerships);
   3. nationality(ies) (for individuals);
   4. email address;
   5. telephone number;
   6. copy of a document used to verify the identity;
3. name and address of the fiduciary;
4. confirmation from the fiduciary that the identified beneficial owner beneficially owns the respective shares;
5. total number of shares acquired by the fiduciary, split by the form of the shares (ledger based securities, share certificates, etc.); and
6. IBAN of a bank account opened in the name of the fiduciary with a bank established in Switzerland or in another member State of the Organization for Economic Co-operation and Development (OECD).

3.2.3.1 All persons and entities who have acquired shares through a fiduciary who itself holds the Tokenized Shares on distributed ledger addresses that the fiduciary controls (e.g. through a wallet that the fiduciary controls) must themselves or through the fiduciary provide the following additional information:

1. distributed ledger address(es) on which the Tokenized Shares are recorded;
2. total number of Tokenized Shares held on each distributed ledger address referred to under (g) above; and
3. confirmation from the fiduciary that the fiduciary controls the ledger address(es) referred to under (g) above.

3.2.3.2 Professional custodians within the meaning of the Federal Act on Intermediated Securities (e.g. banks, securities firms or DLT-based trading facilities within the meaning of the Financial Market Infrastructure Act) may request to be recorded as nominees in the share register by providing solely the information contemplated under (iii), (v) and (vii) to (ix) above.

3.2.4 Supporting evidence

3.2.4.1 The Company may request supporting evidence in relation to a registration.

3.2.4.2 If the shares are held in tokenized form, the Company may, in particular, request that a beneficial owner or fiduciary acting on behalf of a beneficial owner performs a so-called “satoshi test”, i.e. makes a small transaction from the distributed ledger address purported to be the applicant’s, or otherwise request that the respective beneficial owner or fiduciary demonstrates that it has control over the distributed ledger address on which the tokens are recorded.

3.2.5 New confirmation

The Company can, at any time, request a shareholder to confirm that the information provided in a previous registration request remains accurate and up to date.

3.2.6 Disclosure of beneficial ownership

Shareholders who reach or cross a relevant threshold for the disclosure of the beneficial ownership of the shares must, in addition, comply with applicable legal requirements.

3.2.7 Consequences of registration

3.2.7.1 Once recorded in the Company’s share register, a shareholder is entitled to exercise all the membership and financial rights associated with the shares recorded under its name in the share register.

3.2.7.2 By contrast, as per the Company’s articles of association, an owner of Tokenized Shares who is not registered in the share register does not have any right as a shareholder of the Company. Such owner of Tokenized Shares is in particular not entitled to dividends or other distributions made by the Company, to attend general meetings or to vote on the occasion of such general meetings. In the event of a subsequent registration in the share register, shareholder rights will only arise and accrue for the period that follows the registration. Rights to dividends and other financial shareholder rights that arise before the registration of the shareholder in the Company’s share register will be forfeited to the Company.

3.2.8 De-registration

Upon being informed or otherwise having obtained knowledge of a transfer of shares by a shareholder, the Company will strike off the corresponding entry from the share register.

4 Amendments

The Company may amend these regulations at any time and without prior notice. Amendments to these regulations will be validly made and binding upon all shareholders upon being published in accordance with the Company’s articles of association or otherwise communicated to shareholders, including through a publication on the Company’s website. Amendments to these terms will only affect the acquisition, encumbrance or disposal of shares (including Transactions) entered into after the amendments became effective and will not affect such transactions (including Transactions) previously completed (in the case of ledger-based securities, recorded in the distributed ledger).

5 Applicable Law and Jurisdiction

5.1 These regulations are governed by and must be construed in accordance with the laws of Switzerland, excluding the rules on conflict of laws thereof.

5.2 Any dispute, controversy or claim arising out of or in relation to these terms, including the validity, invalidity, breach or termination thereof, will be subject to the exclusive jurisdiction of the ordinary courts of Zug, Switzerland.