VERSION 2.0
DISP WORLD Platform
Republic of Uzbekistan, Tashkent
25 August 2026
This Notice regarding the DISP-2 token and blockchain registry (the “Notice”) forms an integral part of the User Agreement of the DISP WORLD platform available at https://dispworld.com/ (the “Platform”). It is addressed to all Platform Users who use or may use the DISP-2 blockchain registry functionality, as well as to all Users reviewing information about the Platform’s technical tools. This Notice explains the nature and purpose of DISP-2, describes the data and cryptographic evidence recorded in the blockchain registry, defines the boundaries of the legal characterisation of DISP-2, discloses technical and regulatory risks, and informs Users of the restrictions applicable to the blockchain registry. All Users must review this Notice because it contains information necessary to understand one of the Platform’s key technical components. In the event of any conflict between this Notice and the User Agreement in matters relating to DISP-2 or the blockchain registry, this Notice shall apply as the specific document; the User Agreement shall apply in all other respects.
1. TERMS AND DEFINITIONS
1.1. For the purposes of this Notice, in addition to the terms defined in the User Agreement, the following terms and definitions shall apply:
“DISP-2” means a service registry layer and internal technical mechanism developed and used by the Administration exclusively to generate, verify and record cryptographic evidence relating to event results, judging records, validated logical metrics and other technical metadata. The DISP-2 designation does not imply that a separate digital asset is transferred to Users. DISP-2 is not, and is not intended to be, a cryptocurrency, means of payment, electronic money, security, investment instrument, claim token, debt instrument or other financial instrument. DISP-2 has no monetary value and is not intended to circulate outside the Platform’s technical infrastructure.
“Blockchain Registry” means a decentralised distributed database of control records implemented using blockchain technology on the Polygon network, in which the Platform records cryptographic evidence of the origin, integrity, version and validation of specific technical facts relating to events conducted through the Platform.
“Polygon Network” means a public Ethereum Virtual Machine (EVM)-compatible Layer 2 blockchain network used by the Administration as the technical basis for the DISP-2 blockchain registry. The Polygon Network is independent of the Administration, and the Administration does not control its operation.
“Smart Contract” means software code deployed on the Polygon Network that automatically registers control records, their versions, technical statuses and such internal operating parameters as may be provided by the architecture when the relevant transaction is initiated by the Platform systems.
“Control Record” means the minimum set of technical data recorded in the blockchain registry for a single logical metric or a batch of logical metrics, including the operation and metric-type identifiers, schema and catalogue versions, a cryptographic hash or Merkle root, protected event and policy commitments, a timestamp, a technical status and, where applicable, a reference to a corrective record.
“Logical Metric” means one accepted, unambiguously defined and verifiable semantic fact relating to an event, role, action, action outcome, interaction or compliance with a rule. The actual value of a Logical Metric and its full context are retained outside the public blockchain.
“Metrics Catalogue” means the versioned system of DISP-2 metric types and schemas, maintained separately from the code of the canonical Smart Contract. The developed catalogue contains 402 metric types; the first production pilot is intended to use a limited universal profile of ten types.
“Merkle Root” and “Merkle Proof” mean cryptographic mechanisms used to commit batches of Logical Metrics and subsequently verify individual metrics without recording the full content of each metric on the public blockchain.
“Event Commitment” means a cryptographic value linking a Control Record to a particular Platform event without disclosing the event’s full content or placing a persistent User identifier on the public blockchain.
“Validator” means an authorised technical, system or role-based source of confirmation involved in verifying the admissibility, provenance and quality of a Logical Metric under the active validation policy.
“Cryptographic Hash” means a fixed-length unique string produced by applying a cryptographic hash function to data or an agreed canonical representation of data. A hash can be used to verify data integrity but cannot be used to retrieve the source content. Personal data of participants must not be recoverable from a public Control Record.
“Internal Technical Consumption” means a machine-calculated registry operating parameter applied only to successfully finalised useful operations. It is not a price of DISP-2, a tariff, a monetary obligation of a User, a means of payment or evidence of proprietary value.
“Network Fee” or “Gas Fee” means the fee charged by the Polygon Network for processing a transaction. This fee is not paid to the Administration; it is paid directly to the Polygon protocol. In the first Platform release, Network Fees are paid by the Administration in its own name.
“Regulatory Risk” means the risk that actions of public authorities, legislative changes or official interpretations by competent authorities may impose restrictions or prohibitions on the use of blockchain technology or specific blockchain solutions in jurisdictions where the Platform operates.
“Technical Risk” means the risk of failure, error, delay, unavailability, incorrect validation or loss of integrity in blockchain or off-chain infrastructure arising from the technical characteristics of the systems used or circumstances outside the Administration’s control.
“ICO” (Initial Coin Offering) means an initial offering of tokens or coins for fundraising purposes. The Administration does not conduct or plan to conduct an ICO and does not raise financing through DISP-2.
1.2. Other terms shall have the meanings given to them in the User Agreement and other Platform documents or their generally accepted meanings in the technology industry.
2. NATURE AND PURPOSE OF DISP-2
2.1. DISP-2 is exclusively a service registry layer established by the Administration for the technical purpose of transparently, immutably and verifiably recording the provenance, integrity, version and validation of event results, judging records, Logical Metrics and other verifiable facts generated within the Platform. Distributed ledger technology is used because of the immutability of Control Records and the possibility of independent cryptographic verification, providing an additional layer of trust compared with reliance on a single centralised database.
2.2. DISP-2 is not and must not under any circumstances be characterised or treated as: a cryptocurrency or digital currency of any kind; a means of payment or exchange accepted for goods, work or services; electronic money within the meaning of the laws of the Republic of Uzbekistan or any other applicable jurisdiction; a security, unit, share or other instrument conferring participation in capital or profits; a debt instrument or claim against the Administration or any other person; an investment asset acquired with an expectation of income; a utility token in the conventional sense involving transfer of a token by the Administration to Users; or an object of civil rights capable of being bought, sold, exchanged, gifted or otherwise transacted between Users.
2.3. DISP-2 exists solely as technical records and internal software parameters within the Platform infrastructure and the Polygon Network. DISP-2 is not distributed or transferred to Users, credited to their accounts or wallets, withdrawn by Users from the Platform, or exchanged by Users for other digital assets or fiat currency. Users acquire no ownership, proprietary or contractual rights in DISP-2, any internal reserve or the Blockchain Registry.
2.4. The Administration, acting through its technical systems, is the sole entity that uses DISP-2. Users may create source data through the Platform interfaces, but a public blockchain transaction may be initiated only by the Administration’s system after the applicable schema, processing-purpose, quality, uniqueness and validator-confirmation checks have been completed. Users may not independently initiate transactions with the DISP-2 Smart Contract.
2.5. Access to DISP-2 blockchain registry functionality is made available to Organizers and Mentors subscribed to a Pro or Caesar plan, or as otherwise expressly provided by the then-current Platform tariffs. The functionality may be unavailable under other plans, without restricting access to other Platform functions. Access to registry functionality does not require the User to maintain a cryptocurrency wallet and does not result in the User receiving DISP-2.
2.6. The developed DISP-2 catalogue contains 402 metric types relating, among other matters, to event context, participation and roles, actions and outcomes, interactions, rule compliance, judging, organisation, audience, streaming, and data quality and provenance. The first production pilot is intended to use ten universal types: event start; event end; participation; participant role; active participation duration; observed action type; action outcome; reaction time; interaction type; and rule-compliance status. The remaining types are not automatically activated and may be introduced only in stages following technical, legal and privacy assessment.
2.7. The Metrics Catalogue and its versions are maintained separately from the canonical Smart Contract. This makes it possible to add new event profiles and data schemas without replacing the core technical infrastructure and to verify every historical record against the schema version in force when that record was created.
2.8. The technological and public-interest purpose of DISP-2 is to improve transparency of results and data provenance, preserve correction history, reduce the risk of undetected record alteration and provide a verifiable basis for analytics across sport, education, competitions, debates, live streaming and other events. DISP-2 is not intended to create a universal trustworthiness score or assess a person’s intelligence, mental state or social worth, and must not be used as the sole basis for decisions producing legally significant consequences for a User.
3. DATA RECORDED IN THE BLOCKCHAIN REGISTRY
3.1. Only the minimum necessary control data and cryptographic evidence relating to a single Logical Metric or a batch of Logical Metrics are recorded in the DISP-2 Blockchain Registry:
3.1.1. Operation identifier and metric-type identifier: technical values used to distinguish a particular operation and identify the applicable semantic schema without revealing the actual metric value.
3.1.2. Schema version and catalogue version: identifiers of the technical rules under which the Control Record was generated and must subsequently be verified.
3.1.3. A cryptographic hash of a single metric or the Merkle Root of a batch: evidence of the integrity of an agreed set of off-chain data without disclosure of its full content.
3.1.4. Event and, where applicable, policy commitments: cryptographic commitments providing a verifiable link between the record, the relevant event and the rules under which it was generated.
3.1.5. The number of Logical Metrics, a timestamp or permitted time bucket, and the technical status of successful finalisation.
3.1.6. The validator-set hash, confidence indicators and quality flags, but only to the extent permitted by the active schema and data-processing policy.
3.1.7. A reference to a prior Control Record or the technical relationship CORRECTS or SUPERSEDES where a new record corrects or replaces a previously recorded fact.
3.1.8. Internal operating parameters, including the amount of Internal Technical Consumption calculated by the system where such parameters are included in the active Smart Contract configuration. Such parameters are not a price, payment obligation or market value of DISP-2.
3.2. The following data are not recorded in the public Blockchain Registry under any circumstances:
3.2.1. Personal data of event participants, including names, surnames, email addresses, usernames, dates of birth, countries of residence, IP addresses, telephone numbers, wallet addresses or any other persistent identifier capable of directly identifying a particular participant.
3.2.2. The actual value of a Logical Metric and its full context, unless disclosure is made to an authorised recipient through a separate lawful verification mechanism.
3.2.3. Video, audio, location, sensor, biometric, physiological or other raw telemetry data.
3.2.4. Payment data, including subscription payments, direct settlements between Users, bank card or account details.
3.2.5. Full judging records, including detailed scores, judges’ comments and other judging particulars.
3.2.6. Identity or corporate verification data (KYC/KYB), including documents, biometric data, corporate registration details, verification results and identification files.
3.2.7. User consents, legal bases and purposes of processing, complaint history, moderation decisions, support correspondence, advertising materials and advertising-placement data.
3.2.8. Detailed source evidence, disclosure keys, internal references capable of linking an event-scoped pseudonym to a persistent User account, and other restricted-access information.
3.3. The Administration confirms and warrants that excluding personal data and sensitive source data from the public Blockchain Registry is a mandatory architectural requirement rather than an optional condition. Personal data are processed and protected in accordance with applicable law, including Law of the Republic of Uzbekistan No. ZRU-547 dated 2 July 2019, On Personal Data (LexUZ). The technical safeguards used by the Administration are intended to prevent unauthorised recording of personal data on the public blockchain.
3.4. A public Control Record must not in itself be used to de-anonymise a User. Any authorised matching of a Control Record with source data may take place only within the Platform’s internal systems or under a specifically established procedure, on a lawful basis and by a properly authorised recipient.
4. TECHNICAL ARCHITECTURE OF THE BLOCKCHAIN REGISTRY
4.1. The Blockchain Registry is implemented on the Polygon Network, a public EVM-compatible Layer 2 blockchain. Polygon has been selected because of its technical characteristics, including comparatively lower transaction costs than Ethereum Layer 1, throughput suitable for the expected Platform volume and an established infrastructure. The Administration may migrate to another blockchain network if technical, economic or regulatory conditions change, subject to prior notice to Users.
4.2. The canonical Smart Contract uses a universal Control Record structure rather than separate fields and functions for each of the 402 metric types. The Smart Contract recognises the metric-type identifier, schema and catalogue versions, cryptographic evidence, Event Commitment, technical status and other minimum parameters; the actual metric value and full context remain within protected off-chain infrastructure.
4.3. Batch registration uses a Merkle Root architecture. A single transaction may commit a batch of Logical Metrics, and an individual metric can subsequently be verified by a Merkle Proof. This model reduces public data volume and network costs and does not require the Smart Contract to process every leaf in a separate loop.
4.4. Before finalisation, a Control Record passes the applicable technical process, which may include schema, permitted-purpose, data-quality and source checks, deduplication, confirmation of the number of Logical Metrics, the required validator quorum, availability of off-chain evidence and compliance with transaction limits.
4.5. Raw video, audio, sensor or other telemetry does not by itself constitute a finalised Logical Metric. Duplicates, technical retries, rejected, cancelled or expired operations must not produce a duplicate Control Record or repeated Internal Technical Consumption.
4.6. Incorrect records are corrected using an append-only model: the original record is neither deleted nor overwritten; a new Control Record is created with the relationship CORRECTS or SUPERSEDES. This preserves a verifiable history of the original fact, the correction and the current version.
4.7. Under the universal MVP profile, each accepted Logical Metric has the same technical weight irrespective of metric type, User role, country, advertising revenue or numerical audience size within a validated aggregate. The architecture does not permit artificial increases in Internal Technical Consumption through fictitious metrics, repeated processing of the same operation or an audience multiplier.
4.8. The proposed configuration of the canonical registry layer provides for a predetermined cap on internal technical units and no function for creating additional units after deployment of the relevant Smart Contract. This is an engineering parameter intended to support predictability and auditability and does not constitute a public issuance, offering, sale or distribution of DISP-2 to Users.
4.9. Internal Technical Consumption arises only after successful finalisation of a useful Control Record. A non-recoverable portion provided by the active configuration may be technically removed from the available internal layer, while another portion may be returned to the relevant technical reserve. These actions are performed solely by the Administration’s systems, are not a User payment and create no proprietary rights for a User.
4.10. Each confirmed Control Record is publicly accessible on the Polygon Network only to the extent of the minimum data actually recorded. Full metric values, judging records, personal data, video, audio and other source information remain solely within internal or other approved Platform systems and are not publicly available.
4.11. In the first Platform release, Network Fees for recording transactions on Polygon are paid by the Administration in its own name. Users do not directly pay Network Fees. Internal Technical Consumption and Polygon Network Fees are distinct categories and are accounted for separately.
5. LEGAL CHARACTERISATION OF DISP-2
5.1. The Administration hereby officially states and confirms the following with respect to the legal nature of DISP-2:
5.1.1. DISP-2 is not an object of civil rights capable of participating in civil circulation. DISP-2 is not a thing, proprietary right, result of work, service, security or other protected result of intellectual activity within the meaning of the civil legislation of the Republic of Uzbekistan.
5.1.2. DISP-2 is not a means of payment and is not intended to be used as a means of payment. Under the laws of the Republic of Uzbekistan, the use of crypto-assets as a means of payment in the Republic of Uzbekistan is prohibited. DISP-2 is not and cannot be used for settlements between Users or between Users and the Administration. The Administration does not accept DISP-2 as payment for any service.
5.1.3. DISP-2 is not an investment instrument. Its acquisition or “holding” does not confer any right to income, profit, dividends, interest or any other payment. The Administration does not and does not intend to make any promise or forecast concerning the future value, liquidity or return of DISP-2.
5.1.4. The Administration characterises DISP-2 as a technical tool: a component of the Platform software architecture implementing a decentralised registry of verifiable facts and cryptographic evidence. In legal nature, DISP-2 is closest to a technical data-recording and verification protocol that does not create independent proprietary rights.
5.2. This characterisation reflects the Administration’s position and its reasonable understanding of applicable law as at the date of this Notice. The Administration cannot guarantee that the regulatory authorities of the Republic of Uzbekistan or other jurisdictions in which the Platform operates will adopt the same characterisation. If the law or the official regulatory position of competent authorities changes, the Administration will bring the DISP-2-related activities of the Platform into compliance with the new requirements in a timely manner.
5.3. Users must not treat this Notice or any other Platform material concerning DISP-2 as legal or tax advice. A User intending to conduct transactions involving crypto-assets other than DISP-2, or requiring advice on cryptocurrency or token regulation in a particular jurisdiction, should consult a qualified legal or tax adviser.
6. ACTIVITIES NOT PERFORMED BY THE ADMINISTRATION IN RELATION TO DISP-2
6.1. To prevent ambiguity, the Administration expressly states that it does not and does not intend to carry out the following activities in relation to DISP-2:
6.1.1. The Administration does not conduct or plan to conduct an ICO, IDO (Initial DEX Offering) or any other public token offering for investment or fundraising purposes.
6.1.2. The Administration does not distribute or credit DISP-2 to Users for Platform activity, event achievements, payment of subscription plans or on any other basis. Users do not and cannot receive DISP-2 in any wallet.
6.1.3. The Administration does not provide or plan to provide liquidity for DISP-2 and does not organise or support trading in DISP-2 on digital-asset exchanges or decentralised platforms.
6.1.4. The Administration does not promise or guarantee any future value of DISP-2. Any third-party statement concerning the value or investment potential of DISP-2 is unauthorised by the Administration and inconsistent with the purpose of DISP-2.
6.1.5. The Administration does not allow Users to sell, transfer, exchange or otherwise dispose of DISP-2 to other Users or third parties.
6.1.6. The Administration does not use DISP-2 to raise investment in the Platform or any other project.
6.1.7. The Administration does not register DISP-2 as a security, payment instrument or financial instrument in any jurisdiction in which the Platform operates.
7. TECHNICAL RISKS OF BLOCKCHAIN INFRASTRUCTURE
7.1. The use of blockchain technology, cryptographic evidence and distributed data processing involves technical risks of which Users must be aware. By accepting the User Agreement and this Notice, a User confirms that the User has reviewed and accepts the following risks:
7.1.1. Polygon Network unavailability. The Polygon Network is an independent decentralised infrastructure not controlled by the Administration. It may be temporarily unavailable because of technical failure, congestion, attacks or other circumstances. During such unavailability, recording Control Data may be delayed or temporarily impossible. The Administration must nevertheless preserve the relevant data in its internal systems and submit the Control Record once network access is restored.
7.1.2. Technology changes. Blockchain technology, including the Polygon Network, continues to evolve. Changes to Polygon technology, protocol or economics may require migration to another network or a substantial change to the implementation of the Blockchain Registry. The Administration will provide prior notice if such a migration becomes necessary.
7.1.3. Irreversibility of records. Once a transaction has been confirmed on Polygon, the Blockchain Registry record is irreversible and cannot be deleted or amended. Incorrect data cannot be withdrawn from the blockchain; the Administration will instead create a new corrective record marked CORRECTS or SUPERSEDES. Users must take this feature into account when confirming source data.
7.1.4. Smart Contract compromise. The Smart Contract is software code that may theoretically contain vulnerabilities or be attacked. The Administration takes reasonable measures to audit and test the Smart Contract but cannot guarantee absolute protection against every possible attack. If a vulnerability is identified, the Administration will take prompt remedial and notification measures.
7.1.5. Changes in Network Fees. Polygon Network Fees may change materially depending on network demand and other factors. Although the Administration pays such fees in the first release, a significant increase may require a review of that approach.
7.1.6. Force majeure affecting blockchain infrastructure. Global technical failures, attacks on underlying internet infrastructure, public-authority action restricting access to blockchain networks and other extraordinary events may cause complete or partial unavailability of the Blockchain Registry. Such circumstances shall not constitute a breach of the User Agreement by the Administration where it has taken reasonable steps to mitigate their consequences.
7.1.7. Unavailability or loss of off-chain data. A cryptographic Control Record demonstrates the integrity of an agreed dataset but does not replace storage of the source content. Damage, loss or unavailability of an approved off-chain repository may restrict substantive verification even where the on-chain record remains available.
7.1.8. Source inaccuracy or validation error. A blockchain record confirms the fact and time of a particular cryptographic commitment, but does not itself guarantee the objective truth of the underlying observation. An error by an Organizer, Judge, automated labelling system, sensor or Validator may require a corrective record.
7.1.9. Batch-cryptography implementation errors. Incorrect formation of a Merkle tree, leaf, nonce, canonical schema or proof may make an individual metric unverifiable or cause a batch to be rejected. The Administration takes reasonable measures to perform machine checks and testing but cannot eliminate every software defect.
7.1.10. Schema and policy changes. New versions of the Metrics Catalogue, validation rules and technical policies apply to future operations. A configuration error or version incompatibility may temporarily restrict the recording or verification of particular metric types.
7.2. The Administration shall not be liable to Users for losses resulting from any risk listed in this section where it has taken reasonable measures to prevent and mitigate that risk. Nothing in this section limits liability for a breach caused by the Administration’s own negligence or wilful misconduct.
8. REGULATORY RISKS
8.1. Blockchain technology and digital assets are subject to active regulation in many jurisdictions. Users must be aware of the following regulatory risks:
8.1.1. Changes in regulation in the Republic of Uzbekistan. The laws of the Republic of Uzbekistan governing digital assets and blockchain technology continue to evolve. New legislation or official guidance from regulators may require modification of the technical implementation of DISP-2, registration as a regulated asset or other action by the Administration. If such circumstances arise, the Administration will bring the Platform into compliance with the new requirements and notify Users of material changes in a timely manner.
8.1.2. Regulatory restrictions in Platform jurisdictions. Regulation of blockchain and digital assets varies substantially across jurisdictions targeted by the Platform, including Türkiye, Central Asia and Europe. Users in those countries must independently ensure that their use of the Platform’s Blockchain Registry functionality complies with the laws of their country of residence. The Administration is not responsible for a User’s non-compliance with the laws of the User’s country of residence.
8.1.3. Non-recognition of a Blockchain Registry record as a legally significant document. The Administration does not guarantee that a DISP-2 Blockchain Registry record will be recognised as a legally significant or evidentiary document in any particular jurisdiction. A record is technical evidence that cryptographic evidence was created and committed and may be used as supplementary evidence, but it does not replace official documents requiring legal certification under applicable law.
8.2. The Administration engages with regulatory authorities concerning the use of blockchain technology and DISP-2 within the limits established by applicable law and shall comply with the requirements of competent authorities.
9. NO INVESTMENT INTENT
9.1. This Notice, the User Agreement, the Role Rules and other Platform documents are not and must not be treated as: an offer to buy, sell or otherwise acquire DISP-2 or any other digital asset; an invitation to invest in the Platform or in DISP-2; a securities prospectus or any other document relating to the issuance of financial instruments; or advertising or promotion of DISP-2 as an investment product.
9.2. The Administration does not provide investment recommendations or advice concerning investments in cryptocurrencies, tokens or other digital assets. Users make any such investment decisions independently, at their own risk and, where appropriate, after consulting a professional investment adviser.
9.3. If a User receives a third-party proposal to buy, sell, exchange or invest in DISP-2, the User should treat the proposal with caution because it is not authorised by the Administration and is inconsistent with DISP-2’s purpose as a service registry layer. The Administration recommends promptly reporting such proposals to the email address specified in section 12 of this Notice.
10. RESTRICTIONS ON USE OF THE BLOCKCHAIN REGISTRY
10.1. DISP-2 Blockchain Registry functionality is intended exclusively to generate, verify and record Control Records relating to events and validated Logical Metrics created within the Platform. Any other use of the Blockchain Registry or attempt to interact with the DISP-2 Smart Contract outside the authorised Platform interface and technical systems is unauthorised.
10.2. Organizers, Judges, Mentors, operators and other Users providing source information are responsible for the accuracy of the data they submit to the Platform. The Administration performs the prescribed technical checks of structure, source, uniqueness and confirmation, but does not guarantee that every source observation corresponds to objective reality unless such verification forms part of a separately stated external-validation service.
10.3. A Blockchain Registry record is technical evidence that the Platform system generated and committed the relevant cryptographic evidence at a specified time under a specified schema version. It is not an official legal document and does not replace official documentation of sporting results, gaming tournaments, education, competitions or other events where such documentation is required by applicable law.
10.4. Analytical conclusions, forecasts and AI hypotheses derived from Logical Metrics are not identical to the underlying Control Records. An unvalidated automated-model output must not be presented as an established fact, and DISP-2 is not used to assign a universal trustworthiness score or make a legally significant decision about a User without the human oversight required by law and Platform rules.
10.5. Providing a User with access to verify a Merkle Proof or to an authorised disclosure of off-chain data does not grant rights in the software code, internal repositories, registry reserves or any other component of the Administration’s infrastructure.
11. AMENDMENTS TO THIS NOTICE
11.1. The Administration may unilaterally amend this Notice in the following circumstances: a change to the technical implementation of the DISP-2 Blockchain Registry, including a change of blockchain network, Control Data, active Metrics Catalogue, validation procedure, batch registration or internal operating model; a change in law or in the position of a competent authority concerning blockchain technology or DISP-2; or any other material change in the legal or technical context in which DISP-2 operates.
11.2. The Administration shall notify Users of an amendment in accordance with section 17 of the User Agreement at least 15 (fifteen) days before the amendment takes effect. Continued use of the Blockchain Registry functionality after the effective date constitutes acceptance of the amended terms.
11.3. The current version of this Notice is permanently available on the Platform. Users are encouraged to check it periodically, particularly when the regulatory context in their country of residence changes.
12. FINAL PROVISIONS
12.1. Acceptance of the User Agreement includes acceptance of this Notice in full. By using the DISP-2 Blockchain Registry functionality, a User confirms that the User has reviewed and accepts the nature, purpose, restrictions and risks of DISP-2 described in this Notice.
12.2. This Notice and all relationships arising in connection with use of the DISP-2 Blockchain Registry are governed by the laws of the Republic of Uzbekistan. Disputes relating to this Notice shall be resolved in the manner set out in the User Agreement.
12.3. This Notice is permanently available on the Platform at https://dispworld.com/legal/token-notify. Questions concerning this Notice should be sent to the Administration using the email address stated in the contact details below.
12.4. If any provision of this Notice is held invalid or unenforceable, the remaining provisions shall remain valid and enforceable.
12.5. This Notice is executed in English and Turkish. Both versions are provided for User information. In the event of any inconsistency in interpretation for the purposes of the laws of the Republic of Uzbekistan, the English version shall prevail.
12.6. Official legal and regulatory information links: Presidential Resolution No. PP-3832; Regulation on the issuance, registration of issuance and circulation of crypto-assets, registration No. 3397; Law of the Republic of Uzbekistan No. ZRU-547, On Personal Data; official NAPP guidance. These links are provided for convenience and do not replace verification of the current version of the relevant legal instrument.
ADMINISTRATION DETAILS
GR ATTRACTOR Limited Liability Company
254, 1st passage, Usta Shirin Street, Miskin CCA, Almazar District, Tashkent, Republic of Uzbekistan
Tax Identification Number: 313127023
Email for DISP-2 and Blockchain Registry enquiries: Gr22attract@gmail.com
Email for general enquiries: Gr22attract@gmail.com
Platform website: https://dispworld.com/