public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Matt Corallo <lf-lists@mattcorallo.com>
To: Alejandro Ranchal Pedrosa <a.ranchalpedrosa@gmail.com>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>,
	Alejandro Ranchal Pedrosa via bitcoin-dev
	<bitcoin-dev@lists.linuxfoundation.org>,
	bitcoin-dev@lists.linuxfoundation.org
Cc: "TUCCI Sara" <sara.tucci@cea.fr>, "Önder GÜRCAN" <Onder.GURCAN@cea.fr>
Subject: Re: [bitcoin-dev] A BIP proposal for transactions that are 'cancellable'
Date: Thu, 06 Sep 2018 13:31:58 +0000	[thread overview]
Message-ID: <8CA4E834-061C-4EE9-A69D-CAE69A08FE7D@mattcorallo.com> (raw)
In-Reply-To: <3d4162e0-1f8b-0f23-85fc-9d18d4352cae@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1921 bytes --]

I think a simple approach to what you want to accomplish is to simply have a multisig option with a locktime pre-signed transaction which is broadcastable at the 24h mark and has different spendability. This avoids introducing reorg-induced invalidity.

On September 6, 2018 9:19:24 AM UTC, Alejandro Ranchal Pedrosa via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
>Hello everyone,
>
>We would like to propose a new BIP to extend OP_CSV (and/or OP_CLTV) in
>order for these to allow and interpret negative values. This way,
>taking the example shown in BIP 112:
>
>HASH160 <revokehash> EQUAL
>IF
>     <Bob's pubkey>
>ELSE
>     "24h" CHECKSEQUENCEVERIFY DROP
>     <Alice's pubkey>
>ENDIF
>CHECKSIG
>
>that gives ownership only to Bob for the first 24 hours and then to
>whichever spends first, we basically propose using the negative bit
>value:
>
>HASH160 <revokehash> EQUAL
>IF
>     <Bob's pubkey>
>ELSE
>     "-24h" CHECKSEQUENCEVERIFY DROP
>     <Alice's pubkey>
>ENDIF
>CHECKSIG
>
>meaning that both would have ownership for the first 24 hours, but
>after that only Bob would own such coins. Its implementation should
>not be too tedious, and in fact it simply implies considering negative
>values that are at the moment discarded as for the specification of
>BIP-112, leaving the sign bit unused.
>
>This, we argue, an increase the fairness of the users, and can at times
>be more cost-effective for users to do rather than trying a
>Replace-By-Fee
>transaction, should they want to modify such payment.
>
>We would like to have a discussion about this before proposing the
>BIP, for which we are preparing the text.
>
>You can find our paper discussing it here:
>https://hal-cea.archives-ouvertes.fr/cea-01867357 (find attached as
>well)
>
>Best,
>
>-- 
>Alejandro Ranchal Pedrosa, Önder Gürcan and Sara Tucci-Piergiovanni

[-- Attachment #2: Type: text/html, Size: 2298 bytes --]

  reply	other threads:[~2018-09-06 13:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-06  9:19 [bitcoin-dev] A BIP proposal for transactions that are 'cancellable' Alejandro Ranchal Pedrosa
2018-09-06 13:31 ` Matt Corallo [this message]
     [not found]   ` <CABaiX-2L9oVdta=aRH91uE=iPRv4cX6zU0=+oF+2oWqnu=64YQ@mail.gmail.com>
2018-09-06 16:33     ` Matt Corallo
2018-09-07  7:07       ` Alejandro Ranchal Pedrosa
2018-09-06 15:16 ` Gregory Maxwell
2018-09-06 20:32   ` Brandon Smith
2018-09-07  5:02     ` Terry McLaughlin
2018-09-07  7:12     ` Alejandro Ranchal Pedrosa
2018-09-07 12:51       ` Brandon Smith
2018-09-07 13:47         ` TUCCI Sara
2018-09-06 16:14 ` vizeet srivastava

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=8CA4E834-061C-4EE9-A69D-CAE69A08FE7D@mattcorallo.com \
    --to=lf-lists@mattcorallo.com \
    --cc=Onder.GURCAN@cea.fr \
    --cc=a.ranchalpedrosa@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=sara.tucci@cea.fr \
    /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