I turn any ideainto ↓production systems.

While most people were simply buying Bitcoin in 2017, I needed to know how it worked under the hood. So, I did what I always do: I started building.

I co-founded ParsiChain, an umbrella organization for our early ventures: ParsiCoin (a CryptoNote privacy coin), ParsMining (hardware and hosting), ParsXC (P2P exchange), and ParsPool (mining pool). To ensure my theoretical knowledge matched my code, I simultaneously enrolled in a blockchain development course at Sharif University of Technology. Solidity, consensus mechanisms, cryptographic primitives. This was my true entry into Web3. Not as a trader, but as an engineer.

Soon, I fell down the mining rabbit hole. I co-founded ParsMining (holding the majority stake) and scaled it into a ~$10K/month operation, selling over 400K miner hosting slots. I designed the entire stack: from custom cooling enclosures for maximum hash performance and datacenter architecture, down to the backend infrastructure, e-commerce, and inventory systems.

That deep hardware obsession eventually led me to run the technical due diligence for a $100M acquisition of 40,000 Antminer S19 Pros.

But the real test wasn't scaling; it was survival.

When Iran's internet went completely dark for months, isolating us from the global network, letting the ASICs sit idle wasn't an option. We spun up ParsPool on top of YIMP, customized the Stratum protocol for forwarding and aggregation with NiceHash, and engineered a network bridge to bypass domestic restrictions.

Here is the cyberpunk reality of that era: running rigs on subsidized electricity during a state-level blackout wasn't exactly low-profile. Most miners genuinely thought we were a government honeypot. Only our closest friends trusted us enough to share their IPs and point their hashrate our way. Yet, in a zero-trust environment during a national network partition, we successfully mined a BCH block and hundreds of DOGE/DGB blocks, completely offline from the global grid.

After years of building the shovels, I wanted to dig. I became obsessed with algorithmic trading, tearing apart and optimizing 400+ strategies across Pine Script, MQL4, and MQL5. Figuring out what works and why became an addiction.

But existing tools frustrated me. They were slow, repainting was everywhere, and nobody could offer true tick-level accuracy. So, I built my own engine from scratch: EPP.

EPP is a real-time, event-driven tick processor written entirely in Go, engineered to eliminate repainting at the root. It chews through 210,000 ticks per second across Binance, OKX, Bybit perps, and any CCXT-supported exchange. I designed a custom DSL so strategies could be written declaratively and executed at native Go speed, then integrated it with TradingView to serve as a high-performance trading terminal.

Its core architecture is based on composable algorithms. You build atomic components (a trailing stop, an ATR filter, a regime detector) and snap them together like Lego bricks to form a complete strategy. You can inspect every metric tick-by-tick, run profiling analysis, feed data to LLMs for pattern recognition, and generate Wyckoff diagrams to identify optimal setups. The pipeline is strict: backtest, demo, paper trade, live. The whole system revolves around one uncompromising principle: don't lose money.

Building didn't stop there. Along the way, I wrote smart contracts (DeFi dApps, ERC-20s, staking interfaces), built MCP servers, engineered AI memory systems, and automated 50+ workflows, leaving a trail of dozens of repositories on my Git servers, each representing a rabbit hole I had to explore.

Today, I operate as a one-man SRE department. I maintain dozens of live services on my own infrastructure: trading bots, data pipelines, monitoring dashboards, Telegram bots, n8n workflows, AI agents, custom DNS/mail servers, reverse proxies, and multiple web apps. Everything is Dockerized and deployed across Hetzner, Cloudflare, and AWS, with CI/CD pipelines running on a self-hosted Gitea instance. No DevOps team. No SRE department. Just one engineer who treats uptime as a personal obligation.

From compiling a single privacy coin to writing a Go-based high-frequency trading engine, every project I build serves as the foundation for the next.

I'm a builder who thrives when I own the entire stack, from the first line of code to production deployment. I'm looking for a remote, async, crypto-native team working on trading systems, DeFi, or developer tooling. If you move fast and care about what's actually under the hood, let's talk.