mortdeus/solana-copy-sniper-mev-trading-bot: A Rust and Node.js Solana Sniper Bot
🆓Free High speed solana mev arbitrage Sniper Copy Trading Bot, gRPC shred stream Pumpfun Bundler, Pumpfun Contract, Yellowston Geyser, token launcher, AI raydium pool creator, volume, sandwich, raydium swap bot, pumpswap auto Volume, Maker bot, 0xblock, best 0 block solana trading bot solana trading bot solana trading bot solana trading bot
At a glance
- What is it?
- A repository with four separate Solana trading bot implementations, two in Node.js and one in Rust, plus a Helius websocket variant. It is BSD-3-Clause licensed, and the README does not document installation steps.
- Who is it for?
- Use this repository if you want to read or adapt existing Rust and Node.js Solana trading code and you are comfortable working without documented setup steps. Do not adopt it if you need a maintained, installable product: the README documents no installation and no configuration keys, and the repository has no releases.
- Can I use it commercially?
- Yes. BSD-3-Clause is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 16 days ago.
- What is it written in?
- Mainly Rust, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- mortdeus/solana-copy-sniper-mev-trading-bot4,518 ★ · +47
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| mortdeus/solana-copy-sniper-mev-trading-bot | 4.5k | 4.5k |
47 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What the solana-copy-sniper-mev-trading-bot repository actually contains
The repository is not one bot. The top-level layout holds four separate implementations in numbered folders: "#_sniper (Rust) using jito Shred stream/", "1_solana sniper bot(node) using gRPC/", "2_copy trading bot(node) using gRPC/" and "3_sniper bot(node) using using Helius websocket/".
The intended audience is a developer who already understands Solana transaction mechanics and wants a starting point for copy trading, sniping new launches, or MEV extraction. It also advertises paid custom development through a Telegram handle, so the repository doubles as a lead generator for the author's services.
The folder naming is the clearest signal of scope. Each entry pairs a transport with a strategy: Jito shred stream for the Rust sniper, gRPC for the Node.js sniper and the Node.js copy trader, and a Helius websocket for a third Node.js sniper. That is four implementations across three transports.
How the Rust and Node.js implementations differ in data flow
The Rust implementation sits in "#_sniper (Rust) using jito Shred stream/", and the README does not describe how it works.
The Node.js implementations sit in "1_solana sniper bot(node) using gRPC/", "2_copy trading bot(node) using gRPC/" and "3_sniper bot(node) using using Helius websocket/", and the README does not describe them either.
The README's only technical claims sit in its support offer: "Off-chain signing for speed" and custom sell logic optimization. None of these are shown as code in the README, so treat them as a description of intent rather than a verified inventory.
Installing the bot: what the README does and does not give you
The README has no Quick Start or install section. It gives no package install line, database schema, environment variable, port or config key.
Because of that, the only reproducible step you can take from the documentation is to clone the repository and inspect a folder. The commands below are the standard git operations for that, not steps the README provides.
git clone https://github.com/mortdeus/solana-copy-sniper-mev-trading-bot.git
cd solana-copy-sniper-mev-trading-bot
lsAfter that you should see the four numbered implementation folders plus the documentation files listed in the repository root: CODE_OF_CONDUCT.md, CONTRIBUTING.md, LICENSE, PROGRAM_LOGIC_DIAGRAM(Node).md, PROGRAM_LOGIC_DIAGRAM(Rust).md, SECURITY.md and README.md. The two PROGRAM_LOGIC_DIAGRAM files are the closest thing to architecture documentation in the repository, and they are the first thing to open.
From there, the README gives no build or run command for either language. You would have to read the source in the folder you choose. If you need a documented install path before you commit time, this project does not currently provide one.
The PnL table and why it is not evidence
The README contains no trade results, PnL figures or Solscan links. Its only performance language is the support pitch ("Sell Logic Optimization: Maximize your profit potential") and "Start your journey to profitable trading today!"
Where this bot is the wrong tool
If you want a running product, this is the wrong repository. There are no releases and the README has no setup instructions. You would be reading source code and writing your own setup, not following instructions.
The repository metadata says BSD-3-Clause and a LICENSE file sits at the root; the README does not mention a licence. The README also does not state what happens to the code if you deploy it and lose money, which is the normal case for a trading bot repository and worth noting because the repository is presented alongside paid development services.
Alternatives with a different approach
The closest comparison inside this repository is between its own folders: a Rust sniper on Jito shred stream, two Node.js bots on gRPC (a sniper and a copy trader) and a Node.js sniper on a Helius websocket. The README does not say how they differ beyond those folder names.
Outside the repository, hosted trading bots are the other option: you do not read their code or change their sell logic. This repository is the opposite trade: you get the source and the responsibility. The README's own framing supports that reading, since it advertises custom development and professional support rather than a hosted product.
A third option is to build directly on an RPC provider's own SDK and skip the bot layer entirely. That is more work than cloning four folders, but it removes the question of whether the repository's landing logic is current.
Maintenance, licensing and upgrade cost
The last push to the default branch was on 2026-10-30, and the repository is not archived. That is recent activity. It is not the same as a maintained release cycle: the repository has no published releases. The practical upgrade cost is therefore unknown, because there is no version to upgrade from and no changelog describing what changed between pushes.
On licensing, the repository metadata declares BSD-3-Clause and a LICENSE file is present at the root; the README does not mention a licence, so the file that matters is LICENSE. Read it before you redistribute anything. Nothing here is legal advice, and the README does not discuss what obligations apply if you deploy the bot as a service.
The paid development channel is part of the maintenance picture. The README routes feature requests and custom work to a Telegram handle, which means the roadmap is not visible in the repository. If you depend on a feature that does not exist yet, there is no issue tracker or milestone to check.
Editorial conclusion
Use this repository if you want to read or adapt existing Rust and Node.js Solana trading code and you are comfortable working without documented setup steps. Do not adopt it if you need a maintained, installable product: the README documents no installation and no configuration keys, and the repository has no releases. Read the LICENSE file (BSD-3-Clause per the repository metadata) before you reuse any code, and read PROGRAM_LOGIC_DIAGRAM(Rust).md and PROGRAM_LOGIC_DIAGRAM(Node).md before assuming what the entry points actually do.
Frequently asked questions
What is the best sniper bot for Solana?
The README does not make a comparative claim against other bots. It describes this repository as offering four implementations, two in Node.js and one in Rust plus a Helius websocket variant, and its README offers custom development and sell logic optimization through Telegram. Choosing between them depends on whether you want latency or remote control.
How much does a sniper auto trader bot cost?
The README does not state a price for this repository, and it does not list any paid tier for the code itself. It does advertise custom development, sell logic optimization and 24/7 support through a Telegram handle, but no rate is given.
Are meme coin snipers profitable?
The README shows no trade results or PnL figures, so the documentation does not support a claim about profitability.
Which Solana trading bot is the best?
The README does not rank this bot against others. It lists the transports each implementation uses, Jito shred stream for the Rust sniper and gRPC or Helius websocket for the Node.js bots, and leaves the comparison to the reader.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/mortdeus-solana-copy-sniper-mev-trading-bot)Star history chart for your README
[](https://hysenlabs.com/projects/mortdeus-solana-copy-sniper-mev-trading-bot)Was this useful?