This means that it's only a good idea if either a) you can limit the participants, and you somehow trust the participants with the most computing power than (e.g.) a simple majority of authorized participants, or b) you do not limit the participants, and you trust anyone in the world with the most computing power more than you trust anyone you would pick for some other reason.
For some applications - e.g. money for people who don't trust their governments or aren't well-served by the inter-government norms around currency exchange - they're legitimately in situation B. Sending and receiving bits to literally anyone is better than not being able to send and receive currency at all, and since a 51% attack will be noticed, it's unlikely to be used on any individual small-time user.
For provenance tracking between a set of companies identified in advance, I have difficulty understanding how you can be in situation B, and you're not in situation A.
If you instead want a cryptographically-verified immutable append-only log, there are lots of non-blockchain structures for immutable append-only logs that permit only a finite set of writers. Certificate Transparency is one of them: issued certificates cannot leave the log, and there are mechanisms for pre-logging certificates before issuance, but the only things worth logging are certificates from trusted (or partly-trusted) certificate authorities. Anyone can participate in the trust process, but transactions themselves only come from a limited set of participants, so you get to completely bypass proof-of-having-more-computers-than-everyone-else.
Yes. I actually like the concept of Bitcoin, but it's very annoying how so many of its fans seem to think Satoshi Nakamoto invented Merkle trees.
But the best example is that nonsense of "permissioned blockchains".
If you have an application where forging or forking the tree isn't meaningful (e.g., any possible Certificate Transparency Merkle tree can be merged at any point into any other one), then the thing that Satoshi invented is not useful to you, and having it cost $2 billion to build such a Merkle tree is a waste.
There are many companies that interact with API services from other companies.
> * you want participation to be permissionless
Is this something CTO's are requesting?
> * It is also desirable if you think they could be hacked, or have downtime--ie, to remove the company as a single point of failure.
The blockchain can be hacked as well.
> * you want it outlive the life of the particular corporations involved.
The corporations are the ones who would be driving this.
It is if:
* you want if you want more than one company to cooperate
* you want participation to be permissionless
* you want it outlive the life of the particular corporations involved.
* you want join ownership
* It is also desirable if you think they could be hacked, or have downtime--ie, to remove the company as a single point of failure.