From: Peter Todd <pete@petertodd•org>
To: Anthony Towns <aj@erisian•com.au>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Surprisingly, Tail Emission Is Not Inflationary
Date: Mon, 11 Jul 2022 12:59:53 -0400 [thread overview]
Message-ID: <YsxXCQihhSrYuIfS@petertodd.org> (raw)
In-Reply-To: <20220711023247.GA21856@erisian.com.au>
[-- Attachment #1: Type: text/plain, Size: 2108 bytes --]
On Mon, Jul 11, 2022 at 12:32:47PM +1000, Anthony Towns wrote:
> This isn't necessarily true: if the losses are due to a common cause,
> then they'll be heavily correlated rather than independent; for example
> losses could be caused by a bug in a popular wallet/exchange software
> that sends funds to invalid addresses, or by a war or natural disaster
> that damages key storage hardware. They're also not independent over
> time -- people improve their key storage habits over time; eg switching
> to less buggy wallets/exchanges, validating addresses before using them,
> using distributed multisig to prevent a localised disaster from being
> catastrophic.
People clearly continue to make downright irrational decisions about coin
security, doing things putting their entire crypto savings at risk for claimed
5% returns.
Even if people were rational, the coin loss rate would clearly reach a floor
because as the probability of coin loss goes down, bothering to spend extra
effort to decrease that already small chance is pointless. You mentioning black
swan events actually strengthens my point: at low coin loss rates the true loss
rate is dominated by black swan events. So it's pointless to go to extra effort
to prevent them.
Finally, you're forgetting that coin loss also includes *intentional* losses
from proof-of-sacrifice protocols. There are a number of examples on Bitcoin.
Again, they put a floor on how much coin loss could diminish.
> loss rate. If that's the case, then the rate at which funds are lost will
> vary chaotically, leading to "inflationary" periods in between events,
> and comparatively strong deflationary shocks when these events occur.
Give me an example of an *actual* inflation rate you expect to see, given a
disaster of a given magnitude.
If you actually do the numbers on this, you'll realize it takes absolutely
catastrophic black swan events that make WW2 look like a minor conflict to make
even insignificant inflation rate changes due to changes in lost coins.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-07-11 17:00 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 12:46 Peter Todd
2022-07-09 14:26 ` Eric Voskuil
2022-07-09 15:15 ` Peter Todd
2022-07-09 15:24 ` Eric Voskuil
2022-07-09 15:31 ` Peter Todd
2022-07-09 17:43 ` naman naman
2022-07-09 17:48 ` Peter Todd
2022-07-10 6:54 ` naman naman
2022-07-10 2:10 ` Tobin Harding
2022-07-10 7:08 ` vjudeu
2022-07-11 18:25 ` Larry Ruane
2022-07-10 10:18 ` Jacob Eliosoff
2022-07-11 2:32 ` Anthony Towns
2022-07-11 6:15 ` Stefan Richter
2022-07-11 10:42 ` Giuseppe B
2022-07-11 12:56 ` Erik Aronesty
2022-07-11 23:57 ` Anthony Towns
2022-07-13 18:29 ` Zac Greenwood
2022-07-11 16:59 ` Peter Todd [this message]
2022-07-11 17:44 ` Bram Cohen
2022-07-13 14:06 ` Alfred Hodler
2022-07-09 14:57 John Tromp
2022-07-09 15:13 ` Peter Todd
2022-07-11 18:44 ` Dave Scotese
2022-07-09 20:53 Eric Voskuil
2022-07-09 20:54 Eric Voskuil
2022-07-09 21:59 ` ZmnSCPxj
2022-07-10 14:17 ` alicexbt
2022-07-10 16:38 ` alicexbt
2022-07-10 17:29 ` Peter Todd
2022-07-10 17:27 ` Peter Todd
2022-07-10 18:12 ` vjudeu
2022-07-18 11:34 ` David A. Harding
2022-07-18 19:14 ` Erik Aronesty
2022-07-18 21:48 ` Eric Voskuil
2022-07-25 15:04 ` Erik Aronesty
2022-07-26 15:44 ` jk_14
2022-07-26 17:05 ` Erik Aronesty
2022-07-09 22:21 Peter
[not found] <mailman.80287.1657405305.8511.bitcoin-dev@lists.linuxfoundation.org>
2022-07-10 7:44 ` John Tromp
2022-07-10 17:42 Eric Voskuil
2022-07-19 18:36 Peter
2022-07-20 14:35 ` Eric Voskuil
2022-07-26 20:01 jk_14
2022-08-15 21:46 jk_14
2022-08-17 11:10 ` Erik Aronesty
2022-08-16 16:05 Peter
2022-08-19 17:21 ` aliashraf.btc At protonmail
2022-08-20 15:30 ` Billy Tetrud
2022-08-17 8:54 jk_14
2022-08-17 13:43 jk_14
2022-08-18 15:29 ` Breno Brito
2022-08-18 15:44 ` Billy Tetrud
2022-08-18 20:49 ` Erik Aronesty
2022-08-18 20:22 jk_14
2022-08-19 5:34 vjudeu
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=YsxXCQihhSrYuIfS@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=aj@erisian$(echo .)com.au \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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