From: Mark Friedenbach <mark@friedenbach•org>
To: Natanael <natanael.l@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] If you had a single chance to double the transactions/second Bitcoin allows...
Date: Fri, 7 Aug 2015 16:01:05 -0700 [thread overview]
Message-ID: <CAOG=w-vSVsceZg2OmBGMBfN0Hci2r8cwiOeyYwxBbwaFLK09kg@mail.gmail.com> (raw)
In-Reply-To: <CAAt2M19Hp-rXbqTvQN8A24Ojmc=8O0agbaAD5hLOj1zt-Rf+-A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1717 bytes --]
Actually I gave a cached answer earlier which on further review may need
updating. (Bad Mark!)
I presume by "what's more likely to matter is seconds" you are referencing
point of sale. As you mention yourself, lightning network or green address
style payment escrow obviates the need for short inter-block times.
But with lightning there is a danger of channels being exhausted in the
time between blocks, causing the need for new channels to be established.
So lightning does in fact benefit from moderately shorter inter-block
times, although how much of an issue this will be is anyone's guess now.
Still the first two points about larger SPV proofs and selfish mining still
hold true, which sets the bar particularly high for justifying more
frequent blocks.
On Fri, Aug 7, 2015 at 3:46 PM, Natanael <natanael.l@gmail•com> wrote:
> Den 7 aug 2015 23:37 skrev "Sergio Demian Lerner via bitcoin-dev" <
> bitcoin-dev@lists•linuxfoundation.org>:
> >
> > Mark,
> > It took you 3 minutes to respond to my e-mail. And I responded to you 4
> minutes later. If you had responded to me in 10 minutes, I would be of out
> the office and we wouldn't have this dialogue. So 5 minutes is a lot of
> time.
> >
> > Obviously this is not a technical response to the technical issues you
> argue. But "minutes" is a time scale we humans use to measure time very
> often.
>
> But what's more likely to matter is seconds. What you need then is some
> variant of multisignature notaries (Greenaddress.it, lightning network),
> where the combination of economic incentives and legal liability gives you
> the assurance of doublespend protection from the time of publication of the
> transaction to the first block confirmation.
>
[-- Attachment #2: Type: text/html, Size: 2254 bytes --]
next prev parent reply other threads:[~2015-08-07 23:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 21:18 Sergio Demian Lerner
2015-08-07 21:27 ` Mark Friedenbach
2015-08-07 21:37 ` Sergio Demian Lerner
2015-08-07 22:46 ` Natanael
2015-08-07 23:01 ` Mark Friedenbach [this message]
2015-08-07 23:08 ` Sergio Demian Lerner
2015-08-07 23:17 ` Mark Friedenbach
2015-08-10 20:44 ` Michael Ruddy
2015-08-10 21:01 ` Pieter Wuille
2015-08-10 22:11 ` Sergio Demian Lerner
2015-08-10 22:31 ` Pieter Wuille
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='CAOG=w-vSVsceZg2OmBGMBfN0Hci2r8cwiOeyYwxBbwaFLK09kg@mail.gmail.com' \
--to=mark@friedenbach$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=natanael.l@gmail$(echo .)com \
/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