public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Praveen Baratam <praveen.baratam@gmail.com>
To: bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Multi CSV Transaction
Date: Tue, 20 Feb 2018 22:23:25 +0530	[thread overview]
Message-ID: <CAAQs3wucifHfjZ6VJJ2tWL-vzERzL=341aCL666MY+6_vKC-yQ@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 388 bytes --]

Hello Everybody,

I need a little clarity about how OP_CHECKSEQUENCEVERIFY (CSV) works in
transactions.

Can I use multiple CSV end points as depicted in the figure below? I
basically want to allow different conditions at different delays.

[image: Inline image 3]

I just want to know if OP_CHECKSEQUENCEVERIFY can be used to achieve the
above.

Thank you.

Praveen
ᐧ

[-- Attachment #1.2: Type: text/html, Size: 1520 bytes --]

[-- Attachment #2: Multi CSV.png --]
[-- Type: image/png, Size: 119739 bytes --]

             reply	other threads:[~2018-02-20 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-20 16:53 Praveen Baratam [this message]
2018-02-21  0:59 ` [bitcoin-dev] Multi CSV Transaction Daniel Robinson
2018-02-21  2:36   ` Praveen Baratam

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='CAAQs3wucifHfjZ6VJJ2tWL-vzERzL=341aCL666MY+6_vKC-yQ@mail.gmail.com' \
    --to=praveen.baratam@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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