Technical architecture for the future.
A deep dive into the technology powering Verda's supply chain transparency protocol. Built for scale, security, and real-world constraints.
Technical Deep Dives
System Layers
Consumer Interface Layer
QR scanning app, web portal, embeddable brand widgets
Supply Chain Actor Layer
Farmer mobile app, factory portal, distributor interface, retailer POS
IoT & Sensor Layer
Temperature loggers, GPS trackers, humidity sensors, NFC/RFID readers
Business Logic Layer
Product registry, journey composer, certification engine, anomaly detector
Data & Storage Layer
Relational data, time-series IoT readings, documents, event streaming
Blockchain Verification Layer
On-chain anchoring, Merkle proofs, verification contracts
Why We Chose Each Technology
Blockchain
400ms finality, <$0.001 per transaction. We anchor millions of events daily — Cost-efficient blockchain transaction fees.
Go + Rust
Go for business logic: fast compilation, excellent concurrency. Rust for cryptographic operations and the blockchain program.
TimescaleDB
Billions of IoT time-series readings. Native compression (10x storage reduction), and it's just PostgreSQL underneath.
Kafka
Real-time event streaming with at-least-once delivery. During harvest season, we see 100x traffic spikes. Kafka absorbs the burst.
React Native
Consumer app (Android-first, offline SQLite sync for rural areas). Works on $50 smartphones in low-bandwidth regions.
SvelteKit
Admin dashboards — smallest bundle size, critical for low-bandwidth regions. Fast and reactive UI.
Trust Architecture
- Device-level signing: Every IoT sensor has a unique key pair. Data signed at the edge before transmission.
- Merkle proofs: Batch anchoring to blockchain every 60 seconds. Verify individual records without downloading chain state.
- Multi-party verification: Handoff events require signatures from both sender and receiver.
- Tamper detection: Physical tamper-evident seals on sensors. Device health monitoring detects interference.
- Zero-knowledge proofs: Coming in Phase 3 — verify claims without revealing supplier identities.
Developer Interface
RESTful API with webhook support. GraphQL coming in Phase 2.
// Get product journey
GET /api/v1/products/:qr_code/journey
{
"product_id": "PRD-2024-001234",
"name": "Single Origin Coffee - Flores",
"journey": [
{
"event": "harvest",
"timestamp": "2024-03-15T06:30:00Z",
"location": { "lat": -8.5, "lng": 121.1 },
"actor": "Farmer: Made Wirata",
"verified": true
}
],
"certifications": ["organic", "fair-trade"],
"cold_chain_status": "maintained",
"merkle_proof": "0x7f3a..."
}Building in the Open
Core protocol will be open-sourced in Phase 3. We believe food traceability should be a public good, not a walled garden. Interoperability is a feature.