Renewing warning against storing private keys in Blockchain Wallet. Rob at Gli.ph claims their API generated a new address/private key when I first linked it to Blockchain (with whitelisted IP), but that address (
https://blockchain.info/address/1EKqFXn3UmaZaJP5swqCUm3mbpdp63VhwR) never showed up, so I couldn't have deleted it, by accident (an 8 step process) or otherwise. He swears up and down that it's working correctly, but clearly it isn't, if private keys are
ever getting erased without the possibility of user input.
Hey there, As I mentioned in the few hours we've worked together over the past two days trouble shoot this, I'm sorry we weren't able to work this out or trace exactly what happened with the first .001 I sent to you over Gliph.
I understand that not everyone out there has the best experience with Blockchain.info or even Coinbase. We generally recommend people use Coinbase with Gliph at this point. We understand that not everyone feels comfortable with either service's use of private keys and that the way Gliph works with Bitcoin may not suit every Bitcoin user.
I recognize that 2FA is a requirement for some folks, and while we don't support that for sending, we do support that for receipt of Payment in Marketplace on both wallet services.
I think it is reasonably important to say that I was able to successfully send Bitcoin to your attached blockchain account, and while you offered to return it, I said you were welcome to keep it.
I also want to clarify that we have not had a problem reported similar to this yet, which makes it hard to reproduce.
I am sorry we weren't able to make Gliph Marketplace work for you.
If other folks are considering listing in Gliph Marketplace we'd love to have you give it a shot. It is just two weeks old and we're continuing to improve it over time.
