From: Robert McKay <robert@mckay•com>
To: Mike Hearn <mike@plan99•net>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Tor / SPV
Date: Wed, 15 Jan 2014 23:37:15 +0000 [thread overview]
Message-ID: <60844494f46e330ec38f9275bc33f30b@webmail.mckay.com> (raw)
In-Reply-To: <5747D5DF-879B-4A60-8BD6-18251E7D5F47@plan99.net>
On Wed, 15 Jan 2014 23:51:21 +0100, Mike Hearn wrote:
> The goal of all that is that we get to keep our existing IPv4 based
> anti-sybil heuristics, so we can’t possibly make anything worse,
> only better. Plus, we’ve now set things up so in future if/when we
> come up with a better anti-sybil system based on anonymous identities
> or other fancy crypto, we can take out the “connect via clearnet”
> step and go straight to using hidden services with only a very small
> set of code changes and no new protocol work.
I think it might be ok to use proof-of-stake on as an anti-sybil scheme
on tor.. people would obviously not want to associate their wallet with
their IP address, but is there any harm in associating it with a
(temporary) tor service id (especially one that isn't used for anything
other than relaying bitcoin transactions)? If each node you connect too
can sign some challenge with a key that controls some BTC (and your
client node verifies that the funds are different) then that might be
useful.. even if it were only a small 0.01BTC stake that would be
similar to the cost of obtaining another IP through a cheap VPS or VPN
and significantly higher than the cost to an attacker who is able to
MITM everything and operate on any IP anyway.
Rob
next prev parent reply other threads:[~2014-01-16 0:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 22:51 Mike Hearn
2014-01-15 23:07 ` Brooks Boyd
2014-01-15 23:32 ` Mike Hearn
2014-01-16 2:26 ` Brooks Boyd
2014-01-16 4:30 ` Miron
2014-01-16 10:25 ` Mike Hearn
2014-01-16 3:54 ` Isidor Zeuner
2014-01-15 23:37 ` Robert McKay [this message]
2014-01-16 4:29 ` Miron
2014-01-16 4:40 ` Miron
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=60844494f46e330ec38f9275bc33f30b@webmail.mckay.com \
--to=robert@mckay$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/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