From: "Jeremy Spilman" <jeremy@taplink•co>
To: bitcoin-development@lists•sourceforge.net,
"Peter Todd" <pete@petertodd•org>
Subject: Re: [Bitcoin-development] Privacy and blockchain data
Date: Tue, 07 Jan 2014 22:34:46 -0800 [thread overview]
Message-ID: <op.w9cu78gsyldrnw@laptop-air.hsd1.ca.comcast.net> (raw)
In-Reply-To: <20140106025312.GC2356@savin>
>
> 2) Common prefixes: Generate addresses such that for a given wallet they
> all share a fixed prefix. The length of that prefix determines the
> anonymity set and associated privacy/bandwidth tradeoff, which
> remainds a fixed ratio of all transactions for the life of the
> wallet.
>
Interesting thought to make the privacy/bandwidth trade-off using
vanitygen and prefix filters.
But doesn't this effectively expand the universe of potential spies from
'the global attacker' who is watching your SPV queries, to simply 'the
globe' -- anyone with a copy of the blockchain?
Some stats on UTXO set size: (slightly stale -- as of block 270733)
7.4m unspent outputs
2.2m transactions with unspent outputs
2.1m unique unspent scriptPubKeys
Side note: the top 1,000 scriptPubKeys have 10% of all unspent outputs.
Let's say you use an 8-bit prefix (1/256) that would be ~10,000
transactions in the UTXO you would be monitoring. But if I knew a few
different days / time-periods you transacted, I could figure out your
prefix.
Of course, anyone you transact with would know your prefix outright.
Wouldn't this also allow obvious identification of spend versus change
addresses in a transaction?
next prev parent reply other threads:[~2014-01-08 6:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 2:53 Peter Todd
2014-01-08 6:34 ` Jeremy Spilman [this message]
2014-01-10 10:10 ` Peter Todd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=op.w9cu78gsyldrnw@laptop-air.hsd1.ca.comcast.net \
--to=jeremy@taplink$(echo .)co \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=pete@petertodd$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox