[amluto]

Because mining, staking, and various consensus protocols along those lines are useless for these applications?

Or maybe worse. A blockchain is a distributed system and is subject to the CAP theorem. And they handle it pretty badly: they are global and they are utterly intolerant of network partitions. They handle consistency by throwing out conflicting transactions, which is probably not what you want for something like supply chain visibility.

Just use a database.

[mradek]

> just use a database

Totally. But I’m thinking of protocols that give people insight into what’s happening and a way for them to join that protocol and start working.

Like imagine activity pub (mastodon protocol) or xmpp - both are protocols to enable real time comms.

If there were protocols to run your business that you could be a part of, and attempt to fix the issues of loads getting cancelled last minute due to dispatching errors, etc. stakeholders would know where the fault lies and payments could be adjusted based on where things went well or wrong.

[amluto]

Can you imagine trying to chat using an XMPP-like protocol on a blockchain? It won’t work hilariously poorly.

In any event, sticking real world logic on a blockchain is no more open than sticking code on GitHub. You still can’t interact with someone else’s deployment unless they let you.