Proof Provision – How to trust the source without knowing the source.
The full article was originally published by Geo Data Block on Medium. Read the full article here.
Hi folks, we are back again!
In GeoDB we continue working hard in order to allow users to benefit from our services as soon as possible. Within the last days we have released new versions of GeoCash for both Android and iOS devices, so we encourage you to help us to test the app by downloading it and start sharing your data in exchange for GEOs*.
However, with this post we are going to present something different, that is, the proof provision protocol based on IOTA that we use to add trust to data.
In GeoDB we aim at allowing users to commercialize their data. This process needs mechanisms that give credibility to the data provided, so it is necessary to guarantee some data properties as a way of data validation. For example, it is important to know when data was created and when it was provided.
Considering this constraint, we have defined a protocol based on DLT to publish data validation information. In particular, we use the IOTA ledger because this DLT allows us to give transparency to the validation process as it is immutable and public. Regarding the verification mechanisms we use sha256 .
“Ok this is fine, but if all information is meant to be released to the public, what happens with the privacy of the user that provides the data? Anyone with access to IOTA could check who received rewards for which proofs, and make inferences of which data belongs to the same user”.
(GeoDB enthusiast, 2020)
We are aware of that issue and that’s why we use mechanisms, such as asymmetric cryptography, to reduce the risk of user privacy breach.
Keeping in mind all previous considerations, we define a proof provision protocol that gathers all these requirements.
Proof Provision Protocol
The two main elements of the provision protocol are: the proof provision channels, and the provision strategies. These two elements as well as the workflow of the protocol are described below.