Thanks Manoj for these structural questions. I believe in 100% honesty and real world logic not some surface level web3 integration that will fail on the ground. We have provided our detailed response on the 4 points based entirely on the reality of Somaliland:
1. Onboarding, UX & Hybrid Approach (Reply For Point 1)
In Somaliland, local merchants, traders and passengers depend entirely on seamless mobile money systems such as ZAAD and e-Dahab. It’s the lifeblood of our local economies. If we require a first-time Web3 user to open Metamask or Coinbase Wallet, secure seed phrases, and complex transactions for just transporting their cargo, or just taking a ride, massive friction will be created. They will view Web3 as a burden that hurts their daily survival, not helping it.
Our strategy is to bring in Web3 by value first and tech later. We build trust by providing them with a great, reliable transport service and they pay through their familiar ZAAD/e-Dahab systems.
As they experience the efficiency over time, we’ll organically educate them on how Optimism powers the background and naturally spark their curiosity to adopt Web3. We need to give them time and build some real interest and not force instant friction.
2. Smartphone and Internet Penetration (Response to 2)
Yes, internet connectivity and smartphone penetration are very strong along the Borama-Hargeisa transit route. The local community has high-speed mobile internet, which is more than enough to interact with our platform. The digital infrastructure is already fully deployed on the ground, the only thing holding it back is the crypto-UX, which our hybrid approach elegantly solves.
3. Receiving Technical Guidance & Ecosystem Alignment (Re: Point 3)
Oh yes, absolutely. I am looking for structural feedback, technical guidance and ecosystem partners before we go for any financial grants or funding pathways. My goal is not to get a donation but become a long term, active block member of the Optimism Collective.
My number one thing is getting the technical architecture right, with the help of the community.
4. Onchain Data, Operations and Pilot Scope (Response to Point 4)
The end-user front-end payments will remain on mobile money for now but the whole operational backbone of our project will be running on Optimism:
* Logistics & GPRS Tracking: Vehicle transit distances, route logs and GPRS tracking metrics will be securely anchored on-chain.
* Financial Transparency: The OP Stack will be used for storing all operational data, including the company’s internal revenue ledger, cargo logs and capital tracking to ensure full transparency.
Our Proposed Pilot Milestone Plan:
Our main operational vehicle as become broken for good and is at the end of its mechanical life, to be perfectly honest. Additionally, we cannot use or engage other active vehicles on the local network for this pilot. If I tried to take or use the vehicles of other drivers to test my Optimism project, they would see this as a direct disruption to their daily livelihood because they use these vehicles to provide sustenance and food for their children and families. Also the passengers are always in a rush due to their busy jobs and they will see it as a major disturbance if we force an unfamiliar Web3 onboarding on them during their commute.
Therefore, the most practical and effective solution is to secure ecosystem grant funding to purchase our first independent, dedicated vehicle (1 manual gear box asset) to launch a controlled 3-month prototype on Borama-Hargeisa Corridor.
Once we have a first asset secured through a structured milestone grant we will have 100% operational control to run the pilot independently, capture all live transit data and bridge the passenger metrics directly onto the Optimism backend. That will deliver the real on-chain usage metrics and active addresses the Collective expects to see before scaling the fleet.
We are all ready and open on any technical ideas, developer support or community volunteers to help us bridge local mobile money infrastructure with the Superchain!