From: Braun Brelin <bbrelin@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Question regarding transactions with NLOCKTIME > 0
Date: Sun, 21 Jun 2015 09:10:20 +0200 [thread overview]
Message-ID: <CAJ2Ovpi_qYFqXZ9hWdobVj1Km04soXVm7GwN+M3Ay8yhZCHhGg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
Hi all,
When a transaction with N_LOCKTIME>0 is created, does that transaction get
stored in a block on the blockchain or is it stored in the mempool until
the actual time (or block number) exceeds the current value? If it is
stored on the blockchain, how does that affect the concept of pruning that
is supposed to be going in to version 0.11? I.e. if I create a transaction
that doesn't take effect for 10 years, and that transaction is stored in a
block, does that block stay on the active list for that period of time?
Thanks,
Braun Brelin
[-- Attachment #2: Type: text/html, Size: 669 bytes --]
next reply other threads:[~2015-06-21 7:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-21 7:10 Braun Brelin [this message]
2015-06-21 8:45 ` s7r
2015-06-21 12:11 ` Braun Brelin
2015-06-21 12:32 ` s7r
2015-06-21 16:54 ` Jeff Garzik
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=CAJ2Ovpi_qYFqXZ9hWdobVj1Km04soXVm7GwN+M3Ay8yhZCHhGg@mail.gmail.com \
--to=bbrelin@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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