From: Sergio Demian Lerner <sergio.d.lerner@gmail.com>
To: Natanael <natanael.l@gmail.com>
Cc: Arnoud Kouwenhoven - Pukaki Corp via 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 20:08:02 -0300 [thread overview]
Message-ID: <CAKzdR-ofEnFxUeGSNyMLKrbFu6F8qoYnDaf=gWvwWu_b0+AXWg@mail.gmail.com> (raw)
In-Reply-To: <CAAt2M19Hp-rXbqTvQN8A24Ojmc=8O0agbaAD5hLOj1zt-Rf+-A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1956 bytes --]
In some rare occasions in everyday life, what matters is seconds. Like when
paying for parking in the car while some other cars are behind you in the
line. You don't want them to get upset.
I takes me tens of minutes to shop. But once you choose your merchandise
and your payment starts processing, if the payment system allows several
payments to be pending simultaneously and you're not blocking the next
person to pay, then I don't care waiting some minutes for confirmation. But
saving 10 minutes of confirmation is a lot.
I ague that our time is mostly measured in minutes (but I don't have any
sociological, cultural, genetic or anthropological evidence). It takes
minutes to read an e-mail, minutes to correct a bug, minutes to have lunch,
minutes to drive to the office, minutes to talk to your kids. A payment
taking 1 minute is much better than a payment taking 10. If I could choose
a single thing to change to Bitcoin, I would lower the payment time, even
within the minute scale.
Sergio
On Fri, Aug 7, 2015 at 7: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: 2560 bytes --]
next prev parent reply other threads:[~2015-08-07 23:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 21:18 [bitcoin-dev] If you had a single chance to double the transactions/second Bitcoin allows 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
2015-08-07 23:08 ` Sergio Demian Lerner [this message]
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='CAKzdR-ofEnFxUeGSNyMLKrbFu6F8qoYnDaf=gWvwWu_b0+AXWg@mail.gmail.com' \
--to=sergio.d.lerner@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=natanael.l@gmail.com \
/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