That would then be an entirely different situation?
MiddleKnight
You are describing a one party state. Kind of optimistic to assume that if you manage to hand all of the power to one organization, with no real opposition, that it won't be corrupted (more than it already is).
Denmark has a Lutheran state church officially recognised by the constitution.
It's mp3 quality through an old tiny battery driven DAC...
I'm pretty sure that using the term "Semite" in any other context than the modern interpretation of "antisemitic", meaining prejudice against Jews, stopped being a thing roughly around the same time that we stopped treating the bible as an authority on the classification of human races. Same with Hamites and Japhetites.
nation…..thing
we prefer the term "sui generis geopolitical entity" ;)
Having a bunch of answers to very poor questions is not the goal.
If you managed to parse out a good question in there of general interest that has not been answered yet, you can submit it yourself and provide your own answer. That way you are actually adding something valuable to the site.
I agree that it is really hard to contribute in a meaningful way though.
You are claiming that
-
a blockchain would somehow make it easier to detect tampering or make stronger guarantees about the log integrity (I think you are being a bit vague here honestly)
-
That a blockchain is easier to set up than my proposed alternative.
Regarding 1: If the other parties just store the log, you just compare what the company provided with what the peers have stored. Then you see EXACTLY what has changed. I still don't understand what it is you claim a blockchain can do here that just having the peers store a copy of the logs cannot and how it is somehow less brittle.
Regarding 2: it can literally be as simple as serving the log from a webserver (with authentication if you only want the peers to be able to read it) and then have the peers scrape it periodically. Or send an email every night. Yes you need to provision infrastructure and integrate with your logging system. But that is the same for hosting a blockchain based system.
You could do the same by broadcasting your events to all your peers and having each peer save everyone's events.
But this is also a prerequisite to running a blockchain right? This is essentially the mempool. Then you have a layer on top which does more stuff (the actual blockchain part)
Surely implementing only the sending of log event is simpler than also adding all the hashing and consensus stuff(which in practice adds no real utility) on top?
So it is not really private to one business, but shared between a couple handfuls. The consensus of this group is then trusted.
In that case, to write a log entry I would have to publish the log into some mempool shared among the group as it is logged. At this point, each member can just store the log entry and then later verify it of asked. Again, it seems like the entire block chain part of this system is redundant and what is really providing utility is the idea of storing your logs with someone else as you create them so you cannot later claim something didn't happen.
But just to understand the idea of private blockchains better. Would this be some kind of hardcore "code is law" arrangement where each Company is competing on hash power with all the others to prevent them from rewriting the logs to their advantage (and in the best case being able to rewrite the log to their advantage).
Or is there some a priori agreement on what a reasonable amount of hash power is, that you just hope one company doesn't choose to outspent by a factor 100 the day they really need to rewrite the log?
I guess in that case it will be clear to everybody what has happened. But if you choose to act on this common sense version of events instead of the "truth of the blockchain consensus" you are, once again, undermining the entire idea of using a block chain.
Only taking cash does not "just work" in denmark, because many people don't walk around with cash anymore.