How elar64/solana-pumpfun-bundler-volume-bot works
Project type and purpose
• This is a backend-only, command-line utility (“Bot”) for automating Solana token operations: bundling, staggering, sniping, balance checks, transfers, etc.
• No web front-end; it’s a single-process Python application that interacts with blockchain RPC endpoints.
File structure
• Top-level files:
• main.py: entry point, parses CLI flags, invokes workflows
• config.py / constants.py: environment/configuration and constant definitions
• pump_fun.py: core logic for bundling, staggering, sniping, transfers
• find_instruction.py: helper module to compose Solana instructions
• utils.py: helpers (e.g., logging, wallet loading, RPC wrapper)
• data/pks.txt: input data (public keys list)
• requirements.txt: dependencies
• No DB; uses flat files and in-memory structures.
• Relies on external Solana RPC endpoints and possibly third-party Solana Python libraries.
README for additional insights
• It enumerates features (bundle launch, sub-wallet funding, balance checks, etc.).
• Usage is purely CLI (py main.py), so design around a command dispatcher.
a. Main Components:
1. CLI Interface (main.py)
2. Configuration Layer (config.py / constants.py)
3. Core Logic Modules:
– pump_fun.py (bundler & volume workflows)
– find_instruction.py (instruction builder)
– utils.py (RPC client, wallet loader, logging)
4. Data Store: data/pks.txt (public key inputs)
5. External Service: Solana RPC Node(s)
b. Interactions:
– User invokes CLI → main.py
– main.py reads config & constants → chooses feature workflow
– Workflow calls functions in pump_fun and find_instruction
– Those modules use utils to load wallets, read pks.txt, construct transactions
– utils sends transactions/queries via HTTP(S) to Solana RPC endpoint
– Responses returned → processed, logged, displayed in CLI
c. Architectural Patterns / Principles:
– Modular separation: configuration vs. business logic vs. utility/helper code
– Single-process sequential workflows—no microservices, but clear functional layering
– External dependency inversion: RPC client abstracted in utils
d. Key Technologies / Libraries:
– Python 3.x
– Solana Python SDK (or HTTP RPC calls)
– Standard libs (argparse for CLI, logging)