public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Jorge Timón" <jtimon@jtimon.cc>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] CHECKSEQUENCEVERIFY - We need more usecases to motivate the change
Date: Mon, 19 Oct 2015 12:43:05 +0200	[thread overview]
Message-ID: <CABm2gDpGUgK5UMqfsZZBfyuxs4hb+N1Y23if_J8EmXisAqiRUA@mail.gmail.com> (raw)
In-Reply-To: <878u73hadl.fsf@rustcorp.com.au>

On Fri, Oct 16, 2015 at 3:26 AM, Rusty Russell via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> ... Gavin just told me about setmocktime.  That's fast service!

Once more functions (specially consensus-critical functions) take
nTime explicitly as parameter instead of relying on the
library-unfriendly GetAdjustedTime(), then SetMockTime() will be less
necessary for testing. For example, see
https://github.com/jtimon/bitcoin/commit/88a35548518a27c7d24efe064e1bf4e5b3029578#diff-524ba4b43aa70d393ef51ab42a6d25f2L52


  reply	other threads:[~2015-10-19 10:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-03 14:30 [bitcoin-dev] CHECKSEQUENCEVERIFY - We need more usecases to motivate the change Peter Todd
2015-10-03 18:49 ` jl2012
2015-10-04  8:35 ` Anthony Towns
2015-10-04 12:04   ` s7r
2015-10-05 22:03     ` Alex Morcos
2015-10-06  0:19       ` Mark Friedenbach
2015-10-06 11:09         ` Peter Todd
2015-10-06  0:28 ` Btc Drak
2015-10-06  1:58 ` Rusty Russell
2015-10-08 17:41   ` Peter Todd
2015-10-09  1:38     ` Rusty Russell
2015-10-15 13:47       ` Alex Morcos
2015-10-15 16:27         ` Btc Drak
2015-10-15 16:37           ` Adam Back
2015-10-15 16:41             ` Alex Morcos
2015-10-15 18:31             ` Mark Friedenbach
2015-10-15 23:18           ` Rusty Russell
2015-10-16  1:26             ` Rusty Russell
2015-10-19 10:43               ` Jorge Timón [this message]
2015-10-06 20:00 ` Joseph Poon
2015-10-08 17:43 ` Peter Todd

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=CABm2gDpGUgK5UMqfsZZBfyuxs4hb+N1Y23if_J8EmXisAqiRUA@mail.gmail.com \
    --to=jtimon@jtimon.cc \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=rusty@rustcorp.com.au \
    /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