I build software that has to be correct and stay up.
I'm Yasir, a Rust and Distributed Systems Engineer in Nairobi. Teams bring me in for protocol code, blockchain infrastructure, and backends where a bug or an outage costs real money. I work remotely with teams in any time zone.
Where I can help
- Performance-critical Rust
- Proof systems, protocol logic, and hot paths written once in Rust, then shipped as a crate, a CLI, and a WebAssembly package so your backend and frontend run the same tested code.
- Blockchain infrastructure
- Execution clients, JSON-RPC services, RPC routing and failover, and the tooling developers use to build on your chain.
- Backends that have to stay up
- Event-driven services on Kafka or Redpanda, real-time APIs over WebSockets, and PostgreSQL data models built for production load.
- Products, end to end
- Turning requirements into a shipped product, then running it: architecture, delivery, monitoring, and support.
Recent work
IOTA
I lead notarization, audit trails, and proof of inclusion: Rust infrastructure for building and verifying proofs, plus the libraries, CLI, and WebAssembly APIs developers integrate with.
Tideblock
Designed low-latency Solana RPC infrastructure with request routing and automatic failover.
Bitfinity Network
Built on an Ethereum-compatible execution client and its JSON-RPC layer.
Shipzen and PrismPOS
Products I build and operate through Shariff Consultancy, used every day in logistics and business operations.
How it works
Tell me the problem
Send a short note about what you're building and where you're stuck.
Scope it
I read the code or system, then send back a written plan with what I'd do, what it costs, and what you get.
Build it
Work lands in your repository in small reviewed changes, with regular progress updates.
Hand it over
You get tests, documentation, and a walkthrough, so your team can own it after I leave.
Common questions
- What kind of work do you take on?
- I work on backends, distributed systems, and blockchains, mostly in Rust. That means services that have to stay up under real load, systems that span many machines, and the infrastructure blockchains run on, like nodes and RPC services.
- Who will I be working with?
- Me, directly. There's no agency in between and no handoff to someone else.
- Can you work in our existing codebase?
- Yes. Scoping starts with reading your code or system, and the work lands in your repository as small reviewed changes.
- How does an engagement start?
- Email a few sentences about what you're building, where you need help, and when you'd like to start. I'll read the code or system and send back a written plan with what I'd do, what it costs, and what you get.
- How do you charge?
- Each engagement is priced from the written plan, so you know what it costs before any work starts.
- What do we get when the work is done?
- Tests, documentation, and a walkthrough, so your team can own the work after I leave.
- Can you help after the project ends?
- Yes. I can stay on for production support, fixing issues and making changes as your system grows.
Tell me what you're building
A few sentences is enough: what you're building, where you need help, and when you'd like to start. If it's a good fit, I'll suggest a time to talk. If it isn't, I'll say so and point you to someone who can help.