It sounds smart. Just swap out the sha1 for public-key signatures and rename the "value chain" to "block chain" and Bob's your uncle. No but seriously: "SHA wh

It sounds smart. Just swap out the sha1 for public-key signatures and rename the "value chain" to "block chain" and Bob's your uncle. No but seriously: "SHA which I have chosen in this article has 160 bits, so after more than 2^160 entries have been put into the DHT collisions will occur" Collisions are largely related to the content that you are hashing. If you are hashing sequential 160 bit chunks of data then Joe's math is theoretically correct. If you are hashing DVD ISO images then you can use math to predict why you should never use sha1. If you needed to cram it into 160 bits for some hardware reason then you could implement some form of write failure recovery to redistribute writes over them remaining available key space but this would get slower and slower the less and less space you have unless you implement some kind of free space map.