public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Adam Back <adam@cypherspace.org>
To: Benjamin <benjamin.l.cordes@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] A Proposed Compromise to the Block Size Limit
Date: Sun, 28 Jun 2015 14:37:57 +0200	[thread overview]
Message-ID: <CALqxMTGXcbES5Pwz3cWO+PQK5kmf3rZ_i00=b=PBnO678XuF0A@mail.gmail.com> (raw)
In-Reply-To: <CAOoPuRarNoPwLxVqjJ_g4b6HsWJecB-oCdfEjaknKbUnKdnmEg@mail.gmail.com>

On 28 June 2015 at 12:29, Benjamin <benjamin.l.cordes@gmail.com> wrote:
> I agree that naive scaling will likely lead to bad outcomes. They might have
> the advantage though, as this would mean not changing Bitcoin.

Sure we can work incrementally and carefully, and this is exactly what
Bitcoin has been doing, and *must* do for safety and security for the
last 5 years!
That doesnt mean that useful serious improvements have not been made.

> Level2 and Lightning is not well defined. If you move money to a third
> party, even if it is within the constrained of a locked contract, then I
> don't think that will solve the issues.

I think you misunderstand how lightning works.  Every lightning
transaction *is* a valid bitcoin transaction that could be posted to
the Bitcoin network to reclaim funds if a hub went permanently
offline.  It is just that while the hubs involved remain in service,
there is no need to do so.  This is why it has been described as a
(write coalescing) write cache layer for Bitcoin.>

I believe people expect lightning to be peer 2 peer like bitcoin.

Adam


  reply	other threads:[~2015-06-28 12:37 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-28  5:34 [bitcoin-dev] A Proposed Compromise to the Block Size Limit Raystonn
2015-06-28 10:07 ` Adam Back
2015-06-28 10:29   ` Benjamin
2015-06-28 12:37     ` Adam Back [this message]
2015-06-28 16:32       ` Raystonn .
2015-06-28 17:12         ` Mark Friedenbach
2015-06-28 17:18           ` Benjamin
2015-06-28 17:29           ` Gavin Andresen
2015-06-28 17:45             ` Mark Friedenbach
2015-06-28 17:51             ` Adam Back
2015-06-28 18:58               ` Adam Back
2015-06-28 21:05                 ` Gavin Andresen
2015-06-28 21:23                   ` Michael Naber
2015-06-28 22:07                   ` Adam Back
2015-06-29  0:59                     ` Eric Lombrozo
2015-06-29  1:13                     ` Eric Lombrozo
2015-06-29  1:45                     ` Andy Schroder
2015-06-30  0:42                     ` Tom Harding
2015-07-10  2:55                 ` Tom Harding
2015-06-28 17:53             ` Jorge Timón
2015-06-28 19:22             ` Andrew Lapp
2015-06-28 19:40               ` Benjamin
2015-06-28 12:32   ` Milly Bitcoin
  -- strict thread matches above, loose matches on Subject: below --
2015-06-27 14:39 Michael Naber
2015-06-27 15:21 ` Peter Todd
2015-06-27 15:29   ` Randi Joseph
2015-06-27 15:32     ` Peter Todd
2015-06-27 16:19   ` Michael Naber
2015-06-27 17:20     ` Peter Todd
2015-06-27 17:26       ` Benjamin
2015-06-27 17:37         ` Peter Todd
2015-06-27 17:46           ` Benjamin
2015-06-27 17:54             ` Peter Todd
2015-06-27 17:58               ` Venzen Khaosan
2015-06-27 19:34               ` Benjamin
2015-06-27 15:33 ` Adam Back
2015-06-27 16:09   ` Michael Naber
2015-06-27 16:28     ` Mark Friedenbach
2015-06-27 16:37     ` Peter Todd
2015-06-27 17:25       ` Michael Naber
2015-06-27 17:34         ` Peter Todd
2015-06-27 18:02           ` Jameson Lopp
2015-06-27 18:47             ` 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='CALqxMTGXcbES5Pwz3cWO+PQK5kmf3rZ_i00=b=PBnO678XuF0A@mail.gmail.com' \
    --to=adam@cypherspace.org \
    --cc=benjamin.l.cordes@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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