Exhibit 10.4

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 1 of 69 CERTAIN IDENTIFIED INFORMATION HAS BEEN EXCLUDED FROM THIS EXHIBIT BECAUSE IT IS BOTH (I) NOT MATERIAL AND (II) IS A TYPE OF INFORMATION THAT THE REGISTRANT TREATS AS PRIVATE OR CONFIDENTIAL. [***] INDICATES THAT INFORMATION HAS BEEN REDACTED. XDT TOKEN FACTORY MASTER SERVICES AGREEMENT XPERT SOFTWARE SOLUTIONS PTE. LTD. × XDT — XDT Infrastructure I, LLC · Quanome Technologies, Inc. (Nasdaq: QNME) Private AI Cloud · XDT Token Factory · Party B runs the model, Party A calls the API Framework agreement — the commercial and technical terms of each transaction are in an Order under Schedule 1 MSA No. XDT-TF-MSA-2026-001 Date of Execution 29-September, 2026 Effective Date the date of signature by both Parties' authorised representatives Nature A framework agreement. Of itself it creates no obligation to provide or take capacity, throughput, services or fees; services are contracted Order by Order, each Order together with this Agreement forming a separate contract (Sections 2.1 and 2.2) Service XDT Token Factory — Party B runs the models Party A selects on infrastructure that Party B procures, owns and operates on its own account, and Party A calls an application programming interface hosted by Party B; the models are not limited as to modality (text, image, video, audio or multimodal) and the interface specification is stated in the Order and is not limited to an OpenAI-compatible format; Party A acquires no ownership of, possession of or access to any hardware Documents twenty-four sections plus Schedules 1–12; each transaction is documented by an Order in the form of Schedule 1 Deal terms The tier, Capacity Basis, Region and facility, tenancy, Phases and Target Service Ready Dates, model configuration, Monthly Commitment Fee, overflow rates, Commitment Term, Prepayment, the elected service-level schedule, permitted territories and the applicable data-protection module are all stated in the Order and none of them appears in the body of this Agreement. Currency USD Governing Law laws of the State of New York, USA Dispute Resolution AAA arbitration (New York, one arbitrator, English); injunctive relief reserved to the courts Schedules Schedule 1 Order Form · Schedule 2 Service Description and Technical Specification · Schedule 3 Service Levels and Service Credits (3A availability / 3B committed throughput) · Schedule 4 Service Readiness Test Protocol (4A / 4B) · Schedule 5 Acceptable Use Policy · Schedule 6 Security, Logging and Audit · Schedule 7 Data Protection and Data Compliance · Schedule 8 Export Control and Cross-Border Compliance · Schedule 9 Customer Weights and Bring-Your-Own Model · Schedule 10 Change Control and Supplementary Orders · Schedule 11 Output Content, Abuse Prevention and Allocation of Responsibility · Schedule 12 Customer Eligibility and Conduct Undertakings

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 2 of 69 Document Architecture and Order of Precedence The table below is the whole document set. How to read it: the body of this Agreement carries the legal and commercial protections that do not change from deal to deal — it is signed once and endures; each transaction and each expansion is documented by an Order alone; Schedules 2 to 10 are standard modules switched on by the Order. The order of precedence on conflict is set out in Section 2.4 and repeated in the last column of this table. Layer Document Contents Signed Precedence 1 Body of this Agreement (Sections 1–24) the legal and commercial protections that do not vary from deal to deal; contains no deal values once the six Sections listed in 2.4(a) rank first; the rest rank below an Order 2 Order (in the form of Schedule 1) every commercial and technical term of that transaction (Schedule 1, §§1–11) per transaction prevails over the remainder of the body and the Schedules as to the matters it states 3 Supplementary Order (Schedule 10) expansion, reduction, phase adjustment, configuration change and other commercial changes to an existing Order as needed ranks with the Order; as to its subject matter the later prevails 4 Schedules 2–12 standard modules; Schedules 3 and 4 each have an A and a B version elected in the Order, Schedule 7 has three jurisdictional modules, Schedule 11 applies wherever generative models are served, and Schedule 12 applies to every Order and cannot be excluded with this Agreement below an Order and the body 5 Party B's technical documentation API reference, operations handbook, status page; Party B may update these unilaterally but not so as to diminish service levels or security controls not signed lowest The Parties Party A (Customer) Legal Name XPERT SOFTWARE SOLUTIONS PTE. LTD. Short Name "Customer" Place of Incorporation Singapore Registration No. UEN 201320369H Registered Address 21 Woodlands Close, #07-01, Primz Bizhub, Singapore 737854 Notice Address 21 Woodlands Close, #07-01, Primz Bizhub, Singapore 737854 Contact Cherie Huang (Strategic Advisor) Email [***] Phone [***] Party B (Supplier) Legal Name XDT Infrastructure I, LLC

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 3 of 69 Short Name "XDT" / "Party B" Place of Formation State of Delaware, USA Registration No. Delaware File No. 10764583 Operating Brand XDT — Private AI Cloud (xdt.com) Notice Address 1475 Thorndale Ave, Suite A, Itasca, IL 60143, USA, Attn: Legal Email legal@xdt.com (with copy to sales@xdt.com) Order-specific contacts are in §10 of the relevant Order Phone +1 (312) 709-8450 Parent (Support Provider) Legal Name Quanome Technologies, Inc. Listing Nasdaq: QNME (a company listed on the Nasdaq Stock Market) · SEC CIK 1996192 Incorporation State of Nevada, USA Role provides parent support for Party B's obligations under this Agreement and each Order under Section 20.4; the Parent is not a service provider This XDT Token Factory Master Services Agreement (this "Agreement") is made as of the Effective Date between Party A and Party B identified above, with the Parent joining solely for the purposes of Section 20.4. Party A and Party B are collectively the "Parties" and individually a "Party". WHEREAS: (a) Party B procures, owns and operates NVIDIA accelerated computing infrastructure on its own account and is the end user and operator of record of such hardware; (b) Party A wishes to obtain inference services in which Party B runs the models and Party A calls an API, and not to acquire ownership, possession or custody of any hardware; and (c) the Parties wish first to settle the legal and commercial terms of such services in a long-form framework, and then to agree the capacity, configuration, price and term of each transaction in an Order, so that the same terms need not be renegotiated transaction by transaction. NOW THEREFORE the Parties agree as follows: 1. Definitions and Interpretation The definitions in this Section apply throughout this Agreement and every Order. Where a definition refers to what "the Order states", the content is fixed by that Order and is not provided for in the body of this Agreement (Section 2.1). 1.1 "Affiliate" means any entity that directly or indirectly controls, is controlled by, or is under common control with a Party; "control" means direct or indirect ownership of more than 50% of the equity or voting rights, or the right to direct the management decisions of an entity by contract or otherwise. 1.2 "Allocation Unit" means the smallest unit in which Party B allocates serving capacity for the relevant generation: for the B300 generation, a node (8 × NVIDIA B300 GPUs per node); for rack-scale generations, a rack. The applicable generation and composition are stated in the Order. 1.3 "Applicable Laws" means any law, regulation, rule, order, administrative decision or requirement of a competent authority having jurisdiction over a Party or over the performance of this Agreement, including U.S. export control and sanctions laws. 1.4 "Acceptable Use Policy" or "AUP" means Schedule 5. 1.5 "Business Day" means a day on which banks are open in New York. 1.6 "Capacity Basis" means the quantity of serving capacity, in Allocation Units, that Party B holds for an Order as stated in that Order. The Capacity Basis is a commitment as to quantity (and, where the Order elects a dedicated tenancy, as to dedication) and does not point to any identified hardware; Party B retains its rights under Section 14.3 to configure, substitute and migrate (Section 4.1).

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 4 of 69 1.7 "Commitment Term" means, for a Phase, the period stated in the Order running from the Service Ready Date of that Phase. Each Phase has its own Commitment Term (Section 19.2). 1.8 "Customer Content" means the prompts, inputs, outputs and files submitted by Party A through, or generated by, the Service Endpoint. 1.9 "Customer Weights" means model weights, adapters, tokenisers and inference configuration files delivered by Party A for hosting by Party B under Schedule 9. 1.10 "Dedicated Serving Pool" means, where the Order elects a dedicated tenancy, the serving capacity made up of the number of Allocation Units stated as the Capacity Basis in that Order, carrying Party A's workloads only and physically isolated in accordance with Section 3.3. Where the Order does not so elect, the service is provided on Party B's shared serving capacity with per-tenant logical isolation. 1.11 "Phase" means each tranche of capacity listed in an Order. Each Phase has its own Service Readiness Test, Service Ready Date, Commitment Term and Monthly Commitment Fee. 1.12 "Monthly Commitment Fee" means the fee per Service Month stated in the Order for a Phase. The Monthly Commitment Fee is payable irrespective of utilisation: it is the consideration for Party B holding and operating the serving capacity for that Phase for Party A (Section 7.1). 1.13 "Order" means a document executed by both Parties in the form of Schedule 1 and referring to this Agreement; "Supplementary Order" means a document varying an existing Order under Schedule 10. Orders and Supplementary Orders take effect on signature by both Parties' authorised representatives (Section 2.2). 1.14 "Overflow" means, where the Order permits overflow, tokens served from Party B's shared capacity rather than from the serving capacity of that Order (Section 7.2). 1.15 "Prepayment" means the prepaid service fees payable by Party A under Section 8 and the Order, applied against the Monthly Commitment Fees of the relevant Phase in accordance with Section 8.2. 1.16 "Region" means the XDT region stated in the Order within which inference is processed (Section 3.4). 1.17 "Services" means the XDT Token Factory services provided by Party B under an Order, this Agreement and Schedule 2. 1.18 "Service Endpoint" means the application programming interface designated by Party B for the relevant Order and the project credentials issued for that Order. The interface specification is stated in the Order, including the protocol and address, endpoint paths, request and response formats, the invocation mode (synchronous, streaming, or asynchronous task submission and retrieval) and whether an OpenAI-compatible format is used. The Service Endpoint is not limited to any particular interface standard or modality; Party B may provide different endpoints and interface specifications for different modalities or models. 1.19 "Service Month" means a calendar month. 1.20 "Service Levels" means the version of Schedule 3 elected in the Order: Schedule 3A (availability) is the default and applies where the Order makes no election or the election is unclear; Schedule 3B (committed throughput) applies only where the Order expressly elects it (Sections 5.1 and 5.2). 1.21 "Service Readiness Test" means the test run on a Phase under the version of Schedule 4 elected in the Order; "Service Ready Minutes" means the written minutes signed by both Parties for that Phase recording that the test has passed; "Service Ready Date" or "SRD" means the date of passing recorded in those minutes. The Commitment Term, the Service Levels and billing all run from the SRD — not from the date of signature (Section 4.5). 1.22 "Total Commitment Value" means the sum of the Monthly Commitment Fees over the Commitment Term of a Phase. 1.23 "Output Unit" means the unit stated in the Order for each model configuration by which that configuration's output is metered: for text and multimodal conversational models, a token (as counted by the tokeniser of the deployed model); for image models, an image; for video models, a second or a frame; for audio models, a second of audio; or such other unit as the Order states. An Output Unit is a unit of measurement, not property, and is not a quantity commitment of any kind save where the Order expressly commits to one under Schedule 3B (Section 5.2). Where the Order states no Output Unit, the default metering unit of Party B's metering system for that model applies. 1.24 "KYC Materials" means the Customer KYC & Export Compliance Questionnaire (XDT-KYC v1.0) and its attachments submitted by Party A to Party B before execution of this Agreement, any material supplied afterwards at Party B's request, and the updates Party A submits under Section 10.9 and Schedule 12 §2. The KYC Materials are representations made by Party A to Party B, on which Party B relies in entering into this Agreement and each Order.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 5 of 69 1.25 Interpretation: headings are for convenience only and do not affect construction; "including" means "including without limitation"; "writing" includes email; "day" means calendar day; a reference to a statute or regulation includes it as amended or replaced from time to time; a reference to a Schedule includes it as amended from time to time in accordance with this Agreement; and a reference in this Agreement to a "token" means, for a non-text modality, the Output Unit of that modality. 2. Structure of the Agreement, Orders and Order of Precedence This Section is the framework provision. It settles one thing: this Agreement supplies terms, not capacity. No obligation as to capacity, throughput, configuration, price or term arises except under an Order. 2.1 Framework nature. This Agreement sets out the legal and commercial terms on which Party B provides, and Party A takes, XDT Token Factory services. Of itself this Agreement obliges Party B to provide no capacity or service and obliges Party A to take no capacity and to pay no fee, and it contains no minimum purchase, exclusivity or sole-supply arrangement. The tier, Capacity Basis, Region and facility, tenancy, Phases, model configuration, Monthly Commitment Fee, overflow rates, Commitment Term, Prepayment, elected service-level schedule, permitted territories and applicable data-protection module are stated in the Order in every case. 2.2 Formation of an Order. An Order is made in the form of Schedule 1 and takes effect on signature by both Parties' authorised representatives. An Order shall state at least: (a) its number and a reference to this Agreement; (b) the tier and the tenancy; (c) the Capacity Basis and the Phases; (d) the Region; (e) the model configuration; (f) the Monthly Commitment Fee; (g) the Commitment Term; and (h) the elected versions of Schedules 3 and 4. An Order that omits item (f) or item (g) is not formed; an Order that omits item (h) takes Schedules 3A and 4A. A quotation, offer or proposal of Party B is not a commitment until Party A has signed an Order. 2.3 Each Order is a separate contract. Each Order, together with this Agreement and the Schedules it incorporates, forms a separate contract for that transaction, independently performable and terminable. The expiry, termination or breach of one Order does not affect any other Order, save in the circumstances listed in Sections 19.6 (termination for Party A's breach), 10.7 (breach of export controls) and 19.8 (compliance termination), in which Party B may exercise its rights across all Orders at once. 2.4 Order of precedence. In the event of conflict the following order applies: (a) Sections 7 (fees, billing and payment), 8 (prepayment), 10 (export controls, sanctions and end use), 14 (title, possession and operator of record), 17 (limitation of liability) and 19 (term, termination and non-cancellability) of the body of this Agreement; (b) the Orders and Supplementary Orders, as to the matters they state (as between them, the later-signed prevails); (c) the remaining provisions of the body of this Agreement; (d) Schedules 2 to 12; and (e) Party B's technical documentation. An Order may not vary the Sections listed in paragraph (a) unless it does so by express terms identifying the specific Section numbers varied and is separately confirmed in writing by both Parties' authorised representatives. 2.5 Incorporation and election of Schedules. Schedules 1 to 12 form part of this Agreement. Schedule 3 exists in two versions — 3A (availability) and 3B (committed throughput) — and Schedule 4 in two versions — 4A (Service Readiness Test) and 4B (Throughput Baseline Test); each Order elects one of each, and an Order electing 3B shall also elect 4B. The applicable modules of Schedule 7 (GDPR / PIPEDA / CCPA) are ticked in the Order; absent a tick, only §§1–5 of Schedule 7 apply. Schedule 11 applies in full, without election, whenever an Order deploys a generative model; and Schedule 12 applies to every Order and cannot be excluded by an Order. 2.6 Orders by Party A's Affiliates. An Affiliate of Party A may sign an Order as a contracting party, assumes all of Party A's obligations under this Agreement in respect of that Order, and Party A is jointly and severally liable for its performance. Such an Affiliate must first pass Party B's compliance and export-control screening (Section 10.5). Party B may likewise designate an Affiliate as the providing entity for an Order under Section 20.2. 2.7 Term of this Agreement. This Agreement takes effect on the Effective Date and continues until the later of: (a) three years from the Effective Date — after which, if no Order is then in effect, either Party may terminate this Agreement on thirty (30) days' written notice; and (b) the expiry or termination of the Commitment Term of the last Order. Termination of this Agreement does not affect any Order then in effect, which continues on the terms of this Agreement until its own expiry or termination (Section 19.1). 3. Scope and Nature of the Services 3.1 Provision of the Services. For each Order, from the SRD of each Phase and for the Commitment Term of that Phase, Party B shall: (a) hold and operate serving capacity for Party A on the Capacity Basis stated in that Order; (b) deploy and run

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 6 of 69 models on it under the model configuration stated in that Order; (c) make the entire output that capacity produces available to Party A through the Service Endpoint; and (d) maintain the Service Levels under the elected Schedule 3. Technical specifications are set out in Schedule 2. 3.2 What Party A obtains is a service, not hardware. Party A receives inference services invoked through the Service Endpoint with project credentials; Party A acquires no access to, possession of or control over any host, virtual machine, container runtime, orchestration system, storage or hardware, and no leasehold interest in any facility. Neither this Agreement nor any Order constitutes a lease, rental, finance lease, bailment or sale of hardware or of computing capacity; an Output Unit (a token, an image, a second of video and so on) is a unit of measurement, not property capable of possession. Section 14 makes further provision. 3.3 Tenancy (disclosed as it is). The Order elects one of two tenancies: (a) a Dedicated Serving Pool with physical isolation — every Allocation Unit of that Order carries Party A's workloads only and shares no node, GPU or local storage with any other tenant; it is deployed in a dedicated cage or dedicated racks with its own compute-network segment and storage volumes, with access control, CCTV and two-person authorisation subject to the facility's conditions (Schedule 6 §3); or (b) shared capacity with logical isolation (the default) — the service runs on Party B's shared serving capacity with per-tenant logical isolation: separate credentials, quotas, logs and storage scopes. Under either election the exact scope of the isolation boundary is as follows: all inference processing of Customer Content takes place within the serving capacity of that Order. The Service Endpoint is a Party B platform component through which request and response payloads transit and are routed — for that limited purpose it necessarily handles Customer Content — but it uses Customer Content for no purpose other than routing and delivering that request, and does not retain it; the technical boundary is set out in Schedule 11 §10. The control plane (authentication, metering, quota, dashboards, alerting) handles metadata only and never Customer Content. Where (a) is elected, the pool is not used to serve any other customer during the Commitment Term and Party A has the annual facility audit right in Schedule 6 §3. 3.4 Region pinning. Inference is processed within the Region stated in the Order. Party B shall not move processing outside that Region during the Commitment Term of that Order except on Party A's written instruction. Party B may change facility within the Region provided that the service levels, technical specifications and security controls set out in this Agreement, that Order and the elected Schedule 3 are not diminished, and shall give Party A not less than ninety (90) days' prior written notice. Emergency exception: where force majeure, a material security incident, a power or cooling failure, a direction of a competent authority or termination by the facility operator has occurred or is imminent at the facility, such that continuing to operate there would endanger service continuity or security, Party B may relocate within the Region immediately and shall notify Party A in writing within twenty-four (24) hours of starting the relocation, stating the cause, the scope and the expected time to restore; the ninety (90) day notice period does not apply to such a relocation and the service levels, technical specifications and security controls shall not be diminished. The building, the identity of the data-centre operator and the power parameters constitute Party B's Confidential Information; where stated in the Order they are as so stated, and otherwise they are disclosed to Party A separately under Section 13.4. 3.5 Exclusions. The Services exclude: Party A's applications and client software; Party A-side networks and equipment; any judgement as to the fitness of model outputs; professional services not stated in the Order; and the installation or running of Party A's own inference framework, scheduler or any other code on Party B's infrastructure — where Party A requires the latter, it is outside the Services under this Agreement and requires Party B's Master Compute Services Agreement, including its annex on customer software installation and change control. Customer Weights are loaded and run by Party B under Schedule 9 and do not constitute access by Party A to the infrastructure. 3.6 Subcontracting. Party B may perform this Agreement and any Order itself or through its Affiliates, an NVIDIA Cloud Partner or other subcontractors, provided that Party B remains fully responsible for such performance and that subcontracting does not alter the end-user and operator-of-record position set out in Section 14. 3.7 Relationship to Party B's other tiers. Should Party A later move to running its own inference stack on Party B's infrastructure (Private Endpoints or Dedicated Managed Clusters), Party B's Master Compute Services Agreement is executed separately; the positions in Sections 10 and 14 of this Agreement are unchanged. 4. Capacity Basis, Phases and Service Readiness 4.1 Capacity Basis. Party B holds serving capacity for an Order on the Capacity Basis stated in that Order and warrants that, throughout the Commitment Term of each Phase, the number of Allocation Units held for that Order is not below the Capacity Basis for that Phase (save for temporary shortfalls during repair or replacement, such units counting as unavailable under the elected Schedule 3 rather than as a breach of this Section, and Party B restoring the number within a reasonable time). The Capacity Basis is a commitment as to quantity (and, where the Order elects a dedicated tenancy, as to dedication) and not an

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 7 of 69 allocation of any identified hardware: Party B retains its rights under Section 14.3 to configure, substitute and migrate, replacement units being of equivalent specification and, under a dedicated tenancy, likewise dedicated to Party A. What Party A obtains under this Agreement is the tokens that capacity produces and the Service Levels of the elected Schedule 3, not hardware (Section 14). 4.2 Phases. Capacity is made ready in the Phases listed in the Order. Each Phase has its own Service Readiness Test, SRD, Commitment Term and Monthly Commitment Fee; from the SRD of a Phase, the serving capacity for that Order is enlarged by the Capacity Basis for that Phase and the Monthly Commitment Fee stated in the Order for that Phase begins to accrue. 4.3 Readiness. Party B shall, at its own cost and risk, procure, deploy, power, cool, commission and test the capacity for each Phase. Contracts for the facility, power, equipment and operations are entered into by Party B in its own name, and no contractual relationship arises between Party A and any such third party. 4.4 Conditions precedent. Party B's readiness obligation under an Order, and the Target SRD of each Phase of that Order, run from the date on which all of the following are satisfied (the "Readiness Start Date"): (a) a non-disclosure agreement between the Parties is in force; (b) Party A has passed Party B's customer due diligence and export-control screening and has delivered the information required under Schedule 8 §1; (c) the Prepayment stated in that Order has been received; and (d) the model configuration for the first Phase of that Order is fixed. Party B has no procurement or deployment obligation before the Readiness Start Date. 4.5 Service Readiness Test and SRD. Before billing for a Phase starts, the Parties run the Service Readiness Test on that Phase under the version of Schedule 4 elected in the Order. On a passing test the Parties sign the Service Ready Minutes for that Phase, and the date of passing recorded therein is the SRD of that Phase. The Commitment Term, the Service Levels and billing all run from the SRD — not from the date of signature. 4.6 Report, confirmation and re-run. Party B shall issue a test report within two (2) Business Days after each run; Party A shall confirm the result or raise specific written objections within ten (10) Business Days of receipt, failing which, after the reminder under Schedule 4A §3.1, the test is deemed passed. Where the test fails for reasons attributable to Party B, Party B shall re-run it within ten (10) Business Days; if it fails twice on re-run for the same cause, Party A may proceed in respect of that Phase under Section 19.7(b). Where the failure or inability to test results from Party A's configuration materials, Customer Weights, test harness, connectivity or confirming personnel not being ready, that run does not count, Party B re-runs the test once Party A is ready, and the Target SRD for that Phase is extended accordingly. 4.7 Party A's cooperation and substitute testing. Party A shall promptly provide the configuration materials, Customer Weights (if any), traffic (where applicable), credentials, contacts and confirming personnel required for the test under the elected Schedule 4. If Party A does not do so within ten (10) Business Days of the test date notified in writing by Party B, Party B may complete the test on its own and issue the report; the date of passing recorded in that report is deemed the SRD of that Phase, and the Commitment Term and billing run from that date. 4.8 Sole remedy for readiness delay. Unless the Order provides otherwise, where the SRD of a Phase occurs after the Target SRD for that Phase stated in the Order for reasons attributable to Party B, service credits accrue from the first (1st) day of delay at one hundred per cent (100%) of one day's Monthly Commitment Fee for that Phase per day of delay, capped in aggregate at three month's Monthly Commitment Fee for that Phase, and are applied from the first invoice for that Phase. If the delay exceeds ninety (90) days, Party A may terminate that Phase by written notice (or, where it is the first Phase of that Order, that Order) and recover amounts paid and unused, including the Prepayment attributable to that Phase. That right lapses once Party B has given the deployment-completion notice for the Phase under Schedule 4A §3.1, provided the Service Readiness Test is then passed or deemed passed; where the test is so passed, the days of delay end on the date of that notice. This Section is Party A's sole remedy for readiness delay. Delay caused by Party A's failure to cooperate (Sections 4.6 and 4.7) or by force majeure is excluded from the days of delay; delay by Party B's upstream suppliers, the facility operator or the original manufacturer is not a cause outside Party B's responsibility — Party B carries its own upstream risk — save in three cases, in each of which the burden of proof is on Party B: (a) the delay is directly caused by a force majeure event as defined in Section 18.1 and Party B has given notice under Section 18.2; (b) the delay is directly caused by a change in applicable law, export controls or sanctions, or by a direction of a competent authority; or (c) the delay is directly caused by NVIDIA or the original manufacturer failing to deliver the equipment on the timelines committed to Party B, and Party B provides Party A with documentation showing that it had contracted for a sufficient quantity on timelines that would have met the Target SRD, together with a copy of the revised delivery timeline received from NVIDIA or the original manufacturer. In each case those days are not counted under this Section; where the cause continues beyond one hundred and twenty (120) days either Party may terminate under Section 18.3 and settlement follows Section 8.3. 4.9 Adjustment of Phases and Capacity Basis. Any addition, acceleration or deferral of a Phase, and any adjustment of the Capacity Basis, requires a Supplementary Order (Schedule 10) or a written instrument signed by both Parties.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 8 of 69 5. Service Levels and Service Credits 5.1 Elected schedule. The Service Levels for an Order are those of the Schedule 3 elected in that Order: Schedule 3A (availability of Allocation Units and of the Service Endpoint) or Schedule 3B (committed throughput). Absent an election, Schedule 3A applies. The elected schedule sets out the committed metrics, the measurement methodology, the excluded time and the credit tiers. 5.2 No throughput or output commitment by default. Save where an Order expressly elects Schedule 3B and states committed figures in it, Party B gives no commitment or warranty as to Output Units per minute (tokens, images, seconds of video and so on), requests, task completion time, time to first token, output speed or any other measure of output. Output depends on the model, precision, context length, concurrency and workload characteristics selected by Party A, all of which are within Party A's control. The reference throughput recorded under Schedule 4 and the figures shown on the dashboard are for information only, are not commitments, and give rise to no credit, termination right or other remedy. The Monthly Commitment Fee purchases the serving capacity and Party B's operation of it, not output (Section 7.9). 5.3 Service credits as sole remedy. Where the commitments of the elected Schedule 3 are not met, service credits are calculated under that schedule. Credits of different categories are not cumulative for the same Service Month — the higher applies — and credits in any Service Month shall not exceed fifty per cent (50%) of the Monthly Commitment Fee for that Phase for that month. Credits are applied to the next invoice and are not paid in cash. Service credits are Party A's sole and exclusive remedy for failure to meet the Service Levels and do not constitute liquidated damages or a pre-estimate of loss, save as provided in Section 5.7 (where applicable) and Section 19.7. Party A shall claim in writing within the period stated in the elected Schedule 3, with request identifiers and timestamps, and Party B confirms against metering data within ten (10) Business Days; a claim not made in time is waived. 5.4 Excluded time. Unavailability or shortfall arising from the causes listed in §3 of the elected Schedule 3 is not counted in the calculation of the Service Levels — in outline: maintenance, Party A-side causes, suspension or throttling under this Agreement, configuration changes and a model becoming unavailable, force majeure, and any other cause not attributable to Party B or Party B-managed infrastructure. The elected Schedule 3 governs as to the full list. 5.5 Reporting and dashboard. Party B shall issue the monthly report required by the elected Schedule 3 by the fifth (5th) Business Day of each month and shall give Party A access to a dashboard showing per-minute throughput, latency and error rates for Party A's projects. Where Schedule 3A is elected, dashboard figures are for information only. 5.6 Metering record. Party B's monitoring and metering systems are the system of record for the Service Levels, Overflow and usage; Party A may audit the metering controls under Section 12.3. Where Party A disputes the metering for a month, the Parties reconcile Party B's metering data against Party A's request logs (request identifiers and timestamps), and the reconciliation governs. 5.7 Sustained-shortfall exit (applies only where the Order elects Schedule 3B and ticks this Section). Where an Order elects Schedule 3B and ticks this Section, if Monthly Throughput Attainment for a Phase of that Order is below the exit threshold stated in Schedule 3B in three (3) consecutive Service Months, Party A may terminate the commitment for that Phase (or, where every Phase of that Order is so affected, that Order) on thirty (30) days' written notice without an early-termination charge; the Prepayment is governed by Section 8.3. Where an Order elects Schedule 3A, failure to meet the Service Levels gives rise to no termination right. 6. Model Configuration, Capacity Adjustments and Change Control 6.1 Model configuration. Party A specifies the model configuration in the Order: a catalogue model or Customer Weights (Schedule 9), the context-length setting, the concurrency setting, precision and quantisation, and the retention setting. Party B deploys and runs models on that Order's serving capacity accordingly and provides them through the Service Endpoint. A model configuration is a deployment setting and is not a commitment as to throughput, latency or output (Section 5.2). 6.2 Configuration changes. Party A may request in writing under Schedule 10 a change to the model configuration (a different model, context length, concurrency, precision or retention setting). Up to two (2) routine changes per Phase per calendar month are free of charge; a change beyond that frequency, or one requiring a new model to be brought into the catalogue, a re-run of the baseline test, a change to network or storage topology, or an estimated effort exceeding forty (40) person-hours, is a complex change for which the Parties agree the implementation period and the fee separately and record them in a Supplementary Order, and Party B is not bound by the period below. Party B implements a routine change within ten (10) Business Days and verifies model loading and Service Endpoint connectivity under the elected Schedule 4. A configuration change does not alter the Monthly Commitment Fee, the Commitment Term or the SRD; unavailability during implementation is excluded from the Service Levels (Section 5.4). Where the change requires serving capacity beyond that

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 9 of 69 Order's Capacity Basis, Section 6.3 applies. Party B may decline a configuration on security, licensing, compliance or stability grounds, giving reasons so far as reasonably practicable. 6.3 Expansion. Subject to Party B's available capacity, Party A may at any time request in writing an enlargement of the serving capacity of an Order or an additional Order; Party B responds with a Supplementary Order or a new Order, handled as an additional Phase with its own Target SRD, Commitment Term and Monthly Commitment Fee. Where a Region is oversubscribed, Party B allocates capacity first to requests with longer commitment terms. Party B is under no obligation to accept any request for expansion. 6.4 Reduction. The serving capacity of an Order may be reduced at renewal of that Order only, unless that Order provides otherwise. 6.5 Model versions and deprecation. Version updates of a model stated in an Order (including security and minor-version updates) are applied automatically by Party B in the ordinary course of operations and notified to Party A through the dashboard or release notes; Party A may request pinning to a particular version where Party B supports it. A change to a different model requires Party A's written request or agreement under Section 6.2. Where Party B intends to retire a catalogue model, it shall give not less than ninety (90) days' written notice and use reasonable efforts to provide a successor; emergency retirement required for security, licensing or legal reasons is not subject to that notice period but shall be notified immediately, with a successor provided as soon as practicable. Where a model can no longer be provided because a licensor withdraws its licence, the law prohibits it or the original developer ceases support, that is not a breach by Party B; Party A may select another catalogue model or deliver Customer Weights, and the Monthly Commitment Fee, the Commitment Term and the Prepayment are not adjusted — what Party B commits to is the serving capacity and its operation, not a particular model. Where the Order elects Schedule 3B, a model substitution is re-baselined under Schedule 4B and, if no successor has passed a baseline within sixty (60) days of the notice, Party A may reduce the commitment for that configuration pro rata or terminate it without an early-termination charge. 6.6 Model licences. Party B provides catalogue models on the terms of its licences with the licensors; restrictions in or changes to those licence terms are not a breach by Party B. Party A is responsible for the licensing and export-control classification of Customer Weights (Schedule 9). 6.7 Fees irrespective of utilisation; no roll-over. The Monthly Commitment Fee does not vary with Party A's actual usage; unused capacity is not rolled over, credited or refunded, unless the Order provides otherwise. The capacity is held and operated for Party A whether or not the traffic arrives. 6.8 Effect of a Supplementary Order. Where a Supplementary Order is inconsistent with this Agreement, it prevails as to the matters it states, save for the Sections listed in Section 2.4(a). 7. Fees, Billing and Payment 7.1 Monthly Commitment Fee. Party A shall pay the Monthly Commitment Fee for each Phase as stated in the Order. The Monthly Commitment Fee is payable irrespective of utilisation: it is the consideration for Party B holding and operating serving capacity for Party A, not for output. 7.2 Ownership of output and overflow. All output produced by the serving capacity of an Order, of whatever modality, belongs to Party A and is not separately charged — the Monthly Commitment Fee covers that capacity's entire output. Requests beyond that capacity's capability at the time are rate-limited by Party B (HTTP 429) and do not overflow to shared capacity; only where the Order permits overflow is traffic overflowing to Party B's shared capacity metered as Overflow at the rates stated in the Order (per Output Unit; input and output priced separately, or priced per task), aggregated per Service Month and billed in arrears. Party A acknowledges that overflow traffic is processed outside the isolation boundary of that Order's serving capacity (Section 3.3). Where the Order elects Schedule 3B, output above the Committed Throughput is neither cut off nor separately charged, but no throughput commitment applies to it. 7.3 Billing and payment terms. Billing runs from the SRD of each Phase. Unless the Order provides otherwise, the Monthly Commitment Fee is billed monthly in advance: Party B invoices the Monthly Commitment Fee for the next Service Month on or before the tenth (10th) day of the preceding month, and Party A shall pay by USD wire transfer to Party B's designated account no later than the twenty-fifth (25th) day of the month preceding that Service Month; the first invoice, for the month in which the SRD falls, is pro-rated from the SRD on actual days and is payable within ten (10) days after the SRD. Overflow charges (if any) are billed in arrears with the next invoice. Party A shall not set off any amount other than service credits confirmed in writing by Party B. 7.4 Payment account. Party A shall pay only into: (i) a bank account in Party B's own name stated on the invoice or in the Order; or (ii) an account in the name of the Parent (Quanome Technologies, Inc.) stated in the Order and designated as Party

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 10 of 69 B's collection account — payment into that account constitutes good discharge to Party B, the Parent holds such amounts solely as Party B's collection agent, and Party B may switch the collection account to an account in its own name by a written payment direction verified by call-back. Party B may, at its discretion, agree in writing to accept payment on Party A's behalf from a third party designated by Party A, provided that: (a) the payer has first passed Party B's screening under Section 10.5, including as to its ultimate beneficial owners and source of funds; (b) the payer, Party A and Party B have signed a payment agreement in a form acceptable to Party B under which the payer pays solely on Party A's behalf and acquires no right under this Agreement or any Order; (c) payment is made from an account in the payer's own name; (d) Party A remains fully liable for every amount due; and (e) any refund is paid only to the account from which the payment was received. Financing exception: where Party B assigns or pledges its receivables for project financing under Section 20.3, Party B may by a written payment direction signed by its authorised representative nominate either a controlled collection account in Party B's own name or an account of the assignee or its agent; the direction must identify the invoices or periods affected and is subject to the same call-back verification by Party A. Once verified, payment by Party A in accordance with that direction constitutes good discharge. Party A's refusal without proper cause to act on a verified payment direction does not affect the due date or the accrual of interest on those amounts. Party A shall not act on an unverified payment direction. Changes of account details take effect only upon written confirmation by both Parties verified by call-back. Source of funds. Party A represents and warrants that every amount under this Agreement and the Orders is paid from an account in Party A's own name (or, where agreed under this Section, in the name of an approved payer) and from lawfully obtained funds, and this representation applies equally to any approved payer. Where any amount is funded in whole or in part by third-party financing or a shareholder loan, Party A shall, before payment, disclose to Party B in writing the name and place of incorporation of the provider of the funds and cooperate in Party B's screening of that provider under Section 10.5. Party B may decline funds whose source it cannot verify; declining is not a breach by Party B and does not cause the amount to be treated as paid. 7.5 Late payment. Late payments bear interest at 0.05% per day, or the maximum rate permitted by applicable law if lower. If a payment is more than thirty (30) days overdue, Party B may suspend the service under Section 9.6; the Monthly Commitment Fee continues to accrue during suspension and the affected time is excluded from the Service Levels. 7.6 Taxes. Prices are exclusive of tax. Party A shall bear all sales, use, value added, goods and services and similar transaction taxes arising under this Agreement and any Order. If applicable law requires Party A to withhold any tax, Party A shall gross up the payment so that Party B receives the amount it would have received absent the withholding, and shall provide tax receipts to Party B within thirty (30) days. Taxes on Party B's own income are borne by Party B. 7.7 Disputed amounts. If Party A disputes an invoiced amount in good faith, it shall notify Party B in writing with reasons before the due date and shall pay the undisputed portion when due. A valid dispute must identify, line by line, the invoice items and amounts disputed and the facts relied on, with supporting evidence; a notice that does not do so is not a dispute under this Section and the amount falls due as invoiced. The Parties shall complete a reconciliation within thirty (30) days of the dispute being raised. If the dispute is not resolved by the end of that period, Party A shall within a further five (5) Business Days pay the disputed amount into a third-party escrow account jointly designated by the Parties or, where the Parties so agree in writing, pay it to Party B subject to adjustment once the dispute is resolved; if Party A does neither, the amount is treated as undisputed and bears interest from the original due date. Once resolved, the disputed portion is payable within ten (10) Business Days after resolution; if the dispute is not upheld, interest under Section 7.5 accrues from the original due date. 7.8 Price fixed. The Monthly Commitment Fee and any overflow rates are fixed for the Commitment Term and are not subject to adjustment for changes in power, equipment, model licensing or labour costs. Pricing for any renewal term is to be separately agreed. 7.9 Scope of the consideration. The Monthly Commitment Fee purchases the serving capacity stated in the Order, Party B's operation of it and the Service Levels of the elected Schedule 3. Party B gives no commitment as to Output Unit counts, throughput, latency or any measure of output (Section 5.2), nor as to the content of the output or the accuracy, reliability, lawfulness or commercial value of model outputs (Section 15.4 and Schedule 11). 7.10 Costs of recovery. Where Party A is late in paying any amount under this Agreement or any Order, or Party B takes any step to enforce its rights to payment, its settlement rights under Section 8.3 or amounts payable after termination, Party A shall indemnify Party B against all reasonable costs so incurred, including external legal fees, the fees of the arbitral institution and the arbitrators, expert fees, collection costs, the costs of interim and enforcement measures, and the costs of enforcing an award or judgment. This item is independent of the indemnity provisions and is not conditional on Party B succeeding on the whole of the principal claim — Party B is entitled to its costs where it succeeds on the substantial part of what it claimed. Costs claimed under this item are not subject to the cap (see Section 17.3). For the avoidance of doubt, this item applies equally to a claim brought by Party A against Party B that does not succeed.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 11 of 69 8. Prepayment 8.1 Where an Order provides for a Prepayment, Party A shall pay it upon execution of that Order (or at the Phase milestones stated in that Order); the percentage, amount and timing are as stated in the Order. 8.2 The Prepayment is held by Party B and is applied month by month from the first Service Month against the Monthly Commitment Fee for that month in the proportion the Prepayment bears to the Total Commitment Value (as stated in the Order), until the Prepayment is exhausted, Party A paying the unapplied balance for that Service Month in cash. It does not bear interest prior to application and is non-refundable save as provided in Section 8.3. 8.3 Refund. Party B refunds the Prepayment only where a Phase is terminated before its SRD under Section 4.8 or Section 19.7(a)–(b) for reasons attributable to Party B, or under Section 18.3 by reason of force majeure — that is, where the serving capacity for that Phase is not delivered — in which case Party B refunds the Prepayment attributable to that Phase, without interest. Otherwise, whatever the ground on which this Agreement, any Order or any Phase is terminated (including force majeure termination under Section 18.3 after the SRD, Section 19.7(c)–(d) and Section 19.8), Monthly Commitment Fees paid and the Prepayment are not refundable; Party B ceases to charge Monthly Commitment Fees from the date of termination. Once the serving capacity for a Phase has been delivered (SRD), Party B has no further refund or compensation obligation in respect of that Phase; Party A's remedy for the Service Levels is limited to the service credits under Section 5.3. Where Party A terminates early or repudiates in breach, Party B applies the Prepayment against losses and amounts payable arising from the breach, reserving the right to claim any shortfall. The Prepayment is neither a deposit nor security: it is prepaid service fees applied in accordance with Section 8.2. Read together with the non-cancellability provisions in Section 19. 8.4 Party B may grant security over, or assign, the Prepayment and its receivables under this Agreement and the Orders for the purposes of its project financing, provided that no such arrangement increases Party A's obligations or diminishes Party A's rights. Party B shall notify Party A in writing of any such arrangement. 8.5 Credit assurance. An Order may state the credit assurance Party A is to provide, in the form elected in that Order — a bank standby letter of credit, a guarantee from a parent of adequate financial standing, or a rolling payment security deposit, or such other form as the Parties agree in writing — in the amount and for the period stated in the Order, and as a general rule not less than the aggregate of the prepayment and service fees for twelve (12) months from the trigger date. Party A shall provide or top up that credit assurance within twenty (20) Business Days of Party B's written notice on any of the following objective trigger events: (a) Party A has been late in payment by more than fifteen (15) days twice in any twelve (12) month period, or by more than thirty (30) days on a single occasion; (b) a change of control of Party A (other than one referred to in Section 20.1); (c) Party A, or an Affiliate providing security for it, is downgraded below investment grade by any rating agency, or its auditor issues a going-concern qualification; (d) Party A defaults on material indebtedness or becomes subject to a petition for bankruptcy, liquidation, reorganisation or receivership; or (e) where Party A is a project entity established for the Order, its net assets fall below twenty per cent (20%) of the amounts payable for the remainder of the term. Failure to provide or top up on time is a material breach; Party B may suspend and may terminate under the termination provisions. Drawing on the credit assurance does not prevent Party B recovering any excess. Party B shall consent in writing to the release of the assurance once the relevant risk has ceased. 9. Party A's Obligations and Acceptable Use 9.1 Party A shall comply with the Acceptable Use Policy set out in Schedule 5 and with Party B's technical documentation as published from time to time, and is responsible for the acts and omissions of its authorised users. 9.2 Party A is responsible for the lawfulness of Customer Content and Customer Weights, and shall ensure that it holds all rights, licences and consents necessary for such use. 9.3 Credentials, access and resale. Party A shall send traffic through the project credentials issued for the relevant Order so that it can be attributed and metered; shall safeguard those credentials; and shall not hand credentials issued by Party B to any third party or permit any third party to invoke the service in Party A's name. Party A may use the output of the service (including inference capacity metered in tokens) in its own products and services, and may resell or distribute it to its customers and resellers through Party A's own endpoints and credentials; where Party A thereby has downstream users (including the customers of its resellers), Schedule 8 §5 applies in full, and Party A is answerable to Party B for the acts of its downstream users as for its own. For the purposes of this Agreement, resale or distribution under this Section is treated as Party A providing capability downstream through its own products, and every provision of this Agreement and its Schedules concerning downstream users applies accordingly.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 12 of 69 9.4 Content monitoring (disclosed as it is). Where the Order elects a Dedicated Serving Pool, Party B performs compliance monitoring at the metadata layer only (access identity, source geography, utilisation, anomalous patterns) on the single-tenant hardware basis, and neither inspects Customer Content nor applies automated content filtering. Where the Order is for shared capacity, Party B additionally applies automated abuse filtering consistent with its published Acceptable Use & Export Control Policy; a filtered request is not a conforming request. In either case Party A's acceptable-use obligations under Schedule 5 are not reduced; where Party B detects red flags from metadata, complaints or notices from competent authorities, it proceeds under Sections 9.6 and 10. 9.5 Traffic discipline. Party A shall notify Party B in writing before any material change in request shape, model or concurrency requirements so that the configuration can be adjusted under Section 6.2, and shall maintain its own connectivity and client-side retry behaviour (including exponential back-off). Requests beyond the capability of that Order's serving capacity at the time are rate-limited by Party B (HTTP 429); that is not unavailability and gives rise to no remedy. Where the Order elects Schedule 3B, Party A shall keep traffic within the Named Profile stated in that schedule and shall not construct load that materially departs from the profile assumptions for the purpose of manufacturing Demand Windows or triggering credits. 9.6 Suspension. Party B may suspend all or part of the service under one or all Orders upon written notice if: (a) Party A's payment is overdue beyond the period in Section 7.5; (b) Party A breaches the AUP in Schedule 5, Section 10, Schedule 8, Schedule 11 or Schedule 12, or an Eligibility Event under Schedule 12 §1 occurs; (c) Party B reasonably considers that continued provision would cause it to breach applicable law or would endanger the security of the platform, the network or other customers; or (d) Party A fails to deliver the annual attestation under Schedule 8 §6. Except in the emergency circumstances of (b) and (c), Party B shall first allow a cure period of five (5) Business Days. Suspension does not relieve Party A of its payment obligations, and time during suspension is excluded from the Service Levels. 10. Export Controls, Sanctions and End-Use Undertakings This Section may not be deleted, weakened or varied by an Order (Section 2.4). The NVIDIA B300 is a high- performance computing item subject to the strict jurisdiction of the U.S. Department of Commerce, Bureau of Industry and Security (BIS). This Section is the compliance basis on which Party B holds and operates such items and provides inference capability to Party A as a cloud service. The operational screening, geographic control, logging and audit procedures are set out in Schedule 8. 10.1 Party A undertakes to comply with U.S. export control laws (including the Export Administration Regulations), economic sanctions laws (including the sanctions programmes administered by OFAC), and the laws of the Region and of Party A's places of business. 10.2 Restricted parties. Party A represents and warrants that neither it nor its directors, officers, controlling shareholders or ultimate beneficial owners is listed on the U.S. Entity List, Denied Persons List, Unverified List, Military End-User List or SDN List, or on the corresponding lists of the EU, the UN, the UK or Canada, nor is controlled by any such person. Party A shall notify Party B in writing within three (3) Business Days of becoming aware of any change. 10.3 Prohibited uses. Party A shall not use the service for: (a) any military application, government classified programme or cyber-attack activity; (b) the design, development, production or use of nuclear, chemical or biological weapons or missiles; (c) unauthorised cryptanalysis or circumvention of security controls; or (d) any other end use prohibited by applicable export control laws. 10.4 Anti-circumvention. Party A shall not, directly or indirectly and by any technical means (including sublicensing access, proxying, tunnelling, API forwarding or resale), make the service available in or to any comprehensively sanctioned country or territory, or to any person listed under Section 10.2. Party A shall not circumvent Party B's API-layer geofencing or access controls. 10.5 End-user and end-use cooperation. At Party B's reasonable request, Party A (and any of its Affiliates ordering under Section 2.6) shall provide information and supporting documents as to its identity, ownership structure, ultimate beneficial owners, end use and end users, and shall cooperate with compliance reviews by Party B, its upstream suppliers and governmental authorities. Party A acknowledges that Party B has undertaken obligations in respect of such reviews to its suppliers and to the competent authorities. 10.6 Territorial restriction. The service may be accessed only from the territories stated in the Order; Party B enforces geofencing at the API layer and may block known VPN, proxy and Tor exit nodes. Access from any other territory requires Party B's prior written consent; Party B may first need the consent of its upstream suppliers and therefore gives no undertaking as to turnaround time.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 13 of 69 10.7 Consequences of breach. Upon any breach of this Section, Party B may suspend or terminate the service under all Orders immediately and without any cure period, and Party A shall bear all resulting losses and legal liabilities. Such termination is treated as termination for Party A's breach under Section 19.6 and the Prepayment is non-refundable. Action taken by Party B under this Section does not constitute a breach by Party B and gives rise to no liability. 10.8 Party B's reservation. Party B may decline to provide any information, access or service that it reasonably considers would cause it to breach applicable law, its suppliers' compliance undertakings or its internal compliance policies, and no such refusal constitutes a breach. 10.9 Ongoing notification. Party A shall notify Party B in writing within three (3) Business Days of any of the following: (a) a change in end use or in the nature of the workloads; (b) a change in the persons actually using or benefiting from the service; (c) a change in Party A's control, principal ownership or directors; (d) any change in or addition to the territories from which the service is accessed; (e) Party A, its Affiliates, shareholders, directors, officers or ultimate beneficial owners becoming listed on any list referred to in Section 10.2, or becoming subject to an investigation in that connection; or (f) Party A becoming aware of any fact that may cause Party B to breach its export control undertakings. Party A acknowledges that Party B is subject to ongoing notification obligations of the same nature towards its upstream suppliers and the competent authorities, and that Party A's notice is Party B's sole source of that information. Late or inaccurate notice entitles Party B, in addition to its rights under Section 19.6, to report to the competent authorities as required by law. 10.10 Downstream access. Where Party A provides capabilities based on the service to its own customers as part of its own products or services, or resells or distributes the service to its customers or resellers under Section 9.3, Party A shall: (a) screen each downstream user against the lists referred to in Section 10.2 before granting access, and retain the records; (b) bind downstream users by contract to Sections 10.3 (prohibited uses), 10.4 (anti-circumvention) and 10.6 (territorial restriction); (c) retain access, usage and administrative logs in accordance with Schedule 8; (d) where a downstream user in turn provides the service to its own customers, require it by contract to perform obligations equivalent to (a) to (c) in respect of those customers; and (e) state in §8 of the Order the name and place of incorporation of each of its direct resellers, and notify Party B in writing within ten (10) Business Days after any change or addition. The applicable standards are set out in Schedule 8 §5. 10.11 API-only access. The Services under this Agreement give Party A no access at the host, container-runtime, orchestration or hardware level, and Party A shall not install or run any software on Party B's infrastructure (Sections 3.5 and 14.6). Customer Weights are hosted by Party B under Schedule 9 and do not constitute access by Party A to the infrastructure. 11. Data Protection and Data Compliance 11.1 Roles. In respect of personal data contained in Customer Content ("Personal Data"), Party A is the controller (or the equivalent role under applicable law, such as "business") and Party B is the processor (or "service provider"). Party A alone determines the purposes, scope and legal basis of the processing; Party B processes Personal Data only on Party A's instructions and for the purpose of providing the Services to Party A. The applicable data-protection module (GDPR / PIPEDA / CCPA or other) is ticked in the Order and set out in Schedule 7. 11.2 The retention setting determines the data footprint. The Order states the retention setting for each configuration. Where zero retention is selected, Party B retains no prompt or output for any purpose beyond serving the request in question and accordingly holds no Personal Data on a continuing basis, and its obligations under this Section are correspondingly limited to the period of processing; where limited retention is selected, retention is only for the purpose designated in the Order and for the stated number of days. Logs contain metadata only (request identifier, timestamp, Output Unit counts, source geography, model identifier) and no content. "Zero retention" refers to the content layer; the metadata layer is retained for 10 years under Schedule 8 §3 and cannot be switched off; and incident evidence is preserved on an event-triggered basis under Schedule 11 §§9 and 12 — the three layers are distinguished in Schedule 7 §1 and the technical boundary of zero retention is in Schedule 11 §10. 11.3 Party B's obligations. Party B shall: (a) not use Personal Data for its own purposes, not use it to train any model of Party B or of any third party, not sell Personal Data and not use it for cross-context behavioural advertising; (b) implement and maintain the technical and organisational security measures set out in Schedule 6; (c) bind personnel with access to Personal Data to confidentiality and train them, granting access by role and on a least-privilege basis; (d) notify Party A within seventy- two (72) hours of confirming a security incident involving Personal Data (Section 12.4); (e) assist Party A, so far as reasonably necessary, with data-subject requests, data-protection impact assessments and enquiries from supervisory authorities, Party A bearing the reasonable cost of assistance beyond Party B's ordinary operations. 11.4 Sub-processors. Party A gives Party B a general authorisation to engage its Affiliates, NVIDIA Cloud Partners and facility operators as sub-processors for the provision of the Services (Section 3.6). Party B shall put in place written

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 14 of 69 arrangements with each sub-processor no less protective than this Section and remains responsible to Party A for their performance. Party B's current list of sub-processors is provided separately as Party B's Confidential Information under Section 13.4. Party B shall give not less than thirty (30) days' notice of the addition or replacement of a sub-processor; Party A may object in writing within ten (10) Business Days on reasonable data-protection grounds, and the Parties shall negotiate an alternative in good faith; if no alternative is agreed and Party B cannot avoid the sub-processor without materially affecting the Services, Party A may terminate the affected Order under Section 19.7(c). 11.5 Cross-border transfer and place of processing. The principal transfer control under this Agreement is the pinning of the place of processing: inference is processed within the Region stated in the Order, Party B does not move processing out of that Region during the Commitment Term (Section 3.4), and Party B does not copy Personal Data outside the Region (disaster- recovery copies require Party A's written consent). Where the Region is in the United States and Party A or its data subjects are in the European Economic Area, the United Kingdom, Switzerland, Canada or another jurisdiction requiring a transfer mechanism, the mechanism under the module ticked in Schedule 7 applies (including standard contractual clauses or their equivalent), and Party B shall execute it. Party A is responsible for determining whether its own transfer to Party B is lawful in its own jurisdiction. 11.6 Return and deletion. Within thirty (30) days after termination or expiry of this Agreement or the relevant Order, Party A may export any Customer Content and Customer Weights retained with Party B. Following that period, Party B shall delete them in accordance with NIST SP 800-88 within thirty (30) days and, upon Party A's written request, provide a certificate of deletion. Where retention is required by applicable law or Party B's internal archival policies, Party B may retain one (1) copy and shall keep it confidential and restricted in use. 11.7 Party A's obligations and restrictions. Party A shall: (a) obtain all legal bases, notices and consents necessary for its submission of Customer Content; (b) not submit special categories of personal data, health data, financial account data, government identification numbers, children's personal data or data subject to sector-specific regulation, unless the Order expressly permits it and states the corresponding safeguards; (c) not use the Services for fully automated decisions producing legal or similarly significant effects for individuals unless Party A assumes full compliance responsibility for such decisions; and (d) be responsible for the lawfulness of its instructions. All liability arising from data submitted in breach of this Section rests with Party A and attracts the indemnity in Section 16.1. 11.8 Audit. Party A's audit rights in respect of data protection are limited to Section 12.3 and are not additional to it; documentation and certifications are governed by Section 12.5. 11.9 Conflict. Where a module ticked in Schedule 7 conflicts with this Section, that module prevails as to the processing of Personal Data; where that module conflicts with the remainder of this Agreement, this Agreement prevails, save to the extent that applicable data protection law mandates otherwise. 12. Security, Logging and Audit 12.1 Party B shall implement and maintain technical and organisational security measures no less protective than those set out in Schedule 6, including tenant isolation, encryption in transit and at rest, role-based access control, access and administrative logging, API-layer geofencing, end-use monitoring and the retention setting. These controls are platform specifications and are validated at the readiness stage before a Region carries customer workloads. 12.2 Verifiability available today (independent of any roadmap feature): (a) the contractual audit rights in this Section; (b) delivery of access and administrative logs to Party A's SIEM at the frequency stated in the Order; (c) a named NOC team, identifiable to auditors; (d) quarterly security reviews; and (e) where the Order elects a Dedicated Serving Pool, an annual facility audit right in addition (Schedule 6 §3). 12.3 Audit rights. Once every twelve (12) months, on not less than thirty (30) days' prior written notice, Party A may audit Party B's controls relevant to this Agreement (including metering controls) at Party A's cost, by its own personnel or by an independent auditor acceptable to both Parties. Audits are limited so as not to access other tenants' data; on-site audits of third- party facilities are subject to the access rules of the facility operator, and Party B shall use reasonable efforts to facilitate them. Where a material non-conformity is identified, Party B shall submit a remediation plan within thirty (30) days and remediate accordingly; the cost of any re-audit arising from a material non-conformity is borne by Party B. 12.4 Security incidents. Party B shall notify Party A in writing within seventy-two (72) hours of confirming a security incident affecting Customer Content, Customer Weights or Party A's serving capacity, describing what is known, the scope of impact and the measures taken, and shall provide updates as the investigation proceeds.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 15 of 69 12.5 Compliance documentation. Party B's security documentation and compliance roadmap are provided separately as Party B's Confidential Information under Section 13.4 and are not part of this Agreement. Party B makes no commitment as to any specific certification or framework unless expressly stated in the Order. 12.6 Confidential computing (roadmap). Party B's CPU TEE, GPU confidential computing and remote attestation capabilities are roadmap / preview items. They are not commitments under this Agreement and create no delivery obligation or timing commitment; if and when available, they will be agreed by Supplementary Order. 13. Data, Content, Intellectual Property and Confidentiality 13.1 Customer Content. Party A and its licensors retain all rights in Customer Content, Customer Weights and outputs. Party B processes Customer Content solely to perform this Agreement and the Orders, does not use it to train any model of Party B or of any third party, does not disclose it to third parties, and asserts no rights in it. 13.2 Retention and logs. Retention of Customer Content is governed by Section 11.2 and the retention setting stated in the Order; logs contain metadata only and no content. 13.3 Party B intellectual property. Party B retains all rights in its platform, the Service Endpoint, tooling, documentation, metering and operations systems and any improvements thereto; rights in catalogue models are retained by Party B or its licensors (Customer Weights excepted). No implied licence is granted to Party A under this Agreement. Party B may use, without charge, any feedback or suggestions Party A provides about the Services, but acquires no rights in Customer Content thereby. 13.4 Confidentiality. Any mutual non-disclosure agreement between the Parties, whether existing or subsequently executed, continues to apply to information exchanged under this Agreement and the Orders; in the event of conflict within its subject matter, that agreement prevails. If no non-disclosure agreement is in force, each Party shall keep the other's confidential information confidential and shall not use or disclose it other than for the purposes of this Agreement for five (5) years from disclosure. The Orders and their commercial terms are the Confidential Information of both Parties. A claim for breach of confidence, whether brought under this Section or under that non-disclosure agreement, is subject to the cap in Section 17.2 save where Section 17.3 expressly provides otherwise; any liability provision of that non-disclosure agreement inconsistent with this sentence does not apply to information exchanged under this Agreement and the Orders. 13.5 Public-company disclosure. Party A acknowledges that Party B's Parent is a Nasdaq-listed company and may be required by securities laws, stock exchange rules or competent authorities to disclose the existence, key terms or full text of this Agreement or any Order, and may file it as a material contract. Party B shall, so far as reasonably practicable, notify Party A in advance and consult in good faith regarding commercially sensitive terms for which confidential treatment may be sought. 13.6 Material non-public information. Party A acknowledges that it may receive material non-public information concerning Party B's Parent and undertakes to comply with applicable securities laws, not to trade in the Parent's securities on the basis of such information, and not to tip or recommend to others. 13.7 Publicity. Neither Party shall use the other's name, logos or trademarks, or issue any press release regarding this Agreement or any Order, without the other's prior written consent, save for the mandatory disclosures described in Section 13.5. 14. Title, Possession and Operator of Record This Section may not be deleted, weakened or varied by an Order (Section 2.4). It is the factual basis both of the export-control position (Party B signs the end-user certification in its own name) and of the revenue-recognition position (principal under ASC 606, gross presentation). 14.1 Party B procures, owns and operates all hardware used to provide the Services on its own account and is the end user and operator of record of such hardware. 14.2 Party A receives a service and does not acquire ownership, possession, control or custody of any hardware, nor any leasehold or possessory interest in any facility. Neither this Agreement nor any Order constitutes a lease, finance lease, bailment or sale of hardware or of computing capacity; a service level is a service level and an Output Unit is a unit of measurement, and neither is property capable of possession. 14.3 Party B retains full discretion over the configuration, maintenance, repair, replacement, firmware, model deployment method and operational scheduling of the hardware, provided that the service levels and technical specifications set out in this Agreement, the relevant Order and the elected Schedule 3 are not diminished. Party B may substitute hardware, adjust the

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 16 of 69 composition of capacity or migrate workloads within the Region; the Capacity Basis does not point to any identified hardware. Where the Order elects a Dedicated Serving Pool, replacement units are likewise dedicated to Party A; during repair or replacement the number of Allocation Units for that Order may temporarily fall below the Capacity Basis, such units counting as unavailable under the elected Schedule 3 rather than as a breach of Section 4.1, and Party B shall restore the number within a reasonable time. 14.4 Party A shall not create any encumbrance over the hardware, the hardware does not form part of Party A's assets, and Party A's creditors have no rights in respect of it. Party A shall reflect this Section faithfully in its accounting treatment. 14.5 Party B signs End-User Certifications and related compliance documents in its own name with its suppliers, the original manufacturers and the competent authorities. Party A shall cooperate as required under Section 10.5 but does not thereby become the end user of such items. 14.6 Party A's access is API-only. Party A's entire contact with Party B's infrastructure is limited to submitting requests to, and receiving responses from, the Service Endpoint; Party A acquires no standing or temporary administrative, host or scheduling access. Customer Weights are loaded and run by Party B under Schedule 9 and do not alter this Section. Nothing in this Agreement or in any Order gives Party A possession, control or scheduling authority over any hardware, and any practice to the contrary is a breach in respect of which Party B may suspend immediately under Section 9.6 and proceed under Section 19.6. 15. Representations and Warranties 15.1 Each Party represents and warrants to the other that: it is duly organised and validly existing under the laws of its jurisdiction; it has obtained all corporate authorisations necessary to execute and perform this Agreement and each Order; this Agreement constitutes its legal, valid and binding obligations; and its execution and performance do not violate its constitutional documents, any contract binding on it, or applicable law. 15.2 Party B warrants that: it will provide the Services with the skill and care of a competent provider in the industry; the Services will conform in all material respects to the technical specifications in Schedule 2, the relevant Order and the Service Levels of the elected Schedule 3; and it has the right to provide the Services and holds the licences and authorisations necessary to do so. 15.3 Party A warrants that: (a) all representations in Section 10 are true, accurate and complete; (b) the KYC Materials were true, accurate and complete, with no material omission, on the date submitted and on the date of execution of this Agreement, and its ownership chain has been disclosed in full up to natural persons and can be reconciled to official records; no verification, screening or confirmation by Party B under Section 10.5, Schedule 8 or Schedule 12 reduces Party A's responsibility for the KYC Materials or constitutes Party B's acceptance of the facts stated in them; (c) its use of the Services complies with the AUP in Schedule 5 and with Section 11.7; it holds all rights and consents necessary for the processing of Customer Content and Customer Weights; and the warranties in Schedule 9 §4 concerning Customer Weights are true and accurate; (d) it is the genuine user of the Services, does not act for any undisclosed third party and does not enter into this Agreement or any Order on behalf of any undisclosed principal; (e) save as disclosed in the KYC Materials, no government, state-owned enterprise, government body, military or political party holds, directly or indirectly, any interest in Party A or its parent, appoints any of its directors or otherwise controls it, and none of its shares is held by a nominee or trustee or issued in bearer form; (f) save as disclosed in the KYC Materials, neither Party A nor its shareholders, directors, officers or ultimate beneficial owners has any ownership, employment, family or contractual relationship with the Parent, Party B or any of their respective directors, officers or employees, or with any person who introduced Party A to Party B; no agent or intermediary acts for Party A in this transaction, and no person will receive a commission or fee from Party A in connection with it; (g) save as disclosed in the KYC Materials, none of its directors, officers or ultimate beneficial owners, or their immediate family members, is currently or has within the last three (3) years been a government official, a manager of a state-owned enterprise, a political-party official, a military or judicial officer or an official of a public international organisation; (h) save as disclosed in the KYC Materials, within the last five (5) years none of Party A, its parent, directors, officers or ultimate beneficial owners has been investigated, penalised or prosecuted, or entered into a settlement, in relation to export controls, sanctions, anti- money laundering, anti-bribery, fraud or data protection, and neither Party A nor any Affiliate has been refused service or had an account terminated by any supplier for compliance reasons or had an export licence denied or revoked by any authority; and (i) it has told the individuals named in the KYC Materials how Party B handles their personal information and has obtained any consent required by applicable law. 15.4 Disclaimer. Save for the warranties expressly given in this Agreement, Party B gives no other warranty, express or implied, including any implied warranty of merchantability, fitness for a particular purpose, non-infringement, or that the Services will be uninterrupted or error-free. Party B gives no warranty as to the accuracy, reliability or lawfulness of any

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 17 of 69 model output, as to whether it infringes third-party rights, as to whether it is capable of intellectual property protection, or as to its fitness for Party A's purposes; generative models may produce inaccurate, misleading, offensive or infringing content, which is inherent in the technology, and Party A is responsible for its own judgement in using such output (Schedule 11 §2). 16. Indemnities 16.1 Party A's indemnity. Party A shall defend and indemnify Party B, its Affiliates, the Parent and their directors, officers and employees against: (a) Party A's breach of Section 10 (export controls, sanctions and end use) or Schedule 8; (b) Party A's breach of the AUP in Schedule 5; (c) third-party claims relating to Customer Content, Customer Weights or Output Content (including claims in intellectual property, rights of publicity and likeness, privacy, defamation and under legislation concerning deepfakes and digital replicas); (d) Party A's breach of Section 9.3 or Section 11.7; (e) Party A's breach of Schedule 11 or Schedule 12, including as to its downstream users' Output Content and eligibility; and (f) Party A's breach of the warranties in Section 15.3, or any untruth, inaccuracy or incompleteness in the KYC Materials. 16.2 No intellectual property indemnity from Party B. Party B assumes no obligation to defend, indemnify or compensate Party A in respect of any third-party claim that the Services, a catalogue model, Customer Weights or model outputs infringe intellectual property rights. The intellectual property risk of the models Party A selects and of its use of outputs is borne by Party A; Party B gives no express or implied warranty of non-infringement (Section 15.4). If any part of the Services is held to infringe, or Party B considers that it may, Party B may in its discretion replace, modify or discontinue that part, the remainder of this Agreement and Party A's payment obligations being unaffected and no refund being due. 16.3 The indemnified party shall promptly notify the indemnifying party, tender control of the defence, and provide reasonable cooperation. The indemnifying party shall not, without the indemnified party's written consent, enter into any settlement that: (a) imposes a monetary obligation on the indemnified party; (b) admits fault by it; (c) imposes on it any non- monetary obligation or restriction, including a requirement to stop or change any service, product, configuration or practice, to accept ongoing audit, monitoring or reporting obligations, or to make any public statement; or (d) does not give it a full and unconditional release in respect of that claim. Assumption of the defence: if the indemnifying party does not confirm within ten (10) Business Days of notice that it will conduct the defence, does not conduct it diligently, or the Parties have a conflict of interest in respect of that claim, the indemnified party may assume the defence and settlement itself, and the indemnifying party remains liable for all reasonable costs so incurred (including legal fees) and for the outcome, and shall not claim any reduction by reason of that assumption. 17. Limitation of Liability 17.1 To the maximum extent permitted by applicable law, neither Party is liable for indirect, incidental, consequential or punitive damages, or for loss of profit, revenue, goodwill or data, or business interruption, whether or not advised of the possibility of such loss. This Section does not apply to the following amounts, which are contractually agreed sums payable (a debt) and not damages, and which are not excluded by this Section merely because they are economically equivalent to Party B's revenue or profit: (a) the Monthly Commitment Fees and overflow charges payable by Party A under Section 7 and the Prepayment payable under Section 8; (b) the amounts payable by Party A under Section 19.4 (including the Monthly Commitment Fees for the remainder of the Commitment Term of the affected Phase and, on withdrawal before the SRD, for the whole Commitment Term), as reduced by mitigation under Section 19.5; (c) any balance payable by Party A on settlement under Section 8.3; and (d) the amount of third-party claims and reasonable costs indemnified by Party A under Section 16. 17.2 Save as set out in Section 17.3, each Party's aggregate liability under this Agreement and all Orders shall not exceed the Monthly Commitment Fees and any overflow fees actually paid by Party A to Party B in respect of the relevant Order in the three (3) months preceding the claim. 17.3 Matters not subject to the cap: (a) Party A's payment obligations (including Monthly Commitment Fees, overflow fees, the Prepayment, the costs of recovery under Section 7.10, the credit-assurance obligation under Section 8.5 and amounts payable under Section 19); (b) Party A's breach of Section 10 (export controls, sanctions and end use) or Schedule 8; (c) Party A's breach of §3 (prohibited output) or §4 (safety filters) of Schedule 11, or of §1 (eligibility), §3 (use) or §4 (evidence and cooperation) of Schedule 12; (d) the indemnities in Section 16; and (e) fraud, wilful misconduct, and liability that cannot be limited under applicable law (including death and personal injury). For the avoidance of doubt, either Party's liability for breach of the confidentiality obligations in Section 13, and Party B's liability under Section 11, are subject to the cap in Section 17.2.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 18 of 69 17.4 Party A shall bring any claim within twelve (12) months of becoming aware, or when it ought reasonably to have become aware, of the relevant facts, failing which the claim is waived; this does not apply to claims for payment or to the matters listed in Section 17.3. 17.5 The Parent's liability under Section 20.4 shall not exceed the liability that Party B would bear under this Section in the same circumstances. 18. Force Majeure 18.1 Neither Party is in breach for failure to perform caused by events beyond its reasonable control (including acts of God, fire, earthquake, flood, war, terrorism, epidemic, strikes, grid or telecommunications backbone failure, governmental action, changes in export controls or sanctions, withdrawal of a licence by a model licensor, and supply interruption by the original manufacturer or upstream suppliers), for so long as such event continues. Payment obligations are neither excused nor deferred. Time during force majeure is excluded from the Service Levels. 18.2 The affected Party shall notify the other within five (5) Business Days, describing the nature and expected impact of the event, and shall use reasonable efforts to mitigate and to resume performance. 18.3 If a force majeure event continues for more than one hundred and twenty (120) consecutive days, either Party may terminate the affected Phase by written notice. Where the Phase is terminated before its SRD (the serving capacity not delivered), Party B refunds the Prepayment attributable to that Phase; where it is terminated after its SRD, amounts paid and the Prepayment are not refundable and Party B ceases to charge Monthly Commitment Fees from the date of termination. Neither Party shall have any further liability to the other in respect of that Phase. 19. Term, Termination and Non-Cancellability 19.1 Term of this Agreement. As provided in Section 2.7: this Agreement takes effect on the Effective Date and continues until terminated under that Section when no Order is in effect, or until the expiry or termination of the Commitment Term of the last Order, whichever is later. Termination of this Agreement does not affect any Order then in effect. 19.2 Term of each Order. The Commitment Term of each Phase of an Order runs from the SRD of that Phase for the number of months stated in that Order; where the Order elects "co-terminous", the Commitment Term of each subsequent Phase expires on the same day as that of the first Phase. IMPORTANT: each Order is irrevocable from execution and non-cancellable from the SRD. Party B procures and deploys capacity in reliance on Party A's Order; Party A may not terminate unilaterally during the Commitment Term, save as provided in Section 5.7 (where ticked in the Order) and Section 19.7; and no refund of fees or of the Prepayment is due save where the serving capacity is not delivered (Section 8.3). 19.3 Non-cancellability. An Order, once signed by both Parties, constitutes an irrevocable commitment by Party A; from the SRD of each Phase, that Phase is non-cancellable for its Commitment Term. 19.4 Consequences of early termination by Party A. If Party A withdraws an Order before the SRD of a Phase, or during the Commitment Term terminates unilaterally, repudiates, or by act or omission prevents Party B from continuing to provide the Services, Party A shall pay Party B: (a) all unpaid amounts accrued to the date of termination; and (b) the Monthly Commitment Fees for the remainder of the Commitment Term of the affected Phase (or, on withdrawal before the SRD, for the whole Commitment Term). The Prepayment paid is applied against those amounts and is not refundable. 19.5 Mitigation. Party B shall use commercially reasonable efforts to resell the released serving capacity (including through its MaaS or other tiers) and shall credit against the amount payable under Section 19.4(b) the net revenue actually received from that capacity during the remainder of the Commitment Term of the affected Phase. Party B shall report on mitigation in writing quarterly. Net revenue means the amounts actually received on reselling that capacity, less the direct incremental costs of achieving the resale (sales commission, migration and reconfiguration costs, and incremental support costs for the new customer), and without deducting Party B's fixed costs or general overhead. Two further deductions apply: (a) the variable operating costs actually saved as a result of Party A's termination (power and usage-based third-party charges not incurred while the capacity is unsold); and (b) where payment is made as a lump sum, a discount to the date of payment at five (5%) per annum over the remainder of the Commitment Term. The Parties agree that Sections 19.4 and 19.5, read together, constitute reasonable compensation for Party B's actual loss and not a penalty, and that such compensation is proportionate to the irrevocable upstream commitments Party B has undertaken for that Order in equipment, facilities, network and licences.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 19 of 69 19.6 Termination by Party B for Party A's breach. Party B may terminate this Agreement, any Order or any Phase by written notice if: (a) Party A fails to pay and does not cure within fifteen (15) days of written demand; (b) Party A breaches Section 10, Schedule 5, Schedule 8, Schedule 11 or Schedule 12, the KYC Materials or the warranties in Section 15.3 prove untrue, or an Eligibility Event under Schedule 12 §1 occurs (no cure period); (c) Party A becomes subject to bankruptcy, liquidation, reorganisation, receivership or similar proceedings; or (d) Party A materially breaches any other provision and fails to cure within thirty (30) days of written notice. In the circumstances of (b) and (c), Party B may terminate all Orders at once. Sections 19.4 and 19.5 apply on such termination. 19.7 Termination by Party A for Party B's breach. Party A may terminate the affected Phase or Order by written notice if: (a) readiness is delayed beyond the period in Section 4.8; (b) the Service Readiness Test fails twice on re-run for the same cause (Section 4.6); (c) Party B materially breaches Section 11, Section 12 or Section 13 and fails to cure within thirty (30) days of written notice; or (d) Party B becomes subject to bankruptcy, liquidation, reorganisation, receivership or similar proceedings. Where an Order elects Schedule 3B and ticks Section 5.7, the sustained-shortfall exit in that Section applies in addition. For an Order electing Schedule 3A, failure to meet the Service Levels is not a ground for termination under this Section (Section 5.3). Refunds and the Prepayment are governed by Section 8.3: only under (a) and (b) (the serving capacity not delivered) is the Prepayment attributable to that Phase refunded; otherwise no refund is due. 19.8 Compliance termination. If a change in applicable law, export controls or sanctions, or a requirement of Party B's upstream suppliers, the original manufacturer, a model licensor or a competent authority, makes it unlawful for Party B to continue providing the Services to Party A or would cause Party B to breach its compliance undertakings, Party B may terminate the affected Phase, the affected Order or all Orders immediately by written notice without further liability. Refunds and the Prepayment are governed by Section 8.3: where the Phase is terminated before its SRD, the Prepayment attributable to that Phase is refunded; where after its SRD, amounts paid and the Prepayment are not refundable and Party B ceases to charge Monthly Commitment Fees from the date of termination. Where the circumstance arises from any act, omission or change in status of Party A or its Affiliates, shareholders or ultimate beneficial owners, Section 19.6 applies. 19.9 Renewal. Not later than six (6) months prior to expiry of the Commitment Term of an Order, either Party may initiate renewal negotiations; at renewal Party A may reduce the serving capacity of that Order under Section 6.4. Absent a written renewal, the Phase terminates on expiry of its Commitment Term and Party B is under no obligation to hold the capacity thereafter. 19.10 Survival. Sections 1, 2.3, 2.4, 7 (in respect of amounts accrued prior to termination), 9.3, 10, 11.6, 13, 14, 16, 17, 19.4, 19.5 and 21 to 24, and any provision which by its nature should survive, continue in effect after termination of this Agreement or of any Order. 20. Assignment, Entity Designation and Parent Support 20.1 Party A shall not assign any rights or obligations under this Agreement or any Order without Party B's prior written consent. A change of control of Party A is deemed an assignment requiring Party B's written consent, not to be unreasonably withheld, provided that the assignee or new controller must first pass Party B's compliance and export-control screening. 20.2 Entity designation. On assumption by the designated entity, the original contracting entity is released from liability for that Order from the date of assumption but remains responsible for obligations and liabilities that accrued before that date, and the parent support provision applies equally to the designated entity. Party B may designate any of its directly or indirectly controlled Affiliates, or any other Affiliate under the direct or indirect control of Quanome Technologies, Inc. (including a sister project entity) (including a project entity established for a particular resource pool) as the contracting and service- providing entity for this Agreement or for an Order, and may assign the corresponding rights and obligations to that entity upon written notice to Party A. Such designation does not alter the terms of this Agreement or that Order or diminish Party A's rights. 20.3 Financing assignment. Party B may assign or pledge its receivables, accounts and contract rights under this Agreement and the Orders to lenders, financiers or their agents without Party A's consent, upon written notice to Party A. Party A shall provide reasonable cooperation in issuing customary acknowledgements (including confirmation of payment directions), without assuming additional obligations and without waiving any defence or right of set-off under this Agreement. 20.4 Parent support. Quanome Technologies, Inc. (Nasdaq: QNME) undertakes to Party A to procure the performance by Party B (including any entity designated under Section 20.2) of its obligations under this Agreement and the Orders. If Party B fails to perform, the Parent shall, within thirty (30) days of written notice from Party A, perform or procure performance by another Affiliate. This is a performance support undertaking and is neither a guarantee nor an independent demand instrument. The Parent's liability is co-extensive with and subject to the same limits as Party B's (Section 17.5), and the Parent has the benefit of all defences available to Party B under this Agreement. Three further limits apply: (a) cap — the Parent's aggregate

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 20 of 69 liability under this Agreement and all Orders shares the single aggregate cap in Section 17.2 with Party B and does not create a second cap; (b) duration — this support runs from the Effective Date until twelve (12) months after expiry of the Commitment Term of the last Order; and (c) no double recovery — Party A shall not recover the same loss from both Party B and the Parent, and any amount recovered from either reduces the liability of the other. (d) prior claim and cure — Party A must first claim against Party B in writing, specifying what Party B has failed to perform and the provision relied on, and allow Party B not less than thirty (30) days to cure (fifteen (15) days for a payment claim); only if Party B fails to cure within that period may Party A claim against the Parent under this Section, and any such claim shall enclose that earlier request and an explanation of the failure to cure. This cure period is a condition precedent to the Parent's obligation and is not a procedure for establishing a breach by Party B. 21. Notices 21.1 Notices shall be in writing and delivered to the addresses and email addresses set out in the Parties tables (or to the Order contacts stated in the relevant Order), or as changed under Section 21.3. 21.2 Deemed receipt: on delivery if by hand; on signature if by international courier; on the day of transmission if by email (absent a bounce-back received by the sender). Notices of termination under Section 19 and claims under Section 16 must be sent by both international courier and email. Email is the primary channel and courier the secondary one: where the preceding sentence requires both, the time of deemed receipt is the time the email was transmitted, the courier delivery is supplementary, and a failure of that courier delivery — including refusal, an unattended address or an address no longer in use — does not affect the notice having taken effect by email. Refusal and loss of contact: where the addressee refuses to accept a notice, or delivery fails because it has not updated its address or email under Section 21.3, the notice is deemed received on the date of first attempted delivery or transmission. Invalid mailbox: where the sender receives a permanent bounce-back, it shall resend by the other channel within three (3) Business Days and the date of resending is the date of receipt. This Section does not affect service of process in arbitration or court proceedings, which follows the applicable procedural rules. 21.3 Changes of address require not less than five (5) Business Days' prior written notice to the other Party. 22. General Provisions 22.1 Entire agreement. This Agreement, together with its Schedules, the Orders and the Supplementary Orders, constitutes the entire agreement between the Parties as to its subject matter and supersedes all prior oral or written understandings and representations, including any Letter of Intent and any Allocation Offer previously executed; any non-disclosure agreement between the Parties continues in force in accordance with Section 13.4. 22.2 Order of precedence. See Section 2.4. 22.3 Amendment. Amendments to this Agreement must be in writing and signed by the Parties' authorised representatives; amendments to an Order are made by Supplementary Order under Schedule 10. Unilateral updates by Party B to its technical documentation do not amend this Agreement and shall not diminish service levels or security controls. Updates by Party B to Schedules 2 to 10 apply only to Orders signed after the update and, absent the Parties' written agreement, not to existing Orders. 22.4 Waiver. No failure or delay in exercising any right operates as a waiver of it, and no single or partial exercise precludes any further exercise. 22.5 Severability. If any provision is held invalid or unenforceable, the remainder is unaffected and the Parties shall negotiate in good faith a replacement provision of the closest permissible effect. 22.6 Independent parties. The Parties are independent contractors. Nothing in this Agreement creates a partnership, joint venture, agency or employment relationship, and neither Party may bind the other. 22.7 Third-party rights. Save for the indemnified parties named in Section 16.1 and the Parent under Section 20.4, this Agreement confers no rights on any third party. 22.8 Anti-corruption. Each Party shall comply with the U.S. Foreign Corrupt Practices Act, the UK Bribery Act and other applicable anti-corruption and anti-money-laundering laws, and shall not directly or indirectly offer, promise or accept any improper advantage. 22.9 Finders and commissions. Each Party confirms that, save as disclosed to the other in writing, it has not agreed to pay any commission, finder's fee or introduction fee to any third party in connection with this Agreement or any Order. Any such fee

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 21 of 69 is borne solely by the Party that agreed to it, creates no obligation for the other Party, and forms no part of any amount payable under this Agreement. 23. Governing Law and Dispute Resolution 23.1 This Agreement, the Orders and any non-contractual dispute connected with them are governed by the laws of the State of New York, USA, without regard to its conflict-of-laws rules. The United Nations Convention on Contracts for the International Sale of Goods does not apply. 23.2 Disputes shall first be referred to senior executives of each Party for good-faith resolution within thirty (30) days. 23.3 Failing resolution, the dispute shall be finally resolved by arbitration administered by the American Arbitration Association under its Commercial Arbitration Rules then in force, seated in New York, before one (1) arbitrator, in English. The award is final and binding and may be enforced in any court of competent jurisdiction. Where disputes arise under more than one Order between the same parties, either Party may apply for consolidation. 23.4 Injunctive relief reserved. Either Party may seek interim or permanent injunctive relief in any court of competent jurisdiction in respect of confidentiality (Section 13), export controls (Section 10) or intellectual property, without first pursuing negotiation or arbitration and without waiving the arbitration agreement. 23.5 The arbitration proceedings and their existence are Confidential Information, save for disclosure necessary to enforce an award or required by law, regulation or stock exchange rules. 24. Language and Counterparts 24.1 This Agreement is executed in English. Any Chinese translation provided is for reference only; the English text prevails. 24.2 This Agreement and each Order may be executed in counterparts, each of which is an original and all of which together constitute one instrument. Electronic signatures and scanned copies have the same effect as originals.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 22 of 69 Signature Page — Master Services Agreement The undersigned, having fully understood this Agreement and its Schedules, sign below on behalf of their respective companies. The Parent signs solely for the purposes of Section 20.4. This page executes the Master Services Agreement; each transaction is separately executed on an Order in the form of Schedule 1. Party A XPERT SOFTWARE SOLUTIONS PTE LTD (Customer) Signed by: /s/ Thomas Long Print Name: Thomas Long Title: Director Date: 29-September-2026 (Common Seal, if applicable) Party B XDT INFRASTRUCTURE I, LLC (XDT — Supplier) Signed by: /s/ Yang Li Print Name: Yang Li Title: Manager Date: September 29, 2026 (Common Seal, if applicable) Parent (solely for Section 20.4) QUANOME TECHNOLOGIES, INC. (Nasdaq: QNME) Signed by: /s/ Yang Li Print Name: Yang Li Title: Chief Executive Officer Date: September 29, 2026 — This Master Services Agreement contains 24 sections and Schedules 1–12, executed in duplicate, one copy held by each Party —

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 23 of 69 Schedule 1 · Order Form This Schedule is the form of an Order. One Order is signed for each transaction and each expansion; once signed by both Parties an Order forms, with the Master Services Agreement, a separate contract (Sections 2.2 and 2.3). This form may be extracted and circulated on its own. If the Monthly Commitment Fee or the Commitment Term in §7 is left blank, the Order is not formed (Section 2.2). 1. Order identification Order No. XDT-TF-MSA-2026-001-O01 Master Agreement made under the XDT Token Factory Master Services Agreement (no. XDT-TF-MSA- 2026-001, effective 2026-09-29), all terms and Schedules of which are incorporated into this Order Order Date 29-September, 2026 Party A XPERT SOFTWARE SOLUTIONS PTE. LTD. (UEN 201320369H, Singapore); where an Affiliate of Party A orders, state its legal name and place of incorporation, and Section 2.6 applies Party B XDT Infrastructure I, LLC 2. Tier and tenancy Tier XDT Token Factory — Party B runs the model, Party A calls the Service Endpoint Tenancy ☑ dedicated capacity pool · full physical isolation (Section 3.3(a), Schedule 6 §3): dedicated nodes, a separate cage or rack, a separate compute network segment and separate storage volumes; no hardware shared with any other tenant; logical isolation layered on top; the annual facility audit right applies ☐ shared capacity · logical isolation Isolation boundary all inference on Customer Content takes place within this Order's serving capacity; the Service Endpoint and control plane are Party B platform components handling metadata only (Section 3.3). ☐ Dedicated endpoint hostname / private connectivity: not elected Content monitoring Dedicated pool: metadata-layer compliance monitoring only, no automated content filtering; shared capacity: automated abuse filtering in addition (Section 9.4) 3. Region, facility and Capacity Basis Region United States · [***] — processing pinned for the Commitment Term (Section 3.4) Facility [***] Operator the facility operator's name will be notified to Party A separately under Section 13.4 once the operator authorises disclosure; this does not affect the validity of this Agreement (Party B Confidential Information) Capacity Basis 64 XDT B300 Allocation Units, being sixty-four (64) NVIDIA HGX B300 servers (8 × NVIDIA B300 GPUs each, 512 GPUs in total), dedicated to Party A and fully physically isolated; delivered in a single Phase (§4). A commitment as to quantity and dedication, not an allocation of identified hardware; Party B retains its substitution and migration rights under Section 14.3, replacement units being likewise dedicated (Section 4.1) Platform generation XDT B300 — standard node configuration on the NVIDIA HGX B300 NVL16 platform, air-cooled; OEM, BOM and deployment are Party B's internal matters Operations 24×7, operated by [***]; the operator's name is disclosed separately as Party B's Confidential Information under Section 13.4 and is not stated in this Agreement Service Endpoint designated by Party B in writing before the test date is notified under Schedule 4A;

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 24 of 69 project credentials for this Order are issued at the Service Readiness Test Interface spec ☑ OpenAI-compatible ☐ Party B REST ☐ other: ___; mode ☑ synchronous ☑ streaming ☐ asynchronous task submission and retrieval. Interface documentation version: v1.0, as delivered by Party B before the Service Readiness Test (Section 1.18) 4. Phases and Target Service Ready Dates Phase Capacity Target SRD Phase 1 (sole Phase) sixty-four (64) Allocation Units, being 64 NVIDIA HGX B300 servers (512 GPUs), dedicated · fully physically isolated, delivered in a single Phase within two (2) months of the Readiness Start Date (Section 4.4; the Readiness Start Date includes receipt of the first tranche of the Prepayment, see §7) Phase 2 not applicable — delivered in a single Phase — The Readiness Start Date is determined under Section 4.4 and includes receipt of the first tranche of the Prepayment (§7). Unless this table states otherwise, the Target SRD of each Phase is two (2) months from that Phase's reference date — the Readiness Start Date for Phase 1, and the Phase 1 SRD for Phase 2. Where this table states a specific date, the later of that date and the two-month period governs. The sole remedy for readiness delay is in Section 4.8. Early service of part of Phase 1: where Party B offers at least thirty-two (32) Allocation Units for the Service Readiness Test before the whole Phase (the unit- count item in Schedule 4A §1 applying to the units offered) and they pass or are deemed to pass, those units enter service on that date. Until the SRD of the whole Phase, Party A pays for the units in service the Monthly Commitment Fee pro rata to their number out of sixty-four (64), the Prepayment being applied to that fee in the proportion stated in §7, and delay credits and any termination under Section 4.8 apply only to the units not yet in service, the Prepayment attributable to them being their pro rata share. The Commitment Term runs from the SRD of the whole Phase. 5. Models and configuration This section states the models to be deployed under this Order and their configuration. Models are not limited as to modality, and the Output Unit follows the modality (Section 1.23). Complete one column per model configuration; where there are more than two, continue on a continuation sheet. Common parameter Configuration A Configuration B (not used) Model identifier [***] not applicable Modality ☑ text / chat ☑ image ☑ video ☑ audio ☑ multimodal ☑ embeddings / other: ___ not applicable Weights ☑ catalogue ☐ Customer Weights (Schedule 9) not applicable Output Unit ☑ token ☑ image ☑ video second ☐ frame ☐ audio second ☐ task ☐ other: ___ not applicable Precision & quantisation the deployed model's released precision (BF16 / FP8); no additional quantisation. NVFP4 quantisation for higher throughput is available as a configuration change under Section 6.2 not applicable Retention setting ☑ zero retention (default) ☐ ___ days (purpose: ___). The technical boundary of zero retention is set out in Schedule 11 §10 not applicable

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 25 of 69 Retrieval window not applicable — synchronous and streaming modes only (Schedule 11 §10) not applicable Prompt cache ☑ permitted (default; reduces latency and cost) ☐ disabled (no cross-request caching of prompt prefixes; materially increases latency and unit cost, commercial effect per Section 7) not applicable Usage logs ☑ retained (default) ☐ not retained — Party B does not retain request identifiers, Output Unit counts, model identifiers or start and end times (Schedule 8 §3). Available only where this Order is on a fixed monthly committed fee, "overflow" in §7 is marked "not permitted", and Schedule 3B (committed throughput) is not elected — attainment under Schedule 3B is determined from request-level metering, so switching usage logs off would leave nothing to measure and the two cannot coexist; by electing it Party A acknowledges that there will be no historical usage reports, no request-level basis for reconciliation, and a reduced ability to evidence abuse investigations and the statutory safe harbours (Schedule 11 §9) not applicable Content-bearing diagnostics ☑ permitted, retained 7 days (default) ☐ disabled (reduced fault-diagnosis capability) not applicable Safety filter ☑ keep the model's built-in filters enabled (default) ☐ request that they be disabled (requires Party B's separate written consent; Schedule 11 §4 applies) not applicable Applicable Phases ☑ Phase 1 (sole Phase) not applicable Modality-specific parameters — complete only the rows for the modalities actually used under this Order. Modality Parameters Configuration A Configuration B Text · chat maximum context length · maximum output length · maximum concurrent requests 128k tokens, or the model's native maximum if lower / 16k tokens / initial configuration 2,048, adjusted by Party B within the serving capacity; requests beyond the capacity at the time are rate-limited under Section 9.5 — Image maximum resolution · maximum images per generation · sampling steps · maximum concurrency not applicable — Video maximum resolution · frame rate · maximum duration per generation · not applicable —

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 26 of 69 sampling steps · maximum concurrent tasks Audio sample rate · maximum audio length per request · maximum concurrency not applicable — Embedding · other — not applicable — A model configuration is the setting on which Party B deploys a model and is not a commitment as to throughput, latency, task completion time or output (Section 5.2). Configuration changes are handled in writing under Section 6.2 and Schedule 10 and do not alter the Monthly Commitment Fee or the Commitment Term. The retention setting also determines the data footprint under this Order and the scope of the Schedule 7 obligations (Section 11.2). Where a generative image, video or audio model is deployed, Schedule 11 applies in full. 6. Election of Service Levels Schedule 3 elected ☑ Schedule 3A — availability (cluster availability ≥ 99.9%; no commitment as to throughput, latency or output volume; Service Credits are the sole remedy and give rise to no right of termination) ☐ Schedule 3B — committed throughput Schedule 4 elected ☑ Schedule 4A — Service Readiness Test (accompanies Schedule 3A) ☐ Schedule 4B — throughput baseline test Exit right ☐ applies (only where Schedule 3B is elected) ☑ does not apply Committed Throughput (only if 3B) not applicable — Schedule 3A elected Order-stated values in Schedule 3 P1 response 15 minutes; planned maintenance ≤ 8 hours per Service Month; credit tiers per the elected Schedule 3 (50% monthly cap, Section 5.3) Log delivery ☐ real-time ☑ daily ☐ weekly (Section 12.2(b), Schedule 6) Certification commitments none unless listed here: [________________] (Section 12.5) 7. Commercial terms Item Phase 1 Phase 2 (if any) Monthly Commitment Fee USD [***] per Service Month, irrespective of utilisation (Section 7.1) not applicable — single Phase Commitment Term 60 months from the Phase 1 SRD not applicable — single Phase Total Commitment Value USD 100,915,200 (USD [***] per GPU- hour × [***] GPUs × [***] hours per month = [***] GPU-hours per month × USD [***] = USD [***] per month × [***] months) not applicable Prepayment USD 45,000,000.00, payable in two tranches: (a) 30% of the Prepayment = USD 13,500,000.00, payable within [***] calendar days after Party B notifies Party A in writing, enclosing a redacted copy of the order acknowledgements, that the original equipment manufacturer of the servers (the "OEM") has confirmed Party B's purchase orders for the full Phase 1 capacity; (b) the remaining 70% of the not applicable

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 27 of 69 Prepayment = USD 31,500,000.00, payable within [***] Business Days after Party B notifies Party A in writing that the OEM has requested payment of the balance of the equipment price before shipment, enclosing a redacted copy of that request. Use of the Prepayment: Party B shall apply the Prepayment to the build-out of the serving capacity under this Order — in aggregate [***] to the price of the servers payable to the OEM, and the balance to network procurement and other build-out costs of this Order. Within ten (10) Business Days after Party A's written request, Party B shall provide, for the payments made from the Prepayment: (i) a certificate of its authorised representative stating the amounts so applied; (ii) copies of Party B's remittance confirmations for those payments, with bank account details redacted; and (iii) redacted copies of the OEM's order acknowledgement, notice of readiness to ship and shipping documents, from which prices, payment terms, NVIDIA project registration details, serial numbers, the identity of the facility operator, personal data and other commercially sensitive or third-party confidential information have been removed. Party B is not required to provide its supply contracts or purchase orders. Party A shall treat all such documents as Party B's Confidential Information under Section 13.4 and shall use them only to verify the application of the Prepayment. Party A acknowledges that the Parent, as a Nasdaq-listed company, will announce this Agreement in a current report on Form 8-K that describes this intended application of the Prepayment, and consents to that disclosure. The Readiness Start Date under Section 4.4 is the date on which all the conditions in that Section are satisfied, Section 4.4(c) being deemed satisfied upon receipt of the first tranche. If the second tranche is not received within the period in (b), the Target SRD shall be extended day-for-day until receipt, and Sections 7.5, 9.6 and 19.6(a) apply

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 28 of 69 to the overdue tranche. No default, late-payment interest under Section 7.5 or suspension right under Section 9.6 arises in respect of the second tranche before it is due. Until the second tranche is received, Party B is not required to make purchase commitments exceeding the amount of the first tranche. Application: applied month by month from the first Service Month against the Monthly Commitment Fee in the proportion the Prepayment bears to the Total Commitment Value — USD [***] of each full month's fee — Party A paying the balance of USD [***] in cash for each full Service Month (pro rata for a part month), over sixty (60) months (Section 8.2). Credit assurance ☑ None — with USD 45,000,000.00 prepaid, no credit assurance is required under this Order; on a trigger event under Section 8.5 Party B may require it under that Section. Ownership of output all output of this Order's serving capacity, of whatever modality, belongs to Party A and is not separately charged (Section 7.2); no quantity is committed (Section 5.2); responsibility for output content is in Schedule 11 Overflow ☑ not permitted — this Order is fixed capacity at a fixed monthly fee, with no overflow Overflow rates not applicable — overflow is not permitted under this Order Unused capacity not rolled over, credited or refunded (Section 6.7) Price adjustment fixed for the Commitment Term (Section 7.8) Payment terms by the 25th of the preceding month; the month of the SRD within 10 days after the SRD (Section 7.3). ☐ otherwise agreed: [●] Payment account the account of the Parent, Quanome Technologies, Inc., designated under Section 7.4(ii) as Party B's collection account: account no. [***] of Quanome Technologies, Inc. at [***] · ABA [***] · SWIFT [***] · beneficiary account name [***] · beneficiary address [***] · account no. [***] · memo (mandatory; a wire without it is returned): [***]. The account name is confirmed by Morgan Stanley's account confirmation letter; any change is subject to call-back verification under Section 7.4 Late interest 0.05% per day (Section 7.5) Renewal notice six months before expiry (Section 19.9) The Total Commitment Value is an estimate of the Monthly Commitment Fee × the number of months in the Commitment Term for each Phase. Amounts actually payable are governed by the billing rules in Section 7, the actual SRD of each Phase and any executed Supplementary Order. 8. Permitted territories and cross-border export control Permitted territories [***] (covering API calls and account administration; account administrators located in: [***]; Section 10.6; Party B enforces geofencing at the API layer and blocks known VPN

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 29 of 69 / proxy / Tor exits). Access from any territory not listed is prohibited; any change or addition requires a prior written request and Party B's written consent, and Party B may first need the consent of its upstream suppliers and gives no undertaking as to turnaround time Downstream use [●] internal use only [●] used in Party A's own products ☐ resale or distribution (where either of the last two is ticked, Schedule 8 §5 applies in full) Direct resellers [________________] (complete where resale or distribution is elected: legal name and place of incorporation of each direct reseller; Section 10.10(e)) Downstream territories [***] (complete where downstream use is elected; must be a subset of the permitted territories) Statement of end use [________________] (completed by Party A; the change-notification duty in Sections 10.5 and 10.9(a) is measured against this statement) End-user entities [●]Party A only ☐ Party A and the following Affiliates: [________________] (each entity must pass screening) ☐ together with downstream users managed under Schedule 8 §5 Annual attestation date on or before 31 January each year (Schedule 8 §6) KYC and screening completed before credentials are issued; a condition precedent under Section 4.4(b) 9. Data-protection module Module elected ☐ GDPR (Schedule 7 §6) ☐ PIPEDA (Schedule 7 §7) ☐ CCPA / CPRA (Schedule 7 §8) ☑ none applicable — Party A has confirmed that the workloads process no personal information; should that change, the relevant module must first be elected by Supplementary Order Categories and data subjects [________________] (completed by Party A; under zero retention Party B holds no Personal Data on a continuing basis, Section 11.2) Nature and purpose processing on Party A's instructions for the purpose of providing inference through the Service Endpoint; not used for training (Section 11.3) Special categories ☐ not submitted (default, Section 11.7(b)) ☐ submitted with Party B's written consent, safeguards: [________________] Transfer mechanism pinning of the place of processing is the principal control (Section 11.5); where a transfer instrument is also required: ☐ EU SCCs (module two) ☐ UK IDTA / Addendum ☐ other: [●] Party A DP contact [________________] 10. Notice contacts (this Order) Role Party A Party B Commercial [***] [***] Technical & operations [***] [***] Security incidents [***] security@xdt.com Compliance & export control [***] compliance@xdt.com Invoicing [***] ar@xdt.com

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 30 of 69 11. Variations to the Master Agreement (if any) This Order does not vary the Master Agreement save as expressly stated below. The Sections listed in Section 2.4(a) (Sections 7, 8, 10, 14, 17 and 19) may not be varied by this §11 except upon separate written confirmation under Section 2.4. Section varied As varied Confirmed None — Party A ____ Party B ____ Execution of this Order The undersigned execute this Order and confirm that it is subject to all terms and Schedules of the Master Services Agreement (no. XDT-TF-MSA-2026-001). This Order, together with that Agreement, forms a separate contract (Section 2.3). Party A XPERT SOFTWARE SOLUTIONS PTE LTD (Customer) Signed by: /s/ Thomas Long Print Name: Thomas Long Title: Director Date: 29-September-2026 (Common Seal, if applicable) Party B XDT INFRASTRUCTURE I, LLC (XDT — Supplier) Signed by: /s/ Yang Li Print Name: Yang Li Title: Manager Date: September 29, 2026 (Common Seal, if applicable)

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 31 of 69 Schedule 2 · Service Description and Technical Specification This Schedule sets out the composition of the service and the technical specifications that do not vary from deal to deal. The deal-specific values — Region, Capacity Basis, configuration, price and term — are in the Order (Schedule 1). 1. Division of responsibility • Party B: procuring, deploying, powering, cooling, monitoring and troubleshooting the capacity, firmware and model- version maintenance, and hardware substitution and migration within the Region. • Party A: its applications, clients, credential management, connectivity and retry behaviour, and its judgement in using and relying on model outputs. • The scope of, and exclusions from, the Services are in Sections 3.1 and 3.5. 2. Service Endpoint and access Service Endpoint the address and interface specification stated in the Order (Section 1.18); not limited to any interface standard or modality Modalities text · chat · image · video · audio · multimodal · embedding; the available models and their parameters are stated in §5 of the Order Invocation mode synchronous · streaming · asynchronous task submission and retrieval (the usual mode for video, long-form audio and batch generation: submission returns a task identifier, with callback or polling on completion) Model identifier as recorded in §5 of the Order Credentials project credentials issued per Order; separate quotas, logs and storage scopes per project Transport TLS 1.2 or above; encryption in transit and at rest Rate limiting requests beyond the capability of that Order's serving capacity return HTTP 429; not unavailability (Section 5.4) Compatibility Party B maintains backward compatibility of the Service Endpoint; breaking changes on not less than 90 days' notice 3. Allocation Unit specification B300 generation one Allocation Unit = one node = 8 × NVIDIA B300 GPUs; standard node configuration on the NVIDIA HGX B300 NVL16 platform, air-cooled Rack-scale generations one Allocation Unit = one rack, as composed in the Order System sourcing the OEM, BOM, network and storage selection and deployment method are Party B's internal matters, subject to Party B's discretion under Section 14.3 4. Dashboard and reporting • A customer-visible dashboard showing per-minute Output Units, latency or task completion time, and error rates per project. For an Order electing Schedule 3A, dashboard figures are for information only and are not commitments. • A monthly service report as required by the elected Schedule 3, by the 5th Business Day of each month. • For an Order with a Dedicated Serving Pool, the monthly report additionally lists the number of Allocation Units for the month and any substitutions (without serial numbers). 5. Support and operations Coverage 7×24 NOC 24×7 NOC; named team, identifiable to auditors (Section 12.2(c)) Incident severity P1 service down · P2 severe degradation · P3 functional · P4 enquiry; response times per the elected Schedule 3

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 32 of 69 Planned maintenance not less than 5 Business Days' notice; monthly allowance per the elected Schedule 3 Emergency maintenance to prevent imminent failure, notified as soon as practicable and reported afterwards Change notification changes affecting the interface or behaviour are announced in release notes and on the dashboard

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 33 of 69 Schedule 3A · Service Levels and Service Credits — Availability This Schedule applies by default (Section 5.1). It commits to one thing: that the serving capacity under the Order and the Service Endpoint are in service. Throughput, latency and output are outside the commitment (Section 5.2); where a throughput commitment is required, the Order elects Schedule 3B instead. 1. Definitions Service Month a calendar month Allocation Unit available the unit is powered, passes health checks, has the model stated in the Order loaded, and can receive requests or accept task submissions through the Service Endpoint Allocation Unit unavailable for reasons attributable to Party B or Party B-managed infrastructure, the unit fails any condition above, from the earlier of Party B's monitoring alert or Party A's report until restoration Monthly availability per unit (total minutes in the Service Month − minutes unavailable, net of the exclusions in §3) ÷ total minutes Endpoint availability the share of minutes in the Service Month in which the Service Endpoint is reachable and does not, for reasons attributable to Party B, return 5xx on well-formed authenticated requests or refuse task submissions Cluster availability (total minutes in the Service Month − Cluster Unavailable Minutes, net of the exclusions in §3) ÷ total minutes. A Cluster Unavailable Minute is a minute within a period of at least five (5) consecutive minutes during which, for reasons attributable to Party B or Party B-managed infrastructure: (a) the Service Endpoint is unreachable, or five per cent (5%) or more of well-formed, authenticated requests within the Order's configured limits fail with a 5xx error or time out (requests rate-limited under Section 9.5 (HTTP 429) and other 4xx responses are not failures); or (b) fewer than ninety per cent (90%) of the Allocation Units in the Capacity Basis, rounded down to a whole unit, are available. Monthly Commitment Fee the commitment fee for that Phase for that Service Month, excluding overflow charges Reference metrics throughput (Output Units per minute), time to first token or task completion time, output speed, error rate, task success rate — shown on the dashboard and in reports for information only; not commitments, no credits 2. Committed metrics Metric Commitment Measurement Cluster availability ≥ 99.9% per calendar month, for the Order's serving capacity as a whole, net of the exclusions in §3 P1 response within 15 minutes unless the Order states otherwise from monitoring alert or Party A's report, whichever is earlier Planned maintenance no more than 8 hours per Service Month unless the Order states otherwise, on ≥ 5 Business Days' notice excluded from availability Reference metrics no commitment dashboard and monthly report, information only (Section 5.2); includes task completion time and task success rate 3. Excluded time Unavailability arising from the following is not counted towards availability: • Planned maintenance within the allowance in §2, notified as required; emergency maintenance to prevent imminent failure, notified as soon as practicable and reported afterwards.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 34 of 69 • Party A's applications, client software, credential management, network or connectivity. • Suspension or throttling under Schedule 5, Section 9.6 or Section 10, or regulatory action arising from Customer Content or use. • The implementation period of a configuration change requested by Party A (Section 6.2); a model becoming unavailable because a licensor withdraws its licence, the law prohibits it or the developer ceases support (Section 6.5); Customer Weights being refused, suspended or removed (Schedule 9). • Rate-limiting (HTTP 429) of requests beyond the capability of that Order's serving capacity at the time — that is the capacity ceiling, not unavailability. • Force majeure (Section 18), including new export-control, sanctions or regulatory measures after the Effective Date. • Any cause not attributable to Party B or Party B-managed infrastructure. 4. Service credits Monthly cluster availability Credit (% of the Monthly Commitment Fee for the Phase) Notes ≥ 99.9% no credit — 99.0% to below 99.9% 10% — 95.0% to below 99.0% 25% — Below 95.0% 50% post-incident review under §6 Credits are calculated against the Monthly Commitment Fee for the Phase for that Service Month, and the monthly cap is 50% of that fee (Section 5.3). Availability per Allocation Unit and Service Endpoint availability are reported for information and give rise to no separate credit. 5. Claims and application • Claims are submitted in writing within 30 days after the end of the relevant Service Month, failing which they are waived; Party B confirms against monitoring data within 10 Business Days. • Credits are applied to the next invoice and are not paid in cash; they are Party A's sole and exclusive remedy for failure to meet the Service Levels and give rise to no termination right (Sections 5.3 and 19.7). 6. Reporting • Monthly report by the 5th Business Day: cluster availability, availability per Allocation Unit and for the Service Endpoint (for information), unavailability incidents with attribution, excluded time with reasons, the number of Allocation Units for the month with any substitutions (no serial numbers), overflow tokens (if any), and any credit due. • Customer-visible dashboard with per-minute Output Units, latency or task completion time, and error rates per project — for information only, not a commitment. • Post-incident review within 5 Business Days where any Allocation Unit's monthly availability is below 95%, or where a single incident makes more than 25% of that Order's Allocation Units unavailable for more than 4 hours.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 35 of 69 Schedule 3B · Service Levels and Service Credits — Committed Throughput This Schedule applies only where the Order expressly elects it (Section 5.1), and must be elected together with Schedule 4B (Section 2.5). Electing it means Party B commits to tokens per minute — the committed figures, the Named Profile and the Admission Threshold must be completed in the Order; if left blank, Schedule 3A governs. 1. Definitions Named Profile the parameters recorded in §5 of the Order; the commitment is valid for this profile only Committed Throughput the committed input and output tokens per minute stated in the Order (together "TPM") Service Month a calendar month Measurement Window each clock-aligned 60-second interval in the Service Month Conforming Request a request within the Named Profile, authenticated, well-formed and within quota Offered Load tokens submitted on Conforming Requests in a Measurement Window Demand Window a Measurement Window in which Offered Load is at or above the Committed Throughput. Only Demand Windows are measured — Party B cannot fail to deliver throughput that Party A did not ask for Admission Threshold the maximum time from receipt to first token, stated in the Order; tokens on requests admitted later are not Served Tokens Served Tokens tokens delivered on Conforming Requests admitted within the Admission Threshold Window Attainment min(Served Tokens ÷ Committed Throughput, 100%), input and output separately, the lower of the two Monthly Throughput Attainment the mean Window Attainment across all Demand Windows in the Service Month, excluding Excluded Windows Monthly Commitment Fee the commitment fee for that Phase for that Service Month, excluding overflow charges Two measurement disciplines. The definition of Demand Window means Party A cannot claim a shortfall on traffic it never sent; the definition of Admission Threshold means Party B cannot meet a throughput figure by queueing requests until the minute is over. They are each other's consideration. 2. Committed metrics Dimension Commitment Measurement Throughput attainment ≥ 99.5% per Service Month mean Window Attainment across Demand Windows, from Party B's metering Admission latency as stated in the Order (≥ 98% of Conforming Requests admitted within the Admission Threshold) per-request metering, per Service Month Endpoint availability ≥ 99.5% per Service Month endpoint reachable and not returning 5xx for reasons attributable to Party B; suspension periods excluded Availability per Allocation Unit ≥ 99.5% as defined in Schedule 3A §1 Planned maintenance no more than 8 hours per Service Month unless the Order states otherwise, on ≥ 5 Business Days' notice maintenance windows are Excluded Windows 3. Excluded Windows A Measurement Window is excluded from Monthly Throughput Attainment where the shortfall arises from:

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 36 of 69 • Offered Load below the Committed Throughput — the window is not a Demand Window. • Requests outside the Named Profile: a different model, context length above the maximum, concurrency above the maximum, or a request shape materially departing from the profile assumptions (Section 9.5). • Requests that are not Conforming Requests: malformed, unauthenticated, or outside Party A's quotas. • Planned maintenance within the allowance in §2, notified as required; emergency maintenance to prevent imminent failure. • Party A's own network, client software, retry behaviour or connectivity. • Suspension or throttling under Schedule 5, Section 9.6 or Section 10, or regulatory action arising from Customer Content or use. • Traffic above the Committed Throughput. • The implementation period of a configuration change requested by Party A; a model becoming unavailable (Section 6.5); Customer Weights being refused, suspended or removed (Schedule 9). • Force majeure (Section 18), including new export-control, sanctions or regulatory measures after the Effective Date. • Any cause not attributable to Party B or Party B-managed infrastructure. 4. Service credits Monthly Throughput Attainment Credit (% of Monthly Commitment Fee) Notes ≥ 99.5% no credit — 99.0% to below 99.5% 5% — 97.0% to below 99.0% 10% post-incident review under §6 95.0% to below 97.0% 20% — below 95.0% 30% where the Order ticks Section 5.7, three consecutive Service Months trigger the exit right Two bases, and they are not interchangeable. (a) Phase-level metrics — monthly throughput attainment, admission latency and Service Endpoint availability — are credited on the scale above against the Monthly Commitment Fee for that Phase for that month. (b) The Allocation-Unit-level metric — availability per Allocation Unit — is credited on the same percentages against the share of the Monthly Commitment Fee apportioned to the Allocation Unit that fell short, that share being the Monthly Commitment Fee for that Phase for that month divided by the total number of Allocation Units in that Phase; where more than one unit falls short, each is computed separately and the results are added. A shortfall on a single Allocation Unit shall not be claimed against the Monthly Commitment Fee for the whole Phase. Credits of different categories are not cumulative for the same Service Month — the higher applies — and the monthly cap is 30% of the Monthly Commitment Fee for that Phase (Section 5.3). 5. Claims, application and sustained shortfall • Claims are submitted in writing by the 5th Business Day of the following month with request identifiers and timestamps; Party B confirms against metering data within 10 Business Days. • Credits are applied to the next invoice and are not paid in cash; they are Party A's sole and exclusive remedy for a throughput shortfall (Section 5.3). • Exit threshold: 95%. Where the Order ticks Section 5.7, if Monthly Throughput Attainment is below 95% in three consecutive Service Months, Party A may terminate the commitment for that Phase on 30 days' written notice without an early-termination charge; the Prepayment is governed by Section 8.3. This right is in addition to the credits. Where the Order does not tick it, this item does not apply. 6. Reporting • Monthly report by the 5th Business Day: number of Demand Windows, Window Attainment distribution, admission- latency percentiles, overflow tokens by direction (if any), Excluded Windows with reasons, and any credit due. • Customer-visible dashboard with per-minute throughput, admission latency and error rates per project.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 37 of 69 • Post-incident review within 5 Business Days for any Service Month below 97%, or for any single incident exceeding 30 consecutive Demand Windows below commitment. • For an Order with a Dedicated Serving Pool, the monthly report additionally lists the number of Allocation Units for the month and any substitutions (without serial numbers).

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 38 of 69 Schedule 4A · Service Readiness Test Protocol This Schedule sets out the Service Readiness Test run before billing for each Phase starts, the Service Ready Minutes and the verification after a configuration change (Sections 4.5 to 4.7). What the test confirms is that the serving capacity has been delivered and placed into service: quantity, hardware health, model loaded, endpoint reachable. The test also records a reference output, which carries no pass threshold and is not a commitment. This Schedule accompanies Schedule 3A. 1. Test items Test Method Pass criterion Unit count Count of Allocation Units in the pool verified (no serial numbers listed) not less than the Capacity Basis for the Phase GPU burn-in All GPUs at full load for 48 consecutive hours; temperature, power, throttling and ECC errors monitored zero uncorrectable ECC errors; no sustained hardware thermal throttling (transient clock reductions not exceeding 2% of the burn-in period in aggregate for any GPU) Intra-node interconnect NVLink / NVSwitch bandwidth and topology verification ≥ 90% of the OEM factory-test reference value for the same configuration, measured with the same tool (nvbandwidth device-to-device all-to-all) and version, or, where no OEM reference value is available, ≥ 1,400 GB/s per GPU bidirectional; topology as configured Storage Local NVMe and storage-volume read/write benchmark local NVMe, per node aggregate: read ≥ 20 GB/s, write ≥ 10 GB/s; storage volume, per node: read ≥ 3 GB/s, write ≥ 1.5 GB/s Model loading each Configuration set out in §5 of the Order loads on all Allocation Units in the capacity pool and returns valid output for its modality (text response / image / video clip / audio clip) loaded on every unit with valid output Endpoint connectivity the Service Endpoint is called with project credentials from a Permitted Region; in asynchronous mode, task submission, status query and result retrieval are additionally verified valid responses or a completed task cycle; geofencing effective Security baseline RBAC, geofencing, retention setting, log delivery and isolation configuration verified consistent with Schedule 6 Monitoring handover Metrics, alert and log channels connected; Party A receives end-to-end samples confirmed by Party A The technical thresholds in §1 apply unless the Parties confirm different thresholds in writing before the test; for any item on which §1 states no threshold, Party B's published standard thresholds for that platform generation apply. 2. Reference output (not a commitment) Once the hardware and model-loading items pass, Party B applies load with its reference load generator under the configuration stated in §5 of the Order for 30 minutes and records the reference output for that period by modality: for text, the mean input and output tokens per minute and time-to-first-token percentiles; for image, video and audio, Output Units completed per minute, task-completion-time percentiles and task success rate; together with the error rate. All of the foregoing is recorded in the test report only (not in the Service Ready Minutes or any Schedule to this Agreement), marked "reference only, not a commitment". The reference output carries no pass threshold, does not affect whether the test passes, is not a Service Level under Section 5, and gives rise to no credit or remedy.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 39 of 69 3. Report and Service Ready Minutes Party B issues a test report within 2 Business Days after each run; Party A confirms or raises specific written objections within 10 Business Days of receipt, failing which the test is deemed passed under §3.1 (Section 4.6). On passing, the Parties sign the Service Ready Minutes in the form set out after §3.1: §3.1 Deployment Completion Notice, Acceptance Rejection and SRD Formation Upon completion of deployment and of its own test run under §1, Party B shall issue a written deployment-completion notice to Party A together with the test report. Within ten (10) Business Days after receipt of the notice, Party A shall issue written acceptance or a written rejection identifying each test item in §1 that has not met its pass criterion. If Party A does neither within that period, Party B may give Party A a written reminder, and if Party A does not issue a written rejection within three (3) Business Days after receipt of the reminder, the test is deemed passed. The SRD is the date of Party A's written acceptance or of deemed passing, and billing and the Commitment Term commence on the SRD. For the purposes of Section 4.8, where the test is passed or deemed passed, the days of delay end on the date of Party B's deployment-completion notice. Rectification and re-testing follow §4, and Section 4.7 and §5 of this Schedule apply where Party A does not cooperate. MSA No. XDT-TF-MSA-2026-001 Order No. XDT-TF-MSA-2026-001-O01 Phase ☑ Phase 1 ☐ Phase 2 ☐ Supplementary Order S___ Allocation Units ____ (not below the Capacity Basis for the Phase) Model configuration ☐ Configuration A ☐ Configuration B Test window ____-__-__ __:__ to __:__ (Region local time) §1 items ☐ all passed SRD ______________, 20____ (date the test passed) Signed Party A ________________ Party B ________________ 4. Failure and re-run Where a test run fails for reasons attributable to Party B and Party A issues a written rejection identifying the test items not met, Party B shall, at its sole cost and expense, complete all rectification work and necessary retesting within ten (10) Business Days (a unit that fails being replaced and only that unit re-tested), and promptly issue a retest notice together with the full retest report to Party A upon completion. Upon receipt of such retest notice and retest report, Party A shall have a new ten (10) Business-Day review period to either confirm passing or raise specific written objections supported by evidence, to which the reminder and deemed passing in §3.1 apply. Any delay arising from Party B's failure to complete rectification and retesting within the aforesaid ten (10)-Business-Day period shall be deemed a delay caused by Party B and counted towards delay under Section 4.8. If the test fails twice on re-run for the same root-cause defect notwithstanding rectification in accordance with the foregoing, Party A may proceed in respect of that Phase under Section 19.7(b). A failure or inability to test caused by Party A's configuration materials, Customer Weights, connectivity or confirming personnel not being ready does not count; the test is re-run once Party A is ready and the Target SRD for that Phase shall be extended accordingly.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 40 of 69 5. Where Party A does not cooperate If Party A does not provide configuration materials, credentials or confirming personnel within 10 Business Days of the test date notified in writing by Party B, Party B may complete the test under §§1–2 on its own and issue the report; the date of passing recorded in that report is deemed the SRD of that Phase (Section 4.7), and the Commitment Term and billing run from that date. 6. Verification after a configuration change After a configuration change under Section 6.2 is implemented, Party B verifies only the "model loading" and "endpoint connectivity" items in §1 and issues a brief record; hardware tests are not repeated, throughput is not measured, and the SRD, the Commitment Term and the Monthly Commitment Fee are unchanged.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 41 of 69 Schedule 4B · Throughput Baseline Test Protocol This Schedule accompanies Schedule 3B (Section 2.5). What is tested is whether the Committed Throughput can be delivered sustainably under the Named Profile conditions — not a peak. Save as this Schedule provides otherwise, the hardware and security test items in Schedule 4A §1 apply equally and are completed before the throughput test in this Schedule. 1. Test conditions Item Requirement Notes Profile the named profile fixed in §5 of the Order; model, precision, context and concurrency are all as set by that profile no test until the profile is fixed Load generated by Party A's load generator or Party B's reference load generator; request shape distributed within ± 10% of the average input and output token counts assumed by the profile load script confirmed in writing before the test Concurrency sustained load at the profile's maximum concurrent requests — Target the committed input throughput and committed output throughput applicable from that Phase (the Phase 2 figures are cumulative) §6 of the Order Duration 60 consecutive minutes — Admission Threshold the number of seconds stated in the Order; tokens accepted after that timeout are not counted — Metering Party B's metering system; Party A may reconcile against its own request logs in parallel Section 5.6 2. Pass criteria • All items in Schedule 4A §1 — hardware, model loading, endpoint connectivity, security baseline and monitoring handover — have passed. • In every Measurement Window of the 60 consecutive minutes the Offered Load is at or above the target (all are Demand Windows), and the mean Window Attainment across those 60 windows is ≥ 99.5%. • Admission-latency attainment in the same period meets the figure stated in the Order. • The Service Endpoint returns 5xx for reasons attributable to Party B on no more than 0.1% of requests in the same period. 3. Report and Service Ready Minutes The reporting and confirmation procedure is as in Schedule 4A §3. On passing, the Parties sign the Service Ready Minutes which, in addition to the items listed in Schedule 4A §3, record: Named Profile(s) ☐ Configuration A ☐ Configuration B Committed Throughput input [●] TPM · output [●] TPM Result average window attainment ____% acceptance-latency attainment ____% 5xx ____% Load-script hash [●]

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 42 of 69 4. Failure and re-run • Where the test fails for reasons attributable to Party B, Party B re-runs it within 5 Business Days (Section 4.6). • A failure caused by Party A's harness, connectivity or non-conforming load does not count; the test is re-run once Party A is ready and the Target SRD is extended accordingly. • Where the test reveals that the profile parameters do not match the actual load, the Parties first correct §5 of the Order by Supplementary Order and then test against the corrected profile. 5. Where Party A does not cooperate If Party A does not provide load, credentials or confirming personnel within 10 Business Days of the test date notified in writing by Party B, Party B may complete the test using its reference load generator under the conditions in §1 and issue the report; the date of passing recorded in that report is deemed the SRD of that Phase (Section 4.7), and the commitment and billing run from that date. 6. Re-baselining A change of profile (Section 6.2), an expansion (Section 6.3) and a model substitution (Section 6.5) are each re-baselined under §§1–3 of this Schedule; the prior commitment governs during re-baselining and traffic outside the prior profile is treated under Schedule 3B §3. The result is recorded in new Service Ready Minutes identifying the profile replaced and the Service Month from which it takes effect. Where the new profile requires serving capacity beyond the Order's Capacity Basis, Party B may make its acceptance of the change conditional on a Supplementary Order (including a corresponding adjustment of the Monthly Commitment Fee); where it requires less, the Monthly Commitment Fee is unchanged — the capacity has been held for Party A.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 43 of 69 Schedule 5 · Acceptable Use Policy 1. Prohibited uses • Any military application, government classified programme, or cyber-attack activity. • The design, development, production or use of nuclear, chemical or biological weapons or missiles. • Unauthorised cryptanalysis, penetration testing, or circumvention of any security control, including attacks on or probing of the Service Endpoint, tenant isolation or other security controls. • Attempting to extract, copy or distil the weights, parameters or system prompts of catalogue models, or using outputs of the service to train a model that competes with a catalogue model (Customer Weights and Party A's own data excepted). • Generating or distributing child sexual exploitation material or non-consensual intimate imagery, or use for harassment, defamation, fraud or identity theft. • Sublicensing access, proxying, tunnelling, API forwarding, resale or any other arrangement intended to circumvent export controls or sanctions. • Infringement of third-party intellectual property, privacy or other lawful rights. • Submitting the restricted categories of data listed in Section 11.7(b) unless the Order expressly permits it. • Any use unrelated to the inference workloads stated in the Order, unless the Order provides otherwise. 2. Party A's undertakings Party A hereby reaffirms all representations and undertakings in Section 10 and confirms that: (a) it is the end user of the service, or manages its downstream users under Schedule 8 §5 (including downstream users under a resale or distribution under Section 9.3); (b) it does not use the service on behalf of any undisclosed principal; (c) it will notify Party B in writing within three (3) Business Days of any change in access territory, end use or ownership structure; (d) it will cooperate with compliance reviews by Party B, its upstream suppliers and competent authorities; and (e) it has delivered the KYC documentation required by Party B and completed sanctions screening before credentials are issued. 3. Content monitoring Where the Order elects a Dedicated Serving Pool, Party B applies no automated abuse filtering to Customer Content and performs metadata-layer compliance monitoring only; where the Order is for shared capacity, Party B additionally applies automated abuse filtering consistent with its published Acceptable Use & Export Control Policy, and a filtered request is neither a Conforming Request nor counted towards a Demand Window (Section 9.4). In either case the prohibited uses in §1 and the undertakings in §2 are not reduced; Party B does not inspect, retain or disclose Customer Content by reason of filtering, save as required by law or as necessary to investigate serious abuse. 4. Consequences Breach of any item in this Schedule entitles Party B to suspend immediately under Section 9.6 and to terminate immediately under Section 10.7, with no cure period and across all Orders. The Prepayment is non-refundable and Party A shall indemnify Party B under Section 16.1.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 44 of 69 Schedule 6 · Security, Logging and Audit 1. Platform controls Control Description Validated Tenant isolation dedicated capacity pool: dedicated nodes, a separate cage or rack, a separate compute network segment and separate storage volumes; shared capacity: separate credentials, quotas, logs and storage scope (Section 3.3) at readiness and ongoing Physical isolation dedicated capacity pool only: separate cage or rack, access control, CCTV, two- person authorisation (subject to facility conditions); no hardware shared with other tenants; the control plane processes metadata only (Section 3.3) at readiness and at the annual facility audit Encryption TLS 1.2+ in transit; encryption at rest at readiness and ongoing RBAC Role-based access control; least privilege; two-person authorisation for privileged operations at readiness Logging access logs and administrative-action logs (metadata layer), pushed to Party A's SIEM at the frequency stated in the Order; retained 10 years (Schedule 8 §3) at readiness and ongoing Geofencing Access restricted at the API layer to the territories stated in the Order; known VPN / proxy / Tor exits blocked at readiness and ongoing End-use monitoring compliance monitoring at the metadata layer; no automated content filtering on the dedicated capacity pool, with automated abuse filtering additionally applied on shared capacity (Section 9.4) ongoing Retention Per the retention setting stated in the Order; logs contain metadata only at readiness and ongoing Region pinning Control plane records where inference is processed; no migration out of the Region ongoing Decommission sanitisation Media that held Customer Weights or retained content are sanitised under NIST SP 800-88 before decommissioning, with records kept each occurrence These controls are platform specifications and are validated at the readiness stage before a Region carries customer workloads (Section 12.1). 2. Verifiability commitments Commitment Frequency Clause Contractual audit right (incl. metering) once every 12 months Section 12.3 Log delivery to SIEM as stated in the Order (real-time / daily / Section 12.2(b)

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 45 of 69 weekly) Named NOC team ongoing, visible to auditors Section 12.2(c) Quarterly security review quarterly Section 12.2(d) Annual facility audit (Dedicated Serving Pool) once a year (Dedicated Serving Pool) Section 12.2(e) · §3 of this Schedule Incident notification within 72 hours of confirmation Section 12.4 Monthly service report by the 5th Business Day of each month the elected Schedule 3 3. Dedicated Serving Pool and physical isolation Where the Order elects a Dedicated Serving Pool: (a) the pool serves Party A only during the Commitment Term and shares no node, GPU or local storage with any other tenant; (b) it is deployed in a dedicated cage or dedicated racks with its own compute-network segment and storage volumes, with access control, CCTV and two-person authorisation subject to the facility's conditions; (c) Party A may exercise a facility audit right once a year, subject to the access rules of the facility operator, which Party B shall use reasonable efforts to facilitate; (d) before any Allocation Unit leaves the pool (including on substitution or release), its storage media are sanitised in accordance with NIST SP 800-88 with records issued, and it is re- verified before return; and (e) Party B states the number of Allocation Units for that Order in the Service Ready Minutes and in the monthly report. A Dedicated Serving Pool does not alter Section 14: the pool remains owned, configured and operated by Party B, and Party A still accesses it only through the Service Endpoint. Party A may by Supplementary Order request the release of idle capacity back to Party B; before release and before return the capacity is sanitised in accordance with NIST SP 800-88 and re-verified, on the commercial terms of that Supplementary Order. Remote attestation and confidential computing are roadmap items and are not commitments under this Schedule (Section 12.6). Party B makes no commitment as to any specific certification or framework unless expressly stated in the Order (Section 12.5).

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 46 of 69 Schedule 7 · Data Protection and Data Compliance This Schedule implements Section 11. Sections 1 to 5 apply to every Order; Sections 6 to 8 are jurisdictional modules and apply only where ticked in §9 of the Order (Section 2.5). This Schedule does not alter the limitation of liability in Section 17 (Section 17.3). 1. Roles and details of processing Roles Party A is controller / business; Party B is processor / service provider (Section 11.1) Nature receiving the requests Party A submits through the Service Endpoint, generating responses in the Region and under the model configuration stated in the Order, and retaining or immediately discarding them per the retention setting stated in the Order Purpose solely to provide the Services to Party A; not for training any model, not sold, not for cross-context behavioural advertising Categories and data subjects as stated by Party A in §9 of the Order; Party B does not control what Party A submits Duration under zero retention, the period of serving the request in question; under limited retention, until the number of days stated in the Order; after termination, deleted under Section 11.6 Place of processing the Region stated in the Order, not moved out during the Commitment Term (Sections 3.4 and 11.5) Zero retention is the default and recommended setting for this service. Where zero retention is selected, Party B retains no prompt or output for any purpose beyond serving the request in question and therefore holds no Personal Data on a continuing basis, so that most obligations under this Schedule are correspondingly limited to the period of processing (Section 11.2). Limited retention brings Personal Data into Party B's environment, and Party A should assess its own compliance obligations accordingly. What "zero retention" refers to — the three layers of data and how each is treated. This service handles three categories of data on entirely different retention rules; wherever this Agreement says "zero retention" it means, and means only, the first layer. Layer What it is Under zero retention Why ① Content prompts, input materials, outputs (text / image / video / audio) and derivatives of them Not retained. Discarded once processing completes; the technical boundary (inputs and result objects of asynchronous tasks, caching, error diagnostics) is set out in Schedule 11 §10 no business or legal reason to retain; not retaining means no continuing holding of personal data (Section 11.2) ② Metadata · access side principal identifier, timestamp, source IP and resolved geolocation, authentication result, administrative actions Must be retained and cannot be switched off; contains no content whatsoever (Schedule 8 §3) the only evidence that the regional restriction is enforced; the evidence required to assert the statutory safe harbours (Schedule 11 §9) ② Metadata · usage side Request identifier, Output Unit counts, model identifier, start and end times The entire layer may be left unretained — elected in §5 of the Order; available only where there is a fixed monthly committed fee and overflow is not permitted (Schedule 8 §3) under a fixed monthly fee Party B can invoice without metering, and the service levels are measured by Allocation Unit and endpoint rather than per request; this layer is therefore not commercially necessary ③ Incident evidence records relating to a specific incident, which may include fragments of content Not generated in the ordinary course; preserved only on an incident trigger — on receipt of notice from a rights holder or a competent authority, on identification of a red flag, where a report is required by law, or where Party A gives notice under Schedule 11 §12 preservation is a precondition to asserting the safe harbours; zero retention is the default, preservation is the exception, and the exception is incident- triggered (Schedule 11 §9 and §12)

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 47 of 69 Two consequences of which Party A should be aware before choosing a retention setting: (a) layer ② metadata may itself constitute personal data in some jurisdictions (a source IP, for example); Party B processes it on the basis of legal obligation and performance of the contract, not consent, and Party A as controller should disclose this in its own privacy notice. (b) Under zero retention Party B cannot execute access, rectification or deletion for a specific data subject (§4 of this Schedule) — not as a refusal to cooperate but because there is no retrievable content to act on; Party A must perform those obligations in its own systems. Where Party A requires deletion to be executable on Party B's side, it shall elect limited retention in §5 of the Order, understanding that this brings personal data into Party B's environment and widens both Parties' compliance obligations. 2. Party B's measures • Implement and maintain the technical and organisational security measures in Schedule 6: TLS 1.2+ in transit, encryption at rest, role-based least-privilege access, and access and administrative logging. • Bind personnel with access to Personal Data to confidentiality and train them; two-person authorisation for privileged operations. • Notify Party A in writing within 72 hours of confirming a security incident involving Personal Data, describing what is known, the scope of impact and the measures taken, with updates as the investigation proceeds (Section 12.4). • Delete after termination under Section 11.6 and, on request, issue a certificate of deletion. • Not use Personal Data for its own purposes; not disclose it to third parties other than sub-processors and as required by law. • Where a competent or law-enforcement authority makes a request concerning Customer Content, notify Party A first to the extent legally permitted and provide only what it is legally required to provide. 3. Sub-processors Category Role Location Party B Affiliates operations, monitoring and support United States NVIDIA Cloud Partner operating partner equipment operations within the facility the Region stated in the Order Data-centre operator facility, power and physical access control; no access to Customer Content the Region stated in the Order The legal names and contact details of the current sub-processors are provided separately as Party B's Confidential Information under Section 13.4. Additions and replacements follow Section 11.4: 30 days' notice, with Party A able to object in writing on reasonable data-protection grounds within 10 Business Days. 4. Data-subject requests and assistance • Under zero retention Party B holds no retrievable Personal Data and cannot execute access, rectification or deletion for a specific data subject; Party A performs those obligations in its own systems. • Under limited retention Party B shall, within 10 Business Days of Party A's written request, assist so far as technically feasible in locating, exporting or deleting the relevant records. • Where Party B receives a data-subject request directly, it shall not respond substantively (beyond confirming its role as processor) and shall forward it to Party A within 5 Business Days. • Party B provides reasonable assistance with data-protection impact assessments and enquiries from supervisory authorities; Party A bears the reasonable cost of assistance beyond Party B's ordinary operations. 5. Audit and evidence Party A's audit rights in respect of data protection are limited to Section 12.3 (once every 12 months, on 30 days' notice, at Party A's cost, without access to other tenants' data). Party B additionally provides a written description of the controls listed in Schedule 6, a summary record of security incidents and, where available, third-party assessment reports — all provided separately as Party B's Confidential Information under Section 13.4. Party B makes no commitment as to any specific certification or framework unless expressly stated in the Order.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 48 of 69 6. GDPR module (EEA / UK / Switzerland) Applies only where "GDPR" is ticked in §9 of the Order. This Section constitutes the processor terms required by Article 28 of Regulation (EU) 2016/679 (and the corresponding provisions of the UK GDPR and the Swiss FADP): • Party B processes Personal Data only on Party A's documented instructions (this Agreement and the Order constitute those instructions); where Party B considers an instruction to infringe applicable data protection law it shall inform Party A without delay and may suspend that instruction until clarified. • Confidentiality (§2), security (Article 32, see Schedule 6), general authorisation of sub-processors with a notification mechanism (§3), assistance with Articles 32 to 36 (§4), assistance with data-subject rights (§4), deletion or return after termination (Section 11.6), and making information available to Party A and allowing audits (§5). • Transfer mechanism: where the Region is outside the EEA, the Parties execute the standard contractual clauses approved by Commission Decision 2021/914 (module two: controller to processor), Party A as data exporter and Party B as data importer; UK data takes the IDTA or the UK Addendum, and Swiss data the corresponding amendments. The clauses so selected are incorporated into this Agreement and prevail over this Schedule in the event of conflict. Options: Clause 7 (docking) does not apply; Clause 9 takes option 2 (general written authorisation) with a 30-day notice period; Clause 11 does not include an independent dispute-resolution body; and the governing law and courts under Clauses 17 and 18 are those of Ireland. The Appendices are completed by §§1–3 of this Schedule and §9 of the Order. • Transfer impact assessment: Party B shall provide, so far as reasonably necessary, the information known to it concerning government access requests in the jurisdiction of processing in order to assist Party A's assessment; Party B is not obliged to provide information it is prohibited by law from disclosing. 7. PIPEDA module (Canada) Applies only where "PIPEDA" is ticked in §9 of the Order. Party B processes personal information as Party A's service provider and confirms that: (a) processing is limited to what is necessary to provide the Services to Party A; (b) Party B affords a level of protection comparable to that required by the Personal Information Protection and Electronic Documents Act in accordance with Schedule 6; (c) Party A acknowledges, and shall inform its individuals, that personal information is processed in the Region stated in the Order (the United States) and may therefore be subject to the laws and government access requests of that jurisdiction; (d) Party B assists Party A with access and correction requests under §4 of this Schedule; (e) security incidents involving a real risk of significant harm are notified under §2 of this Schedule so that Party A can discharge its reporting obligations to the Commissioner and to individuals; and (f) where applicable provincial law (including Quebec's Law 25) requires additional terms, the Parties agree them by Supplementary Order. 8. CCPA / CPRA module (California) Applies only where "CCPA / CPRA" is ticked in §9 of the Order. For the purposes of the California Consumer Privacy Act as amended by the CPRA: Party A is the "business" and Party B is a "service provider". Party B acknowledges and undertakes that it: (a) does not sell or share personal information and receives no consideration in exchange for it; (b) processes personal information only for the business purposes set out in this Agreement and the Order, and does not retain, use or disclose it for its own commercial purposes (including cross-context behavioural advertising); (c) does not combine personal information received from Party A with personal information from other sources, save as necessary to detect security incidents or prevent fraud; (d) provides reasonable security measures in accordance with Schedule 6; (e) notifies Party A promptly if it determines that it can no longer meet its obligations under this Section; and (f) permits Party A to take reasonable and appropriate steps under §5 of this Schedule to verify that Party B's processing is consistent with this Section. Party B's sub-processors are bound by obligations comparable to this Section. 9. Conflict Where a ticked module conflicts with §§1–5 of this Schedule, that module prevails; where this Schedule conflicts with the remainder of this Agreement, this Agreement prevails, save to the extent that applicable data protection law mandates otherwise (Section 11.9).

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 49 of 69 Schedule 8 · Export Control and Cross-Border Compliance This Schedule implements Section 10. Party B has given cloud-service undertakings to its upstream suppliers covering the screening of customers and downstream users before access, geographic access control and log retention. Party B can discharge those undertakings only through Party A's performance, and this Schedule passes them through. Where Party A uses the Services internally only and has no downstream users, §5 does not apply and the remaining Sections continue to apply. 1. Information before access (KYC) Item Content Timing Entity legal name, place of incorporation, registration number, registered and operating addresses, organisation chart before credentials are issued; a condition precedent under Section 4.4(b) Ownership direct and indirect shareholders, controllers and ultimate beneficial owners (holding ≥ 10%) before credentials are issued Individuals directors, officers, authorised signatories and technical contacts before credentials are issued End use the nature of the workload, the industry, and the types of downstream user; entered in §8 of the Order before credentials are issued Territories the list of countries and regions from which access is intended; entered in §8 of the Order before credentials are issued Screening Party B screens the above entities and individuals against the lists in Section 10.2 and retains the records before credentials are issued, and re-screened every 12 months thereafter 2. Geographic access control • Access is limited to the territories permitted in §8 of the Order (Section 10.6). Party B enforces geofencing at the API layer; where Party A provides capability downstream through its own products, it shall enforce the same at its application layer by source-IP geofencing and by blocking known VPN, proxy and Tor exit nodes. • Party A shall not instruct, assist or acquiesce in any user circumventing the territorial restriction; upon detecting circumvention, Party A shall immediately suspend that user and notify Party B. • Any change to or addition of permitted territories requires a prior written request and Party B's written consent. Party B may first need the consent of its upstream suppliers and therefore gives no undertaking as to turnaround time. 3. Log retention Log Content Retention Can it be omitted Access Subject identifier, timestamp, source IP and resolved geolocation, authentication result 10 years No — it is the only evidence that the regional restriction (Section 10.6) is enforced, and the evidence required to assert the statutory safe harbours (Schedule 11 §9) Usage Request identifier, Output Unit counts, model identifier, start and end times 10 years Yes — where "usage logs not retained" is elected in §5 of the Order, Party B does not retain the contents of this row; available only where that Order is on a fixed monthly committed fee and overflow is not permitted (otherwise there is no basis on which to invoice) Administrative Account creation, changes and revocation; permission and quota changes 10 years No

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 50 of 69 Screening per §§1 and 5 10 years No The basis of the retention period, disclosed as it is. The 10 years above is the period Party B has undertaken to its upstream suppliers and is stricter than the legal floor; the recordkeeping obligation under applicable law is generally 5 years. If those suppliers' requirements change, Party B may shorten the period to the legal floor upon written notice to Party A, and such shortening is not a breach as regards Party A. These logs are at the metadata layer and contain no content of Party A or its downstream users, consistent with Section 9.4. Logs shall be retrievable by user entity. 4. Availability of records Party A shall provide the records and logs listed in this Schedule within 10 Business Days of Party B's written request. Where a competent authority, Party B's upstream suppliers or the original manufacturer so requires by law or by contract, Party A shall provide them within 5 Business Days of Party B's notice, or shall consent to Party B providing them directly. Party A shall not withhold the metadata-layer records listed in this Schedule on grounds of commercial confidentiality. 5. Downstream access control Applies where "used in Party A's own products" or "resale or distribution" is ticked in §8 of the Order (Sections 9.3 and 10.10). Item Requirement Notes Subjects Every downstream user entity granted access, and its known controllers and ultimate beneficial owners Natural-person users are screened by their employer entity Lists OFAC SDN and Consolidated · BIS Entity List / Denied Persons / Unverified / Military End User · EU · UN · UK · Canada Current versions as at the date of screening Timing Before access is granted; re-screened every 12 months thereafter Existing users re-screened when lists are updated Records Date of screening, lists and versions used, result, person performing retained 10 years Hits access must not be granted; any access already granted must be suspended immediately, and Party B notified in writing within 24 hours Section 10.9(e) applies in parallel Flow-down Sections 10.3, 10.4 and 10.6 are imposed on downstream users by contract Party B may require sample clauses to be produced Flow-down through the chain where a downstream user in turn provides the Services to its own customers, it is required by contract to perform the equivalent obligations of this Section in respect of those customers (screening, records, handling of hits and flow-down) Section 9.3 · Section 10.10(d) Direct resellers name and place of incorporation stated in §8 of the Order; written notice to Party B within ten (10) Business Days after any change or addition Section 10.10(e); Party B may screen them against the lists

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 51 of 69 6. Annual attestation By the date stated in §8 of the Order, Party A shall deliver a written attestation signed by an authorised representative confirming that: (a) the obligations in this Schedule have been performed continuously over the preceding twelve months; (b) all screening hits, circumvention events and territorial changes during that period were notified as required; and (c) all representations and warranties in Section 10 remain true, accurate and complete as at the date of the attestation. Failure to deliver the attestation when due entitles Party B to suspend under Section 9.6(d). 7. Audit Once every 12 months, on not less than 15 Business Days' prior written notice, Party B may audit Party A's performance of this Schedule, limited to screening records, geographic control configuration and logs. Audits required by a competent authority or by an upstream supplier are not subject to the frequency or notice limits. Where a material non-conformity is found, Party A shall remediate within 30 days at its own cost. 8. Consequences Breach of this Schedule constitutes a breach of Section 10 and attracts Section 10.7: immediate suspension or termination of all Orders with no cure period, the Prepayment non-refundable, and the indemnity in Section 16.1; such breach is not subject to the liability cap in Section 17.2 (Section 17.3(b)).

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 52 of 69 Schedule 9 · Customer Weights and Bring-Your-Own Model This Schedule has a single purpose: to let Party A use its own model weights without Party A acquiring any access to the infrastructure. Weights are loaded by Party B, run by Party B, with Party B holding the highest privilege level — of a piece with Sections 14 and 10.11. This Schedule covers weights, adapters, tokenisers and configuration files only; running Party A's own inference framework, scheduler or any code on Party B's infrastructure is outside the Services under this Agreement and requires Party B's Master Compute Services Agreement (Section 3.5). 1. Scope "Customer Weights" means model weights (including fine-tunes and adapters such as LoRA), tokenisers and inference configuration files delivered by Party A for hosting by Party B. Customer Weights are Party A's assets (Section 13.1). This Schedule applies to any configuration for which "Customer Weights" is ticked in §5 of the Order. 2. Delivery and hosting Item Content Timing Delivery Uploaded through an encrypted channel designated by Party B, with format notes, licence and integrity hash 10 Business Days before the planned readiness test Classification Export-control classification of the Customer Weights themselves and the licensing basis (if applicable) With delivery Review Format, licence, security and compliance review; Party B may request further material or refuse 5 Business Days after receipt of complete materials Loading & serving Loaded and served by Party B within its serving stack; Party A obtains no host or runtime access After the review passes Readiness check for Configurations whose model is Customer Weights, loading and endpoint connectivity are verified under the elected Schedule 4; where Schedule 3A is elected, throughput is not tested and not committed Section 6.2 · Schedule 4 3. Party B's rights • Party B may refuse to load, suspend the serving of, or remove any Customer Weights on security, compliance, stability, licensing or export-control grounds, giving reasons so far as reasonably practicable. Resulting unavailability is excluded from the Service Levels and does not relieve Party A of its payment obligations. • Party B uses Customer Weights solely to provide the Services to Party A, not for other customers, not for training, and does not copy them outside the Region (disaster-recovery copies require Party A's written consent). • Party B's access to Customer Weights is role-based, least-privilege and logged, with logs made available to Party A under Schedule 6. 4. Party A's warranties • Party A holds the rights and licences necessary for the Customer Weights; their hosting and serving infringe no third- party rights and comply with the licence terms of the base model. • The Customer Weights are not themselves subject to export control restrictions, or Party A holds all authorisations necessary for their provision and serving; Party A has disclosed their classification to Party B accurately. • The Customer Weights and configuration files contain no executable code, malicious payload or undisclosed call-home behaviour, and are not used to circumvent any restriction in Section 10.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 53 of 69 • The data used to train the Customer Weights were lawfully obtained, and Party A holds all consents necessary for their processing. 5. On termination Upon termination or expiry of the relevant Order or of this Agreement, Party B deletes all Customer Weights and the caches and fine-tuning artefacts derived from them under Section 11.6, issuing a certificate of deletion upon Party A's written request. Party B retains no copies, save for any legally required or archival copy permitted under Section 11.6.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 54 of 69 Schedule 10 · Change Control and Supplementary Orders This Schedule sets out how changes after an Order is formed are handled. The principle: technical changes that do not alter the commercial consideration are handled by written request; any change to capacity, price, term, prepayment or service levels is handled by Supplementary Order (Section 6). 1. Routing table Change Route Takes effect Effect on fees a different model, context length, concurrency, precision or retention setting within the existing Capacity Basis written request (Section 6.2) implemented within 10 Business Days, verified under the elected Schedule 4 none enlarging the Capacity Basis, adding a Phase, adding an Order Supplementary Order or new Order (Section 6.3) on signature, per the new Phase's Target SRD additional Monthly Commitment Fee reducing the Capacity Basis at renewal only (Section 6.4) on renewal per the renewal terms releasing idle capacity (Dedicated Serving Pool) Supplementary Order (Schedule 6 §3) after sanitisation and re- verification per the Supplementary Order changing Committed Throughput or the Admission Threshold (Schedule 3B) Supplementary Order plus re- baselining under Schedule 4B the first day of the Service Month after the new baseline passes as set out in the Supplementary Order switching between Schedules 3A and 3B Supplementary Order (Schedule 4 switches with it) on signature and completion of the corresponding test as set out in the Supplementary Order changing the Region or facility Region: Supplementary Order; facility within the Region: 90 days' notice from Party B (Section 3.4) per the Supplementary Order or the notice a change of Region may reprice adding or changing permitted territories prior written request plus Party B's written consent (Section 10.6, Schedule 8 §2); §8 of the Order is then updated by Supplementary Order the date of Party B's written consent none changing the data-protection module Supplementary Order (updating §9 of the Order and executing any transfer instrument) on signature none changing notice contacts written notice, 5 Business Days in advance (Section 21.3) on expiry of the notice none amending the body of this Agreement a written amendment signed by both Parties (Section 22.3); the Sections listed in 2.4(a) additionally require confirmation under that Section on signature as the case may be 2. Form of a Supplementary Order A Supplementary Order may be made in short form but shall state at least the following items; once signed by both Parties' authorised representatives it forms part of the original Order and the terms of this Agreement apply to it (Sections 1.13 and 6.8). Supplementary Order No. XDT-TF-MSA-2026-001-O01-S01 (numbered sequentially) Order varied Order no. XDT-TF-MSA-2026-001-O01, signed ____-__-__ Master Agreement XDT-TF-MSA-2026-001 Subject of the variation [●] (by reference to the routing table in §1)

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 55 of 69 Capacity Basis as varied [●] (if applicable) Monthly Commitment Fee as varied USD [●] per Service Month (incremental or substitutional, to be stated expressly) Commitment Term as varied [●] months from ☐ the SRD of the Phase covered by this Supplementary Order ☐ co- terminous with the original Order Prepayment [●] (if applicable; applied as under Section 8) Target SRD [●] Schedules 3 / 4 elected ☐ as in the original Order ☐ changed to: [●] Validity valid only if countersigned by Party A within 14 days of issuance by Party B, failing which it lapses Signed Party A ________________ Party B ________________ 3. What is not a change • Party B substituting hardware, adjusting the composition of capacity or migrating workloads within the Region (Section 14.3) — provided the quantity is not below the Capacity Basis and the Service Levels are not diminished. • Version updates and security patches of a model (Section 6.5). • Party B's updates to its technical documentation (Section 22.3) — which shall not diminish service levels or security controls. • Party B designating an Affiliate as the providing entity under Section 20.2.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 56 of 69 Schedule 11 · Output Content, Abuse Prevention and Allocation of Responsibility This Schedule applies in full to any Order under which a generative model is deployed, and is the highest-risk Schedule in this Agreement where a generative image, video or audio model is deployed. It does three things: (1) it places responsibility for Output Content with Party A (§§2–6); (2) it gives Party B the right to act immediately on notice or on red flags (§7); and (3) it preserves Party B's statutory protections — the law provides safe harbours and mitigation for providers that perform their reporting, notice-and-takedown and self-disclosure obligations, and whether Party B can rely on them depends on Party A cooperating under §9 and notifying and preserving under §12. 1. Scope This Schedule applies to the inputs Party A submits through the Service Endpoint (including prompts, reference images, reference audio and video, seeds and control signals) and to all output generated from them (including text, images, video, audio and derivatives), together the "Output Content". Schedule 5 (Acceptable Use Policy) applies concurrently; where this Schedule conflicts with Schedule 5, this Schedule prevails. 2. Responsibility for Output Content rests with Party A Party B runs the model; Party A decides what is generated and how it is used. Party A bears sole responsibility for its inputs, for its instructions to the model, and for the generation, storage, modification, publication, distribution and commercial exploitation of Output Content. Party B neither reviews, approves nor endorses Output Content and gives no express or implied warranty as to its accuracy, lawfulness, non-infringement of third-party rights or fitness for Party A's purposes (Section 15.4). Party A acknowledges that generative models may produce inaccurate, misleading, offensive or infringing content; this is inherent in the technology, is not a breach by Party B, and gives rise to no service credit or other remedy. 3. Prohibited output In addition to the prohibited uses in Schedule 5 §1, Party A shall not use the Services to generate, and shall not instruct or permit its users to generate: • Child sexual abuse material, or any sexualised depiction of a minor, whether photorealistic or not and whether or not asserted to be fictional. • Non-consensual intimate imagery, including nudity or sexual content generated depicting a real person. • Deepfakes of identifiable real persons — realistic depictions of a person's likeness, voice or performance generated without that person's written authorisation, including political figures, public figures and deceased persons whose rights may vest in heirs or arise under state law. • Disinformation relating to elections, public health or public safety, including fabricated official statements, voting instructions and emergency notices. • Substantial reproductions of copyright-protected works, characters or trademarks, or generation intended to circumvent a rightholder's technical measures. • Forged identity documents, currency, negotiable instruments, signatures, seals or official documents. • Processing intended to defeat content provenance signals (such as C2PA or watermarking), or the removal or alteration of provenance signals embedded by Party B or by the model. • Any other content prohibited by applicable law, including the law of Party A's and its users' locations and of the destinations where the content is distributed. 4. Model safety filters shall not be disabled Safety filters built into catalogue models (including NSFW filters, person-recognition restrictions and prompt-refusal mechanisms) remain enabled by default. Any request by Party A to disable or bypass such a filter must be ticked in §5 of the Order and requires Party B's written consent; Party B may refuse for any reason, and a refusal is not a breach, does not relieve Party A of payment obligations and gives rise to no remedy. Where consent is given, Party A bears unlimited responsibility for all Output Content generated while the filter is disabled; that liability is not subject to the cap in Section 17.2 (Section 17.3) and attracts the indemnity in Section 16.1. Circumventing a filter by technical means without consent is a material breach of this Schedule and of Schedule 5, and Party B may suspend immediately under Section 9.6 and terminate all Orders under Section 19.6.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 57 of 69 5. Likeness, name and voice Party A warrants that, where Output Content features the likeness, name, voice or performance of an identifiable natural person, Party A has obtained all written authorisations necessary from that person (or their successors in right) for such generation and use, and has complied with applicable rights of publicity, name and likeness laws and related state legislation (including without limitation the legislation of California and Tennessee concerning digital replicas and voice simulation). Where Party A supplies its own material (photographs, audio or video recordings) as reference input, Party A warrants that it holds the necessary rights in that material and that its use is within the scope of the licence under which it was obtained. 6. Copyright and third-party material • Party A warrants that it holds the necessary rights or licences in all input material it submits. • Party A assesses the copyright position of Output Content for itself. Party B makes no representation or warranty as to whether Output Content is capable of copyright protection, in whom it vests, or whether it infringes third-party copyright; Party B gives no intellectual property indemnity (Section 16.2). • The licence terms of catalogue models may restrict the use, attribution or commercialisation of output. Party A shall review and comply with the licence terms of the models it uses; Party B shall provide the text of the applicable licence terms on Party A's written request. Restrictions in or changes to those terms are not a breach by Party B (Section 6.6). • Where Party A uses Customer Weights, the warranties in Schedule 9 §4 apply and extend to Output Content generated with those weights. 7. Party B's right to act Party B may immediately take one or more of the following steps — suspending the relevant model configuration, removing or blocking particular output, restricting or revoking particular credentials, or suspending the service under that Order or all Orders (Section 9.6) — where: (a) Party B receives a notice or demand from a rightholder, a competent authority, a law- enforcement agency or its upstream suppliers; (b) Party B reasonably suspects, on the basis of metadata, complaints or external reports, that generation of the kind listed in §3 is occurring; or (c) continued provision would cause Party B to breach applicable law, its suppliers' compliance undertakings or model licence terms. Action under this Section is not a breach by Party B, does not relieve Party A of its payment obligations, is excluded from the Service Levels (Section 5.4) and gives rise to no liability. Party B shall explain its action to Party A afterwards so far as reasonably practicable. 8. Notice-and-takedown and Party A's cooperation • Party B maintains a copyright notice-and-takedown process and a designated agent in respect of the services it provides; on receipt of a formally compliant notice Party B may act under §7 and shall forward the notice to Party A. • Party A shall respond in writing within 5 Business Days of receiving a notice forwarded by Party B, stating its position and intended steps, and shall where necessary remove the content from its own systems and distribution channels. • Where Party A provides capability downstream through its own products, Party A shall establish and maintain its own notice-and-takedown, appeal and enforcement process for its downstream users, and shall provide records of its operation within 10 Business Days of Party B's written request. 9. Statutory safe harbours and Party A's duty to cooperate Disclosed as it is: the obligations below rest on Party B and are neither displaced nor transferred by anything in this Agreement — but performing them is itself the basis of Party B's protection from liability. Party B's ability to rely on that protection depends on Party A's cooperation under this Section; where Party A does not cooperate and Party B thereby loses that protection, Party A indemnifies Party B for all consequences under Section 16.1. Matter Party B's obligation and its protection What Party A must do Reporting of child sexual exploitation material Once Party B becomes aware of the relevant facts, applicable law obliges it to report to the competent authority and to preserve records; a good-faith report made in accordance with law is protected by a statutory immunity from civil and criminal liability, but that immunity is conditional on the report being truthful and accurate — in the report Party B may state only the basis on which it acted (metadata, third-party notice, Party A's notification) and must not claim to have reviewed content that it did not review (the must not invoke any confidentiality undertaking, any zero-retention setting or any provision of this Agreement to prevent the report or the preservation of records; must, on Party B's request, provide accurate facts within its knowledge; and must not ask Party B to make any inaccurate statement in the report

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 58 of 69 monitoring position in Section 9.4). Copyright infringement Party B undertakes to establish and maintain, for the Services it provides, a notice-and-takedown process and a registered designated agent, and to take measures against repeat infringers; until that registration is completed Party B makes no representation that it has been; a qualifying service provider is, as a matter of law, shielded from monetary liability for its users' infringing content, provided that Party B lacks knowledge, receives no direct financial benefit from the infringement, and acts expeditiously upon receipt of a compliant notice. must respond in writing within 5 business days of Party B forwarding the notice (§8); must remove the material from its own systems and distribution channels; must not continue to generate content of the same kind after receiving the notice; and must not ask Party B to delay acting Export controls and sanctions The obligations in Section 10 and Schedule 8 fall on Party B. Where a violation comes to light, Party B may make a voluntary self-disclosure to the competent authority; a timely, complete and cooperative disclosure is a statutory basis for mitigation, while deliberate non-disclosure is an aggravating factor. Whether, when and what Party B discloses is for Party B alone to decide. must notify Party B in writing immediately, and in any event no later than 24 hours, after becoming aware of any fact that may constitute a violation (Section 10.9(f)); must preserve the relevant records and not destroy them; must provide accurate information and cooperate in Party B's disclosure and any subsequent proceedings; and bears its own costs of doing so Downstream requirements of model licensors As a licensee, Party B is obliged to pass through the licensor's restrictions on the use of outputs; Party B's restricting a use on that basis is not a breach (Section 6.6). must comply with the licence restrictions passed on by Party B, and must not set its commercial expectations against those licence terms Compulsory process from other authorities Compulsory process that must be complied with by law is handled under Schedule 7 §2: Party A is notified first to the extent the law permits, and only the scope legally required is produced. must not invoke confidentiality to obstruct Party B's performance of a legal obligation; if the process is to be challenged, Party A does so in its own name and at its own cost Party A acknowledges and agrees that any report, disclosure, preservation of records or remedial action taken by Party B in order to rely on any of the foregoing protections is not a breach of Section 13 (confidentiality), Section 11 (data protection) or Schedule 7, gives rise to no service credit or other remedy, and that the related time is excluded from the Service Levels (Section 5.4). 10. The technical boundary of retention Where the Order elects zero retention, Party B retains no input or output for any purpose beyond serving the request in question (Section 11.2 and Schedule 7 §1). Disclosed as it is, however: inference necessarily produces the short-lived retention listed below, and Party B does not use the phrase "zero retention" to deny that it exists. Beyond the table below, zero retention means zero retention. Where What it is How long Can it be switched off Inference buffers decode buffers, intermediate frames, temporary files — inherent to the generation process itself for the duration of generation; released on completion No — it is a constituent part of inference Asynchronous task objects in asynchronous mode, inputs awaiting processing and result objects awaiting retrieval (video, long-form audio and batch generation normally use this mode) until Party A retrieves them, or until the retrieval window stated in the Order expires (24 hours if not stated), whereupon they are deleted No, but the retrieval window may be shortened in §5 of the Order Prompt and prefix cache to reduce latency and cost, the inference stack may cache prompt prefixes in host or device memory and reuse them across requests. This constitutes retention of content across requests the life of the cache; at most until that model instance restarts. Never written to disk, never placed in persistent storage, never shared across tenants — and on a dedicated capacity pool, never shared with any tenant other than Party A (Section 3.3) Yes. If Party A requires it, "prompt caching disabled" is noted in §5 of the Order and Party B disables it for that Configuration; disabling it materially increases latency and unit cost, with the commercial effect as set out in the Order

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 59 of 69 Error diagnostics exception and crash diagnostics, which may contain fragments of content at most 7 days, solely for fault diagnosis; not used for any other purpose and not used for training Yes — Party A may require in §5 of the Order that content-bearing diagnostic collection be switched off, at the cost of reduced fault-diagnosis capability Safety filter records records of filter determinations, which may contain feature values derived from the blocked content at most 30 days No — it is the basis on which §3 and §7 are enforced In every case the foregoing: (a) does not enter Party B's long-term storage; (b) is not used to train any model; (c) is not disclosed to third parties, save where disclosure is legally required or compulsory process is complied with under Schedule 7 §2; and (d) under a Dedicated Serving Pool occurs entirely within that Order's serving capacity (Section 3.3). Where Party A requires stricter handling, it shall state so item by item in §5 of the Order. Nothing in this Section conflicts with the preservation duties in §§9 and 12 of this Schedule — preservation is an event-triggered exception, not routine retention. 11. Downstream users Where Party A provides generative capability based on the Services to downstream users through its own products: (a) Party A shall bind its downstream users by contract to §§3, 4, 5 and 6 of this Schedule; (b) Party A is responsible to Party B for its downstream users' Output Content to the same extent as for its own; (c) the screening and logging obligations in Schedule 8 §5 apply concurrently; and (d) Party A shall maintain a reporting and enforcement channel for downstream users (§8). Party A may not rely on the fact that output was generated by a downstream user to reduce its responsibility under this Schedule. 12. Party A's duties to notify, preserve and evidence This Section is what makes §9 work. Party B's protection rests on being able to prove what it did at the time, and the relevant facts are usually in Party A's hands alone. • Immediate notice. Party A shall notify Party B in writing immediately, and in any event within 24 hours, upon becoming aware that: (a) it or a downstream user has generated content of a kind listed in §3; (b) it has received any third-party claim, notice or complaint concerning Output Content; (c) any competent or law-enforcement authority has approached it concerning Output Content; or (d) a safety filter has been circumvented or credentials used without authorisation. • Preservation. Upon any of the above, Party A shall immediately preserve the relevant records in its possession (including prompts, output, account and access logs, downstream user identities and timestamps) for not less than 5 years or until the matter is finally resolved, whichever is later, and shall not destroy, alter or purge them under a retention policy. Party A's election of zero retention does not reduce this obligation — Party A shall retain the necessary records on its own side. • Evidentiary cooperation. On Party B's written request Party A shall provide those records and a statement of facts within 5 Business Days, truthfully, accurately and completely; Party B may provide them to competent authorities, its upstream suppliers, insurers or legal advisers in order to rely on the protections in §9. Party A shall not withhold the records listed in this item on grounds of trade secrecy, confidentiality or data protection. • No inaccurate statements. Party A shall not request, induce or cause Party B to make an inaccurate statement in any report, disclosure or response, including any statement that Party B reviewed content it did not review. Where Party A's breach of this item causes Party B to lose a statutory protection, Section 16.1 applies and that liability is not subject to the cap in Section 17.2 (Section 17.3). • Consequences. Where Party A fails to notify, preserve or cooperate under this Section, in addition to the indemnity in Section 16.1 Party B may suspend immediately under Section 9.6 and terminate all Orders under Section 19.6. 13. Allocation of responsibility Breach of this Schedule is a material breach. Party B may suspend immediately under Section 9.6 and terminate all Orders under Section 19.6 with no cure period; the Prepayment is non-refundable (Section 8.3). Party A shall defend and indemnify Party B under Section 16.1 against all third-party claims arising from Output Content. Party A's liability for breach of §3 or §4 of this Schedule is not subject to the cap in Section 17.2 (Section 17.3).

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 60 of 69 Schedule 12 · Customer Eligibility and Conduct Undertakings This Schedule applies to every Order and cannot be excluded by an Order. It does three things and only three: (1) it casts Party A's eligibility as continuing conditions — at any moment they are not met, Party B may stop the service immediately; (2) it converts the obligations the law places on Party B into Party A's contractual obligations and continuing warranties, item by item; and (3) it makes Party A liable for all of Party B's loss where Party A's failure to cooperate causes Party B to lose a statutory protection, without the cap in Section 17.2. This Schedule does not, and cannot, alter the obligations the law places on Party B itself. Party B's responsibility to competent authorities is not transferred by it; what this Schedule gives Party B is a right of recovery against Party A and a right to stop. 1. Eligibility — continuing conditions, not one-off representations The following are conditions Party A must satisfy continuously throughout this Agreement and every Order. The failure of any one of them at any moment is an "Eligibility Event" under this Schedule; upon an Eligibility Event, whether or not Party A has given notice and whether or not it is attributable to Party A, Party B may immediately suspend the service under all Orders under Section 9.6 and terminate under Section 19.6, in each case with no cure period. # Continuing condition How it is assessed E1 neither Party A nor any of its directors, officers, controlling shareholders or ultimate beneficial owners is on any list referred to in Section 10.2, nor is any of them controlled by such a person assessed against the then-current version of each list on the date of screening; not conditional on Party A's knowledge E2 direct and indirect holdings in Party A by listed persons are below 50%, individually and in aggregate aggregated, irrespective of whether the shareholders are related to one another; the 50% rule in force under sanctions applies, as does any aggregate-holdings rule under another regime once it takes effect E3 Party A's ultimate parent is not headquartered in a country listed in Country Group D:5 (which includes China; under the EAR, Hong Kong is treated as part of China) or in Macau; or it is, but the use is strictly limited to the inference use set out in §3 and Party B has confirmed it in writing under §1.1 assessed on incorporation documents, public disclosures and Party A's written statement; the place of headquarters, not the place of incorporation E4 Party A is not a person of a comprehensively sanctioned country or region, nor directly or indirectly controlled by such a person as for E1 E5 Party A is the genuine user of the Services, or manages its downstream users under §5 (including downstream users under a resale or distribution); it does not use the Services on behalf of any principal not disclosed to Party B Party A's written statement plus Party B's verification under Section 10.5 E6 Party A continues to meet the state of facts described in the KYC materials it submitted to Party B; any material change in those materials has been notified under §2 assessed on the materials submitted by Party A and its subsequent notices E7 Party A is not under investigation by, and has not been penalised or made subject to restrictive measures by, any competent authority on export-control, sanctions, anti-money-laundering, anti-bribery, fraud or data-compliance grounds Party A's written statement plus publicly available information Quarterly self-certification. Within ten (10) Business Days after the end of each calendar quarter Party A shall deliver a written confirmation, signed by an authorised representative, that E1–E7 were satisfied continuously throughout that quarter. Failure to deliver it entitles Party B to suspend under Section 9.6 and is itself an Eligibility Event. Quarterly self-certification does not replace the annual attestation in Schedule 8 §6, nor the immediate notice obligations in §2. 1. Conditions for Party B's written confirmation under E3 The second limb of E3 is not something to be signed casually. Where Party A's ultimate parent is headquartered in a country listed in Country Group D:5 (which includes China; under the EAR, Hong Kong is treated as part of China) or in Macau, Party B gives its written confirmation only where all five items below are satisfied; if any is not, Party B shall not confirm. This is not an internal process of Party B but the boundary of what Party A may ask for — Party A shall not invoke the

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 61 of 69 commercial relationship, a prior confirmation or any other ground to require confirmation where the conditions are not met. Party B's refusal to confirm is not a breach, does not relieve Party A of its payment obligations and gives rise to no remedy. # Condition Why C1 E1, E2 and E4 are satisfied and Party B has completed and recorded in writing the list screening and the aggregate-holdings calculation Passing screening and this confirmation are two separate conditions: screening answers whether Party A is a person one may not deal with; this item answers whether the transaction needs a further gate. Passing the first does not decide the second C2 The use is limited to inference and is recorded in the end-use statement in §8 of the Order: inference on already-trained models only, no training, pre-training, continued training or fine-tuning, and no use of the output of the Services to train any model (§3). Where Party A declines to state this, no confirmation is given that training is architecturally impossible is Party B's guarantee; the end-use statement is Party A's representation. Both are needed, and without the second Party B has nothing to evidence C3 Party B has completed a red-flag assessment on Party A and recorded its conclusion in writing (the items and sources are set out in Schedule 8) "knowledge" under the export control rules includes reason to know and deliberate avoidance; a confirmation without a written assessment has no basis C4 The Order does not elect Schedule 9 (Customer Weights / bring-your- own model). Where Party A requires Party B to host its own weights, no confirmation is given Party B's undertakings to its upstream suppliers prohibit training or hosting models for restricted third parties; inference on Party B's catalogue models falls outside that, but placing Party A's own weights with Party B may fall within "hosting" C5 The Committed Term of the Order does not exceed twelve (12) months; where it does, the Order must expressly allocate the consequences of a change in the rules — that is, how the Prepayment under Section 8.3 is treated where Party B terminates for compliance under Section 19.8 and that termination is not attributable to Party A — and must record Party A's written acknowledgement of that risk a change in the control rules applies immediately to services being provided and the fact that the contract was signed first is no defence (Section 19.8). A long term is a bet that the rules will not change; when that bet loses the fight is over who keeps the Prepayment (Section 8.3: not refundable where termination is after the SRD), and this item settles that in one line at signature rather than leaving it to be argued later The confirmation is revocable. Where any condition above ceases to be satisfied after confirmation is given (including a change in Party A's ownership, control or place of headquarters, or the falsity of facts on which the assessment relied), Party A shall notify Party B within twenty-four (24) hours under §2; Party B shall immediately withdraw the confirmation and may suspend under Section 9.6. Party A continuing to use the Services after withdrawal means E3 is no longer satisfied, which is an Eligibility Event attracting the full consequences in §8. 2. Notice — before the event and immediate Trigger Deadline Note A change in shareholding, control or directors (including a proposed transaction) ten (10) business days before the change takes effect or closes — in advance advance notice applies to Orders with a Committed Term of more than thirty-six (36) months; for other Orders, within three (3) business days after the change (Section 10.9(c)) Any Eligibility Event (any of E1–E7 ceasing, or being likely to cease, to be satisfied) twenty-four (24) hours including becoming aware of any investigation, enquiry or list change by a competent authority A change in end use or in the nature of the workload three (3) business days Section 10.9(a) A change in the entity that actually uses or benefits from the Services three (3) business days Section 10.9(b) A change in, or addition to, prior written application and Party Section 10.6; Party B gives no undertaking as to the

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 62 of 69 the regions of access B's written consent time for approval Party A or a downstream user generates content listed in Schedule 11 §3; a third-party claim is received; an authority makes contact; a filter is circumvented twenty-four (24) hours Schedule 11 §12 Party A becomes aware of any fact that may cause Party B to breach its export-control or compliance undertakings twenty-four (24) hours Section 10.9(f) Consequences of late or inaccurate notice. Where a notice is late, incomplete or inaccurate, in addition to Party B's rights under Sections 9.6 and 19.6, Party A is liable for all of Party B's loss arising from the loss or weakening of any statutory protection (Schedule 11 §9) or from any resulting increase in penalty, such liability not being subject to the cap in Section 17.2 (Section 17.3). 3. Conduct — permitted use • Use limited to inference. Party A shall use the Services only for inference on already-trained models (generation, retrieval, classification, transcription and the like) and shall not use them to train, pre-train, continue training, fine-tune or otherwise alter the weights of any model. The Services as provided under this Agreement afford no training capability by design — Party A's entire contact with Party B's infrastructure is limited to submitting requests to, and receiving responses from, the Service Endpoint (Section 14.6) — and this prohibition is therefore absolute: this Agreement provides no application or approval procedure for a training use. Where Party A requires a training use, the tiers under this Agreement do not apply; Party B's Master Compute Services Agreement is executed separately and the application and approval procedure in its Annex 10 §3.1.1 applies (that procedure requires that Party A's ultimate parent not be headquartered in a Country Group D:5 country (which includes China; under the EAR, Hong Kong is treated as part of China) or Macau, or that the necessary export licence has been obtained). Party A shall not attempt to use the Services for training by any means, including indirectly by any means prohibited in the next item of this §3. • No training on outputs. Party A shall not use the output of the Services (including derivatives, synthetic datasets and teacher–student distillation artefacts) to train, fine-tune or improve any model, whether or not that model competes with a catalogue model of Party B, wherever the training takes place and whosesoever compute is used. This item is independent of, and wider than, the prohibition on distilling catalogue models in Schedule 5. • Fixing and evidencing end use. The end use stated in §8 of the Order is a continuing obligation of Party A; Party B may at any time require an explanation and supporting material as to actual use, which Party A shall provide within five (5) Business Days. Refusal, delay or the provision of inaccurate material is a material breach. • No undisclosed principal. Party A shall not use the Services for the benefit of any principal not disclosed to Party B and shall not hand credentials issued by Party B to any third party (Section 9.3). Resale or distribution by Party A to its customers or resellers under Section 9.3 is not caught by this item and is governed by §5; downstream users managed under §5 are not undisclosed persons. • Territorial discipline. Party A shall access the Services only from the territories stated in §8 of the Order and shall not instruct, assist or acquiesce in any circumvention of Party B's geographic controls; where Party A provides capability downstream through its own products it shall enforce source-IP geofencing and block known VPN, proxy and Tor exits at its application layer (Schedule 8 §2). • No circumvention of technical controls. Party A shall not circumvent or attempt to circumvent geofencing, quotas, rate limits, safety filters or any other control imposed by Party B (Schedule 11 §4). 4. Conduct — evidence and cooperation This Section determines whether Party B can rely on its statutory protections and is therefore the most valuable Section of this Schedule. Party B's protection rests on being able to prove what it did at the time, and the relevant facts are usually in Party A's hands alone (Schedule 11 §§9 and 12). • Preservation. Upon any of the circumstances in Schedule 11 §12, Party A shall immediately preserve the relevant records in its possession (prompts, output, account and access logs, downstream user identities, timestamps) for not less than five (5) years or until the matter is finally resolved, whichever is later, and shall not destroy, alter or purge them. Party A's

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 63 of 69 election of zero retention or of no usage logs in the Order does not reduce this obligation — Party A shall retain them on its own side. • Provision. On Party B's written request Party A shall provide those records and a statement of facts within five (5) Business Days, truthfully, accurately and completely; where a competent authority, a law-enforcement agency or Party B's upstream suppliers so require, within two (2) Business Days. Party B may provide them to competent authorities, upstream suppliers, insurers and legal advisers in order to rely on its protections. Party A shall not withhold them on grounds of trade secrecy, confidentiality or data protection. • No inducement of inaccurate statements. Party A shall not request, induce or cause Party B to make an inaccurate statement in any report, disclosure, response or certification, including any statement that Party B reviewed content it did not review. • Cooperation with voluntary self-disclosure. Where Party B decides to make a voluntary disclosure to a competent authority, Party A shall provide all relevant facts in its possession and cooperate with the subsequent process at its own cost. Party A shall not delay Party B's disclosure by any means — the timeliness of a disclosure directly determines the extent of mitigation. • Cooperation with audit. Once every twelve (12) months on fifteen (15) Business Days' notice Party B may audit Party A's performance of this Schedule and Schedule 8; audits required by a competent authority or an upstream supplier are not subject to the frequency or notice limits. Party A shall remediate any material non-conformity within thirty (30) days at its own cost; refusing an audit is an Eligibility Event. 5. Downstream users Where Party A provides capability based on the Services to its own customers through its own products or services, or resells or distributes the Services to its customers or resellers under Section 9.3, the following apply in addition to Schedule 8 §5 and Schedule 11 §11. Party A may not rely on output having been produced by a downstream user, or on a downstream user having been introduced by a reseller, to reduce any of its responsibilities under this Agreement. • Screen each downstream user entity and its known controllers and ultimate beneficial owners before granting access, retaining records for ten (10) years; re-screen every twelve (12) months and upon list updates. • Bind every downstream user by contract to §3 of this Schedule (use), Schedule 11 §§3–6 (output content) and Sections 10.3, 10.4 and 10.6; provide sample terms on Party B's request. • Where a downstream user in turn provides the Services to its own customers, require it by contract to perform obligations equivalent to the two items above in respect of those customers; state the name and place of incorporation of each of Party A's direct resellers in §8 of the Order and notify Party B in writing within ten (10) Business Days after any change or addition (Section 10.10(d) and (e)). • A downstream user that matches a list shall not be granted access; existing access shall be suspended immediately, with written notice to Party B within twenty-four (24) hours. • Maintain a reporting, appeal and enforcement channel for downstream users and provide records of its operation within ten (10) Business Days of Party B's request. 6. Additional undertakings where Party A runs its own stack This Section applies only where the tier stated in the Order is one in which Party A runs its own software stack on Party B's infrastructure (virtualised containers or single-tenant physical nodes). Such tiers are not provided under this Agreement; where Party A requires them, Party B's Master Compute Services Agreement is executed separately and this Section forms part of it (Sections 3.5 and 3.7). It is set out here so that the customer obligations across the three tiers come from one text. # Additional undertaking Why S1 Use remains limited to the scope set out in §3. Party A shall not train, pre-train, continue training or fine-tune any model on Party B's infrastructure, irrespective of whether its own compute allocation would suffice; a training use requires Party B's prior written consent, which Party B may withhold for any reason the catch-all in Section 10 is triggered by "training models for a restricted party"; because the customer runs its own stack, Party B loses the architectural guarantee and must make it up by contract and by evidence S2 Party A shall describe the technical and administrative measures by which it ensures that no training takes place (image review, restriction of job types, internal approval) and shall submit to Party B's verification; any an undertaking alone is not enough; Party B must be able to explain to a competent authority the

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 64 of 69 change to those measures requires advance notice basis on which it relied S3 End-user records. Party A shall create and maintain a record for every entity that actually uses the capacity (legal name · place of incorporation · controller · UBO · use), submit it before that entity goes on the machines, and update it within three (3) business days of any change Party B cannot see activity inside the stack; these records are the only evidence of end users S4 Confirmation of operating and compliance capability. Party A shall confirm in writing that it has the facilities and personnel to operate the equipment and an export-control compliance process (screening · responsible person · records); Party B may require verification on site or remotely addresses the BIS red flag: whether the data centre can be confirmed as capable of operating these items S5 Privilege discipline. Party A acknowledges that it does not obtain, and shall not request, host root, a host shell, out-of-band management or standing administrator access; installation, change and upgrade of its software are in every case carried out by Party B under the procedure in the Customer Software annex if Party B's status as end user and registered operator (Section 14) is displaced by the facts, its self-signed EUC and the related representations become untrue at the same moment S6 Handling of technical information. Information that Party A and its personnel learn through operation — hardware models, interconnect topology, firmware and driver versions and the like — may be used only to operate that capacity, must not be disclosed to any third party, and must not be used to circumvent export controls; Party A shall state truthfully to Party B the nationality and location of its personnel the risk of releasing controlled technology (deemed export) — the risk arises because Party A runs its own stack, so Party A bears the consequences S7 Audit frequency is tightened to once every six (6) months; refusing or obstructing an audit is an Eligibility Event Party B has no technical visibility; audit is the only means of verification S8 Party A is answerable to Party B for everything that happens inside its stack, including the acts of its personnel, contractors and downstream users, and any model it runs and any content it generates on that capacity the price of the mismatch between responsibility and visibility 7. Party A's express acknowledgement of risk Party A expressly acknowledges and agrees that: • Party B does not inspect Customer Content (no automated content filtering under a Dedicated Serving Pool, Section 9.4) and therefore makes no judgement as to its lawfulness; Party A shall not rely on Party B's not having prevented an act as acquiescence or waiver. • Suspension, removal or termination by Party B under Sections 9.6, 10.7, 19.8 or Schedule 11 §7 is not a breach, does not relieve Party A of payment obligations, is excluded from the Service Levels, and gives rise to no compensation or refund (Section 8.3). • A change in applicable law, export controls or sanctions applies immediately to services being provided on a continuing basis, and the prior execution of this Agreement or any Order is not a defence; where Party B terminates on that ground, Sections 19.8 and 8.3 apply. • Party A has obtained its own independent legal advice as to the lawfulness of its use of the Services in its own jurisdiction and in those of its downstream users, and has not relied on any statement of Party B; Party B gives no assurance as to Party A's compliance position. 8. Consequences of breach Upon any breach of this Schedule or any Eligibility Event: (a) Party B may suspend the service under all Orders immediately under Section 9.6, with no cure period; (b) Party B may terminate all Orders under Section 19.6, with Sections 19.4 and 19.5 applying; (c) the Prepayment is non-refundable (Section 8.3); (d) Party A shall defend and indemnify Party B under Section 16.1; and (e) Party A's liability for breach of §1 (eligibility), §3 (use) or §4 (evidence and cooperation) is not subject to the cap in Section 17.2 (Section 17.3). 9. Customer Compliance Certificate (form) The form below is used for the quarterly self-certification under §1 and may also be obtained during due diligence. This page may be used on its own.

XDT — Token Factory Master Services Agreement · Order 01 XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Page 65 of 69 Master Agreement XDT-TF-MSA-2026-001 Order(s) XDT-TF-MSA-2026-001-O01 and any subsequent Period Q____ of ________ Party A XPERT SOFTWARE SOLUTIONS PTE. LTD. E1 Lists ☐ Confirmed: neither we nor any of our directors, officers, controlling shareholders or ultimate beneficial owners is on any restricted-party list, nor controlled by such a person E2 Aggregate ownership ☐ Confirmed: direct and indirect holdings in us by listed persons are below 50%, individually and in aggregate E3 Headquarters ☐ Confirmed: our ultimate parent is headquartered in ________, not in D:5 or Macau ☐ It is, but use is limited to inference and written confirmation has been obtained E4 Sanctioned territories ☐ Confirmed: we are not a person of a comprehensively sanctioned country or region, nor controlled by such a person E5 Genuine user ☐ Confirmed: we are the genuine user and act for no undisclosed third party; downstream users, if any, are managed under Schedule 12 §5 E6 Materials ☐ Confirmed: we continue to meet the facts stated in our KYC materials; changes during the period have been notified under §2 E7 No proceedings ☐ Confirmed: during the period we were not investigated, penalised or made subject to restrictive measures on export-control, sanctions, anti-money-laundering, anti-bribery, fraud or data-compliance grounds Use ☐ Confirmed: during the period the Services were used only for inference; not for training or fine-tuning and not to alter any model weights; and no output was used to train any model (§3) Exceptions ☐ None ☐ Yes, detail: ____________________ (where there is an exception, this certificate is not a valid self-certification under §1) Signed Authorised representative ________________ Title ________________ Date ______________, 20____

XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Document Ref: XDT-TF-MSA-2026-001-O01-S01 · Page 66 of 69 · Confidential XDT INFRASTRUCTURE I, LLC — and — XPERT SOFTWARE SOLUTIONS PTE. LTD. SUPPLEMENTARY AGREEMENT NO. 01 Supplementary Order No. XDT-TF-MSA-2026-001-O01-S01 to Order No. XDT-TF-MSA-2026-001-O01 under the XDT Token Factory Master Services Agreement No. XDT-TF-MSA-2026-001 Supplementary Order No. XDT-TF-MSA-2026-001-O01-S01 (numbered sequentially) Order varied Order No. XDT-TF-MSA-2026-001-O01, dated [●] (the "Order"), for sixty-four (64) Allocation Units (64 NVIDIA HGX B300 servers, 512 GPUs) in a single Phase, United States · [***] Master Agreement XDT Token Factory Master Services Agreement No. XDT-TF-MSA-2026-001, effective [●] (the "Master Agreement") Parties Party A — Customer: XPERT SOFTWARE SOLUTIONS PTE. LTD. (UEN 201320369H, Singapore) Party B — Supplier: XDT INFRASTRUCTURE I, LLC (Delaware File No. 10764583) Subject of the variation (i) readiness delay under Section 4.8 for the Order: termination threshold [***] days (Clause 1); (ii) first tranche: the OEM's confirmation of the purchase orders for all sixty-four (64) Allocation Units (Clause 2); (iii) second tranche: due on the OEM's first request for the balance of the equipment price (Clause 2) Capacity Basis as varied not varied — sixty-four (64) XDT B300 Allocation Units (512 GPUs), single Phase, dedicated and fully physically isolated Monthly Commitment Fee as varied not varied — USD [***] per Service Month Commitment Term as varied not varied — sixty (60) months from the Phase 1 SRD Prepayment amount not varied — USD 45,000,000.00 in two tranches (30% / 70%), applied as under Section 8; the conditions to the two tranches are as stated in Clause 2 Target SRD not varied — within two (2) months of the Readiness Start Date (Section 4.4 and §4 of the Order) Schedules 3 / 4 elected as in the original Order — Schedule 3A (availability) and Schedule 4A (Service Readiness Test) Validity valid only if countersigned by Party A within fourteen (14) days of issuance by Party B, failing which it lapses (Schedule 10 §2) Amendment Date the date on which this instrument is signed by the last of the Parties This instrument is a Supplementary Order under Schedule 10 varying the Order. It is signed by both Parties' authorised representatives and, once so signed, forms part of the Order (Sections 1.13, 6.8 and 22.3). Terms defined in the Master Agreement or the Order have the same meaning in this instrument. The Parties agree as follows.

XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Document Ref: XDT-TF-MSA-2026-001-O01-S01 · Page 67 of 69 · Confidential 1. Readiness delay under Section 4.8, as it applies to the Order 1.1 Section 4.8 of the Master Agreement applies "unless the Order provides otherwise". For the Order, Section 4.8 applies with the change in Clause 1.2. 1.2 The words "ninety (90) days" in Section 4.8 are replaced by the words "[***] days", so that the relevant words read: "If the delay exceeds [***] days, Party A may terminate that Phase by written notice (or, where it is the first Phase of that Order, that Order) and recover amounts paid and unused, including the Prepayment attributable to that Phase." 1.3 Section 19.7(a) of the Master Agreement applies to the Order by reference to the period of [***] days in Clause 1.2. Save as stated in this Clause 1, Section 4.8 applies to the Order without change, including the service credits from the first (1st) day of delay at one hundred per cent (100%) of one day's Monthly Commitment Fee, the aggregate cap of three (3) months' Monthly Commitment Fee, the provisions of Section 4.8 and Schedule 4A §3.1 on when the days of delay end and when that right lapses, the excluded days of delay and the three cases in which delay is not counted, and the statement that Section 4.8 is Party A's sole remedy for readiness delay. §4 of the Order (early service of part of Phase 1) continues to apply, including its rule that delay credits and any termination under Section 4.8 apply only to the units not yet in service. 2. The two tranches of the Prepayment (§7 of the Order) 2.1 In paragraph (a) of §7 of the Order (the first tranche, thirty per cent (30%) of the Prepayment = USD 13,500,000.00), the words "has confirmed Party B's purchase orders for the full Phase 1 capacity" are replaced by the following words: "has confirmed Party B's purchase orders for the whole of the Phase 1 capacity, being all sixty-four (64) XDT B300 Allocation Units comprised in Phase 1 (sixty-four (64) NVIDIA HGX B300 servers, 512 GPUs);" 2.2 The condition to the first tranche is satisfied only where the OEM has confirmed Party B's purchase orders for all sixty-four (64) Allocation Units comprised in Phase 1. A purchase order, order acknowledgement or other confirmation that covers only thirty-two (32) Allocation Units, or any number fewer than sixty-four (64), does not satisfy that condition; the first tranche is neither payable nor due until the condition is satisfied in the form stated in Clause 2.1; and a notice under §7(a) of the Order that does not enclose a redacted copy of the OEM's order acknowledgements for all sixty-four (64) Allocation Units is not effective for the purposes of that paragraph. 2.3 The amount of the first tranche is not varied: it remains thirty per cent (30%) of the Prepayment, being USD 13,500,000.00, and is not reduced, pro-rated or scaled by reference to the number of Allocation Units covered by any purchase order. 2.4 The provision in §4 of the Order permitting Party B to offer at least thirty-two (32) Allocation Units for the Service Readiness Test before the whole Phase continues to apply for the purposes of the Service Readiness Test, billing and Section 4.8 as it applies to the Order, but it does not reduce the number of Allocation Units for which the OEM's confirmed purchase orders must be held under §7(a) of the Order, and the offering of any part of the Phase 1 capacity does not of itself make the first tranche payable or due. 2.5 In paragraph (b) of §7 of the Order (the second tranche, seventy per cent (70%) of the Prepayment = USD 31,500,000.00), the words "that the OEM has requested payment of the balance of the equipment price before shipment" are replaced by the following words: "that the OEM has requested payment of the balance of the equipment price, before shipment, for any of the Phase 1 servers"

XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Document Ref: XDT-TF-MSA-2026-001-O01-S01 · Page 68 of 69 · Confidential The OEM may ship the Phase 1 servers in more than one lot. The notice under §7(b) of the Order may be given on the OEM's first such request, and the second tranche then falls due in full; its amount is not varied and is not reduced, pro-rated or split by lot. 2.6 Save as amended by Clauses 2.1 to 2.5, §7 of the Order continues in full force and effect without change, including the application of the Prepayment to the build-out of the serving capacity, the reporting and verification obligations of Party B, the determination of the Readiness Start Date under Section 4.4, and the treatment of the two tranches under Section 8 of the Master Agreement. 3. Other terms, precedence and effect 3.1 Save as expressly varied by this instrument, the Master Agreement, its Schedules and the Order remain in full force and effect and are ratified and confirmed. In particular, the Capacity Basis (64 Allocation Units), the Monthly Commitment Fee (USD [***]), the Commitment Term (60 months from the Phase 1 SRD), the Total Commitment Value (USD 100,915,200.00), the Prepayment (USD 45,000,000.00), the Readiness Start Date and Target SRD provisions and the elected Schedules 3A and 4A are not varied. This instrument does not amend the body of the Master Agreement. 3.2 This instrument forms part of the Order and prevails as to the matters it states (Sections 1.13, 2.4 and 6.8). 3.3 Sections 23 (governing law and dispute resolution) and 24 (language and counterparts) of the Master Agreement apply to this instrument as if set out in it. This instrument is executed in English and may be executed in counterparts and by electronic signature (Sections 24.1 and 24.2).

XDT is a wholly-owned subsidiary of Quanome Technologies, Inc. (Nasdaq: QNME). Document Ref: XDT-TF-MSA-2026-001-O01-S01 · Page 69 of 69 · Confidential 4. Execution Each Party has caused this Supplementary Agreement No. 01 and Supplementary Order No. XDT-TF-MSA-2026- 001-O01-S01 to be executed by its duly authorised representative. Party A — Customer Party B — Supplier XPERT SOFTWARE SOLUTIONS PTE. LTD. UEN 201320369H · Singapore By: /s/ Thomas Long Name: Thomas Long Title: Director Date: 29-September-2026 XDT INFRASTRUCTURE I, LLC Delaware File No. 10764583 By: /s/ Yang Li Name: Yang Li Title: Manager Date: 29-September-2026 End of instrument