public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Joseph Poon <joseph@lightning•network>
To: Benjamin <benjamin.l.cordes@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] trust
Date: Mon, 10 Aug 2015 21:17:53 -0700	[thread overview]
Message-ID: <20150811041736.GA21351@lightning.network> (raw)
In-Reply-To: <CAOoPuRbTtr1Mu1MtvJ_j0Gp9kt4O=dOLrUwgp82H-smAbwqrOg@mail.gmail.com>

Hi Benjamin,

On Sat, Aug 08, 2015 at 02:01:58PM +0200, Benjamin via bitcoin-dev wrote:
> How do you know who is who online? 

If a node is not online, then the payment can be cancelled and
re-routed.

> If Alice and Bob want to transact and haven't exchanged keys before
> they need public-key infrastructure out-of-band to identify
> themselves. Which means they are using SSL and Certificate authorities
> and trust them. 

Lightning doesn't solve the key exchange problem (perhaps something like
Namecoin will help in the future). Bitcoin faces this problem today. How
do you know the bitcoin address belongs to the recipient without
trusting CAs? What if, in the case of the majority of bitcoin payments
today, the bitcoin address was not signed and the recipient claimed to
have never received their funds? There should be signed proof of payment
in every transaction for this reason.

> If you have non-cooperative hubs they could flood the network and make
> it unusable. And why should hubs cooperate? There are no incentives in
> the system.

There are some incentives towards keeping the system functional via
fees. If you attempt to flood the system, you'll likely be paying some
fees -- someone running a node will not interpret it as an attack, as
they're getting some money (probabably substantially higher as they will
increase fees to ensure network availability).

I agree that it's very important to think through varius attack models.

-- 
Joseph Poon


  reply	other threads:[~2015-08-11  4:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-08  6:10 Thomas Zander
2015-08-08  8:39 ` Adam Back
2015-08-08  8:54   ` Thomas Zander
2015-08-08  9:24     ` Benjamin
2015-08-08 11:08       ` s7r
2015-08-08 12:01         ` Benjamin
2015-08-11  4:17           ` Joseph Poon [this message]
2015-08-08 11:59       ` Milly Bitcoin
2015-08-08 11:54     ` Adam Back
2015-08-08 12:37       ` Thomas Zander
2015-08-10 20:17         ` Jorge Timón
2015-08-10 20:43           ` Milly Bitcoin
2015-08-10 21:43           ` Thomas Zander
2015-08-08  9:05 ` Venzen Khaosan
2015-08-10 21:45 ` Gregory Maxwell

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=20150811041736.GA21351@lightning.network \
    --to=joseph@lightning$(echo .)network \
    --cc=benjamin.l.cordes@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.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