Hope you enjoyed the opportunity to buy at 95% price discount.
Topic: 🧅 [ONION] Privacy Coin with Real Use Cases 🧅 DeepOnion 2.2.2 Released ⚡ - page 488. (Read 298367 times)
July 04, 2018, 10:19:42 AM
Rebound coming
Hope you enjoyed the opportunity to buy at 95% price discount.
Hope you enjoyed the opportunity to buy at 95% price discount.
July 04, 2018, 10:11:47 AM
I will miss the 10% days...
Staking is so good.
Link (Download):
https://deeponion.org/community/attachments/staking-gif.166143/
Verify above image with DeepVault:
Dpy7NidaMrVC1BoxW2Skp14YjyphhnRqYS
And I will start with the 5%, lol. I did never stake before but now I will give a try. Staking is so good.
Link (Download):
https://deeponion.org/community/attachments/staking-gif.166143/
Verify above image with DeepVault:
Dpy7NidaMrVC1BoxW2Skp14YjyphhnRqYS
July 04, 2018, 10:00:02 AM
RightBTC listing in 3 days! Go open an account guys: https://www.rightbtc.com/
I did open and I'm ready to trade during the initial hours where the big money flows in.
Good job mate!
July 04, 2018, 09:42:05 AM
DeepOnion on the move 
Yeah. Just goes out to show some people that when Bitcoin is not bringing the whole market down, altcoins move upwards. July 04, 2018, 09:32:53 AM
We have so many places where you can buy some cheap ONION.... there is no excuse now for not buying and taking advantage of this 
Verified by DeepVault : Djnfcwfuxc5YPaitYdNjdVQkz3TXVxNCUV
I would, but that ugly face is kind of turn off for me.
Thanks mod VokainAnd there is a lot more on the way. We are not short on exchanges, that is for sure.
Can we reach 20 by the end of 2018? July 04, 2018, 09:15:03 AM
RightBTC listing in 3 days! Go open an account guys: https://www.rightbtc.com/
I did open and I'm ready to trade during the initial hours where the big money flows in.
July 04, 2018, 09:10:54 AM
DeepOnion on the move
July 04, 2018, 08:30:20 AM
RightBTC listing in 3 days! Go open an account guys: https://www.rightbtc.com/
July 04, 2018, 08:27:16 AM
We have so many places where you can buy some cheap ONION.... there is no excuse now for not buying and taking advantage of this
Verified by DeepVault : Djnfcwfuxc5YPaitYdNjdVQkz3TXVxNCUV
I would, but that ugly face is kind of turn off for me.
Thanks mod VokainAnd there is a lot more on the way. We are not short on exchanges, that is for sure.
It's good to see the hard work with the exchanges are starting to pay, and now we can add RightBTC to the list.
Yep few more days and RightBTC is a go!
cant wait for it.... July 04, 2018, 08:26:47 AM
from DeepOnion lead dev
Technical Aspect On How DeepOnion Blockchain Is Guaranteed By The Bitcoin Blockchain
Since we announced this new feature, many people liked it, but there are also some skepticism. As many people (even some self-pretend "experts") don't understand how this is done, and how this is possible. So as the lead dev of DeepOnion, I will explain the technical aspect of how this works.
In order to do this, first we need to compute the SHA256 hash of our blockchain to certain height. Each block has its hash, which is the result of all tx and other params in the block, it is called the merkle root hash of the block.
https://en.wikipedia.org/wiki/Merkle_tree (Merkle tree - Wikipedia)
We started from block 1, get its hash, then we go to block 2, get its hash and combine with block 1's hash, etc, until we get to the predefined height. This height is the very recent height we will use. For the last registration with BTC blockchain, we used block 543950 as our last block. All the hashes are combined, and a combined SHA256 hash is then computed, and we get the hash of our blockchain from block 1 to block 543950. This hash is determined as db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe.
If any data in any block changed, the merkle root hash of that block will change, this will result in the combined hash change. Thus when a DeepOnion wallet load the blockchain, we can compute the block hash up to block 543950, and compare the hash with the above mentioned hash, if it matches, then the loaded blockchain is authentic (up to block 543950).
So far there's no Bitcoin blockchain involved. Why we get Bitcoin blockchain involved? because we want be sure that this hash (db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe) can not be changed. If tomorrow, someone created a forked chain, and generated a hash, and say his hash is the correct one, how can you prove which is the right one? For this we register the correct hash into the Bitcoin blockchain, which is the most secure immutable database in the world.
How do we do this? Well I won't go into details, but we can register this hash db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe into the Bitcoin blockchain. And I did it, the registration tx on Bitcoin blockchain is ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e. It is here:
https://blockchain.info/tx/ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e (Bitcoin Transaction ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e)
It is in Bitcoin blockchain at Block 523352. And I can prove that this tx is derived from the hash of DeepOnion Block 1-543950, which is db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe.
I will not go to details how I can prove that, those who have good knowledge of blockchain tech should already know how I do it. Therefore, now I just need to put these info in our wallet code, as you can verify the correctness of our blockchain hash in the Bitcoin blockchain. This is what you see if your blockchain is authentic:
https://deeponion.org/community/threads/technical-aspect-on-how-deeponion-blockchain-is-guaranteed-by-the-bitcoin-blockchain.37940/
Technical Aspect On How DeepOnion Blockchain Is Guaranteed By The Bitcoin Blockchain
Since we announced this new feature, many people liked it, but there are also some skepticism. As many people (even some self-pretend "experts") don't understand how this is done, and how this is possible. So as the lead dev of DeepOnion, I will explain the technical aspect of how this works.
In order to do this, first we need to compute the SHA256 hash of our blockchain to certain height. Each block has its hash, which is the result of all tx and other params in the block, it is called the merkle root hash of the block.
https://en.wikipedia.org/wiki/Merkle_tree (Merkle tree - Wikipedia)
We started from block 1, get its hash, then we go to block 2, get its hash and combine with block 1's hash, etc, until we get to the predefined height. This height is the very recent height we will use. For the last registration with BTC blockchain, we used block 543950 as our last block. All the hashes are combined, and a combined SHA256 hash is then computed, and we get the hash of our blockchain from block 1 to block 543950. This hash is determined as db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe.
If any data in any block changed, the merkle root hash of that block will change, this will result in the combined hash change. Thus when a DeepOnion wallet load the blockchain, we can compute the block hash up to block 543950, and compare the hash with the above mentioned hash, if it matches, then the loaded blockchain is authentic (up to block 543950).
So far there's no Bitcoin blockchain involved. Why we get Bitcoin blockchain involved? because we want be sure that this hash (db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe) can not be changed. If tomorrow, someone created a forked chain, and generated a hash, and say his hash is the correct one, how can you prove which is the right one? For this we register the correct hash into the Bitcoin blockchain, which is the most secure immutable database in the world.
How do we do this? Well I won't go into details, but we can register this hash db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe into the Bitcoin blockchain. And I did it, the registration tx on Bitcoin blockchain is ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e. It is here:
https://blockchain.info/tx/ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e (Bitcoin Transaction ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e)
It is in Bitcoin blockchain at Block 523352. And I can prove that this tx is derived from the hash of DeepOnion Block 1-543950, which is db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe.
I will not go to details how I can prove that, those who have good knowledge of blockchain tech should already know how I do it. Therefore, now I just need to put these info in our wallet code, as you can verify the correctness of our blockchain hash in the Bitcoin blockchain. This is what you see if your blockchain is authentic:
https://deeponion.org/community/threads/technical-aspect-on-how-deeponion-blockchain-is-guaranteed-by-the-bitcoin-blockchain.37940/
With this in mind why can't they just see that our devs are very serious when it comes to the security of our hard earned success. They just wanted the best for their child (DeepOnion), even other parents will do the same. I myself is doing my part not just by waiting but by acting and taking part to be a Vip to promote Deeponion in a very professional manner. So guys let's do something about OUR project not just the wishing to the HOLY MOON to come to us.
July 04, 2018, 07:47:23 AM
Almost 1 year for DeepOnion, we achieved so much in a short period of time and we also have so many things to release.
People with real motivation from this side
People with real motivation from this side
July 04, 2018, 07:06:41 AM
Someone asked me today how many people own ONIONs? but where can we see that info if there is a good source already available for that? we know that in the official forum there are about 13k+ members, etc!
I found the link... 6002 wallets received ONION. After the airdrop, I'm sure a wider distribution was achieved. 
July 04, 2018, 06:28:53 AM
We have so many places where you can buy some cheap ONION.... there is no excuse now for not buying and taking advantage of this
Verified by DeepVault : Djnfcwfuxc5YPaitYdNjdVQkz3TXVxNCUV
I would, but that ugly face is kind of turn off for me.
Thanks mod VokainAnd there is a lot more on the way. We are not short on exchanges, that is for sure.
July 04, 2018, 06:22:16 AM
We have so many places where you can buy some cheap ONION.... there is no excuse now for not buying and taking advantage of this
Verified by DeepVault : Djnfcwfuxc5YPaitYdNjdVQkz3TXVxNCUV
I would, but that ugly face is kind of turn off for me.
Thanks mod Vokain July 04, 2018, 04:56:20 AM
from DeepOnion lead dev
Technical Aspect On How DeepOnion Blockchain Is Guaranteed By The Bitcoin Blockchain
Since we announced this new feature, many people liked it, but there are also some skepticism. As many people (even some self-pretend "experts") don't understand how this is done, and how this is possible. So as the lead dev of DeepOnion, I will explain the technical aspect of how this works.
In order to do this, first we need to compute the SHA256 hash of our blockchain to certain height. Each block has its hash, which is the result of all tx and other params in the block, it is called the merkle root hash of the block.
https://en.wikipedia.org/wiki/Merkle_tree (Merkle tree - Wikipedia)
We started from block 1, get its hash, then we go to block 2, get its hash and combine with block 1's hash, etc, until we get to the predefined height. This height is the very recent height we will use. For the last registration with BTC blockchain, we used block 543950 as our last block. All the hashes are combined, and a combined SHA256 hash is then computed, and we get the hash of our blockchain from block 1 to block 543950. This hash is determined as db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe.
If any data in any block changed, the merkle root hash of that block will change, this will result in the combined hash change. Thus when a DeepOnion wallet load the blockchain, we can compute the block hash up to block 543950, and compare the hash with the above mentioned hash, if it matches, then the loaded blockchain is authentic (up to block 543950).
So far there's no Bitcoin blockchain involved. Why we get Bitcoin blockchain involved? because we want be sure that this hash (db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe) can not be changed. If tomorrow, someone created a forked chain, and generated a hash, and say his hash is the correct one, how can you prove which is the right one? For this we register the correct hash into the Bitcoin blockchain, which is the most secure immutable database in the world.
How do we do this? Well I won't go into details, but we can register this hash db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe into the Bitcoin blockchain. And I did it, the registration tx on Bitcoin blockchain is ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e. It is here:
https://blockchain.info/tx/ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e (Bitcoin Transaction ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e)
It is in Bitcoin blockchain at Block 523352. And I can prove that this tx is derived from the hash of DeepOnion Block 1-543950, which is db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe.
I will not go to details how I can prove that, those who have good knowledge of blockchain tech should already know how I do it. Therefore, now I just need to put these info in our wallet code, as you can verify the correctness of our blockchain hash in the Bitcoin blockchain. This is what you see if your blockchain is authentic:
https://deeponion.org/community/threads/technical-aspect-on-how-deeponion-blockchain-is-guaranteed-by-the-bitcoin-blockchain.37940/
Technical Aspect On How DeepOnion Blockchain Is Guaranteed By The Bitcoin Blockchain
Since we announced this new feature, many people liked it, but there are also some skepticism. As many people (even some self-pretend "experts") don't understand how this is done, and how this is possible. So as the lead dev of DeepOnion, I will explain the technical aspect of how this works.
In order to do this, first we need to compute the SHA256 hash of our blockchain to certain height. Each block has its hash, which is the result of all tx and other params in the block, it is called the merkle root hash of the block.
https://en.wikipedia.org/wiki/Merkle_tree (Merkle tree - Wikipedia)
We started from block 1, get its hash, then we go to block 2, get its hash and combine with block 1's hash, etc, until we get to the predefined height. This height is the very recent height we will use. For the last registration with BTC blockchain, we used block 543950 as our last block. All the hashes are combined, and a combined SHA256 hash is then computed, and we get the hash of our blockchain from block 1 to block 543950. This hash is determined as db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe.
If any data in any block changed, the merkle root hash of that block will change, this will result in the combined hash change. Thus when a DeepOnion wallet load the blockchain, we can compute the block hash up to block 543950, and compare the hash with the above mentioned hash, if it matches, then the loaded blockchain is authentic (up to block 543950).
So far there's no Bitcoin blockchain involved. Why we get Bitcoin blockchain involved? because we want be sure that this hash (db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe) can not be changed. If tomorrow, someone created a forked chain, and generated a hash, and say his hash is the correct one, how can you prove which is the right one? For this we register the correct hash into the Bitcoin blockchain, which is the most secure immutable database in the world.
How do we do this? Well I won't go into details, but we can register this hash db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe into the Bitcoin blockchain. And I did it, the registration tx on Bitcoin blockchain is ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e. It is here:
https://blockchain.info/tx/ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e (Bitcoin Transaction ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e)
It is in Bitcoin blockchain at Block 523352. And I can prove that this tx is derived from the hash of DeepOnion Block 1-543950, which is db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe.
I will not go to details how I can prove that, those who have good knowledge of blockchain tech should already know how I do it. Therefore, now I just need to put these info in our wallet code, as you can verify the correctness of our blockchain hash in the Bitcoin blockchain. This is what you see if your blockchain is authentic:
https://deeponion.org/community/threads/technical-aspect-on-how-deeponion-blockchain-is-guaranteed-by-the-bitcoin-blockchain.37940/
With this in mind why can't they just see that our devs are very serious when it comes to the security of our hard earned success. They just wanted the best for their child (DeepOnion), even other parents will do the same. I myself is doing my part not just by waiting but by acting and taking part to be a Vip to promote Deeponion in a very professional manner. So guys let's do something about OUR project not just the wishing to the HOLY MOON to come to us.
Indeed, we should always bring DeepOnion up in conversations, in real life and social media. Whenever there is a possibility. one by one we shall spread throughout the ever expanding cryptoverse!
July 04, 2018, 04:50:38 AM
We have so many places where you can buy some cheap ONION.... there is no excuse now for not buying and taking advantage of this
Verified by DeepVault : Djnfcwfuxc5YPaitYdNjdVQkz3TXVxNCUV
I would, but that ugly face is kind of turn off for me.
July 04, 2018, 02:29:34 AM
We have so many places where you can buy some cheap ONION.... there is no excuse now for not buying and taking advantage of this
Verified by DeepVault : Djnfcwfuxc5YPaitYdNjdVQkz3TXVxNCUV
July 04, 2018, 02:21:22 AM
from DeepOnion lead dev
Technical Aspect On How DeepOnion Blockchain Is Guaranteed By The Bitcoin Blockchain
Since we announced this new feature, many people liked it, but there are also some skepticism. As many people (even some self-pretend "experts") don't understand how this is done, and how this is possible. So as the lead dev of DeepOnion, I will explain the technical aspect of how this works.
In order to do this, first we need to compute the SHA256 hash of our blockchain to certain height. Each block has its hash, which is the result of all tx and other params in the block, it is called the merkle root hash of the block.
https://en.wikipedia.org/wiki/Merkle_tree (Merkle tree - Wikipedia)
We started from block 1, get its hash, then we go to block 2, get its hash and combine with block 1's hash, etc, until we get to the predefined height. This height is the very recent height we will use. For the last registration with BTC blockchain, we used block 543950 as our last block. All the hashes are combined, and a combined SHA256 hash is then computed, and we get the hash of our blockchain from block 1 to block 543950. This hash is determined as db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe.
If any data in any block changed, the merkle root hash of that block will change, this will result in the combined hash change. Thus when a DeepOnion wallet load the blockchain, we can compute the block hash up to block 543950, and compare the hash with the above mentioned hash, if it matches, then the loaded blockchain is authentic (up to block 543950).
So far there's no Bitcoin blockchain involved. Why we get Bitcoin blockchain involved? because we want be sure that this hash (db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe) can not be changed. If tomorrow, someone created a forked chain, and generated a hash, and say his hash is the correct one, how can you prove which is the right one? For this we register the correct hash into the Bitcoin blockchain, which is the most secure immutable database in the world.
How do we do this? Well I won't go into details, but we can register this hash db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe into the Bitcoin blockchain. And I did it, the registration tx on Bitcoin blockchain is ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e. It is here:
https://blockchain.info/tx/ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e (Bitcoin Transaction ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e)
It is in Bitcoin blockchain at Block 523352. And I can prove that this tx is derived from the hash of DeepOnion Block 1-543950, which is db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe.
I will not go to details how I can prove that, those who have good knowledge of blockchain tech should already know how I do it. Therefore, now I just need to put these info in our wallet code, as you can verify the correctness of our blockchain hash in the Bitcoin blockchain. This is what you see if your blockchain is authentic:
https://deeponion.org/community/threads/technical-aspect-on-how-deeponion-blockchain-is-guaranteed-by-the-bitcoin-blockchain.37940/
Technical Aspect On How DeepOnion Blockchain Is Guaranteed By The Bitcoin Blockchain
Since we announced this new feature, many people liked it, but there are also some skepticism. As many people (even some self-pretend "experts") don't understand how this is done, and how this is possible. So as the lead dev of DeepOnion, I will explain the technical aspect of how this works.
In order to do this, first we need to compute the SHA256 hash of our blockchain to certain height. Each block has its hash, which is the result of all tx and other params in the block, it is called the merkle root hash of the block.
https://en.wikipedia.org/wiki/Merkle_tree (Merkle tree - Wikipedia)
We started from block 1, get its hash, then we go to block 2, get its hash and combine with block 1's hash, etc, until we get to the predefined height. This height is the very recent height we will use. For the last registration with BTC blockchain, we used block 543950 as our last block. All the hashes are combined, and a combined SHA256 hash is then computed, and we get the hash of our blockchain from block 1 to block 543950. This hash is determined as db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe.
If any data in any block changed, the merkle root hash of that block will change, this will result in the combined hash change. Thus when a DeepOnion wallet load the blockchain, we can compute the block hash up to block 543950, and compare the hash with the above mentioned hash, if it matches, then the loaded blockchain is authentic (up to block 543950).
So far there's no Bitcoin blockchain involved. Why we get Bitcoin blockchain involved? because we want be sure that this hash (db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe) can not be changed. If tomorrow, someone created a forked chain, and generated a hash, and say his hash is the correct one, how can you prove which is the right one? For this we register the correct hash into the Bitcoin blockchain, which is the most secure immutable database in the world.
How do we do this? Well I won't go into details, but we can register this hash db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe into the Bitcoin blockchain. And I did it, the registration tx on Bitcoin blockchain is ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e. It is here:
https://blockchain.info/tx/ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e (Bitcoin Transaction ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e)
It is in Bitcoin blockchain at Block 523352. And I can prove that this tx is derived from the hash of DeepOnion Block 1-543950, which is db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe.
I will not go to details how I can prove that, those who have good knowledge of blockchain tech should already know how I do it. Therefore, now I just need to put these info in our wallet code, as you can verify the correctness of our blockchain hash in the Bitcoin blockchain. This is what you see if your blockchain is authentic:
https://deeponion.org/community/threads/technical-aspect-on-how-deeponion-blockchain-is-guaranteed-by-the-bitcoin-blockchain.37940/
With this in mind why can't they just see that our devs are very serious when it comes to the security of our hard earned success. They just wanted the best for their child (DeepOnion), even other parents will do the same. I myself is doing my part not just by waiting but by acting and taking part to be a Vip to promote Deeponion in a very professional manner. So guys let's do something about OUR project not just the wishing to the HOLY MOON to come to us.
July 04, 2018, 01:31:21 AM
from DeepOnion lead dev
Technical Aspect On How DeepOnion Blockchain Is Guaranteed By The Bitcoin Blockchain
Since we announced this new feature, many people liked it, but there are also some skepticism. As many people (even some self-pretend "experts") don't understand how this is done, and how this is possible. So as the lead dev of DeepOnion, I will explain the technical aspect of how this works.
In order to do this, first we need to compute the SHA256 hash of our blockchain to certain height. Each block has its hash, which is the result of all tx and other params in the block, it is called the merkle root hash of the block.
https://en.wikipedia.org/wiki/Merkle_tree (Merkle tree - Wikipedia)
We started from block 1, get its hash, then we go to block 2, get its hash and combine with block 1's hash, etc, until we get to the predefined height. This height is the very recent height we will use. For the last registration with BTC blockchain, we used block 543950 as our last block. All the hashes are combined, and a combined SHA256 hash is then computed, and we get the hash of our blockchain from block 1 to block 543950. This hash is determined as db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe.
If any data in any block changed, the merkle root hash of that block will change, this will result in the combined hash change. Thus when a DeepOnion wallet load the blockchain, we can compute the block hash up to block 543950, and compare the hash with the above mentioned hash, if it matches, then the loaded blockchain is authentic (up to block 543950).
So far there's no Bitcoin blockchain involved. Why we get Bitcoin blockchain involved? because we want be sure that this hash (db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe) can not be changed. If tomorrow, someone created a forked chain, and generated a hash, and say his hash is the correct one, how can you prove which is the right one? For this we register the correct hash into the Bitcoin blockchain, which is the most secure immutable database in the world.
How do we do this? Well I won't go into details, but we can register this hash db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe into the Bitcoin blockchain. And I did it, the registration tx on Bitcoin blockchain is ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e. It is here:
https://blockchain.info/tx/ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e (Bitcoin Transaction ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e)
It is in Bitcoin blockchain at Block 523352. And I can prove that this tx is derived from the hash of DeepOnion Block 1-543950, which is db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe.
I will not go to details how I can prove that, those who have good knowledge of blockchain tech should already know how I do it. Therefore, now I just need to put these info in our wallet code, as you can verify the correctness of our blockchain hash in the Bitcoin blockchain. This is what you see if your blockchain is authentic:
https://deeponion.org/community/threads/technical-aspect-on-how-deeponion-blockchain-is-guaranteed-by-the-bitcoin-blockchain.37940/
Technical Aspect On How DeepOnion Blockchain Is Guaranteed By The Bitcoin Blockchain
Since we announced this new feature, many people liked it, but there are also some skepticism. As many people (even some self-pretend "experts") don't understand how this is done, and how this is possible. So as the lead dev of DeepOnion, I will explain the technical aspect of how this works.
In order to do this, first we need to compute the SHA256 hash of our blockchain to certain height. Each block has its hash, which is the result of all tx and other params in the block, it is called the merkle root hash of the block.
https://en.wikipedia.org/wiki/Merkle_tree (Merkle tree - Wikipedia)
We started from block 1, get its hash, then we go to block 2, get its hash and combine with block 1's hash, etc, until we get to the predefined height. This height is the very recent height we will use. For the last registration with BTC blockchain, we used block 543950 as our last block. All the hashes are combined, and a combined SHA256 hash is then computed, and we get the hash of our blockchain from block 1 to block 543950. This hash is determined as db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe.
If any data in any block changed, the merkle root hash of that block will change, this will result in the combined hash change. Thus when a DeepOnion wallet load the blockchain, we can compute the block hash up to block 543950, and compare the hash with the above mentioned hash, if it matches, then the loaded blockchain is authentic (up to block 543950).
So far there's no Bitcoin blockchain involved. Why we get Bitcoin blockchain involved? because we want be sure that this hash (db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe) can not be changed. If tomorrow, someone created a forked chain, and generated a hash, and say his hash is the correct one, how can you prove which is the right one? For this we register the correct hash into the Bitcoin blockchain, which is the most secure immutable database in the world.
How do we do this? Well I won't go into details, but we can register this hash db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe into the Bitcoin blockchain. And I did it, the registration tx on Bitcoin blockchain is ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e. It is here:
https://blockchain.info/tx/ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e (Bitcoin Transaction ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e)
It is in Bitcoin blockchain at Block 523352. And I can prove that this tx is derived from the hash of DeepOnion Block 1-543950, which is db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe.
I will not go to details how I can prove that, those who have good knowledge of blockchain tech should already know how I do it. Therefore, now I just need to put these info in our wallet code, as you can verify the correctness of our blockchain hash in the Bitcoin blockchain. This is what you see if your blockchain is authentic:
https://deeponion.org/community/threads/technical-aspect-on-how-deeponion-blockchain-is-guaranteed-by-the-bitcoin-blockchain.37940/
With this in mind why can't they just see that our devs are very serious when it comes to the security of our hard earned success. They just wanted the best for their child (DeepOnion), even other parents will do the same. I myself is doing my part not just by waiting but by acting and taking part to be a Vip to promote Deeponion in a very professional manner. So guys let's do something about OUR project not just the wishing to the HOLY MOON to come to us.
There is nothing to prove.
Lets show in the result.
Thanks for everything Deeper
July 04, 2018, 01:22:20 AM
from DeepOnion lead dev
Technical Aspect On How DeepOnion Blockchain Is Guaranteed By The Bitcoin Blockchain
Since we announced this new feature, many people liked it, but there are also some skepticism. As many people (even some self-pretend "experts") don't understand how this is done, and how this is possible. So as the lead dev of DeepOnion, I will explain the technical aspect of how this works.
In order to do this, first we need to compute the SHA256 hash of our blockchain to certain height. Each block has its hash, which is the result of all tx and other params in the block, it is called the merkle root hash of the block.
https://en.wikipedia.org/wiki/Merkle_tree (Merkle tree - Wikipedia)
We started from block 1, get its hash, then we go to block 2, get its hash and combine with block 1's hash, etc, until we get to the predefined height. This height is the very recent height we will use. For the last registration with BTC blockchain, we used block 543950 as our last block. All the hashes are combined, and a combined SHA256 hash is then computed, and we get the hash of our blockchain from block 1 to block 543950. This hash is determined as db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe.
If any data in any block changed, the merkle root hash of that block will change, this will result in the combined hash change. Thus when a DeepOnion wallet load the blockchain, we can compute the block hash up to block 543950, and compare the hash with the above mentioned hash, if it matches, then the loaded blockchain is authentic (up to block 543950).
So far there's no Bitcoin blockchain involved. Why we get Bitcoin blockchain involved? because we want be sure that this hash (db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe) can not be changed. If tomorrow, someone created a forked chain, and generated a hash, and say his hash is the correct one, how can you prove which is the right one? For this we register the correct hash into the Bitcoin blockchain, which is the most secure immutable database in the world.
How do we do this? Well I won't go into details, but we can register this hash db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe into the Bitcoin blockchain. And I did it, the registration tx on Bitcoin blockchain is ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e. It is here:
https://blockchain.info/tx/ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e (Bitcoin Transaction ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e)
It is in Bitcoin blockchain at Block 523352. And I can prove that this tx is derived from the hash of DeepOnion Block 1-543950, which is db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe.
I will not go to details how I can prove that, those who have good knowledge of blockchain tech should already know how I do it. Therefore, now I just need to put these info in our wallet code, as you can verify the correctness of our blockchain hash in the Bitcoin blockchain. This is what you see if your blockchain is authentic:
https://deeponion.org/community/threads/technical-aspect-on-how-deeponion-blockchain-is-guaranteed-by-the-bitcoin-blockchain.37940/
Technical Aspect On How DeepOnion Blockchain Is Guaranteed By The Bitcoin Blockchain
Since we announced this new feature, many people liked it, but there are also some skepticism. As many people (even some self-pretend "experts") don't understand how this is done, and how this is possible. So as the lead dev of DeepOnion, I will explain the technical aspect of how this works.
In order to do this, first we need to compute the SHA256 hash of our blockchain to certain height. Each block has its hash, which is the result of all tx and other params in the block, it is called the merkle root hash of the block.
https://en.wikipedia.org/wiki/Merkle_tree (Merkle tree - Wikipedia)
We started from block 1, get its hash, then we go to block 2, get its hash and combine with block 1's hash, etc, until we get to the predefined height. This height is the very recent height we will use. For the last registration with BTC blockchain, we used block 543950 as our last block. All the hashes are combined, and a combined SHA256 hash is then computed, and we get the hash of our blockchain from block 1 to block 543950. This hash is determined as db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe.
If any data in any block changed, the merkle root hash of that block will change, this will result in the combined hash change. Thus when a DeepOnion wallet load the blockchain, we can compute the block hash up to block 543950, and compare the hash with the above mentioned hash, if it matches, then the loaded blockchain is authentic (up to block 543950).
So far there's no Bitcoin blockchain involved. Why we get Bitcoin blockchain involved? because we want be sure that this hash (db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe) can not be changed. If tomorrow, someone created a forked chain, and generated a hash, and say his hash is the correct one, how can you prove which is the right one? For this we register the correct hash into the Bitcoin blockchain, which is the most secure immutable database in the world.
How do we do this? Well I won't go into details, but we can register this hash db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe into the Bitcoin blockchain. And I did it, the registration tx on Bitcoin blockchain is ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e. It is here:
https://blockchain.info/tx/ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e (Bitcoin Transaction ba839a3a2d7c9e5a80cc891195e0518c37cded079c6ea8a8ce826b002d4c954e)
It is in Bitcoin blockchain at Block 523352. And I can prove that this tx is derived from the hash of DeepOnion Block 1-543950, which is db2b4c6d31844020af9ef4eb9253692efd65f35be85859f73ab7e4b41436eabe.
I will not go to details how I can prove that, those who have good knowledge of blockchain tech should already know how I do it. Therefore, now I just need to put these info in our wallet code, as you can verify the correctness of our blockchain hash in the Bitcoin blockchain. This is what you see if your blockchain is authentic:
https://deeponion.org/community/threads/technical-aspect-on-how-deeponion-blockchain-is-guaranteed-by-the-bitcoin-blockchain.37940/
With this in mind why can't they just see that our devs are very serious when it comes to the security of our hard earned success. They just wanted the best for their child (DeepOnion), even other parents will do the same. I myself is doing my part not just by waiting but by acting and taking part to be a Vip to promote Deeponion in a very professional manner. So guys let's do something about OUR project not just the wishing to the HOLY MOON to come to us.
Jump to: