Quote from: phishead on October 22, 2015, 03:10:38 AM

Quote from: ranlo on October 22, 2015, 02:59:40 AM

Quote from: phishead on October 22, 2015, 02:53:49 AM

Quote from: ranlo on October 21, 2015, 11:30:44 PM

Quote from: phishead on October 21, 2015, 10:37:17 PM

Quote from: matrix zion on October 21, 2015, 10:34:33 PM

the first thing is to not reuse addresses. rather, generate a new address every time

Well with a lot (if not all) wallets that you use, the wallet generates a new address each time you receive bitcoins to the previous address... so that's already implemented.

I'm not aware of any that do that. Can you name some? Xapo, Circle, Coinbase, Blockchain.info, MultiBit, Bitcoin QT, Electrum, (I know I'm missing a lot here) definitely don't.

Well I personally use breadwallet for iOS... I know for a fact this wallet does, but have used blocktrail in the past as well that did it... I have just assumed that all wallets changed the wallet address after each transaction had been received?

That's definitely the exception, rather than the norm. Some, like Coinbase, will make a new one when you send a transaction, but not when you receive one.

Well in that case, if you use Android, I would suggest you look into getting blocktrail (I think blocktrail is supported by Android)... Regardless, this thread does seem to go off tangent very quickly haha.

But blocktrail seems to be a very secure wallet, while offering that service. I just prefer bread because it connects directly to the blockchain network.

I think it's actually on topic. Different addresses for each received transaction is a huge thing. Is Bread the one that does dynamic fees, too?