public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Satoshin <satoshin@mybitcoincenter•com>
To: Peter Todd <pete@petertodd•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 23:07:41 -0400	[thread overview]
Message-ID: <5D9DDB14-9E0F-419B-A069-25448F1FA473@mybitcoincenter.com> (raw)
In-Reply-To: <20190401011112.6icdkyjocf4qh5oz@petertodd.org>

Hi Everyone,
     First portion of your First BIP is excellent- with this field the protocol can actually attain HFT- by  pinning of value at time of trade for later unblock scaling as a mark to market tool which is used in HFT.

The Second BIP of a minimum price would never allow Bitcoin to pass the SEC test of a viable asset. - I hope that portion was actually a Joke since it makes no sense economically. 
If one has ever seen a stock drop 90% in one day then you would understand the volatile nature of future valuation.

Prices have to be able to go higher and lower based on market demand and not tethering to perceived norms. If the US dollar was crashed and it went down to Venezuelan currency levels [hypothetically then where would your 50k limit lead the currency} Never say never- 

Best Regards
XX
 
> On Mar 31, 2019, at 9:11 PM, Peter Todd via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> 
> 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
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev



  parent reply	other threads:[~2019-04-01  3:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01  0:30 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
2019-04-01  2:55   ` Omar Shibli
2019-04-01  3:02   ` ZmnSCPxj
2019-04-01  3:07   ` Satoshin [this message]
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=5D9DDB14-9E0F-419B-A069-25448F1FA473@mybitcoincenter.com \
    --to=satoshin@mybitcoincenter$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=pete@petertodd$(echo .)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