From: Flavien Charlon <flavien.charlon@coinprism•com>
To: Peter Todd <pete@petertodd•org>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP 65 and OP_CHECKLOCKTIMEVERIFY inquiry...
Date: Fri, 28 Nov 2014 11:45:19 +0000 [thread overview]
Message-ID: <CABbpET_VLEZ5W+gTJWYXhafTDWd-dqj79iXjPFkARwV0K3CJTg@mail.gmail.com> (raw)
In-Reply-To: <3A394B8C-FD24-4134-A8B8-CCAF63ECB5B0@petertodd.org>
[-- Attachment #1: Type: text/plain, Size: 2483 bytes --]
> This breaks existing invariants and would make the coins potentially less
fungible because they wouldn't be reorg safe.
I'm not sure coins are ever reorg safe. All it takes is a double spend in
the history of your coins for them to become invalid after a reorg. Because
of that, there are already less fungible coins. This is why we recommend 6
confirmations for important payments.
On Fri, Nov 28, 2014 at 3:18 AM, Peter Todd <pete@petertodd•org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
>
>
> On 27 November 2014 18:46:23 GMT-05:00, Gregory Maxwell <
> gmaxwell@gmail•com> wrote:
>
> <snip 100% accurate commentary from gmaxwell>
>
> >The things you're suggesting were all carefully designed out of the
> >proposal, perhaps the BIP text needs some more clarification to make
> >this more clear.
>
> It does; it is still a draft. That said I think writing up some actual
> working examples, in code, of CHECKLOCKTIMEVERIFY using protocols is a
> bigger priority. Micropayment channels comes to mind, as well as a
> greenaddress-style wallet.
>
> When I get a chance I'm going to rebase the initial implementation and add
> to it a command-line-flag to verify CHECKLOCKTIMEVERIFY as an IsStandard()
> rule for testing purposes.
> -----BEGIN PGP SIGNATURE-----
> Version: APG v1.1.1
>
> iQFQBAEBCAA6BQJUd+luMxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8
> cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhWmcB/0UK030Q6TSpi95x0Gh
> hGYaSAInUWpbZzZtP+1AFrGDGRdGo0glFFf8xggI+U5kuc0woPYrn/VEGcprPhvs
> KQFZrirXVr7Q09TVlHiPDen5v3Y7xwL5kQDUrBPP71Pe3R2o6IbfdwxsZ8+yYso8
> hY6WQmImQpKJd4gEd76w1QrF8Btl1Jz/PGh4EE3GSPGlflvBwA6igSiRoD/czb1x
> 63y4AsPEil2hrmIjTZHqwnl40BqnmZ8qpNLWeIEjE++pbkxLTjvUcPy03/wtTWZA
> 5dCGeY5WavgZsPazhSdaTtM5/7wPSQQ0PDXNHdHgmewkvbyBpy78orV/3bEG+xFz
> 2SWi
> =4OmI
> -----END PGP SIGNATURE-----
>
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
>
> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 3343 bytes --]
next prev parent reply other threads:[~2014-11-28 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 22:56 Richard Moore
2014-11-27 23:46 ` Gregory Maxwell
2014-11-28 3:18 ` Peter Todd
2014-11-28 11:45 ` Flavien Charlon [this message]
2014-11-28 12:03 ` 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=CABbpET_VLEZ5W+gTJWYXhafTDWd-dqj79iXjPFkARwV0K3CJTg@mail.gmail.com \
--to=flavien.charlon@coinprism$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=pete@petertodd$(echo .)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