Uber quietly switched on autonomous rides in Zagreb this week. The announcement was sparse—no technical partner named, no vehicle specifications, no safety driver disclosure. Just a press release dressed in optimism. But the silence around the data layer is deafening. In an industry built on trustless coordination, Uber is still relying on the oldest form of trust: corporate goodwill. That is a covenant written in sand, not in code.
I have been tracking the intersection of decentralized systems and mobility since 2014, when I spent six months dissecting Satoshi's whitepaper alongside the Gitcoin Code of Conduct. Back then, I realized that traditional economic models failed to account for trustless coordination. Today, that gap is even more dangerous. Autonomous vehicles generate terabytes of decision data per hour—every braking event, every lane change, every sensor reading. Who holds that data? Who verifies it? Who is accountable when the algorithm fails?
In Zagreb, the answer is likely a private server farm owned by Uber's unnamed third-party provider—probably Wayve, given Uber's 2024 investment in the British startup. But whether it is Wayve, Motional, or Aurora, the architecture is the same: opaque, centralized, and vulnerable to single-point failure. The 2018 Uber fatality in Arizona taught us that a single data point, hidden or manipulated, can cost lives and set the industry back years. The community demanded transparency, but the industry responded with press releases.
The core of the problem is not technical—it is institutional. We have the cryptographic tools to build an immutable, auditable record of every autonomous decision. We have zero-knowledge proofs that can verify sensor data without revealing sensitive locations. We have decentralized storage networks like Arweave that can archive logs for centuries. Yet the industry refuses to adopt them. Why? Because the current players—Uber, Waymo, Cruise—see data as a competitive moat, not a public good. They want to control the narrative, not share it.
But a ledger is not a luxury; it is a necessity. Consider the following use cases, each grounded in my own audit experience:
1. Vehicle Identity and Safety Certification — Every autonomous vehicle should carry a soulbound token that records its safety certifications, software versions, and fleet history. This token, anchored on a public blockchain, cannot be revoked or altered by a single corporation. It is a permanent record of the vehicle's provenance. In Zagreb, Uber's vehicles—likely retrofitted with sensors from a third party—should have such tokens. Without them, a passenger has no way to verify that the vehicle has passed the latest crash test or that its software is not running a vulnerable fork.
2. Immutable Event Logs — Every autonomous ride generates a sequence of events: traffic light changes, pedestrian crossings, sudden braking. These events should be hashed and written to a blockchain, creating a tamper-proof chain of custody. If an accident occurs, investigators can query the public ledger, not a private database that might be wiped or modified. During my 2020 audit of Compound Finance's governance, I spent 200 hours mapping voting centralization risks. The same principle applies here: the ability to audit history is the foundation of trust. Uber's current architecture provides no such audit trail.
3. Smart Contract Insurance — Liability is the biggest open question in autonomous mobility. Who pays when a car chooses to hit a pedestrian versus a wall? Traditional insurance is slow, opaque, and expensive. Smart contracts can automate claims based on oracle data from the vehicle's logs. If the ledger shows that the vehicle followed all traffic rules, the manufacturer's insurance pool pays out automatically. If the logs show a software bug, the developer's pool is triggered. This is not science fiction; it is a direct application of the decentralized finance principles I have championed since the ICO disillusionment in 2017. The cost of fraud drops to near zero, and the speed of settlement rises from months to minutes.
4. Decentralized Fleet Governance — Uber's platform model is already a step toward decentralization, but it stops at the API layer. The next step is to allow the community—drivers, passengers, and regulators—to vote on route parameters, pricing models, and safety thresholds using tokenized governance. Imagine a DAO that manages the autonomous fleet in Zagreb, where each ride contributes to a treasury that funds future upgrades. This is not a utopian dream; it is the logical extension of the open-source movement I have dedicated my career to. Open source is a covenant, not just a license. It requires that the community has a voice, not just a seat at the table.
But the contrarian voice must be heard. Blockchain proponents often overhype without considering real-world constraints. Autonomous vehicles require millisecond-level responses; on-chain verification today adds seconds of latency. Storing full sensor data on a public chain would be prohibitively expensive and would violate privacy regulations like GDPR. The counter-argument is valid: we cannot put everything on-chain. The solution is a hybrid architecture. Use blockchain for attestations—hash the data, store the full log off-chain, and only bring disputes to the chain. Use zero-knowledge proofs to prove that a vehicle followed a green light without revealing the exact time or location. This is not a trade-off; it is a design pattern that respects both security and privacy.
Another criticism: the industry is already heavily regulated. Why add another layer of complexity? Because regulation is reactive; code is proactive. The EU's AI Act classifies autonomous driving as a high-risk system, but it relies on companies to self-report compliance. A blockchain-based audit trail transforms self-reporting into self-evidence. Regulators can query the public ledger without needing a warrant. This is the difference between faith in people and faith in math. Faith in people is costly; faith in math is free.
Let me be clear: I am not arguing that Uber should fork its entire operation onto a blockchain tomorrow. That would be naive and reckless. But the Zagreb launch is a perfect opportunity to start small. Anonymize the vehicle IDs, hash the event logs, and publish them on a testnet. Invite researchers to audit the data. Prove that the system is not a black box. This is what I did in 2020 when I published the Compound governance audit on GitHub—500 stars in a week, and the governance improved because the community could see the risks. The same principle applies to autonomous vehicles.
I have seen the cost of missing this step. In 2017, I reviewed 40 ICO whitepapers and identified predatory tokenomics in 30% of them. The projects that ignored transparency failed. The ones that embraced open auditing—like Compound and Uniswap—survived and thrived. Autonomous mobility is no different. The hype will burn out; the robustness will remain in the ledger. Uber's Zagreb launch is a small step, but without a cryptographic foundation, it is a step on quicksand.
The takeaway is not a conclusion, but a vision. Imagine a future where every ride is logged on a public chain, where every accident is resolved by a smart contract, and where every vehicle's identity is a sovereign token. This is not a replacement for good engineering or robust regulation. It is a scaffold that holds the system together when things go wrong. Code is the only law that does not sleep. We need to ensure that its ledger is open, auditable, and immutable. Otherwise, we are building an autonomous future on a foundation of trust in the few. And that is the opposite of decentralization.
I seek the signal amidst the noise of the crowd. The signal in Zagreb is not the rides themselves—it is the absence of a ledger. Let that absence be the catalyst for change. The autonomous revolution will not be centralized; it will be cryptographically certified.
