From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org,
Matthew Roberts <matthew@roberts•pm>
Subject: Re: [bitcoin-dev] BIP clearing house addresses
Date: Thu, 4 Aug 2016 03:27:34 +0000 [thread overview]
Message-ID: <201608040327.36571.luke@dashjr.org> (raw)
In-Reply-To: <CAAEDBiGMGWLeC81vkojGwEqQTT1HQaE=a3z114u6=FXXM2DRtQ@mail.gmail.com>
On Wednesday, August 03, 2016 6:16:20 PM Matthew Roberts via bitcoin-dev
wrote:
> In light of the recent hack: what does everyone think of the idea of
> creating a new address type that has a reversal key and settlement layer
> that can be used to revoke transactions?
This isn't something that makes sense at the address, since it represents the
recipient and not the sender. Transactions are not sent from addresses ever.
> You could specify so that transactions "sent" from these addresses must
> receive N confirmations before they can't be revoked, after which the
> transaction is "settled" and the coins become redeemable from their
> destination output. A settlement phase would also mean that a transaction's
> progress was publicly visible so transparent fraud prevention and auditing
> would become possible by anyone.
This is already possible. Just nLockTime your withdrawls for some future
block. Don't sign any transaction that isn't nLockTime'd at least N blocks
beyond the present tip.
Luke
next prev parent reply other threads:[~2016-08-04 3:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 18:16 Matthew Roberts
2016-08-03 21:13 ` Troy Benjegerdes
2016-08-03 23:55 ` Tier Nolan
2016-08-04 2:07 ` Matthew Roberts
2016-08-04 3:27 ` Luke Dashjr [this message]
2016-08-04 3:49 ` Andrew Johnson
2016-08-04 4:53 ` Matthew Roberts
2016-08-04 12:43 ` Erik Aronesty
2016-08-06 10:39 ` s7r
2016-08-06 11:13 ` Tier Nolan
2016-08-07 5:35 ` Matthew Roberts
2016-08-07 22:59 ` Erik Aronesty
2016-08-08 0:48 ` Matthew Roberts
2016-08-08 9:56 ` Tier Nolan
2016-08-08 10:09 ` Erik Aronesty
2016-08-08 11:01 ` Tier Nolan
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=201608040327.36571.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=matthew@roberts$(echo .)pm \
/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