Quote from: xploited on March 16, 2014, 05:12:35 PM

Quote from: mintzone on March 16, 2014, 04:10:23 PM

Quote from: JpHysteriak on March 16, 2014, 03:37:59 PM

I did it ! Just export your dogecoin privkey and import it on the dgb wallet. Works fine !

That really works? O.o
Wow... I wonder how those .dat files work anyways

Interestingly enough because of how private keys are generated and how addresses are validated in the clients in any coins based on bitcoin if the address prefix is the same, 'D' in our case, both addresses and private keys will be valid on both coins blockchain. Thats not to say your coins come with you from one blockchain to the other, just that the private key generated for an address on one blockchain will also be valid on the other if the address prefix match.

Now, you may ask yourself (as I did when I first discovered this), well, isn't this a security concern. Can't somebody on doge coin generate a private key that could access your address? This however is incredible improbable (or unfeasible depending on which term you like better) and no more likely then someone on the DigiByte blockchain generating an address that is already in use on the DigiByte blockchain. I could get into the absurdity of the numbers but needless to say the amount of possible addresses is beyond large. Imagine the number of atoms in all the matter on earth... and that would only be a small portion of the possible address space.

People in the past have occasionaly sent their DigiBytes to a Doge address on an exchange. Because the private key to the address they were sending already existed on the Doge blockchain and was owned by the exchange, the exchange was able to import the private key from one blockchain to another and redeem the otherwise lost coins.

This of course is totally up to the desecration of the exchange.

We've looked into possible solutions but have only come up with bandaids that aren't worth implementing and don't actually fix the underlying cause.

My only suggestion currently, as poor as a suggestion as it might be, is to remain diligent about verifying you are sending to a DigiByte address. Almost every instance of this has been related to DigiBytes being sent to an exchange. Double check your on the DigiByte deposit page when you generated a deposit address and that your not mixing up Doge and DGB or anyother coin that might start with D

It also doesn't hurt to send a very small amount and verify it was deposited to your account correctly before you send a larger amount. Its much better to risk losing 1 DigiByte to the void then 50k.

Interesting response. Thanks xploited!