If you run a trading desk, a signal group or a startup and you need a Solana bot that gets its transactions landed early, I build it. I'm Oussama Allamou, known as 0xMowgli. I design and ship sniper engines, copy-trade engines and the backend around them: market data over gRPC from dedicated nodes, hot state in Redis, and a Jito fee strategy set per trade. What you get is a system running in production, with the measurements to show how it performs.
/ 01 · Scope
Detect a new pool or launch from the stream, decide in memory, send the buy. Filters, sizing, fees, tips and retries are configurable.
Track target wallets in real time and mirror their trades with your own sizing, filters and exits.
Positions, entries and PnL computed from the same stream that drives execution, so the numbers match what happened on chain.
Transaction building, priority fees, Jito bundles and tips, more than one send path, and confirmation tracking.
Dedicated nodes, Geyser gRPC and shred streams, with Prometheus and Grafana watching all of it.
/ 02 · Process
You tell me the strategy, the venues and what counts as fast enough. I tell you what is realistic and what it needs.
I get the stream right before writing strategy code. A bot is only as early as its data.
Landing transactions reliably comes next. Strategy logic sits on top and stays easy to change.
Small size, real conditions. I track where each transaction lands relative to the event and tune from that.
You get the code, the deployment and the dashboards. I keep operating it, or your team does.
/ 03 · Proof
Low-latency Solana trading engine
My own engine, built alone: architecture, backend and infrastructure. It is live, so you can judge it yourself.
Multi-chain Telegram trading bot for Chainge Finance
Sniping and Jupiter-routed swaps on Solana inside a multi-chain Telegram bot, where I led the backend.
I also build private Solana sniper engines and copy-trade engines for clients. They make money for the people who own them, so I describe them only in general terms here. Details are shared on a call.
/ 04 · FAQ
It depends on what surrounds the bot. A single-strategy engine for one venue, running on infrastructure you already have, is a matter of weeks. A product with user wallets, fees, an interface and its own nodes is a matter of months. The buy transaction is the small part. Most of the time goes into the data path, landing transactions under load, and the cases where something fails halfway.
For anything that competes on timing, yes, or at least dedicated access. Shared public RPC endpoints are rate-limited, and you see events later than competitors streaming from their own hardware. For a copy-trade bot with relaxed timing, a paid gRPC provider can be enough to start. I can tell you which case you are in once I see the strategy.
No, and be careful with anyone who does. Speed depends on your hardware, where it sits relative to the current leader, your fee strategy, and what competitors do in the same slot. I make the system as fast as its infrastructure allows and show you the measurements. Profit depends on the strategy, and the strategy is yours.
Jito runs a block engine that accepts bundles: groups of transactions that land together and in order, or not at all, with a tip paid for inclusion. For sniping and anything where ordering matters, it is usually part of the send path. I set the tip strategy per trade, because overpaying on every transaction eats the edge.
TypeScript on Node.js and NestJS, gRPC for market data, Redis for hot state, PostgreSQL for records, Docker on Linux, and bare metal where latency matters.
/ Related
/ Contact
Tell me the strategy and what you run today. I'll tell you what it takes to make it fast.