From: Jeff Garzik <jgarzik@bitpay.com>
To: Tom Harding <tomh@thinlink.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] deterministic transaction expiration
Date: Wed, 6 Aug 2014 13:24:28 -0400 [thread overview]
Message-ID: <CAJHLa0MDhcQuZGDrJFXyExCGWaEkvXuy0zvqTgG2TqPDuzHCzQ@mail.gmail.com> (raw)
In-Reply-To: <53E25F8A.5070905@thinlink.com>
[-- Attachment #1: Type: text/plain, Size: 3557 bytes --]
That won't necessarily work through large reorgs. You don't want to create
a situation where a miner cannot mine a previously mined transactions.
On Wed, Aug 6, 2014 at 1:02 PM, Tom Harding <tomh@thinlink.com> wrote:
>
> Today we have first-eligible-height (nLockTime), and mempool expiration
> measured from this height would work for the goals being discussed, no fork
> or protocol rev.
>
> With first-eligible-height and last-eligible-height, creator could choose
> a lifetime shorter than the max, and in addition, lock the whole thing
> until some point in the future.
>
>
>
> On 8/6/2014 9:15 AM, Jeff Garzik wrote:
>
> A fork is not necessarily required, if you are talking about information
> that deals primarily with pre-consensus mempool behavior. You can make a
> "network TX" with some information that is digitally signed, yet discarded
> before it reaches miners.
>
>
> On Wed, Aug 6, 2014 at 11:42 AM, Peter Todd <pete@petertodd.org> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>>
>>
>> On 6 August 2014 08:17:02 GMT-07:00, Christian Decker <
>> decker.christian@gmail.com> wrote:
>> >+1 for the new field, overloading fields with new meaning is definitely
>> >not
>> >a good idea.
>>
>> To add a new field the best way to do it is create a new, parallel, tx
>> format where fields are committed by merkle radix tree in an extensible and
>> provable way. You'd then commit to that tree with a mandatory OP_RETURN
>> output in the last txout, or with a new merkle root.
>>
>> Changing the tx format itself in a hard-fork is needlessly disruptive,
>> and in this case, wastes opportunities for improvement.
>> -----BEGIN PGP SIGNATURE-----
>> Version: APG v1.1.1
>>
>> iQFQBAEBCAA6BQJT4kzQMxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8
>> cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhamzCAC+zRaXRodP63+ke3K+
>> Viapiepvk4uIOlqxqtMB2O0zWcyu2+xCJDiRPykK/6HLDBeFDEC9/dGK8++Lovl6
>> //qZ340LOPFlgT2kYy9E5h/yX469fhtsWhBCv2K47fWwkMS0S/0r4SQnCkbt2R2c
>> 4dQjkoldhw6rNMBTUmwvhSlL30KsT/msWTZiX7DW/YjfOzezEJzy+mYyKp9Sk7ba
>> 1fOiBXORk7mNOs7sTYTvje3sqEGpGTOLP08cY/RCEvl6bG8mHkPqwiojq+3biHFP
>> RsoBVu1f5cbnU7Wq0gPNdVnQssnEQDadyTX8gT0Wze7PuVyaZT2mXFZBKzSHuLy2
>> sJKN
>> =oPSo
>> -----END PGP SIGNATURE-----
>>
>>
>
>
> --
> Jeff Garzik
> Bitcoin core developer and open source evangelist
> BitPay, Inc. https://bitpay.com/
>
>
> ------------------------------------------------------------------------------
> Infragistics Professional
> Build stunning WinForms apps today!
> Reboot your WinForms applications with our WinForms controls.
> Build a bridge from your legacy apps to the future.http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
>
>
>
> _______________________________________________
> Bitcoin-development mailing listBitcoin-development@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
>
> ------------------------------------------------------------------------------
> Infragistics Professional
> Build stunning WinForms apps today!
> Reboot your WinForms applications with our WinForms controls.
> Build a bridge from your legacy apps to the future.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
[-- Attachment #2: Type: text/html, Size: 6061 bytes --]
next prev parent reply other threads:[~2014-08-06 17:24 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 0:58 [Bitcoin-development] deterministic transaction expiration Kaz Wesley
2014-08-01 1:06 ` Peter Todd
2014-08-01 1:37 ` Kaz Wesley
2014-08-01 1:38 ` Matt Whitlock
2014-08-01 2:28 ` Gregory Maxwell
2014-08-01 3:26 ` Matt Whitlock
2014-08-01 3:31 ` Gregory Maxwell
2014-08-05 18:01 ` Alex Mizrahi
2014-08-02 0:36 ` Tom Harding
2014-08-05 17:02 ` Flavien Charlon
2014-08-05 17:48 ` Jeff Garzik
2014-08-05 18:54 ` Mike Hearn
2014-08-05 19:08 ` Jeff Garzik
2014-08-05 19:10 ` Kaz Wesley
2014-08-05 19:36 ` Jeff Garzik
2014-08-06 4:01 ` Tom Harding
2014-08-06 12:55 ` Jeff Garzik
2014-08-06 13:54 ` Mike Hearn
2014-08-06 14:44 ` Tom Harding
2014-08-06 15:08 ` Jeff Garzik
2014-08-06 15:17 ` Christian Decker
2014-08-06 15:42 ` Peter Todd
2014-08-06 16:15 ` Jeff Garzik
2014-08-06 17:02 ` Tom Harding
2014-08-06 17:21 ` Mark Friedenbach
2014-08-06 17:34 ` Peter Todd
2014-08-06 17:24 ` Jeff Garzik [this message]
2014-08-06 16:31 ` Mark Friedenbach
2014-08-06 17:20 ` Peter Todd
2014-08-06 17:30 ` Mark Friedenbach
2014-08-06 17:38 ` Peter Todd
2014-08-08 17:38 ` Tom Harding
2014-08-08 18:13 ` Jeff Garzik
2014-08-08 18:42 ` Kaz Wesley
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=CAJHLa0MDhcQuZGDrJFXyExCGWaEkvXuy0zvqTgG2TqPDuzHCzQ@mail.gmail.com \
--to=jgarzik@bitpay.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=tomh@thinlink.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