On Wed, Feb 4, 2015 at 2:23 PM, Isidor Zeuner
wrote:
> Hi there,
>
> traditionally, the Bitcoin client strives to hide which output
> addresses are change addresses going back to the payer. However,
> especially with today's dynamically calculated miner fees, this
> may often be ineffective:
>
> A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/06/2015 03:08 PM, Jeff Garzik wrote:
> Yes. You can certainly add additional inputs and outputs -- and as
> such you can increase privacy and defrag your wallet at the same
> time.
A lot could be done to make regular spends resemble CoinJoin
Yes. You can certainly add additional inputs and outputs -- and as such
you can increase privacy and defrag your wallet at the same time.
On Fri, Feb 6, 2015 at 2:11 AM, Wladimir wrote:
> On Wed, Feb 4, 2015 at 2:23 PM, Isidor Zeuner
> wrote:
>
> > A possible approach to handle this issue wou
On Wed, Feb 4, 2015 at 2:23 PM, Isidor Zeuner
wrote:
> A possible approach to handle this issue would be to add a randomized
> offset amount to the payment amount. This offset amount can be small
> in comparison to the payment amount.
>
> Any thoughts?
Adding/subtracting a randomized offset amou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/04/2015 02:23 PM, Isidor Zeuner wrote:
> Hi there,
>
> traditionally, the Bitcoin client strives to hide which output
> addresses are change addresses going back to the payer. However,
> especially with today's dynamically calculated miner f
On Wed, Feb 04, 2015 at 03:23:23PM +0100, Isidor Zeuner wrote:
> Hi there,
>
> traditionally, the Bitcoin client strives to hide which output
> addresses are change addresses going back to the payer. However,
> especially with today's dynamically calculated miner fees, this
> may often be ineffect
6 matches
Mail list logo
