public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: Luke Dashjr <luke@dashjr.org>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Softfork proposal for minimum price of $50k USD/BTC
Date: Sun, 31 Mar 2019 21:11:12 -0400	[thread overview]
Message-ID: <20190401011112.6icdkyjocf4qh5oz@petertodd.org> (raw)
In-Reply-To: <201904010030.34825.luke@dashjr.org>

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

On Mon, Apr 01, 2019 at 12:30:34AM +0000, Luke Dashjr via bitcoin-dev wrote:
> Certain parts of the community have been selling bitcoins for unreasonably
> low prices. This has halted Bitcoin's valuation at $20k and even driven the
> price down below $15k! However, clearly Bitcoin is worth much more than
> that, and there is widespread support for higher prices.
> 
> In light of this, I have written and implemented two BIPs: one to add a
> signed price field to Bitcoin transactions, and the other to softfork a
> minimum price of $50k USD/BTC a year from today.

I believe I've found a serious vulnerability in your proposal: there's no limit
on the maximum supply of USD.

-- 
https://petertodd.org 'peter'[:-1]@petertodd.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2019-04-01  1:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01  0:30 [bitcoin-dev] Softfork proposal for minimum price of $50k USD/BTC Luke Dashjr
2019-04-01  1:04 ` Ricardo Filipe
2019-04-01  2:57   ` Thomas France
2019-04-01  3:04   ` Dave Scotese
2019-04-01  1:11 ` Peter Todd [this message]
2019-04-01  2:55   ` Omar Shibli
2019-04-01  3:02   ` ZmnSCPxj
2019-04-01  3:07   ` Satoshin
2019-04-01  8:55     ` LORD HIS EXCELLENCY JAMES HRMH
2019-04-01  2:54 ` Omar Shibli
2019-04-01 11:22 ` Melvin Carvalho
2019-04-01 11:50   ` Dana L. Coe
2019-04-02 16:48     ` Aymeric Vitte

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=20190401011112.6icdkyjocf4qh5oz@petertodd.org \
    --to=pete@petertodd.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=luke@dashjr.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