Every time you convert USDT to Naira on ZWAP in under 30 seconds, you're interacting with systems designed by Dominion Afiakurue. What feels instant to you is the result of thousands of architectural decisions — each one made to ensure that speed, reliability, and security are never in conflict.
What a CTO Actually Does at a Payment Startup
The title "CTO" means different things at different companies. At a large corporation, it might be mostly internal politics and budget approvals. At ZWAP, it means something very specific: Dominion builds the thing.
His role spans five critical areas:
1. System Architecture
ZWAP's technical architecture is Dominion's most important contribution. He designed a system that handles high-volume P2P trading, real-time price feeds, wallet management, and fiat settlement — all running simultaneously without bottlenecks.
The architecture follows a microservices approach where each core function operates independently. The trading engine, wallet service, notification system, and compliance module each run as separate services communicating through lightweight message queues.
This means a spike in trading volume doesn't slow down wallet operations. A compliance check doesn't block a price update. Everything runs in parallel. Dominion chose this architecture not because it's trendy, but because it's resilient. When you're building financial infrastructure for a continent, downtime isn't just inconvenient — it's people unable to pay rent, buy food, or send money home.
2. Security Engineering
In the crypto space, security isn't a feature — it's the entire product. A single breach can destroy years of trust overnight. Dominion treats security as a first-class concern, not an afterthought.
Every API endpoint is authenticated and rate-limited. Every transaction is encrypted end-to-end. Every wallet operation requires multi-layer verification. The system includes real-time fraud detection that monitors for unusual patterns — sudden large transfers, rapid successive conversions, login attempts from new devices — and flags them instantly.
Dominion implemented a "defense in depth" strategy: even if one layer fails, multiple other layers exist to prevent damage. No single point of failure can compromise user funds.
3. API and Developer Infrastructure
ZWAP isn't just a consumer app — it's a platform. Dominion built the API layer that allows third-party developers to integrate ZWAP's payment infrastructure into their own applications. A merchant in Lagos can accept USDT payments through their website using ZWAP's API. A fintech startup in Accra can use ZWAP as their crypto-to-fiat conversion backend.
The API was designed with developer experience in mind: clean documentation, consistent error handling, webhook support for real-time notifications, and SDKs for popular languages. Dominion's philosophy is that if a developer can't integrate ZWAP in under an hour, the API isn't good enough.
4. Performance Optimization
Dominion obsesses over latency. Every millisecond matters when someone is waiting for their money. He implemented caching strategies for frequently accessed data, database query optimization, and CDN distribution for static assets.
The result: ZWAP's core conversion flow completes in under 30 seconds for most transactions, with the backend processing in milliseconds. The remaining time is spent on blockchain confirmations — outside ZWAP's control but minimized through smart network selection.
5. Team Leadership
Dominion doesn't just write code — he builds the team that writes code. He's personally involved in every technical hire, conducting rigorous interviews that test systems thinking, debugging instinct, and the ability to make good decisions under pressure.
He runs weekly architecture reviews where the engineering team discusses ongoing projects, challenges, and trade-offs. These aren't status updates — they're genuine technical discussions where the best idea wins, regardless of who suggests it.
Dominion's Engineering Philosophy
- Build for failure. Every component is designed assuming other components will fail. Can the trading engine still function if the notification service goes down? Can users access their wallets if a database replica lags? The answer must always be yes.
- Measure everything. If you can't measure it, you can't improve it. Every API call, every database query, every background job is tracked, logged, and alertable.
- Simplicity scales. The simplest solution that works is almost always the best one. Dominion reaches for complex tools only when simple ones genuinely can't do the job.
What's Next
Dominion is currently focused on expanding ZWAP's infrastructure to support more African currencies and payment rails, building a real-time settlement system that reduces confirmation times further, and developing internal tooling that makes the engineering team significantly more productive.
His long-term vision: ZWAP's infrastructure becomes the default payment layer for African developers — the same way Stripe became the default for internet businesses globally.
Behind every seamless ZWAP transaction is Dominion's conviction that great infrastructure should be invisible. Users should never think about servers, databases, or APIs. They should just think: "That was easy."
