Volvo built a cryptocurrency. The press release sounds like innovation. The reality is a sandbox experiment with no public code, no economic model, and no exit to the open market. I’ve audited enough enterprise blockchain pilots to recognize the pattern: a permissioned ledger, a toy token, and a PR cycle designed to signal tech-forward thinking. Code is law, but audit is mercy—and here, there is no code to audit.
Context
Volvo, the Swedish automotive manufacturer, announced a proprietary cryptocurrency for supply chain testing with its suppliers. The news broke via Crypto Briefing, a handful of lines with zero technical detail. The project appears to be a private, permissioned blockchain test—likely built on Hyperledger Besu or R3 Corda, the standard enterprise frameworks. No white paper, no GitHub repository, no consensus mechanism disclosed. The token is described as “proprietary,” meaning it exists solely within Volvo’s controlled environment.
This is not new. In 2017, I saw similar announcements from JPMorgan (JPM Coin), Walmart (Hyperledger food traceability), and Maersk (TradeLens). Most never scaled. TradeLens shut down in 2022 after years of low adoption. The reason: enterprise blockchains that treat tokens as internal tokens, not as composable assets, fail to capture network effects. Volvo’s move fits this script perfectly.
Core
Let’s disassemble the technical claim. A proprietary cryptocurrency for supply chain testing implies a native token on a distributed ledger. But what kind of ledger? Permissioned, almost certainly. Volvo controls the validator nodes. Suppliers connect via API. The token is not mined; it is minted by Volvo and issued to simulate payments or inventory transfers. There is no proof-of-work, no proof-of-stake, no on-chain governance. It is a database with a crypto wrapper.
I’ve worked on similar architectures. In 2020, I audited a supply chain token for a major European automaker. The project had a custom ERC-20-like token on a Hyperledger Fabric channel. The “cryptocurrency” was functionally a prepaid card: Volvo would issue 1,000 tokens to Supplier A, who would send 500 tokens to Supplier B upon delivery. The entire system ran on three nodes, all controlled by the parent company. No independent verification. No smart contract audit because the code was considered a business tool, not a financial instrument.
Here’s the critical insight: the word “cryptocurrency” implies decentralization, open access, and censorship resistance. Volvo’s token has none of that. It is a permissioned digital asset. Composability is leverage until it is liability—and this token cannot compose with anything outside Volvo’s private network. It can’t be swapped on Uniswap, can’t be used as collateral on Aave, can’t be bridged to Ethereum. It is a siloed tool, isolated from the entire DeFi ecosystem.
The economic design is equally hollow. No supply cap, no emission schedule, no value accrual mechanism. The token is likely fungible within the test environment, but what gives it value? The answer: Volvo’s promise to accept it in settlement of invoices. That’s a corporate IOU, not a cryptocurrency. Logic dictates value, perception dictates volume—here, perception is manufactured by a single entity. If Volvo stops accepting the token, it becomes a dead entry in a database.
From a risk perspective, the project has no systemic threat. It’s not audited publicly, but for a permissioned test, that’s standard. The real danger is overhyping: media might interpret this as “Volvo embraces blockchain,” driving retail investors to buy unrelated tokens. But the rational take is clear: this test adds nothing to the crypto markets.
Contrarian
Now the counter-intuitive angle. Maybe Volvo’s approach is exactly what enterprise blockchain needs. They are not trying to build a public chain. They are using a private token to solve a specific internal problem: supplier invoice reconciliation, data transparency, or automated payments. The choice to call it a “cryptocurrency” might be marketing, but the underlying technology—immutable records, automated execution—has real value for supply chains.
The blind spot? Volvo is ignoring the power of public composability. By keeping the token private, they forfeit the ability to connect with the wider crypto ecosystem. Their suppliers might already use public blockchains for other purposes (e.g., tokenized trade finance). A private token forces them to maintain a separate infrastructure. The cost of integration often kills enterprise blockchain projects. I’ve seen it firsthand: in 2021, I evaluated a similar pilot for a logistics firm. The ledger worked perfectly in isolation, but when they tried to link it to DeFi liquidity pools for instant settlement, the permissioned architecture broke. The architects had to rebuild from scratch.
The lesson: blind faith in permissioned chains is the only true vulnerability. Volvo should instead consider a hybrid model: use a public Layer-2 for settlement and a private channel for sensitive data. That would give them both control and composability. But their current design lacks this vision.
Takeaway
Volvo’s test will likely stay in testing. No public launch, no token sale, no market impact. The real question is not whether the token works, but whether the architecture can escape its own silo. The contract executes, the architect pays. If Volvo’s architects don’t plan for interoperability, they will pay in missed opportunities.
I’ll be watching for one signal: a public testnet or an open-source codebase. Without that, this is just another blockchain press release in a decade of them. Trust no one, verify everything, build twice.
