public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Alex Kotenko <alexykot@gmail.com>
To: Mike Hearn <mike@plan99.net>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	Lawrence Nahum <lawrence@greenaddress.it>
Subject: Re: [Bitcoin-development] instant confirmation via payment protocol backwards compatible proto buffer extension
Date: Mon, 16 Jun 2014 21:32:40 +0100	[thread overview]
Message-ID: <CALDj+BYYp_d5t4vNs9t3D0SCW4mPjVR+X4J=VyrkxuiFsYkS=g@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP384LFKaCbAL-p06FQdHHp1bqmcRs+XZDbwVXVrPRDS7g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 913 bytes --]

True, enough philosophy. Once this BIP will be finalized - we will it's
schedule implementation in XBTerminal. This is a solution to the problem we
have, probably best one we have to date, so we will use it.


2014-06-16 19:09 GMT+01:00 Mike Hearn <mike@plan99.net>:

> I think many of us feel it'd be better if this kind of thing were not
> needed at all, however, the best way to ensure it doesn't end up being used
> is to write code, not to try and block alternative approaches. If Bitcoin
> is robust the market should sort it out. If it's robust for some
> transactions and not others, that makes for a fun project for a future
> generation of hackers to sort out.
>
> OK, enough philosophy - let's try and keep this thread just for discussion
> of the BIP itself from now on. If you'd like to continue debating the
> Future of Bitcoin please change the subject line and break it out into a
> new thread.
>

[-- Attachment #2: Type: text/html, Size: 1390 bytes --]

  parent reply	other threads:[~2014-06-16 20:33 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-14 12:00 [Bitcoin-development] instant confirmation via payment protocol backwards compatible proto buffer extension Lawrence Nahum
2014-06-14 12:57 ` Andreas Schildbach
2014-06-15  9:22   ` Lawrence Nahum
2014-06-15 12:46     ` Andreas Schildbach
2014-06-15 14:09       ` Lawrence Nahum
2014-06-18 12:09       ` Lawrence Nahum
2014-06-18 13:25         ` Mike Hearn
2014-06-18 15:59           ` Daniel Rice
2014-06-18 16:09             ` Mike Hearn
2014-06-19 17:36               ` Daniel Rice
2014-06-25 14:01         ` sebastien requiem
2014-06-16 12:19 ` Mike Hearn
2014-06-16 12:25   ` Mike Hearn
2014-06-16 15:09   ` Daniel Rice
2014-06-16 15:26     ` Lawrence Nahum
2014-06-16 16:00       ` Daniel Rice
2014-06-16 16:07         ` Mike Hearn
2014-06-16 15:41     ` Paul Goldstein
2014-06-16 15:48       ` Mike Hearn
2014-06-16 16:30         ` Lawrence Nahum
2014-06-16 16:45           ` Mike Hearn
2014-06-16 16:56             ` Lawrence Nahum
2014-06-16 17:01               ` Mike Hearn
2014-06-16 17:16                 ` Lawrence Nahum
2014-06-16 18:02                   ` Alex Kotenko
2014-06-16 18:09                     ` Mike Hearn
2014-06-16 20:29                       ` Daniel Rice
2014-06-16 20:32                         ` Mike Hearn
2014-06-16 20:37                           ` Daniel Rice
2014-06-16 20:46                             ` Mike Hearn
2014-06-16 20:53                               ` Daniel Rice
2014-06-16 20:55                                 ` Mike Hearn
2014-06-16 20:50                             ` [Bitcoin-development] Fidelity bonds for decentralized instant confirmation guarantees Peter Todd
2014-06-16 21:02                         ` [Bitcoin-development] instant confirmation via payment protocol backwards compatible proto buffer extension Daniel Rice
2014-06-16 20:32                       ` Alex Kotenko [this message]
2014-06-16 17:44                 ` Jorge Timón
2014-06-17 15:58                 ` Isidor Zeuner
2014-06-18  1:39         ` Tom Harding
2014-06-17 15:58     ` Isidor Zeuner
2014-06-18  9:15       ` Mike Hearn
2014-06-18 20:47       ` Natanael
2014-06-18  2:01     ` Tom Harding
2014-06-16 15:28   ` Lawrence Nahum
2014-06-16 15:43     ` Mike Hearn
2014-06-16 17:05       ` Lawrence Nahum
2014-06-16  8:53 Daniel Rice

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='CALDj+BYYp_d5t4vNs9t3D0SCW4mPjVR+X4J=VyrkxuiFsYkS=g@mail.gmail.com' \
    --to=alexykot@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=lawrence@greenaddress.it \
    --cc=mike@plan99.net \
    /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