From: Pieter Wuille <pieter.wuille@gmail.com>
To: Nick Pudar <nick@pudar.com>,
Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP - Dead Man's Switch
Date: Mon, 11 Dec 2017 10:26:40 -0800 [thread overview]
Message-ID: <CAPg+sBi9nYHCcN8ct=_iqWuxDFU1cPwBfbfF8WPX-w+kf6hzfQ@mail.gmail.com> (raw)
In-Reply-To: <DM5PR12MB117879D6648A97D6393F401AC8370@DM5PR12MB1178.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
On Dec 11, 2017 10:23, "Nick Pudar via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:
This topic has come up several times in recent years. While it is well
intentioned, it can have devastating outcomes for people that want to save
long term. If such a system were implemented, it would force people to move
funds around in order to not get nullified. In that process, it introduces
multiple opportunities for errors. Cold storage should be able to stay
cold. I personally would be apprehensive about implementing this kind of a
system.
Furthermore, if it rewards miners with funds that are expired, it creates
terrible incentives. Miners in their best interest could choose to censor
transactions that move funds close to their expiration time, to increase
their own future rewards.
Cheers,
--
Pieter
[-- Attachment #2: Type: text/html, Size: 1763 bytes --]
next prev parent reply other threads:[~2017-12-11 18:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 17:30 [bitcoin-dev] BIP - Dead Man's Switch Teweldemedhin Aberra
2017-12-11 18:12 ` Douglas Roark
2017-12-11 18:12 ` Nick Pudar
2017-12-11 18:26 ` Pieter Wuille [this message]
2017-12-11 18:13 ` Radoslaw Biernacki
2017-12-11 18:28 ` Chris Riley
2017-12-11 18:34 ` Luke Dashjr
2017-12-12 1:10 ` Teweldemedhin Aberra
[not found] ` <CALC81COEqhkX04MyJ=hxGgapVTqSeSYXJJUgutxWp5GbZmSSmQ@mail.gmail.com>
[not found] ` <5a2f9240.0abddf0a.0333.1139@mx.google.com>
2017-12-12 14:02 ` Ricardo Filipe
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='CAPg+sBi9nYHCcN8ct=_iqWuxDFU1cPwBfbfF8WPX-w+kf6hzfQ@mail.gmail.com' \
--to=pieter.wuille@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=nick@pudar.com \
/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