LP Ranger is free, open-source software published on GitHub. Depending on your relationship to this software, one or more of the following characterizations applies to you or to others in connection with its use.
The Creator is the individual developer who authored LP Ranger and published it on GitHub. The Creator is not registered with or regulated by the U.S. Securities and Exchange Commission in connection with the creation of this software. The Creator does not operate any deployed instance of LP Ranger, does not custody any user funds, does not receive any compensation in connection with the software’s operation, has no visibility into any transaction executed by any deployed instance, and exercises no control over any running instance of this software.
The Offeror is any person — including the Creator, to the extent the Creator mentions, describes, distributes, or promotes LP Ranger in any context — who makes this software available to others. The Offeror is not registered with or regulated by the U.S. Securities and Exchange Commission in connection with the offering of this software. Nothing communicated by the Offeror in connection with LP Ranger constitutes a solicitation to engage in any specific transaction, investment advice, or a recommendation regarding any crypto asset, trading venue, execution route, or liquidity position.
The Operator is the person running this software — that is, you. You downloaded this software, you deployed it on your own infrastructure, you connected it to your own self-custodial wallet, and you configured it according to your own parameters. You are the operator of this instance of LP Ranger. The Operator is not registered with or regulated by the U.S. Securities and Exchange Commission in connection with the operation of this software for the Operator’s own self-custodial wallet. All transactions executed by LP Ranger are initiated by the Operator’s own configuration, signed by the Operator’s own wallet, and submitted to the public blockchain on the Operator’s own behalf.
If you are running LP Ranger as a hosted service for third parties — that is, if other users are accessing your deployed instance of LP Ranger to manage their own wallets and positions — you are acting as a Covered User Interface Provider within the meaning of the SEC Staff Statement Regarding Broker-Dealer Registration of Certain User Interfaces Utilized to Prepare Transactions in Crypto Asset Securities (File No. 4-894, April 13, 2026). In that capacity, additional obligations may apply to you under federal securities law. You should review that statement and consider seeking legal counsel before operating LP Ranger as a hosted service for others.
THIS SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT.
BY USING THIS SOFTWARE, YOU ACKNOWLEDGE AND AGREE THAT:
DO NOT USE THIS SOFTWARE WITH FUNDS YOU CANNOT AFFORD TO LOSE.
The Creator, Offeror, and Operator of LP Ranger have no affiliation of any kind — including no ownership interest, no revenue-sharing arrangement, no control relationship, no contractual relationship, no compensation arrangement, no referral or incentive agreement, and no other formal or informal relationship — with 9mm, the 9mm DEX Aggregator, 9mm Pro V3, PulseChain, or any person or entity associated with their creation, offering, or operation.
LP Ranger connects to and interacts with the following trading venues and distributed ledger trading systems on PulseChain solely because they are the protocol for which this software was designed:
The Creator and Offeror of LP Ranger holds token positions in several crypto assets on PulseChain whose protocols are directly related to or compete with the protocols LP Ranger interacts with. These positions are disclosed in the interest of full transparency. The Creator and Offeror does not believe these holdings constitute a material conflict of interest in the traditional securities law sense, but discloses them so that users can make their own informed assessment. Two holdings — described below — represent substantial positions by token supply and are disclosed with particular specificity for that reason.
These disclosures reflect the Creator and Offeror’s holdings at the time of the current Disclosure version date. Token holdings may change over time. The Creator and Offeror commits to updating this disclosure promptly if holdings change in a manner that would be material to a reasonable user’s assessment of this software.
LP Ranger charges no fees of any kind. There is no percentage fee, flat fee, per-transaction fee, or protocol fee collected by the Creator, Offeror, or Operator in connection with the use of this software. All trading fees earned from liquidity provision accrue directly to the user’s own wallet. The only costs incurred in connection with LP Ranger’s operation are standard PulseChain network gas fees, which are paid directly to the network and would be required for the same transactions regardless of whether LP Ranger is used to execute them.
LP Ranger accepts voluntary donations, which are entirely optional, not connected to any transaction, and have no effect on software functionality or routing behavior.
LP Ranger displays post-trade information including transaction hashes, token amounts received, USD values at time of execution, gas costs, tick ranges, and historical rebalance event logs. This information is derived exclusively from publicly available on-chain data — specifically, transaction receipts and event logs recorded on the PulseChain public ledger, which are readable by anyone with access to a PulseChain RPC endpoint.
All such data is retrieved directly from the blockchain by the software running on your own machine and stored locally in a rebalance_log.json file on your own infrastructure. No trade data, transaction history, wallet addresses, token amounts, or any other post-trade information is transmitted to, processed by, stored by, or accessible to the developer, offeror, or any third party in connection with the operation of this interface. The developer has no visibility into any transaction you execute or any position you manage using this software.
This local transaction history is maintained solely for your own operational reference. It is the equivalent of reading your own transaction history from a public block explorer — the operator of this software is you, reading data that is already public, on hardware you control.
Swap transactions in LP Ranger take one of two paths. In the primary path, the application obtains a swap quote from the 9mm DEX Aggregator over an encrypted HTTPS connection; the quote request and the resulting calldata are not exposed to any public mempool or on-chain location prior to submission, so no advance signal of swap intent is available to searchers before the user signs. The aggregator-returned guaranteedPrice floor is embedded in the calldata and causes the transaction to revert rather than execute at a price below the user’s slippage tolerance. In the unlikely case that the Aggregator is not working, the swap is executed directly on the same 9mm Pro V3 liquidity pool that LP Ranger is managing for its rebalance or compound action (V3 SwapRouter fallback); in that path the amountOutMinimum parameter is derived from the user’s slippage tolerance applied to a simulated quote and provides the same revert-on-sandwich economic defense.
In both paths, the signed transaction is submitted to the public PulseChain mempool and is therefore subject to generic mempool observation between submission and block inclusion. No private mempool routing, Flashbots-equivalent service, or atomic execution is used. The slippage tolerance setting — configurable by the user — is the primary user-controlled defense against adverse execution. See the in-app educational dialogs for guidance on appropriate slippage tolerance settings for different pool types.
LP Ranger implements a comprehensive set of security controls governing private key handling, encrypted storage, network access, request authentication, and transaction safety. A full description of these controls is maintained in the LP Ranger Security Architecture Documentation (a high-level overview) and in the LP Ranger Security Engineering Documentation (the details) in the project’s GitHub repository. Those documents reflect current security practices as actively maintained by the Creator and may be updated independently of the Disclosure version date — users are encouraged to review them directly for the most current information.
The following is a summary of the primary controls in effect as of the current Disclosure version date:
HOST settingguaranteedPrice floor causes the transaction to revert rather than execute at a price below the user’s slippage tolerance. In the unlikely case that the Aggregator is not working, the swap is executed directly on the same 9mm Pro V3 liquidity pool that LP Ranger is managing for its rebalance or compound action — the application constructs the transaction client-side using that pool’s on-chain state (V3 SwapRouter fallback); in that path the amountOutMinimum parameter is likewise derived from the user’s slippage tolerance applied to a simulated quote, providing the same revert-on-sandwich economic defense. The signed transaction in either path is submitted to the public PulseChain mempool and is therefore subject to generic mempool observation between submission and block inclusion. See the MEV Exposure section above for residual mempool risk.For complete technical detail including implementation specifics, audit tooling, and configuration, see the LP Ranger Security Architecture Documentation and the LP Ranger Security Engineering Documentation.
LP Ranger provides comprehensive in-app educational content for every configurable parameter and every non-trivial result metric displayed in the dashboard. Each setting includes a dedicated information dialog covering what the parameter does, recommended values for different pool types, extreme value warnings, and relationships to other parameters. This educational content is accessible at any time during operation via the information buttons throughout the interface and is designed to support informed, user-directed decision-making at every level of the software’s configuration.
All transaction parameters are user-configurable. Default values are set conservatively based on PulseChain network characteristics and Uniswap v3 position management patterns, and are disclosed in the in-app educational dialogs alongside their rationale and recommended alternatives. The in-app Swap Routing information dialog specifically informs users that LP Ranger uses the 9mm DEX Aggregator as its single aggregator by design, and that other aggregators exist — providing route transparency context directly at the point of use.
This software is licensed under the Apache 2.0 License.
Disclosure version: 2026-04-21