TRUEHelp
Contact support Sign in

What is saved on the blockchain and how can I control the authenticity?

Updated 2026-10-15

At TRUE, we build trust through our partners, and documents are displayed on their subdomains.
The metadata of each document is stored on the blockchain and there is nothing we "need" to prove to users - even if we can.

If a customer would really like to show how the storage works etc, we can add a link next to the "download"-button next to each document, but this is something we need to charge extra for - it would mean significantly more questions and support for us.


We build a brand and a technology that stands for truth and authenticity - without showing every transaction, only a very technically minded person would want to see this. I hope this clarifies and explains our strategic decision (that may change in the future) - today that is how we look at this. To see n example where we show the entire transaction, you can follow this link below, where we made a pilot with the Swedish Bolagsverket;

https://bolagsverket.truecrt.com/en/registreringsbevis-matstallet-ab--bpby/


When a verification is made by pressing the button, or by scanning the QR code (with a standard smartphone camera), the metadata is checked on the digital original document and if the data has been changed in any way - the hash will not match the stored hash in the blockchain and we then show this as an error / false. If everything matches the digital original, we let you know that the document is "TRUE Verified". To check a pdf or a printed paper, you must therefore compare the digital original with the paper or pdf and make sure that they are identical, in this way you can know that the paper / pdf is also correct and unmanipulated.

Feel free to test this yourself on a document that is live. Here is an example of a Diploma for DI Gasellen;

https://certifiedad.gasell.di.se/en/di-gasell-netconsult-sweden-ab-2021/

Β 

Want to dig deeper?

Articles on the topic from the TRUE blog.

Still need help?

Our support team answers questions this article does not.

Contact support