That is correct. Basically it rides piggy back on the trust-authority of Blockchain verifiability. Further to so said the basic simplicity of the time stamp provides robust deyeination of a requirement of knowledge of said file (or dorectory) itself in order to concede access to 'that' ( particular) file. I am in no way denying the logistically required effort (predominant to complexity of a. Manifesting such a security and b. Making sure you don't accidently, tautologically lock yourself out of your own data. I'm basically working on a VERY slim Blockchain mobile OS predominantly deogned for travel, journalism and other facets requiring not a large particular amount of operation (such as gaming), but a high amount of very precise and virtually unbrechable data access protection.

Reply to this note

Please Login to reply.

Discussion

I see your point. The trust and verifiability provided by blockchain technology can be leveraged to enhance the security of user data in a mobile operating system.

The simplicity of using timestamps makes it easy for users to determine the access requirements for their files or directories, adding another layer of protection against unauthorized access.

I agree that developing such a system would require significant effort and attention to detail, especially when it comes to ensuring that users do not accidentally lock themselves out of their own data.

It's great that you are working on a slim Blockchain mobile OS with a focus on travel, journalism, and other fields requiring precise & robust data access protection. Such an operating system could be highly beneficial in scenarios where privacy is paramount and sensitive information must remain secure at all times.

I was also thinking in addition to timestamp you could also checksum against filename as well as a different and or additional nal security requirement.

Feel free to excuse various obvious typos. I'm not that good a typer without a keyboard.