WayPoint OpenFleet& Escrow System

Inspiration

The inspiration for Waypoint came from a singular observation: In Ethiopia, the distance between two points isn't measured in kilometers, but in levels of risk. Truck owners fear they won't be paid after a long haul, and merchants fear their high-value cargo will vanish into the "black hole" of unmonitored transit. I realized that "tracking" was only half the battle. To truly solve the problem, we had to link the physical movement of goods to the digital movement of money.

What it does

Waypoint is a "Trust-as-a-Service" platform for the Ethiopian logistics industry. It bridges the gap between physical transportation and financial security by combining two core modules into a single ecosystem. The system acts as a neutral third party to eliminate payment risk.

1.Fund Locking: When a shipment is booked, the payment is held in a secure escrow account.

2.Fayda Integration: It uses Ethiopia’s Fayda National ID for biometric KYC (Know Your Customer). This ensures that every driver and shipper is a verified legal entity.

3.Milestone Releases: Funds are automatically released based on verified delivery triggers, ensuring drivers get paid, and shippers get their goods.

How we built it

Building Waypoint required more than just standard app development; it required creating a secure "handshake" between identity, location, and finance.

1.Mobile (The Driver’s Cockpit): Built with React Native. We used the react-native-background-geolocation library to ensure consistent tracking even when the app is in the background or the phone is locked essential for the geofenced escrow triggers.

2.Backend (The Brain): A hybrid of Node.js (Express) for the real-time API and Python (FastAPI) for the route optimization and LLM processing.

3.Database: PostgreSQL with the PostGIS extension. This was non-negotiable for handling complex spatial queries like, "Is this truck within 500 meters of the warehouse gate?"

Challenges we ran into

Building a cross-domain platform like Waypoint in the Ethiopian context meant we didn't just fight bugs; we fought infrastructure and deep-rooted behavioral habits.

If a driver reaches a milestone in a dead zone, the app couldn't ping the server. A "live-only" app would leave the driver stranded without fuel money because the escrow couldn't "see" them.

Accomplishments that we're proud of

In a country where 4G coverage can be spotty, building a "cloud-only" app is a failure. We are proud of our Offline-First Synchronization engine.

Drivers can "check-in" at remote warehouses with zero signal. Our system caches encrypted, time-stamped telemetry that proves their location retroactively, ensuring no delivery goes unrecorded.

What we learned

We learned that code cannot fix a lack of trust; it can only provide a framework for it. Initially, we thought the best feature was "real-time tracking." We quickly realized that drivers don't want to be tracked they want to be guaranteed. By shifting the narrative from "monitoring movements" to "securing payments," we learned that the success of a B2B platform depends entirely on how it aligns with the user's primary anxiety (for drivers, that’s getting paid; for shippers, that’s cargo safety).

What's next for WayPoint OpenFleet& Escrow System

Integrating Zero-Knowledge Proof (ZKP) infrastructure into Waypoint is the ultimate "power move" for privacy and security. It shifts the system from "Trust me, I have your data" to "Don't trust me, verify the math." Since you've already been exploring the Circom + snarkjs stack, here is how we can architect ZKP specifically for the Waypoint ecosystem.

Built With

• chapaapi
• docker
• fastapi
• faydaid
• leaflet.js
• next.js
• postgis
• postgresql
• redis
• sqlite