We didn’t see the data-sharing terms. Uber’s first European autonomous ride in Zagreb hides a key question: who owns the road data?
When Uber announced its autonomous vehicle service in Zagreb, Croatia, the crypto community reacted with a mix of curiosity and skepticism. The news, reported by Crypto Briefing, was light on technical details—no mention of the vehicle model, sensor configuration, or safety driver. But as an open-source evangelist who has spent years auditing blockchain projects, I saw a familiar pattern: a centralized platform extending its control into a new domain, with little transparency about the data flows and governance structures underneath.
This is not just a story about Uber’s expansion. It’s a story about the critical need for blockchain-based data provenance and decentralized governance in the emerging autonomous mobility ecosystem. If we don’t act now, we risk repeating the same mistakes that have plagued centralized social media and ride-hailing platforms: data monopolies, opaque algorithms, and a concentration of power that undermines user sovereignty.
Context: The Centralized Platform Model
Uber’s autonomous driving strategy has evolved significantly since its 2020 sale of the Advanced Technologies Group (ATG) to Aurora. Today, Uber operates as a platform that aggregates third-party autonomous vehicle technology, rather than developing its own. This is a smart business move—it avoids the massive capital expenditure required for R&D and allows Uber to quickly enter new markets by partnering with local tech providers. In Zagreb, the likely partner is a European startup like Wayve or Oxa, but the exact identity remains undisclosed.
From a blockchain perspective, this model is deeply concerning. Uber controls the user interface, payment processing, and data pipeline. The third-party provider handles the autonomous driving stack, but the data generated—every mile driven, every sensor reading, every passenger interaction—flows through Uber’s servers. This creates a single point of failure, both for privacy and for competition. Without a transparent ledger, users cannot verify how their data is used, and regulators cannot audit the system effectively.
My experience in the 2017 ICO ethics audit taught me that when a project insiders have privileged access to data and decision-making, the system is vulnerable to exploitation. The same principle applies here. Uber’s autonomous platform is a black box, and the passengers are the product.
Core: The Blockchain Solution for Autonomous Mobility
Based on my audit experience, I propose a decentralized alternative: a blockchain-based data provenance layer for autonomous vehicle operations. This would work as follows:
- Data Ownership: Each autonomous vehicle generates a unique digital identity (DID) on a public blockchain. Every sensor reading, trajectory decision, and passenger interaction is hashed and recorded on-chain, creating an immutable audit trail. The user retains ownership of their ride data, with granular consent controls enforced by smart contracts.
- Fleet Coordination: Instead of a centralized server dictating vehicle dispatch, a decentralized autonomous organization (DAO) of vehicle owners and passengers can govern fleet allocation using transparent, verifiable algorithms. This eliminates the need for a platform like Uber to act as a middleman, reducing costs and increasing trust.
- Payments and Insurance: Smart contracts can automate ride payments, with funds released only when the ride is completed and verified by oracles. Insurance claims can be triggered automatically based on on-chain evidence, reducing fraud and administrative overhead.
I saw the power of this model during the 2020 DeFi community bridge, where I organized workshops to demystify Compound and Uniswap mechanics. The same principles apply: transparency, composability, and user sovereignty. Just as DeFi disintermediated traditional finance, decentralized autonomous mobility can disintermediate ride-hailing platforms.
But the technical challenges are significant. Autonomous vehicles generate terabytes of data per hour, and storing all of it on-chain is impractical. The solution is to use off-chain storage (like IPFS or Filecoin) with on-chain hash attestations. Zero-knowledge proofs can verify that a vehicle’s decisions were compliant with safety rules without revealing the underlying sensor data. This is where the AI + crypto convergence becomes critical: we need AI models that can generate succinct proofs of safe driving behavior.
Contrarian: The Case for Centralized Efficiency
Skeptics will argue that blockchain adds unnecessary complexity to an already challenging engineering problem. Uber’s centralized platform is efficient, scalable, and proven. Why fix what isn’t broken?
During the 2022 bear market support network, I saw how centralized systems can fail when markets crash. Uber’s platform is no different: a single regulatory decision or security breach can bring the entire service to a halt. Blockchain offers resilience through redundancy and decentralization. But it comes at a cost: slower transaction throughput, higher energy consumption, and a steeper learning curve for users.
Moreover, autonomous driving is a safety-critical application. Latency matters. A blockchain with a 12-second block time is not suitable for real-time vehicle control. However, we are not proposing to run the vehicle’s control loop on-chain. The blockchain is used for governance, data provenance, and settlement—not for the instantaneous decision-making that happens in the vehicle’s edge computing unit.
Another counter-argument: Uber’s platform model actually encourages competition among technology providers, which could lead to better outcomes for users. A decentralized system might fragment the market, making it harder to achieve network effects. But fragmentation is a feature, not a bug. It allows multiple communities to experiment with different governance models and safety standards, fostering innovation.
Takeaway: The Road Ahead
Uber’s Zagreb launch is a small step for autonomous mobility, but a giant leap for centralized data control. As an open-source evangelist, I see this as a call to action. We need to build the infrastructure for decentralized autonomous mobility before the centralized platforms become too entrenched.
Imagine a future where you can summon an autonomous vehicle that belongs to a DAO, where your ride data is encrypted and stored on your own device, and where the algorithm that dispatches the vehicle is open-source and auditable. This is not a utopian dream—it’s a technical possibility that we can achieve with the right combination of blockchain, AI, and community governance.
The question is not whether Uber will succeed in Zagreb. The question is whether we will let them own the roads of the future.