Topic: ⚡ [ANN] ⚡ DeepOnion TOR ⚡ DeepVault ⚡ Cryptopia 🚀 Airdrop 24/40 🚀 WE DOMINATE! - page 1026. (Read 1167592 times)

This all sounds very cool.SHA 256 is the best hash algorithm for this.I can now imagine many case scenario where DeepVault will be very useful such as for sending a signed contract to someone and before doing that upload a hash of it in blockchain so the receiver can not deny the file being altered and the best part is every deeponion wallet user(running full node) will have the hash of it too so it becomes impossible to cheat anyone by saying that's wrong hash.A very good feature indeed

let say you hold alot of assets in your wallet, you will need to make sure you use correct wallet file (official unaltered ones) (not infected by middle man) it can be done isp,dc, govt, hackers and sort of abusive entitites by offering this service you are all more protected from potential malware and virus versions intended to steal assets, with DeepVault we offer an extra security layer for you...

It is initially for our community but can and will have very vast usage areas in public, we will see them more in time. It can be easy adapted to a web service where people easy use to confirm their documents and files online.

Ok so it's like a digital signature that we do to prove that we own the private key and in deeponion case we can use the same technology for hashes to prove that the person is the owner of the file by using it's deeponion address.I got it now

I think he just means that there is some text in one kind of blue, then some other text in another blue hue, then another text in yet another blue hue. Various fonts and sizes also. It should be quite simple to make things a bit more uniform, he wasn't asking to change what is displayed, just how it is displayed.

It is a difficult balance in providing enough information for non-technical but also keeping it minimalist for more technical users.

If the community believe that it should be changed then we can address that in the future We're always open to suggestions and improvements from our community.

Yes storing the hash in the blockchain prevents the hash from being altered and timestamp it as well.  So that way you can prove that the document was signed at a specific point in time, i believe factom does this as well, but not over TOR thou.

That is awesome! I know MD5 hashes and other alternatives already exist, but even I am usually too lazy to do the checks, so some automated, integrated one-button solution would be perfect.

DeepVault
DeepVault is a blockchain innovation brought to you by the DeepOnion Development team. DeepVault allows users to determine whether or not a file has been changed or corrupted by enabling hash verification of the file.


 
Non-technical users:
A hash is a random string of characters of fixed length (for example: hello = 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824, hello1 = 91e9240f415223982edc345532630710e94a7f52cd5f48f5ee1afc555078f0ab). A hash is unique as no two inputs (files or texts) generate the same hash. For instance, hello and hello1 will have completely different hash values as witnessed in the previous example.

One use for hashing is the ability to generate the hash of a file. What this means is that the current version of the file is hashed at that moment in time. As previously mentioned, even changing 1 character in the file will generate a completely different hash.

This is obviously very useful if you have an important file (such as a legal contract) that you wish to verify its integrity. Upon signing a contract, you could generate its hash using the wallet and store it in the blockchain. You could then check in a few months time that the hash generated earlier matches the current hash of the file. If they match, it means that the file has not been altered and thus the contract is still valid. If they do not match, it means that the file has been altered (if this is a legal document, you need to make sure that someone has not maliciously tampered with it).

The benefit of utilising the blockchain is that it is immutable (cannot be changed). That means that when you store the hash, it is available forever and can never be changed.

Technical Users:
The hash is generated using SHA-256, a current hashing function with no known collisions. The function can also incorporate the user's wallet to provide restriction as to the hash value (a form of cryptographic security).

Important:
DeepVault is not a file store, it is a hash store. You should take every necessary step to secure your documents from tampering by storing them in a secure location.

Thank you for your time and we look forward to answering any of your questions.

By using the blockchain, you are sure that the hash is the one you generated at the 1st time.
Otherwise, the hash you stored could have been altered.. I think this is the point.

It would be best to ignore the posts of haters and trols.
So please don't quote texts of them, and dont waste energy for them.
Lets concentrate on bright future of DeepOnion  

This train has already leave it bus stop, it too late for me to join in now, in fact I don't think I can join in at all

This train has already leave it bus stop, it too late for me to join in now, in fact I don't think I can join in at all

DeepVault
DeepVault is a blockchain innovation brought to you by the DeepOnion Development team. DeepVault allows users to determine whether or not a file has been changed or corrupted by enabling hash verification of the file.


 
Non-technical users:
A hash is a random string of characters of fixed length (for example: hello = 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824, hello1 = 91e9240f415223982edc345532630710e94a7f52cd5f48f5ee1afc555078f0ab). A hash is unique as no two inputs (files or texts) generate the same hash. For instance, hello and hello1 will have completely different hash values as witnessed in the previous example.

One use for hashing is the ability to generate the hash of a file. What this means is that the current version of the file is hashed at that moment in time. As previously mentioned, even changing 1 character in the file will generate a completely different hash.

This is obviously very useful if you have an important file (such as a legal contract) that you wish to verify its integrity. Upon signing a contract, you could generate its hash using the wallet and store it in the blockchain. You could then check in a few months time that the hash generated earlier matches the current hash of the file. If they match, it means that the file has not been altered and thus the contract is still valid. If they do not match, it means that the file has been altered (if this is a legal document, you need to make sure that someone has not maliciously tampered with it).

The benefit of utilising the blockchain is that it is immutable (cannot be changed). That means that when you store the hash, it is available forever and can never be changed.

Technical Users:
The hash is generated using SHA-256, a current hashing function with no known collisions. The function can also incorporate the user's wallet to provide restriction as to the hash value (a form of cryptographic security).

Important:
DeepVault is not a file store, it is a hash store. You should take every necessary step to secure your documents from tampering by storing them in a secure location.

Thank you for your time and we look forward to answering any of your questions.

I love that it is integrated into the wallet. I assume the actual look is a bit of a placeholder though? Otherwise I would suggest cleaning it up a bit, think there are too many different colours, font sizes etc for my liking...

That is awesome! I know MD5 hashes and other alternatives already exist, but even I am usually too lazy to do the checks, so some automated, integrated one-button solution would be perfect.

Love the Deep vault integration into the QT wallet.  DO will set the gold standard for what a QT wallet should be like.  Great job dev team, thanks for continuing to grind to improve the tech and provide as many updates as often possible.  

Thanks to all the Onion moderators that grind to build the movement and ease some of the dev team's burdens so they can focus on the tech.

Thanks to all the supporters that unrelentingly continue to build up the Deep Onion brand through all media channels.