You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This came from a question at BioDigiCon '23, and is heavily paraphrased below!
We provide a guarantee that the data in a download will be the same when it accessed later but that is purely based on trust in us. Could we provide a hash as well to show that the data is as it was? This would also allow external validation as the user could hash the data too.
The text was updated successfully, but these errors were encountered:
Not sure how we would do this exactly but it's worth having a think about. The main issue is what do we hash? Particularly given we provide different formats for download. We could hash the raw data object that each record in the query response has, but then how does the user successfully hash this?
This came from a question at BioDigiCon '23, and is heavily paraphrased below!
We provide a guarantee that the data in a download will be the same when it accessed later but that is purely based on trust in us. Could we provide a hash as well to show that the data is as it was? This would also allow external validation as the user could hash the data too.
The text was updated successfully, but these errors were encountered: