you can build document versioning into a blockchain-backed protocol - I would assume that Digibuild have done this as documents can be both corrected and extended over time. The important factor being that the old version is not erased and thus you can see the history of the document, which could be beneficial.
By uploading said information you are claiming it is true. Whether other people believe it to be true depends on whether they trust you or otherwise have verified for themselves (which can also be asserted cryptographically).
No digital technology can solve epistemology and tell you what is true - but that's not the point, and blockchain applications are not unique in this.
I think a lot of companies, when talking about blockchain technology, really mean a merkle tree - distributed or not, with proof of stake/work or not. The whole point being to cryptographically prove things like chain of custody, who is asserting what facts etc. The benefit to such tools is transparency, which helps in low-trust environments.
I'm pretty sceptical of blockchain applications in general because it became one of the word examples of a technobabble buzzword, but in this case I can see the argument for it.
Thanks for the help you, you took the words out of my mouth haha......Per the question about a previous entry, a prior entry could always be cancelled out with a new entry.
Remember business is still take place on the front end and the blockchain is a back end ledger to verify the data...In the real world, if you accidentally sent an incorrect contract and that metadata hit the ledger, the user would simply cancel the 1st contract and send a new one, this would append the ledger and one could see that a previous version was cancelled and a new contract sent. There are also ways to to verify version history as was mentioned in that previous comment.
