Client Agreement

Preamble

This Integrated Client Agreement ("Agreement") is entered into between CoinSurge LLC, a Utah limited liability company operating the Ranged.pro service ("Ranged.pro"), and the individual or entity identified in the signature block below (the "Client"). This Agreement governs the Client's use of the Ranged.pro service and supersedes all prior communications, representations, and documents regarding the subject matter hereof, including any earlier drafts of terms of service or custody disclosures provided to the Client.

This Agreement incorporates: the Service terms (Parts I–XII), the Security and Custody Model Disclosure (Part II), the Risk Disclosures (Part III), the Service Level Agreement (Part VI, Sections 6.7–6.10), and the Payment Schedule (provided separately). The Privacy Policy, available separately at https://ranged.pro/privacy-policy, is incorporated by reference.

Execution and Binding Effect: This Agreement is binding on the Client upon the Client's execution of the Signature Block at the end of this document. This Agreement is binding on Ranged.pro upon Ranged.pro's transmission of an onboarding confirmation email to the Client's registered email address confirming that the Client's dedicated VPS has been provisioned and the ALM is running. Prior to that transmission, Ranged.pro is not bound by this Agreement and may decline to provide the Service for any reason.

---

Part I — Parties, Scope, and Eligibility

1.1 The Service

"Service" means the automated concentrated liquidity position management software, infrastructure provisioning, initial setup, monitoring infrastructure, and related support services operated by Ranged.pro under the Ranged.pro name. The core software component of the Service is referred to throughout this Agreement as the "ALM" (Automated Liquidity Manager Bot Software). The Service is a software automation and infrastructure management service. It is not investment advice, financial planning, portfolio management, discretionary asset management, brokerage activity, or any other regulated financial service.

1.2 Decision-Making Authority

The Client retains sole authority over strategy selection, range configuration, and all parameters that determine trading behavior. Ranged.pro may describe how strategy parameters work and what effects different configurations produce, but does not recommend, endorse, or advise any particular configuration. The Client makes all final configuration decisions.

1.3 Eligibility

• The Client must be at least 18 years of age, or the age of legal majority in their jurisdiction, whichever is greater. Use of the Service by anyone under this age is strictly prohibited.
• The Client must have the legal capacity to enter into binding contracts under the laws of their jurisdiction.
• The Client represents and warrants that their use of the Service does not violate any applicable law, regulation, or third-party agreement to which the Client is a party.
• By entering into this Agreement, the Client represents and warrants that they are not subject to U.S. economic sanctions, are not located in any U.S.-sanctioned jurisdiction, and are not on any OFAC Specially Designated Nationals (SDN) list or comparable sanctions list. Ranged.pro relies on the Client's self-certification and does not perform independent screening.
• Ranged.pro reserves the right to terminate this Agreement immediately and without liability if it determines, at its sole discretion, that the Client has misrepresented their eligibility.

1.4 Capital Deployment and Managed Custody Risk

There is no enforced limit on the amount of capital the Client may deploy to an ALM-managed wallet. However, the Client must understand a fundamental difference between the custody model used by this Service and the custody model of a hardware wallet:

• Hardware wallet custody: A hardware wallet (e.g., Ledger, Trezor) stores the Client's private key on an offline physical device. Transactions require physical confirmation from the Client. Ranged.pro — or any other party — cannot sign transactions on the Client's behalf without physical access to that device.
• Software-managed key custody (this Service): The Client's private key is stored on a VPS managed by Ranged.pro (see Part II). The ALM uses this key to sign transactions automatically, without requiring physical confirmation from the Client on each transaction. While the ALM is constrained to the transaction types listed in Section 2.2, the key itself is a standard Ethereum-compatible private key with no on-chain spending restrictions beyond what the software enforces. Software-based key storage carries inherent risks — including server compromise, operating system vulnerabilities, and infrastructure-level access — that a hardware wallet is specifically designed to eliminate.

The Client should treat a software-managed wallet with significantly greater caution than a hardware wallet and should only deploy an amount of capital they are prepared to lose per managed wallet address. The Client is solely responsible for their capital deployment decision. Ranged.pro provides no recommendation as to the appropriate amount and makes no representation that any amount is "safe" under this custody model.

Clients who require a fully trustless arrangement — where no party other than themselves can sign transactions — should contact Ranged.pro to discuss a self-hosted license arrangement.

1.5 Geographic Restrictions

Ranged.pro makes no representation that the Service is legally available in all jurisdictions. The Client is solely responsible for determining whether their use of the Service complies with all applicable local, national, and international laws. Ranged.pro reserves the right to restrict access from specific jurisdictions at any time and without notice.

1.6 Regulatory Status

Ranged.pro is a software automation and infrastructure management company. Ranged.pro is not registered as, and does not operate as, any of the following:

• An investment adviser or investment adviser representative under the Investment Advisers Act of 1940 or any state equivalent (including Utah Code 61-1)
• A broker-dealer under the Securities Exchange Act of 1934 or any state equivalent
• A money transmitter or money services business under FinCEN regulations or any state money transmission act (including Utah Code 7-25)
• A commodity trading adviser under the Commodity Exchange Act

Ranged.pro does not hold, pool, transmit, or exercise control over the Client's funds. All on-chain transactions are executed by software running on the Client's dedicated VPS, signed by the Client's own private key, and directed to LP protocol smart contracts — not to addresses controlled by Ranged.pro. Ranged.pro believes this architecture does not constitute money transmission under applicable federal and state law, including Utah's Blockchain Technology Act (2019), which exempts blockchain facilitators from money transmitter licensing requirements.

This Section is Ranged.pro's good-faith assessment and does not constitute legal advice. Clients with questions about the regulatory classification of the Service should consult independent legal counsel.

---

Part II — Security and Custody Model

This section is the authoritative technical disclosure of how the Client's funds are held and what the ALM can and cannot do. It describes the actual architecture in plain language and supersedes any prior summary descriptions.

2.1 Beta-Period Managed Service — Honest Disclosure

The Client should read this section carefully before signing.

Ranged.pro is a fully managed service in its current beta phase. Ranged.pro retains SSH access to the Client's dedicated server for the purpose of providing backend support, deploying software updates, applying security patches, and resolving incidents — all actions intended to keep the Client's ALM running reliably. This is the same operational access model used by any managed hosting provider.

The Client's private keys are non-custodial in the sense that Ranged.pro does not hold, pool, or control the Client's on-chain assets. The Client's LP positions remain in the Client's own wallet at all times. However, the software infrastructure and the server on which the private key is stored are managed by Ranged.pro. Ranged.pro has infrastructure-level access to that server. While Ranged.pro does not claim to be technically incapable of accessing the Client's key material, Ranged.pro represents that it will not do so for any purpose other than those explicitly enumerated in Section 2.5. Clients who require a truly trustless model — where Ranged.pro is technically incapable of accessing their key — should contact Ranged.pro to discuss a self-hosted license arrangement.

The Client's on-chain assets are never held, pooled, or commingled by Ranged.pro. LP positions remain in the Client's own wallet at all times. Ranged.pro's access is to server infrastructure, not to the assets themselves.

2.2 What the Bot Can Do On-Chain

The ALM is capable of executing exactly four types of on-chain transactions, within the chains explicitly configured in the Client's config.yaml. Nothing else.

These are the only contracts the ALM interacts with. By using the Service, the Client acknowledges and accepts the smart contract risk inherent in interacting with decentralized exchange protocols, as further described in Section 3.5.

2.3 What the Bot Software Does Not Do

The ALM software is not programmed to and will not:

• Transfer tokens to any address that is not a whitelisted LP protocol contract
• Call approve() on tokens for any address other than the LP contracts listed above
• Bridge assets cross-chain
• Interact with lending protocols, yield farms, or any contracts not listed above
• Execute transactions on chains that are not explicitly configured in the Client's config.yaml
• Execute any transaction that is not one of the five types listed above

Important clarification: The above describes the behavior of the Ranged.pro ALM software. The Client's private key stored on the VPS is a standard Ethereum-compatible private key with no on-chain spending restrictions. Any party with access to the private key — whether Ranged.pro, the Client, or an unauthorized third party — could in principle use it to sign any transaction the blockchain accepts. The protections listed above are enforced by software, not by the blockchain itself. This is why the honest disclosure in Section 2.1 and the infrastructure access model in Section 2.4 are important context for this Section.

2.4 Dedicated Server Provisioning

As part of the onboarding process, Ranged.pro provisions a dedicated Virtual Private Server ("VPS" or "Droplet") through DigitalOcean for the Client's exclusive use. The VPS account is held and managed by Ranged.pro. The Client does not own or directly control the VPS account — this is a managed infrastructure arrangement, consistent with the managed service model described in Section 2.1.

The Client's private key is stored exclusively on this dedicated VPS. No other client's ALM runs on the same server. The Client has SSH access to inspect their ALM, configuration, and logs at any time (see Section 2.8).

Cloud provider access disclosure: Because Ranged.pro holds the DigitalOcean account, Ranged.pro has access to cloud provider management features beyond SSH, including but not limited to: web-based console access, disk snapshots, server cloning, and server migration. These capabilities are inherent to any cloud hosting account and represent an additional access surface beyond SSH. Ranged.pro will not use these features to access the Client's private key or data except as necessary for the permitted purposes listed in Section 2.5 (e.g., disaster recovery from a corrupted server). The Client who requires full control over the cloud provider account should contact Ranged.pro to discuss a self-hosted license arrangement.

If the Client wishes to own and manage their own VPS account directly, contact Ranged.pro to discuss a self-hosted license arrangement.

2.5 Ranged.pro SSH Access — Permitted Uses

Ranged.pro has SSH administrative access to the Client's dedicated VPS solely for the following permitted purposes:

• Deploying software updates and feature additions
• Restarting the ALM process
• Investigating service incidents
• Applying security patches
• Performing routine maintenance

SSH access is limited to a designated Ranged.pro user account. Root login is disabled as a default configuration; Ranged.pro will not enable root SSH login without documented operational necessity and Client notification.

Ranged.pro will not use SSH access to read, extract, copy, store, transmit, or otherwise access the Client's private key or seed phrase. Ranged.pro will not use SSH access for any purpose other than those expressly listed in this Section.

2.6 SSH Access Revocation

The Client may revoke Ranged.pro's SSH access at any time by removing Ranged.pro's public SSH key from the ~/.ssh/authorized_keys file on the Client's VPS. The Client will receive Ranged.pro's public SSH key in written form during onboarding. Revocation of SSH access constitutes termination of the Service under Part VIII (Term and Termination) of this Agreement, effective upon revocation.

2.7 Client Responsibility for Key Security

The Client is solely responsible for the security of their private key and seed phrase. The Client must not share their private key or seed phrase with Ranged.pro or any third party. If the private key is lost, stolen, compromised, or exposed — whether through the Client's own actions, a third-party breach, or any other cause — Ranged.pro bears no liability for resulting losses.

2.8 Client Verification Access

The Client has SSH access to inspect their ALM, configuration, and logs at any time. The rebalancer user account has limited permissions (no sudo) — sufficient for inspection but not system modification. See the Dashboard & Access Guide provided during onboarding for step-by-step verification instructions.

2.9 Client's Voluntary Assumption of Custody Risk

The Client has read Part II in full and understands that this is a managed service arrangement in which the Client's private key is stored on a VPS controlled by Ranged.pro. The Client voluntarily chooses this arrangement over available alternatives — including self-hosted deployment and hardware wallet custody — with full knowledge of the following:

• Storing a private key on any internet-connected server, whether managed by Ranged.pro or the Client, carries inherent security risks that no software or operational control can fully eliminate.
• Ranged.pro has SSH access to the Client's VPS and the cloud provider holds infrastructure-level access as described in Section 2.4. The Client understands and accepts this access model.
• Ranged.pro has not completed a formal third-party security audit of the managed infrastructure and does not carry cyber liability insurance or a fidelity bond.
• Hardware wallet custody — which would give the Client sole control of their private key — is available but incompatible with the automated managed service model. The Client has elected not to use it for this deployment.

The Client's decision to use the managed service is made freely, voluntarily, and with full knowledge of these risks. The Client waives any claim against Ranged.pro arising from the inherent risks of managed software custody that the Client has accepted under this Section. All losses arising from the Client's use of the Service — regardless of cause — are governed by Part IX of this Agreement.

2.10 What Happens to Your Funds if Ranged.pro Ceases Operations

Your LP positions remain in your wallet. They are never custodied by Ranged.pro. When the ALM stops running:

• Your LP positions continue to exist on-chain, owned by your wallet address
• You can manage them manually through the DEX interface (e.g., 9mm.pro)
• No action from Ranged.pro is required for you to access or withdraw your funds

Ranged.pro will provide a minimum of 30 days written notice before terminating service, giving you time to make alternative arrangements.

---

Part III — Risk Disclosures

3.1 Impermanent Loss

Providing liquidity in a Uniswap V3-style concentrated liquidity pool exposes the Client to impermanent loss ("IL"), which occurs when the relative prices of the pooled tokens diverge from the ratio at the time of deposit. The automated rebalancing executed by the Service may reduce the compounding impact of IL by keeping the position active and collecting trading fees, but it does not eliminate IL, guarantee fee revenue, or guarantee any positive return on the Client's capital.

3.2 Gas Cost Risk

Each rebalance transaction requires payment of on-chain transaction fees ("gas") denominated in the native currency of the Client's configured blockchain network. In volatile market conditions, the ALM may trigger multiple rebalances in a short period, resulting in material cumulative gas expenditure. Ranged.pro implements anti-churn controls to limit unnecessary rebalancing, but these controls do not guarantee that gas costs will not exceed fee income in any given period. Gas is a real and non-recoverable cost borne exclusively by the Client.

3.3 Swap Slippage Risk

Each rebalance workflow includes a token swap to restore the Client's token ratio for the new position. This swap is subject to price slippage, particularly in illiquid pools or during periods of high volatility. Slippage represents an immediate reduction in the effective value of the Client's position at the time of rebalance. Ranged.pro implements slippage tolerance controls, but does not guarantee execution at any specific price.

3.4 Range Configuration Risk

The frequency of rebalancing, and therefore the cumulative cost of gas and swap slippage, is directly determined by the range width and strategy the Client configures. Narrow ranges trigger more frequent rebalances and higher cumulative costs. Wide ranges may result in extended periods of inactivity and reduced fee collection. Ranged.pro describes how configuration parameters affect behavior but does not recommend specific settings or make configuration decisions on the Client's behalf. The Client is solely responsible for their configuration choices and their consequences.

3.5 Smart Contract and Protocol Risk

The Service interacts with smart contracts deployed on the Client's configured blockchain networks, including but not limited to the 9mm V3 DEX protocol (PulseChain), Uniswap V3 (Ethereum, Base, Arbitrum), PancakeSwap V3 (Arbitrum), Aerodrome CL / Slipstream (Base), and Shadow / Algebra V3 (Sonic). Smart contracts are immutable once deployed and may contain undiscovered bugs, logic errors, or vulnerabilities. Third-party protocol upgrades, migrations, or deprecations may alter contract behavior in ways Ranged.pro cannot predict or control. Ranged.pro is not liable for losses arising from smart contract failures, protocol exploits, or third-party protocol changes.

3.6 MEV and Front-Running Risk

Rebalance transactions submitted to blockchain mempools are publicly observable prior to confirmation. Large rebalances in pools with limited liquidity depth may be susceptible to miner extractable value (MEV) attacks, including sandwich attacks. Ranged.pro implements TWAP price protection to mitigate exposure to price manipulation, but cannot eliminate MEV risk.

3.7 Blockchain Network Risk

The Service depends on the continued operation of the Client's configured blockchain network(s). Network outages, consensus failures, reorganizations, regulatory actions, or other events outside Ranged.pro's control may prevent the Service from executing transactions, monitoring positions, or functioning as intended. Ranged.pro will attempt to resume normal operation as soon as possible following any network disruption but is not liable for losses arising during periods of network unavailability.

3.8 Multi-Chain and Cross-Chain Risk

The Service supports multiple blockchain networks (PulseChain, Ethereum, Base, Arbitrum, Sonic). Each network has distinct risk profiles including different gas token prices, block times, liquidity depths, validator/sequencer infrastructure, and regulatory exposure. The Client is responsible for understanding the specific risks of each network on which they operate a position. Ranged.pro does not represent that conditions on one network are comparable to any other.

3.9 No Performance Guarantee

The Service executes transactions based on the Client's pre-configured parameters. It does not predict, forecast, or optimize for future price movements. Past rebalancing performance, whether described in marketing materials, community communications, or Ranged.pro's own public disclosures, does not guarantee future results. Liquidity provision is speculative. The Client may lose some or all of the capital they deploy.

3.10 Tax Obligations

Each on-chain transaction executed by the Service — including but not limited to fee collection, liquidity removal, token swap transactions, and liquidity minting — may constitute a taxable event in the Client's jurisdiction. In high-frequency rebalancing scenarios, the Service may generate hundreds of taxable events per year. The Client is solely responsible for tracking, reporting, and remitting all applicable taxes arising from their use of the Service. Ranged.pro does not provide tax advice and does not generate tax reports. The Client should consult a qualified tax professional familiar with digital asset taxation in their jurisdiction.

---

Part IV — Ranged.pro Access, Data Collection, and Security

4.1 SSH Access — Permitted Uses

As described in Part II, Ranged.pro has SSH access to the Client's VPS for maintenance and support purposes only. SSH activity may be logged by the VPS operating system's audit infrastructure.

4.2 Automated Heartbeat Telemetry

The ALM software installed on the Client's VPS transmits an automated status payload ("heartbeat") to Ranged.pro's monitoring infrastructure approximately every five (5) minutes. This heartbeat contains only the following data:

• Bot software version and uptime
• Position status: token ID, pool address, current in-range/out-of-range status, active strategy
• Wallet address (public address only — not private key or seed phrase)
• Native token balance (balance amount only — not private key or signing credentials)
• Sanitized error messages, from which all sensitive data including key material, RPC credentials, and configuration secrets is stripped prior to transmission

The heartbeat payload does not contain and is technically incapable of containing: private keys, seed phrases, RPC API credentials, or any wallet signing material. Heartbeat data is retained by Ranged.pro for a rolling thirty (30) day period and then permanently deleted.

4.3 Dashboard Access

Ranged.pro has read-only access to the Client's dashboard — including position data, analytics, rebalance history, and performance metrics — for the purposes of support, incident response, and service quality monitoring. The Client is issued their own dashboard login credentials during onboarding and has independent access to the same data.

4.4 Data Ranged.pro Does Not Access

Ranged.pro does not have access to, and will not attempt to access:

• The Client's seed phrase or mnemonic recovery phrase, which is never requested, never transmitted to Ranged.pro, and never stored on Ranged.pro systems
• Funds, wallets, or on-chain positions in any account not explicitly connected to the managed ALM instance
• The Client's accounts on any external exchange, custodian, or financial service

4.5 Ranged.pro Security Obligations

Ranged.pro maintains reasonable administrative, technical, and physical security controls to protect the monitoring infrastructure that receives heartbeat telemetry and hosts the fleet management dashboard. These controls include access control restrictions on the monitoring control plane, encrypted data transmission between the ALM and monitoring systems, and routine security review of deployed software dependencies.

Ranged.pro will provide prompt written notification to the Client at the Client's registered email address within seventy-two (72) hours of becoming aware of any confirmed security breach of Ranged.pro systems that has materially compromised, or is reasonably likely to have compromised, the Client's SSH credentials, heartbeat data, or dashboard access. Notification will describe the nature of the breach, data potentially affected, and steps Ranged.pro is taking in response.

4.6 Privacy

To the extent any heartbeat or dashboard data constitutes personal data under applicable privacy law (including the California Consumer Privacy Act (CCPA)), Ranged.pro will process such data solely for the purposes described in this Agreement and will comply with applicable legal requirements regarding its collection, storage, and deletion. Ranged.pro's full Privacy Policy is available at https://ranged.pro/privacy-policy.

4.7 Data Handling Commitments

Ranged.pro collects and processes a limited set of data in connection with the Service: the Client's name, email address, jurisdiction of residence, public wallet address, heartbeat telemetry (Section 4.2), and dashboard analytics (Section 4.3). Ranged.pro's complete data practices — including what is collected, how it is used, how long it is retained, and the Client's rights — are described in the Privacy Policy at https://ranged.pro/privacy-policy.

Ranged.pro commits to the following:

• Ranged.pro will not sell, rent, or trade the Client's data to any third party.
• Ranged.pro will process Client data only for the purposes of providing the Service, as described in this Agreement and the Privacy Policy.
• Third-party service providers that process data on Ranged.pro's behalf are limited to: DigitalOcean (hosting), Google Workspace (email), and Stripe (payments). Ranged.pro will notify the Client before adding any new third-party data processor.
• Upon termination of the Service, Ranged.pro will delete all Client heartbeat telemetry within 30 days and make analytics data available for download for 30 days, as described in Section 8.4.
• The Client may request access to, correction of, or deletion of their personal data at any time by contacting team@ranged.pro. Ranged.pro will respond within 30 days.
• Ranged.pro processes all data on servers located in the United States.

---

Part V — Third-Party Dependencies

The Service depends on third-party infrastructure and protocols outside Ranged.pro's control, including: decentralized exchange protocols used for swap routing; RPC endpoints for each configured blockchain network (multiple fallback providers are configured); DEX protocols (9mm V3, Uniswap V3, PancakeSwap V3, Aerodrome CL, Shadow/Algebra V3); and the DigitalOcean VPS cloud platform. Failures, outages, upgrades, or adverse changes to any of these dependencies may interrupt or impair the Service. Ranged.pro is not affiliated with any of these third parties and is not liable for losses arising from their unavailability or malfunction. The Client's waiver of claims in Section 9.3 applies to all third-party dependency failures.

---

Part VI — Service Description and Limitations

6.1 What the Service Does

The Service monitors the Client's configured concentrated liquidity position(s) at approximately sixty (60) second intervals and executes on-chain rebalance transactions when the position exits its configured price range, subject to the safety checks described below.

6.2 Available Strategies

The Service supports multiple configurable management strategies, including symmetric, directionally-biased, trend-following, and monitoring-only modes. The available strategy set may be updated over time as the Service evolves. Strategy selection and configuration is the Client's responsibility.

6.3 What the Service Does Not Do

The Service does not:

• Make discretionary trading or investment decisions on the Client's behalf
• Time the market or predict future price movements
• Manage assets outside the liquidity position(s) explicitly configured in the managed instance
• Execute high-frequency arbitrage or other trading strategies unrelated to LP management
• Guarantee execution of any specific rebalance within any specific timeframe
• Guarantee service continuity during blockchain network outages, RPC failures, or third-party dependency failures
• Provide tax reporting, accounting, or legal compliance services

6.4 Safety Mechanisms — Best-Effort Disclaimer

The Service implements multiple risk mitigation mechanisms, including:

• TWAP-based price manipulation protection: validates current price against a time-weighted average before executing rebalances
• Anti-churn delay: requires the position to remain out of range for a configurable confirmation period (default: 10–60 minutes depending on chain) before triggering a rebalance
• Gas price limits: will not execute transactions if the network gas price exceeds a configured maximum
• Loss-based kill switch: automatically stops rebalancing if cumulative losses within a rolling window exceed a configured threshold (default: -5% in 48 hours, or 3 consecutive loss-generating rebalances)

These mechanisms are provided as best-effort risk reduction tools. They are not guaranteed to prevent adverse outcomes under all market conditions. The Client acknowledges that no automated safety system eliminates execution risk.

6.5 Kill Switch Disclosure

The Service includes a configurable automatic kill switch that halts all rebalancing activity if the ALM detects sustained adverse performance. By default, the kill switch activates if cumulative position losses exceed 5% within any 48-hour window, or if 3 consecutive rebalances result in net losses. When the kill switch activates, the ALM stops executing transactions and notifies the Client via Telegram. The kill switch does not close, remove, or otherwise modify the Client's open LP position. The Client's position remains on-chain in its current state until the Client manually intervenes or re-enables the ALM.

The Client may adjust or disable the kill switch parameters through their configuration file. Ranged.pro is not responsible for losses incurred after the Client modifies or disables the kill switch.

6.6 Recovery State

The Service maintains a recovery state file on the Client's VPS that captures position state before critical on-chain actions. If the ALM terminates unexpectedly during a rebalance, this file enables detection of stranded funds and supports manual recovery. Ranged.pro will make reasonable efforts to assist the Client in recovering stranded funds following an unexpected interruption, but does not guarantee recovery in all circumstances.

6.7 Uptime Commitments

Ranged.pro monitors all client ALMs via a central telemetry system. Every five (5) minutes, the Client's ALM transmits a heartbeat signal. ALM status is determined by the time since the last received heartbeat:

Monthly uptime target, measured as time in Healthy status divided by total monitored time: 95%.

Exclusions from uptime calculation: The following events are outside Ranged.pro's control and are excluded from uptime calculations: blockchain RPC outages or public node degradation; chain reorganizations, halts, or protocol-level failures; DEX smart contract upgrades or emergency pauses; Force Majeure Events (see Section 9.3); scheduled maintenance windows (see Section 6.10); and outages caused by Client-side changes to .env, config.yaml, or wallet settings made without coordination with Ranged.pro.

6.8 Incident Response Commitments

Bot incidents (Stale or Dead status): Ranged.pro targets acknowledgment and initial investigation within 2–3 business days of a detected incident. Business hours: Monday–Friday, 9 AM–6 PM Mountain Time, excluding US federal holidays.

Support requests (non-incident): Ranged.pro targets a response within 2–3 business days via email or the Client's designated support channel.

When a Stale or Dead incident is detected: (1) Ranged.pro receives a Telegram alert; (2) Ranged.pro investigates logs via SSH on the Client's VPS; (3) Ranged.pro attempts to restart the ALM or address the root cause; (4) if resolution requires more than a restart, Ranged.pro contacts the Client with an ETA; (5) once resolved, Ranged.pro confirms Healthy status and sends the Client a brief incident summary. The Client's position is not modified during an outage unless the Client requests it.

6.9 What the Service Does Not Guarantee

In addition to the limitations in Section 6.3, the Service does not guarantee:

• Trading profitability. Rebalancing is automated, but market outcomes depend on price movements that neither party can predict. Impermanent loss and fee revenue are inherent to providing liquidity.
• Guaranteed transaction execution. On-chain transactions may fail due to gas price spikes, RPC timeouts, or smart contract conditions. The ALM retries failed transactions, but completion is not guaranteed within any specific time window.
• RPC reliability. Ranged.pro configures multiple fallback RPC endpoints per chain. If all endpoints for a chain are simultaneously degraded, the ALM cannot transact until connectivity is restored.
• Swap execution price. The ALM uses configurable slippage protection, but swap execution prices depend on on-chain liquidity at the time of execution.

6.10 Planned Maintenance

Ranged.pro will provide at least twenty-four (24) hours advance written notice for any scheduled maintenance that requires stopping the Client's ALM. Maintenance windows are capped at two (2) hours per calendar month without Client approval. Planned maintenance is excluded from the uptime calculation in Section 6.7.

---

Part VII — Fees and Payment

Fees, billing frequency, accepted payment methods, and payment terms are set forth in the Payment Schedule provided to the Client separately at or before the start of Service. The Payment Schedule is incorporated into this Agreement by reference.

7.1 Non-Payment and Service Suspension

If a payment fails or a subscription lapses, Ranged.pro will provide written notice to the Client's registered email address. If payment is not received within 14 calendar days of that notice, Ranged.pro may suspend the Service.

Service suspension means: the ALM process will be stopped and will no longer monitor or execute transactions on the Client's position. The Client's VPS will remain provisioned and the Client's private key and position will remain entirely under the Client's control. Suspension does not close, modify, or interact with the Client's on-chain position in any way. Ranged.pro will not initiate a suspension during a rebalance cycle that is actively in progress; suspension will occur at the next clean state checkpoint.

7.2 Fee Changes

Ranged.pro may change the fee structure with thirty (30) days written notice to the Client's registered email address. Fee changes are not retroactive. The Client may terminate this Agreement before the effective date of a fee change without penalty under Part VIII.

---

Part VIII — Term and Termination

8.1 Initial Term and Renewal

This Agreement begins upon the Client's first payment. Following receipt of payment, Ranged.pro will provision the Client's dedicated VPS and have the ALM running within 24–48 hours. The Agreement continues on a month-to-month basis from the payment date until terminated by either party in accordance with this Part.

8.2 Termination by Either Party

Either party may terminate this Agreement with fourteen (14) calendar days written notice delivered to the other party's registered contact address. Written notice may be delivered by email. Notice is effective upon confirmed delivery.

8.3 Immediate Termination by Ranged.pro

Ranged.pro may terminate this Agreement immediately and without prior notice if:

• The Client is found to be using the Service for any unlawful purpose, including but not limited to money laundering, sanctions evasion, or tax evasion
• The Client's conduct creates a security risk to Ranged.pro's monitoring infrastructure
• The Client materially breaches this Agreement and fails to cure the breach within five (5) days of written notice
• Continued operation of the Service for the Client would expose Ranged.pro to legal, regulatory, or financial risk that Ranged.pro reasonably cannot bear

8.4 Offboarding Protocol

Upon termination — regardless of cause — the following offboarding procedures will be executed:

• Ranged.pro will stop the ALM process at the next clean state checkpoint. If a rebalance transaction is in progress at the time of termination, Ranged.pro will allow it to complete before stopping the ALM, unless immediate termination is required for security reasons.
• Ranged.pro will export the Client's strategy configuration file, rebalance history, and available analytics data in a machine-readable format (JSON or CSV) and make it available for the Client to download for a period of thirty (30) days following termination.
• Ranged.pro will revoke its own SSH access to the Client's VPS within forty-eight (48) hours of the effective termination date.
• Ranged.pro will delete all Client heartbeat telemetry from Ranged.pro systems within thirty (30) days of the effective termination date.
• The Client's funds and on-chain position remain entirely under the Client's own control before, during, and after termination. Ranged.pro does not close, liquidate, or interact with the Client's on-chain position as part of the offboarding process.

It is the Client's sole responsibility to monitor their on-chain position following termination of the Service.

---

Part IX — Assumption of Risk, Waiver of Claims, and Indemnification

9.1 No Warranty

THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE." THE OPERATOR MAKES NO WARRANTIES, EXPRESS OR IMPLIED, REGARDING PROFITABILITY, FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, NON-INFRINGEMENT, UNINTERRUPTED OPERATION, OR ANY SPECIFIC OUTCOME FROM USE OF THE SERVICE. NO ORAL OR WRITTEN STATEMENT BY THE OPERATOR OR ITS REPRESENTATIVES SHALL CREATE ANY WARRANTY NOT EXPRESSLY SET FORTH IN THIS AGREEMENT.

9.2 Assumption of Risk

THE CLIENT ACKNOWLEDGES THAT USE OF THE SERVICE INVOLVES SIGNIFICANT FINANCIAL AND TECHNOLOGICAL RISK, INCLUDING BUT NOT LIMITED TO: LOSS OF DIGITAL ASSETS DUE TO MARKET PRICE MOVEMENTS; IMPERMANENT LOSS; GAS COSTS; SWAP SLIPPAGE; MEV AND SANDWICH ATTACKS; SMART CONTRACT FAILURES OR EXPLOITS; PROTOCOL UPGRADES OR DEPRECATIONS; RPC AND BLOCKCHAIN NETWORK OUTAGES; THIRD-PARTY DEPENDENCY FAILURES; AND THE INHERENT RISKS OF MANAGED SOFTWARE CUSTODY DESCRIBED IN PART II.

THE CLIENT HAS INDEPENDENTLY EVALUATED THESE RISKS, HAS SOUGHT OR WAIVED INDEPENDENT LEGAL AND FINANCIAL COUNSEL, AND FREELY AND VOLUNTARILY ASSUMES ALL SUCH RISKS AS A CONDITION OF USING THE SERVICE. THE CLIENT'S DECISION TO USE THE SERVICE — INCLUDING THE AMOUNT OF CAPITAL DEPLOYED, THE STRATEGY CONFIGURED, AND THE CUSTODY MODEL ACCEPTED — IS THE CLIENT'S OWN AND IS MADE WITHOUT RELIANCE ON ANY REPRESENTATION OR RECOMMENDATION BY THE OPERATOR.

9.3 Waiver of Claims

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE CLIENT WAIVES ANY AND ALL CLAIMS, DEMANDS, AND CAUSES OF ACTION AGAINST THE OPERATOR AND ITS OFFICERS, AGENTS, SUCCESSORS, AND ASSIGNS ARISING FROM OR RELATED TO: (A) LOSS OF DIGITAL ASSETS DUE TO MARKET PRICE MOVEMENTS; (B) IMPERMANENT LOSS; (C) GAS COSTS INCURRED IN THE COURSE OF REBALANCING; (D) SWAP SLIPPAGE LOSSES; (E) MEV OR SANDWICH ATTACK LOSSES; (F) SMART CONTRACT FAILURES, PROTOCOL EXPLOITS, OR PROTOCOL UPGRADES; (G) RPC OR BLOCKCHAIN NETWORK OUTAGES; (H) THIRD-PARTY DEPENDENCY FAILURES; (I) THE CLIENT'S OWN CONFIGURATION DECISIONS, INCLUDING RANGE WIDTH, STRATEGY SELECTION, AND TRIGGER PARAMETERS; (J) THE INHERENT RISKS OF MANAGED SOFTWARE CUSTODY VOLUNTARILY ACCEPTED BY THE CLIENT UNDER SECTION 2.9; AND (K) INDIRECT, INCIDENTAL, SPECIAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES OF ANY KIND, INCLUDING LOST PROFITS OR LOST REVENUE.

THIS WAIVER APPLIES REGARDLESS OF THE LEGAL THEORY UNDER WHICH ANY CLAIM IS BROUGHT (CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY, OR OTHERWISE) AND EVEN IF THE OPERATOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. NOTHING IN THIS SECTION WAIVES CLAIMS ARISING FROM THE OPERATOR'S GROSS NEGLIGENCE OR WILLFUL MISCONDUCT, WHICH CANNOT BE WAIVED UNDER APPLICABLE LAW.

9.4 Force Majeure

Neither party shall be liable for delays or failures in performance caused by events beyond its reasonable control ("Force Majeure Events"), including but not limited to:

• Blockchain network outages, consensus failures, chain halts, or reorganizations
• Smart contract protocol failures, exploits, migrations, or deprecations by third-party protocol teams
• RPC infrastructure outages or degradation
• Cloud provider (e.g., DigitalOcean) outages, data center failures, or account-level actions
• Regulatory actions, sanctions changes, or government orders
• Natural disasters, pandemics, wars, or civil unrest
• Cyberattacks, DDoS attacks, or widespread internet disruptions

The affected party will notify the other party as soon as reasonably practicable and make reasonable efforts to resume performance. If a Force Majeure Event prevents Ranged.pro from providing the Service for more than thirty (30) consecutive days, either party may terminate this Agreement without penalty under Section 8.2.

9.5 Client Indemnification

The Client agrees to indemnify, defend, and hold harmless Ranged.pro and its officers, agents, successors, and assigns from and against any and all claims, damages, losses, costs, and expenses (including reasonable legal fees) arising out of or relating to: (a) the Client's use of the Service in violation of this Agreement; (b) the Client's violation of any applicable law, regulation, or third-party right; (c) the Client's configuration decisions, including range width, strategy selection, and trigger parameters; (d) the Client's tax obligations arising from automated transactions; (e) any misrepresentation by the Client regarding their eligibility to use the Service; or (f) any action the Client takes with respect to their on-chain position outside the scope of the Service.

---

Part X — Dispute Resolution

10.1 Informal Resolution

Prior to initiating any formal dispute proceeding, the parties agree to attempt to resolve the dispute in good faith through direct written communication for a period of thirty (30) calendar days from the date one party provides written notice of the dispute to the other party. Neither party may initiate formal proceedings until this informal resolution period has elapsed or has been mutually waived in writing.

10.2 Arbitration, Small Claims, and Individual Basis

Binding Arbitration. Except as provided below, any dispute, claim, or controversy arising from or relating to this Agreement or the Service that cannot be resolved through the informal resolution process in Section 10.1 shall be resolved by binding arbitration administered by JAMS under its Streamlined Arbitration Rules and Procedures, as amended from time to time. The arbitration shall be conducted by a single arbitrator, in English, seated in Salt Lake County, Utah (or conducted remotely by mutual agreement). The arbitrator's award shall be final and binding and may be entered as a judgment in any court of competent jurisdiction. The Federal Arbitration Act governs the interpretation and enforcement of this arbitration agreement.

Small Claims Exception. Either party may bring an individual claim in the small claims court of competent jurisdiction in Salt Lake County, Utah, without first completing informal resolution, provided the claim qualifies for small claims court under applicable Utah law.

Individual Basis Only. All disputes shall be resolved on an individual basis. Neither party may bring or participate in any class action, collective action, or representative proceeding against the other, whether in arbitration or in court. The arbitrator has no authority to consolidate claims or preside over any class or representative proceeding. If this individual-basis requirement is found unenforceable with respect to any claim, that claim shall be severed and heard in court, with all remaining claims proceeding in arbitration.

10.3 Governing Law and Jurisdiction

This Agreement shall be governed by and construed in accordance with the laws of the State of Utah, without regard to its conflict of law provisions. The parties consent to the exclusive jurisdiction of the state and federal courts located in Salt Lake County, Utah.

---

Part XI — Amendments

Ranged.pro may amend these terms with thirty (30) calendar days written notice to the Client's registered email address. Notice of amendment will clearly identify which sections are being changed and summarize the nature of the change.

For amendments that: (a) expand the scope of Ranged.pro access to Client systems or data; (b) narrow the Client's waiver of claims or assumption of risk under Part IX; (c) increase the Client's financial obligations; or (d) materially alter the architecture described in Part II — the Client's affirmative written acknowledgment (email confirmation or countersigned addendum) will be required before the amendment takes effect with respect to that Client. Continued use of the Service alone is not sufficient to constitute acceptance of a material amendment.

For non-material amendments (typographical corrections, clarifications that do not alter substantive rights, updates to third-party dependency lists), continued use of the Service after the effective date constitutes acceptance.

If the Client objects to any amendment, the Client may terminate this Agreement before the effective date without penalty under Section 8.2, with the termination effective on the amendment effective date.

---

Part XII — General Provisions

12.1 Entire Agreement

This Agreement, together with any signed order form, tier-specific addendum, or Exhibit incorporated by reference, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, representations, and understandings — including any earlier custody disclosures or terms of service drafts provided to the Client.

12.2 Severability

If any provision of this Agreement is found to be unenforceable or invalid under applicable law, that provision shall be modified to the minimum extent necessary to make it enforceable, and the remaining provisions shall remain in full force and effect.

12.3 Waiver

No failure or delay by either party in exercising any right under this Agreement shall constitute a waiver of that right. No waiver of any breach shall be deemed a waiver of any subsequent breach.

12.4 Assignment

The Client may not assign this Agreement or any rights or obligations hereunder without Ranged.pro's prior written consent. Ranged.pro may assign this Agreement in connection with a sale of Ranged.pro's business or assets, provided the Client is notified in writing and retains the right to terminate under Section 8.2 if the Client objects to the assignment.

12.5 Notices

All notices under this Agreement shall be in writing and delivered by email to the registered address of the receiving party. Notices are effective upon confirmed delivery. The Client's registered email address is the address provided during onboarding. Ranged.pro's registered email address is team@ranged.pro.

12.6 No Third-Party Beneficiaries

This Agreement is for the sole benefit of the parties hereto and does not create any third-party beneficiary rights.

---

Service Level Terms

Uptime commitments, incident response times, and planned maintenance are set forth in Part VI, Sections 6.7–6.10 of this Agreement. Those sections constitute the complete service level terms and are fully integrated into this Agreement. No separate SLA document exists or is incorporated by reference.

---

Signature Block and Client Acknowledgments

Electronic Acceptance: On the Ranged.pro website, this Agreement is accepted electronically by checking the acceptance box and completing the checkout process. The signature block below is the authoritative paper/PDF form used for offline onboarding. Both methods are equally binding.

By signing below or confirming acceptance electronically at checkout, the Client confirms that they have read this Agreement in full, understand its terms, and agree to be bound by it.

Electronic acceptance occurs when the Client checks the acceptance box and completes the checkout process on the Ranged.pro website. Physical acceptance occurs when the Client signs the paper or PDF signature block below. Either method constitutes full and binding execution of this Agreement.

By executing this Agreement (electronically or in writing), the Client specifically acknowledges:

• They have read and understood the managed service and custody model described in Part II, including that Ranged.pro has SSH access to the Client's dedicated server and that this is not a trustless arrangement.
• They have read and understood the financial risks described in Part III, including impermanent loss, gas costs, swap slippage, and that they may lose some or all capital deployed.
• They have read and understood the risk and waiver provisions in Part IX and voluntarily assume all risks associated with using the Service.
• They are at least 18 years of age, are not a resident of any OFAC-sanctioned jurisdiction, and are not on any applicable sanctions list.
• All on-chain transactions executed by the ALM may constitute taxable events, and they are solely responsible for all resulting tax obligations.

Client Legal Name:    ______________________________________________________

Signature:            ______________________________________________________

Date:                 ______________________________________________________

Jurisdiction of Residence: _________________________________________________

---

Document version 2.2 — CoinSurge LLC