From: Mike Hearn <mike@plan99•net>
To: Patrick Strateman <patrick@intersango•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] CTxIn::nSequence
Date: Fri, 21 Jun 2013 10:20:06 +0200 [thread overview]
Message-ID: <CANEZrP3fRf5T+MtMs01iAoK6op3gte8Dv99=kwgW3Y5KwiUg-Q@mail.gmail.com> (raw)
In-Reply-To: <51C3D0AE.4080101@intersango.com>
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
Indeed, and for a higher level answer, see here:
https://en.bitcoin.it/wiki/Contracts
On Fri, Jun 21, 2013 at 6:03 AM, Patrick Strateman
<patrick@intersango•com>wrote:
> It's well answered by this stack exchange question.
>
> http://bitcoin.stackexchange.com/questions/2025/what-is-txins-sequence
>
>
> On 06/20/2013 05:54 PM, Marko Otbalkana wrote:
>
> Could anyone tell me what CTxIn::nSequence is meant for?
>
> Best Regards,
> -Marko
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
> http://p.sf.net/sfu/windows-dev2dev
>
>
>
> _______________________________________________
> Bitcoin-development mailing listBitcoin-development@lists•sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
[-- Attachment #2: Type: text/html, Size: 2761 bytes --]
prev parent reply other threads:[~2013-06-21 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 0:54 Marko Otbalkana
2013-06-21 4:03 ` Patrick Strateman
2013-06-21 8:20 ` Mike Hearn [this message]
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='CANEZrP3fRf5T+MtMs01iAoK6op3gte8Dv99=kwgW3Y5KwiUg-Q@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=patrick@intersango$(echo .)com \
/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