Blockchain should not be forced simply because it is today’s fashion, but only if it is a better, or at least equivalent (but forward-thinking), solution to a requirement. Proposed blockchain applications such as tolling reciprocity must be scrutinized; first to ensure that a blockchain solution is viable and second to assess the cost and benefit of such an endeavor. In addition, this should be done while keeping in mind that there are alternatives, such as a centralized database with a vetted web application programming interface (e.g., API).
Any convincing proposal to use blockchain for regional or national toll interoperability must go a little deeper than merely trust, immutable, and distributed. What are the nodes, assets, public data, private data, and smart contract examples for handling contingencies and infrequent business rules?
It is one thing (and more fun) to create a system such as Bitcoin from scratch and quite another to coerce a blockchain solution into a system with established business rules and procedures. Ultimately, blockchain represents the culmination of some brilliant concepts but should be utilized and optimized according to the application.