Mesa Upgrade Mechanism Testing: Trailblazers Program Details

Introduction

The Mesa Trail testnet—also referred to as Mesa Upgrade Testing (MUT)—is a structured test environment designed to validate the complete end-to-end upgrade path for the upcoming Mesa Upgrade on Mina Protocol. This includes exercising all mechanisms required for the mainnet upgrade: coordinated network shutdown via stop-slots, state export, package generation, restart under new protocol rules, and validation of Mesa’s updated performance and zkApp capabilities.

To ensure reliable execution and high-quality feedback, o1Labs is organizing a curated group of node operators, zkApp developers, and ecosystem partners in the Trailblazers program. These participants have been selected based on operational capability, prior testnet experience, infrastructure stability, and the need to satisfy specific roles (Block Producers, SNARK Worker Operators, Archive Nodes Operators, zkApp developers). 

In addition to the Trailblazers program, non-incentivized community participants are welcome to join the network, observe the upgrade process, and perform exploratory testing. While they will not be part of the coordinated upgrade validation or incentive program, their participation is encouraged and can provide valuable supplementary data and feedback. o1Labs will also share learnings and findings from the Trailblazers program with the wider community along the way. 

The following document outlines:

• Mesa Trailblazers Program structure and objectives
• Testing Stages: 
  • Stage 1: Berkeley Test Network
  • Stage 2: Upgrade Mechanism Testing (UMT)
  • Stage 3: Mesa Network Testing
• Participant roles and responsibilities
• Technical and operational requirements
• Incentive structure for approved participants
• Communication, reporting, and escalation procedures
• Terms & Conditions of the Trailblazer program

Participants are expected to carefully review and agree to all sections before the start of the program.

Program Details

Node Operators’ roles and their responsibilities

Node operators participating in the Trailblazers program can perform one or more of the following roles:

1. Block Production
2. SNARK Work Production
3. Archive Node, Archive Node API and Rosetta API Provider

Common responsibilities across all roles

1. Follow the specific runbook
   1. Which private key to use
   2. Which node version to run at each moment
   3. When to migrate the nodes to a new version
   4. Monitor the MUT Discord channels, #mesa-upgrade-testnet-announcements and #mesa-upgrade-testnet, and react promptly to the requests by the administration team.
2. Initial Setup
   1. Have the nodes ready for testing by the time specified in the Timeline section of this document
3. Upgrade Requirements
   1. Follow the corresponding MUT Discord channels #mesa-upgrade-testnet-announcements, where instructions to node operators will be given, and #mesa-upgrade-testnet for discussions 
   2. Upgrade to the requested Mina Node version within 24 hours following the announcement in the #mesa-upgrade-testnet-announcements Discord announcement channel.
4. Uptime Expectations
   1. Maintain a minimum of 90% uptime as monitored by the SNARK-work-based uptime system
5. Issue Reporting
   1. Report any abnormal behavior during the testing on Mina Github page with the specified label “mesa-mut”.
6. Configuration
   1. Use the proper configuration that will be provided to set up the nodes.
   2. The nodes shall be configured to restart automatically on crash
   3. Nodes assigned to upgrade using Automode shall be configured to persist the configuration directory across restarts.
7. Log Collection and Reporting
   1. Configure nodes for logging as per instructions.
   2. Share server logs when requested within 12 hours.
   3. Maintain at least 72 consecutive hours of logs at any time.
8. Join the P2P network using the MUT seeds for bootstrapping.
9. Adhere to the minimum specification requirements for each node type

Security

• The Performance Testing Toolset is organized as a separate GraphQL interface that is included only in testnet builds (not available for Mainnet builds) and is activated with certain CLI flags (–itn-graphql-port, –itn-keys) provided to the node.
• CLI flag –itn-keys specifies Ed25519 public keys that are allowed access to the Control GraphQL interface. An authentication mechanism will ensure that only requests signed by specified public keys are allowed, as well as protecting against a range of attacks (such as a request replay attack). This way, it will ensure that access to the GraphQL Control interface of a node will be granted only to engineers from o1Labs facilitating the testnet. Control GraphQL provides a way to:
  • Send transactions from a Mina node to the network
  • Secret keys for transaction sending will be provided by the caller (wallet or Block Producer keys associated with the Mina node will not be used)
  • Configure a Mina node’s networking. E.g., ban communication to certain peers in Mina network
  • Access a Mina node’s information (such as slot allocation)
  • Control block production
• It’s worth noting that GraphQL Control will only use the capabilities of Mina nodes and only in a limited way. It grants the caller no access to file system, firewall configuration, or any other system configuration. 
• Any changes made or actions launched to a Mina node via GraphQL Control will not persist over a Mina node’s restart. The GraphQL Control interface allows the execution of large-scale experiments involving hundreds of Mina nodes without coordination by node operators.

Mesa Upgrade Toolset includes, amongst others:

• GraphQL experimental control
• Libp2p port 
• Prometheus port 
• Uptime data 
• Node status and error collection service 
• Tracing and monitoring service 

Specific responsibilities per role

Block Production

1. 1. Run 2 block producer nodes on a cloud provider or hosted solution of your choice on a dedicated server from the start until the end of the Trailblazers program.
   2. Use the block production private keys that will be assigned to you
   3. 70% of block producers (20 BPs) use Automode settings
   4. 20% of block producers (6 BPs) manually upgrade immediately after packages are ready
   5. 5% of block producers (2 BPs) manually upgrade, post fork, between blocks 100 and 290
   6. 5% of block producers (2 BPs) manually upgrade, post fork, between blocks 291 and 400

Block Producers will be contacted with their assigned upgrade method and times.

SNARK Work Production

1. Run 1 SNARK Coordinator and 1 SNARK Worker pool with 8 SNARK worker processes on a cloud provider or hosted solution of your choice on a dedicated server from the start until the end of the Trailblazers program
2. All SNARK Worker processes should be connected to your SNARK Coordinator
3. Follow the instructions provided to you to set the SNARK Worker pool in either seq or roffset mode
4. Each SNARK Worker process should be allocated 6 cores / 12 threads
5. Use the SNARK production public key that will be distributed

Archive Node, Archive Node API, and Rosetta API Provider

1. Run the Archive Node, Rosetta API, Archive Node API, and all their dependencies on a cloud provider or hosted solution of your choice on a dedicated server from the start until the end of the MUT
2. Make the Rosetta API endpoints available publicly for testing
3. Make the Archive Node API endpoints available publicly for testing
4. Run a PostgreSQL database connected to the Archive Node Process
5. Maintain the Archive Node synced and fix missed blocks as they happen using archive-related tooling
6. After o1Labs’ zkApps tests, ensure the archive node, archive API, and rosetta are synced and up to date.

Technical Requirements

zkApp Developer Role and Responsibilities

The upcoming mainnet upgrade introduces significant and breaking changes that affect the compatibility of currently deployed zkApps. To ensure uninterrupted service, please verify your zkApps’ behavior before and after the upgrade by testing the process outlined in the test plan ahead of time: zkApp Developer Responsibilities

For questions or support, please use #mesa-upgrade-testnet channel in Discord.

Timeline & Test Plan

The total duration of the Trailblazers program will be 21 calendar days, with a tentative start date of June 1, 2026 (the “Starting Date”). o1Labs and its ecosystem partners will conduct internal testing before the Mesa Trail launch. In the event of any security or stability-related issues during the internal testing, the start date may be adjusted. If any changes do occur, the participants will be informed as far in advance as possible. 

Tentative key dates for testnet Initial Period:

• 29 May – Node operators receive testnet instructions
• 29 May ~ 1 June – Node operators receive testnet connection details
• Day 1 – Monday, June 1, 2026 – Testing starts, node operators must have their nodes configured and ready to test according to their roles by 12:00 PM UTC
• Day 2 – 2 June – Node Operators upgrade to the stop-slot-release
• Day 3 – 3 June – Node operators should be available to perform the node migrations to Mesa (hardfork)
• Day 3 – 3 June – Mesa Trail Network first slot
• Days 4 to 21 – Mesa Network testing
• Day 15 – 15 June – Emergency Hardfork test
• Day 21 – 22 June – Trailblazers program completes, network remains open for community testing

As with any testnet, dates are tentative and will depend on the results and progress observed throughout testing. The team will provide regular updates on timelines throughout the program.

If critical bugs and issues are uncovered on the network, it may be necessary to pause the testing, fix the issues, and then restart the testing process. In that case, participants will be requested to pause the testing or participate for an extended Trailblazers duration.

Trailblazers Test Plan

Your role as node operators is paramount in ensuring the success of the Mesa Upgrade Mechanism Testing. Below are the instructions and test plan details for your reference.

• Network Structure: The MUT network mirrors the Mainnet ledger with approximately 200k accounts.
• Participants: There will be 41 community members managing various aspects of the network, with others free to join in.

Network topology

• 30 Block Producers
  • Running 2 Mina Daemons each
• 3 SNARK Work Ops
  • 1 SNARK Coordinator per Op
  • 8 SNARK Workers per Op (note: Worker refers to the SNARK process)
  • Two Ops  running roffset work selection and one running seq
    • SNARK Worker Ops will be contacted with their assigned method
• 3 Archive Nodes
  • Running 1 Archive Node, 1 Rosetta API provider, and 1 Archive Node API provider each
• 5 zkApp Developers
  • Deploying a zkApp before the hardfork and going through the upgrade process after the hardfork, testing the zkApp, and documenting the process

Detailed Trailblazers test plan steps

Reporting of Bugs

All participants are expected to raise any abnormal behavior during the MUT on Github here, adding the “mesa-mut” label.

Escalating of Other Issues

In the dedicated Mesa Trail Discord channel #mesa-upgrade-testnet.

Note: All selected Trailblazer participants will be added to the relevant Discord channels.

Incentives

The incentives are outlined in detail per participant’s role. Please note that the incentives listed below cover the initial period of 21 calendar days of testing commencing on the Starting Date (the “Initial Period”). 

Contingent upon Mesa Trail findings, the timeline may be extended past the Initial Period to accommodate further testing. In case an extension is required, additional testing period(s) will be added to the timeline in 7-day increments. The applicable incentives for extension period(s) are outlined in the “In case of 7-day Extension” sections below. Testers participating in the Initial Period of testing will be required to continue their testing in such extension events. 

Please note:

• Participants must successfully complete KYC/AML requirements and maintain good-standing status throughout testing, including applicable extension periods, for eligibility.
• If applicable, the Program might be paused, or its duration might be extended upon participants uncovering critical bugs or issues on the network. Participants might be required to pause or extend their server rental in such circumstances.

Feedback and Questions:

We have set up a dedicated Discord channel, #mesa-upgrade-testnet, where you can provide feedback and ask questions related to the Mesa Upgrade Testing and Trailblazers programs. We’d be happy to hear from you!

Terms and Conditions

MESA UPGRADE MECHANISM TESTING

TRAILBLAZERS PROGRAM

TERMS AND CONDITIONS

IMPORTANT NOTICE REGARDING DISPUTE RESOLUTION:

THESE TERMS CONTAIN A BINDING ARBITRATION CLAUSE AND CLASS ACTION WAIVER IN SECTION 18. BY AGREEING TO THESE TERMS, PARTICIPANT AGREES THAT ALL DISPUTES WILL BE RESOLVED THROUGH FINAL AND BINDING ARBITRATION ON AN INDIVIDUAL BASIS, AND PARTICIPANT WAIVES THE RIGHT TO A JURY TRIAL AND THE RIGHT TO PARTICIPATE IN CLASS ACTIONS OR OTHER REPRESENTATIVE PROCEEDINGS. PLEASE READ SECTION 18 CAREFULLY.

1. Acceptance of Terms. By participating in the Mesa Upgrade Mechanism Testing Trailblazers Program (the “Program“), you (“Participant“) agree to be bound by these Terms and Conditions (these “Terms“) with O(1) Labs Operating Corporation, a Delaware corporation (“o1Labs“). These Terms, together with the document titled “Mesa Upgrade Mechanism Testing: Trailblazers Program Details” (the “Program Details“), constitute a legally binding agreement. If Participant does not agree to these Terms, Participant may not participate in the Program. In the event of any conflict between these Terms and the Program Details, these Terms shall control.
2. Program Overview. The Program is a structured test environment designed to validate the upgrade path for the Mesa Upgrade on Mina Protocol. The Program operates on a testnet environment (the “MUT Network“) that is separate from the Mina Protocol mainnet and is intended solely for testing purposes. Any tokens used or generated on the MUT Network (“Testnet Tokens“) have no monetary value, cannot be transferred to mainnet, and cannot be exchanged for any currency or asset. Participation in the Program does not guarantee any particular outcome, including successful completion of the Mesa Upgrade or future participation opportunities with o1Labs.
3. Selection and Eligibility
   1. Selection. Participants are selected at o1Labs’ sole discretion based on criteria that may include staking pool size, services and zkApps requiring testing, prior community contributions, node operation experience, infrastructure stability, and team recommendations. Meeting any selection criteria does not guarantee selection.
   2. Eligibility. To participate, Participant must: (i) be at least eighteen (18) years of age or the age of majority in Participant’s jurisdiction; (ii) have the legal capacity to enter into binding agreements; (iii) not be a resident or citizen of, or located in, any jurisdiction subject to comprehensive sanctions by the United States, European Union, United Kingdom, or United Nations; (iv) not be identified on any sanctions list maintained by OFAC or equivalent authorities; (v) successfully complete all Know Your Customer and Anti-Money Laundering (“KYC/AML“) verification requirements within the timeframe specified by o1Labs; and (vi) possess the technical capability and infrastructure necessary for Participant’s assigned role.
   3. Ongoing Compliance and Disqualification. Participant must remain in compliance with all eligibility requirements throughout the Program. o1Labs may verify eligibility at any time and may disqualify any Participant who fails to meet or maintain eligibility requirements, provides false or misleading information, or fails to complete KYC/AML requirements. Disqualification shall result in forfeiture of any unpaid compensation.
4. Participant Roles and Responsibilities
   1. Roles. Each Participant is assigned one or more roles: Block Producer, SNARK Worker, Archive Node Operator, or zkApp Developer. The specific technical and operational requirements for each role are set forth in the Program Details, which Participant agrees to follow.
   2. General Obligations. All Participants shall: (i) follow the runbooks and instructions provided by o1Labs; (ii) monitor the designated Discord channels and respond promptly to announcements; (iii) have all required infrastructure operational by the times specified in the Program Details; (iv) use the configuration settings provided by o1Labs; (v) maintain nodes and infrastructure in accordance with the technical requirements set forth in the Program Details; and (vi) report bugs and abnormal behavior through the designated channels.
   3. Performance Standards. Block Producers, SNARK Workers, and Archive Node Operators shall maintain minimum uptime of ninety percent (90%) as measured by o1Labs’ monitoring systems. All Participants shall upgrade to new software versions within twenty-four (24) hours of announcement. zkApp Developers shall submit a comprehensive written report as specified in the Program Details. Failure to meet performance standards may result in forfeiture of unpaid compensation.
5. Technical Access and Monitoring. Participant acknowledges and agrees that: (a) o1Labs engineers will have access to Participant’s nodes through designated testing tools for purposes of monitoring, testing, and conducting network experiments, as further described in the Program Details; (b) Participant shall configure nodes and provide access credentials as instructed; (c) Participant shall maintain logs and share them with o1Labs upon request within the timeframes specified in the Program Details; and (d) o1Labs may collect and analyze operational data from Participant’s nodes, including uptime metrics, performance data, and log files.
6. Program Duration
   1. Initial Period. The Program shall commence on the date specified in the Program Details (the “Starting Date“) and continue for twenty-one (21) calendar days (the “Initial Period“). Dates are subject to adjustment based on testing progress, and o1Labs will provide advance notice of any changes.
   2. Extension. o1Labs may extend the Program beyond the Initial Period in seven (7) calendar day increments if additional testing is warranted. o1Labs shall provide Participant with at least seventy-two (72) hours’ notice prior to any extension. Participants who participated in the Initial Period must continue through all extension periods to remain eligible for compensation.
   3. Pause and Restart. o1Labs may pause testing, implement fixes, and restart the process if critical issues are discovered. Participant may be required to maintain infrastructure readiness during any pause period.
   4. Infrastructure Costs. Participant is solely responsible for all infrastructure costs, including server rental, cloud fees, and costs incurred during extension or pause periods. o1Labs has no obligation to reimburse infrastructure costs beyond the compensation specified herein.
7. Compensation
   1. Grants. Subject to compliance with these Terms and satisfactory performance, Participant shall be eligible to receive compensation in USDC and MINA tokens as specified in the Program Details for Participant’s assigned role(s). The terms of the grant are specified in these Terms and the Program Details.
   2. Payment Schedule. USDC shall be distributed promptly upon satisfactory performance and completion of onboarding and KYC/AML requirements, expected before the testnet start, and MINA tokens shall be distributed following successful completion of the Program (including any extensions), subject to Participant’s continued compliance.
   3. Extension Compensation. Participants who continue through extension periods shall be eligible for additional compensation as specified in the Program Details.
   4. Taxes. Participant is solely responsible for all taxes arising from compensation received. o1Labs may report compensation to tax authorities and withhold amounts as required by law.
   5. MINA Token Disclaimer. MINA tokens are provided solely as consideration for Participant’s services and do not represent any equity, ownership, or security interest in o1Labs or any affiliated entity. The value of MINA tokens is volatile and may fluctuate significantly; there is no guarantee of value at distribution or thereafter. o1Labs makes no representations regarding the tax treatment of MINA tokens.
   6. Forfeiture. Participant’s right to compensation shall be forfeited if Participant: (i) fails to complete or meet KYC/AML requirements; (ii) fails to meet performance standards; (iii) fails to participate through required extension periods; (iv) breaches these Terms; (v) is disqualified; (vi) voluntarily withdraws prior to completion; or (vii) provides false information, in each case as determined by o1Labs in its sole discretion. The MINA token portion of compensation is evaluated on an all-or-nothing basis; partial completion may result in forfeiture of the entire MINA grant.
8. Independent Contractor Status. Participant is an independent contractor and not an employee or agent of o1Labs. Nothing in these Terms creates a partnership, joint venture, employment, or agency relationship. Participant is not entitled to employee benefits and is solely responsible for all taxes and compliance with applicable laws. Participant shall not represent themselves as an employee, agent, or representative of o1Labs.
9. Confidentiality
   1. Confidential Information. “Confidential Information” means any non-public information disclosed by o1Labs to Participant in connection with the Program, whether disclosed orally, in writing, electronically, or by any other means, including but not limited to: software, source code, and technical documentation; testing procedures, methodologies, and results; security vulnerabilities, bugs, exploits, and remediation measures; network architecture, configurations, and protocols; private keys, credentials, and access tokens; business strategies, plans, and financial information; and any information designated as confidential or that a reasonable person would understand to be confidential.
   2. Obligations. Participant shall: (i) hold all Confidential Information in strict confidence using at least the same degree of care used to protect Participant’s own confidential information, but in no event less than reasonable care; (ii) not disclose, publish, or disseminate Confidential Information to any third party without o1Labs’ prior written consent; (iii) use Confidential Information solely for the purpose of participating in the Program and for no other purpose; (iv) limit access to Confidential Information to those individuals who have a need to know and who are bound by confidentiality obligations at least as protective as those herein; (v) promptly notify o1Labs of any unauthorized disclosure or use of Confidential Information; and (vi) upon termination of participation or upon o1Labs’ request, promptly return or destroy all Confidential Information in Participant’s possession or control and certify such return or destruction in writing upon request.
   3. Exceptions. Confidential Information does not include information that Participant can demonstrate by competent evidence: (i) was publicly available at the time of disclosure or becomes publicly available thereafter through no fault or breach by Participant; (ii) was rightfully in Participant’s possession prior to disclosure by o1Labs without restriction on disclosure; (iii) is rightfully obtained by Participant from a third party who has the right to disclose it without restriction; or (iv) is independently developed by Participant without use of or reference to Confidential Information.
   4. Compelled Disclosure. If Participant is required by law, regulation, or valid legal process to disclose any Confidential Information, Participant shall: (i) provide o1Labs with prompt written notice of such requirement to the extent legally permitted, so that o1Labs may seek a protective order or other appropriate remedy; (ii) cooperate with o1Labs in seeking such protection; and (iii) disclose only that portion of the Confidential Information that is legally required to be disclosed and use reasonable efforts to obtain confidential treatment for any disclosed information.
   5. Security Vulnerabilities. Without limiting the foregoing, Participant shall not publicly disclose, publish, or disseminate any security vulnerabilities, bugs, exploits, or other weaknesses discovered during the Program without o1Labs’ prior written consent. Participant shall report all such discoveries promptly and exclusively to o1Labs through designated secure channels and shall not exploit any discovered vulnerability for any purpose whatsoever.
   6. Duration. The obligations under this Section 9 shall survive termination of these Terms and continue for a period of three (3) years following such termination; provided, however, that with respect to any Confidential Information that constitutes a trade secret under applicable law, such obligations shall continue for as long as such information remains a trade secret.
   7. Remedies. Participant acknowledges that any breach of this Section 9 may cause irreparable harm to o1Labs for which monetary damages would be inadequate, and that o1Labs shall be entitled to seek equitable relief, including injunction and specific performance, in addition to any other remedies available at law or in equity, without the necessity of proving actual damages or posting a bond.
10. Intellectual Property
    1. o1Labs Property. All intellectual property rights in and to the Mina Protocol, Program software, tools, documentation, trademarks, and all related materials (collectively, “o1Labs IP“) are and shall remain the sole and exclusive property of o1Labs or its licensors. Participant receives only a limited, non-exclusive, non-transferable, non-sublicensable, revocable license to use o1Labs IP solely for the purpose of participating in the Program during the Program duration. This license terminates automatically upon the conclusion of Participant’s participation. No implied licenses are granted under these Terms, and all rights not expressly granted are reserved by o1Labs. Nothing herein is intended to override or terminate any exising open source licenses in the Mina Protocol and related software.
    2. Restrictions. Subject to the open source license carveout, Participant shall not, and shall not permit any third party to: (i) copy, modify, adapt, translate, or create derivative works of any o1Labs IP except as expressly authorized in writing; (ii) reverse engineer, disassemble, decompile, or otherwise attempt to derive the source code or underlying algorithms of any software; (iii) remove, alter, or obscure any proprietary notices, labels, or marks; (iv) use any o1Labs trademarks, trade names, logos, or branding without prior written consent; (v) use o1Labs IP for any purpose other than Program participation; or (vi) sublicense, lease, rent, sell, or otherwise transfer any rights in o1Labs IP.
    3. Feedback. Any feedback, suggestions, ideas, bug reports, feature requests, improvements, or other input provided by Participant regarding the Program, Mina Protocol, or any related software or services (“Feedback“) shall be owned exclusively by o1Labs. Participant hereby irrevocably assigns to o1Labs all right, title, and interest in and to any Feedback, including all intellectual property rights therein, and waives any moral rights therein to the fullest extent permitted by law. o1Labs may use, modify, incorporate, and commercialize any Feedback for any purpose without attribution, compensation, restriction, or any obligation to Participant. Participant agrees to execute any documents reasonably requested by o1Labs to evidence or perfect such assignment.
    4. zkApp Developer IP. For Participants assigned the zkApp Developer role, nothing herein is intended to alter or terminate any intellectual property rights in effect prior to Participant’s participation in the Program. However, Participant hereby grants o1Labs a perpetual, irrevocable, worldwide, royalty-free, fully paid-up, non-exclusive, sublicensable license to use, reproduce, modify, display, distribute, and create derivative works of any zkApp code, documentation, reports, or materials deployed, created, or submitted during the Program for any purpose related to the Program, including testing, research, educational, promotional, and commercial purposes.
    5. No Challenge. Participant agrees not to challenge, contest, or take any action to impair o1Labs’ ownership of or rights in o1Labs IP, and not to register or attempt to register any intellectual property rights that are confusingly similar to or incorporate any o1Labs IP.
11. Data Collection and Privacy. Participant acknowledges that o1Labs will collect and process personal data for Program administration, including identification information for KYC/AML verification, wallet addresses, node operational data, and communication records. o1Labs may share such data with service providers, regulatory authorities, and affiliates as necessary. Participant consents to such collection, processing, and sharing.
12. Representations and Warranties. Participant represents and warrants that: (a) Participant has the legal capacity and authority to agree to these Terms; (b) if Participant is an entity, the individual accepting these Terms has authority to bind the entity; (c) Participant’s participation does not violate any law or agreement; (d) all information provided to o1Labs is true and accurate; (e) Participant meets all eligibility requirements; (f) Participant has the technical capability for their assigned role(s); and (g) Participant will comply with all applicable laws.
13. Acknowledgment of Risks. Participant acknowledges the following risks: (a) blockchain technology is experimental and subject to technical risks including software bugs, security vulnerabilities, and network failures; (b) MINA token value is volatile and may decrease or become worthless; (c) the regulatory status of cryptocurrencies is uncertain and may change; (d) Participant may incur infrastructure costs or losses due to hardware or network problems; and (e) Participant may incur tax liabilities from compensation received.
14. Disclaimer of Warranties
    1. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE PROGRAM, MUT NETWORK, PROGRAM MATERIALS, AND ALL RELATED SOFTWARE, TOOLS, DOCUMENTATION, AND SERVICES ARE PROVIDED ON AN “AS IS” AND “AS AVAILABLE” BASIS WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE. O1LABS AND ITS AFFILIATES, LICENSORS, AND SERVICE PROVIDERS HEREBY DISCLAIM ALL WARRANTIES, INCLUDING BUT NOT LIMITED TO: (A) IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT; (B) WARRANTIES ARISING FROM COURSE OF DEALING, COURSE OF PERFORMANCE, OR TRADE USAGE; (C) WARRANTIES REGARDING THE ACCURACY, RELIABILITY, COMPLETENESS, CURRENTNESS, OR TIMELINESS OF ANY CONTENT, INFORMATION, OR DATA; AND (D) WARRANTIES THAT THE PROGRAM OR MUT NETWORK WILL BE UNINTERRUPTED, TIMELY, SECURE, ERROR-FREE, OR FREE OF VIRUSES OR OTHER HARMFUL COMPONENTS.
    2. O1LABS DOES NOT WARRANT THAT: (I) THE PROGRAM OR MUT NETWORK WILL MEET PARTICIPANT’S REQUIREMENTS OR EXPECTATIONS; (II) ANY DEFECTS OR ERRORS WILL BE CORRECTED; (III) THE RESULTS OBTAINED FROM USE OF THE PROGRAM WILL BE ACCURATE OR RELIABLE; OR (IV) THE QUALITY OF ANY INFORMATION OR MATERIALS OBTAINED THROUGH THE PROGRAM WILL MEET PARTICIPANT’S EXPECTATIONS. O1LABS MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING ANY THIRD-PARTY SERVICES, SOFTWARE, OR INFRASTRUCTURE USED IN CONNECTION WITH THE PROGRAM. PARTICIPANT ASSUMES ALL RISK AND RESPONSIBILITY FOR ANY LOSS, DAMAGE, OR INJURY RESULTING FROM PARTICIPATION IN THE PROGRAM.
15. Limitation of Liability
    1. Exclusion of Certain Damages. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL O1LABS, ITS AFFILIATES, OR THEIR RESPECTIVE DIRECTORS, OFFICERS, EMPLOYEES, AGENTS, LICENSORS, OR SERVICE PROVIDERS (COLLECTIVELY, “O1LABS PARTIES“) BE LIABLE TO PARTICIPANT OR ANY THIRD PARTY FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, PUNITIVE, OR EXEMPLARY DAMAGES, INCLUDING BUT NOT LIMITED TO: (I) LOSS OF PROFITS, REVENUE, OR BUSINESS; (II) LOSS OF GOODWILL OR REPUTATION; (III) LOSS OF DATA OR USE OF DATA; (IV) COST OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; (V) BUSINESS INTERRUPTION; (VI) LOSS OF ANTICIPATED SAVINGS; OR (VII) ANY OTHER INTANGIBLE LOSSES, ARISING OUT OF OR IN CONNECTION WITH THE PROGRAM, THESE TERMS, OR PARTICIPANT’S PARTICIPATION IN THE PROGRAM, REGARDLESS OF THE THEORY OF LIABILITY (INCLUDING CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY, OR OTHERWISE) AND EVEN IF ANY O1LABS PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES OR COULD HAVE FORESEEN SUCH DAMAGES.
    2. Cap on Liability. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE TOTAL CUMULATIVE LIABILITY OF ALL O1LABS PARTIES ARISING OUT OF OR IN CONNECTION WITH THE PROGRAM OR THESE TERMS, WHETHER IN CONTRACT, TORT, STRICT LIABILITY, OR ANY OTHER LEGAL OR EQUITABLE THEORY, SHALL NOT EXCEED THE TOTAL AMOUNT OF COMPENSATION ACTUALLY PAID TO PARTICIPANT UNDER THESE TERMS. THIS LIMITATION APPLIES TO ALL CLAIMS IN THE AGGREGATE, INCLUDING WITHOUT LIMITATION ANY CLAIM FOR BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, OR ANY OTHER LEGAL THEORY.
    3. Jurisdictional Limitations; Minimum Required Modification. NOTHING IN THIS SECTION 15 SHALL EXCLUDE OR LIMIT ANY LIABILITY TO THE EXTENT SUCH LIABILITY MAY NOT BE EXCLUDED OR LIMITED UNDER APPLICABLE LAW. IN JURISDICTIONS WHERE ANY EXCLUSION, LIMITATION, OR CAP IN THIS SECTION 15 IS NOT PERMITTED, SUCH PROVISION SHALL BE DEEMED MODIFIED AND SHALL APPLY ONLY TO THE MINIMUM EXTENT NECESSARY TO COMPLY WITH THE MANDATORY REQUIREMENTS OF THAT JURISDICTION.
16. Indemnification. Participant shall indemnify, defend, and hold harmless o1Labs and its affiliates, directors, officers, employees, and agents from any claims, damages, losses, liabilities, costs, and expenses (including reasonable attorneys’ fees) arising from: (a) Participant’s breach of these Terms; (b) Participant’s violation of any law or third-party right; (c) Participant’s negligence or willful misconduct; (d) inaccuracies in Participant’s representations; or (e) Participant’s failure to comply with KYC/AML requirements.
17. Termination
    1. By o1Labs. o1Labs may terminate Participant’s participation at any time, with or without cause, upon written notice (including via email or Discord).
    2. By Participant. Participant may terminate Participant’s participation by providing at least seventy-two (72) hours’ written notice. Voluntary termination prior to completion shall result in forfeiture of unpaid compensation.
    3. Effect. Upon termination, Participant shall cease all Program activities and return or destroy all Confidential Information. Sections 7 (as to forfeitures), 8, 9, 10, 11, 13, 14, 15, 16, 18, and 19 shall survive termination.
    4. Program Termination. o1Labs may suspend, modify, or terminate the Program at any time. In such event, o1Labs will determine appropriate pro-rata compensation, if any, in its sole discretion
18. Dispute Resolution
    1. Informal Resolution. Before initiating any formal dispute resolution proceeding, the parties shall attempt to resolve any dispute, claim, or controversy arising out of or relating to these Terms or the Program (a “Dispute“) through good faith informal negotiations. The party raising the Dispute shall provide written notice describing the Dispute and proposed resolution, and the parties shall negotiate in good faith for at least thirty (30) days before initiating formal proceedings.
    2. Binding Arbitration. Any Dispute not resolved through informal negotiations shall be finally and exclusively resolved by binding arbitration administered by JAMS in accordance with Streamlined Arbitration Rules and Procedures. The arbitration shall be conducted by a single arbitrator selected in accordance with JAMS rules. The seat of arbitration shall be San Francisco, California, and the arbitration may be conducted in person, by telephone, or by videoconference as determined by the arbitrator. The arbitrator shall apply the substantive law of Delaware without regard to conflicts of law principles. The arbitrator’s decision shall be final and binding, and judgment on the award may be entered in any court of competent jurisdiction. The arbitrator shall have the authority to award any remedy that would be available in court, subject to the limitations set forth in these Terms, but shall have no authority to award punitive or exemplary damages except as required by statute.
    3. Class Action and Jury Trial Waiver. PARTICIPANT AND O1LABS EACH AGREE THAT ANY DISPUTE RESOLUTION PROCEEDING SHALL BE CONDUCTED ONLY ON AN INDIVIDUAL BASIS AND NOT IN A CLASS, CONSOLIDATED, OR REPRESENTATIVE ACTION. PARTICIPANT HEREBY IRREVOCABLY WAIVES ANY RIGHT TO PARTICIPATE IN A CLASS ACTION LAWSUIT, CLASS ARBITRATION, OR ANY OTHER REPRESENTATIVE OR CONSOLIDATED PROCEEDING. PARTICIPANT AND O1LABS EACH HEREBY IRREVOCABLY WAIVE ANY RIGHT TO A TRIAL BY JURY IN ANY ACTION OR PROCEEDING ARISING OUT OF OR RELATING TO THESE TERMS OR THE PROGRAM. If the class action waiver is found unenforceable as to any Dispute, then the arbitration agreement shall be null and void as to that Dispute only, and such Dispute shall proceed in court subject to the jury trial waiver.
    4. Costs and Fees. Each party shall bear its own attorneys’ fees and costs in any arbitration, except that the arbitrator may award reasonable attorneys’ fees and costs to the prevailing party if permitted by applicable law or if the arbitrator determines that a claim or defense was frivolous or brought in bad faith. The parties shall share equally the fees and costs of the arbitrator and JAMS, unless the arbitrator determines that a different allocation is appropriate.
    5. Confidentiality. All arbitration proceedings, including any discovery, submissions, awards, and the fact of the arbitration itself, shall be kept confidential by the parties and shall not be disclosed to any third party except: (i) as necessary to prepare for or conduct the arbitration; (ii) as required by applicable law or court order; (iii) to enforce the arbitration award; or (iv) with the written consent of both parties.
    6. Injunctive Relief. Notwithstanding the foregoing, either party may seek temporary or preliminary injunctive relief in any court of competent jurisdiction to protect its intellectual property rights, Confidential Information, or to prevent irreparable harm pending arbitration, without waiving the right to arbitrate. Any such application shall not be deemed a waiver of the arbitration agreement.
    7. Time Limitation. Any Dispute must be brought within one (1) year after the cause of action arises, or it shall be permanently barred. This limitation shall apply regardless of any statute or law to the contrary.
19. General Provisions
    1. Governing Law. These Terms shall be governed by the laws of the State of Delaware without regard to conflict of laws principles.
    2. Entire Agreement. These Terms and the Program Details constitute the entire agreement between the parties regarding the subject matter hereof and supersede all prior agreements and understandings.
    3. Amendment. o1Labs may modify these Terms by posting updated Terms or providing notice through Program communication channels. Continued participation constitutes acceptance of modifications.
    4. Severability. If any provision is held invalid or unenforceable, it shall be modified to the minimum extent necessary or severed, and the remaining provisions shall continue in full force.
    5. Waiver. No failure to exercise any right shall constitute a waiver. Any waiver must be in writing.
    6. Assignment. Participant may not assign these Terms without o1Labs’ written consent. o1Labs may assign without restriction. Any unauthorized assignment is void.
    7. Notices. Notices shall be in writing and deemed given when delivered by email or posted in designated Program communication channels.
    8. Force Majeure. Neither party shall be liable for failure to perform due to circumstances beyond its reasonable control, including acts of God, war, pandemic, government action, or failure of third-party services.
    9. No Third-Party Beneficiaries. These Terms are for the sole benefit of the parties and their permitted successors and assigns.
20. Acknowledgment. BY PARTICIPATING IN THE PROGRAM, PARTICIPANT ACKNOWLEDGES THAT PARTICIPANT HAS READ AND UNDERSTANDS THESE TERMS AND THE PROGRAM DETAILS, HAS HAD THE OPPORTUNITY TO SEEK INDEPENDENT LEGAL ADVICE, AGREES TO BE LEGALLY BOUND BY THESE TERMS, MEETS ALL ELIGIBILITY REQUIREMENTS, AND ACCEPTS THE RISKS DESCRIBED HEREIN.