From: Daniel Newton <djpnewton@gmail.com>
To: Benjamin <benjamin.l.cordes@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Liquid
Date: Wed, 14 Oct 2015 08:37:56 +1300 [thread overview]
Message-ID: <CAOUBo+9D7LQ-S6Rown_sbxxb9366cQj0c0HcU72B=4sBmmS0rg@mail.gmail.com> (raw)
In-Reply-To: <CAOoPuRasL-fmQJMfmF-JVyogdMy0EVKfhUAmT44DxQq--XCdKQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2373 bytes --]
>Again – what does Bitcoin have to do with “market liquidity” and “capital
requirements”?
You seem to be conflating bitcoin with blockstream/liquid. Your question
does not make sense.
>Does Blockstream have commercial products now?
Yes. I am sure that was always their plan in order to stay a viable
commercial entity
On Wed, Oct 14, 2015 at 3:25 AM, Benjamin via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hello all,
>
> I was very surprised to learn that Blockstream will implement Sidechains
> for exchanges [1], [2] and has been working on this privately. Can somebody
> explain this “announcement”? Just a few comments on this “proposal”.
>
> “This new construction establishes a security profile inherently superior
> to existing methods of rapid transfer and settlement, and is directly
> applicable to other problems within existing financial institutions.”
>
> First of all, what does Bitcoin have to do with existing financial
> institutions? Secondly, what in do you mean by “rapid transfer” and
> "settlement"? Bitcoin is anonymous, digital cash. There is no such thing as
> settlement, there is only the transfer of digital cash and that's it
> (settlement is a bad word for this kind of transfer of property). If you
> make up new terms define them accurately and don't play the
> crypto-buzzword-bingo game.
>
> “This, in addition to increasing the security of funds normally subject to
> explicit counterparty risk, fosters conditions that increase market
> liquidity and reduce capital requirements for on-blockchain business
> models.”
>
> Again – what does Bitcoin have to do with “market liquidity” and “capital
> requirements”?
>
> “Blockstream's innovative solutions are definitely a game changer for the
> Bitcoin industry.”
>
> Does Blockstream have commercial products now?
>
> "These initial launch partners include Bitfinex, BTCC, Kraken, Unocoin,
> and Xapo, and discussions are underway with another dozen major
> institutional traders and licensed exchanges. "
>
> ??? so many questions and no answers.
>
> Regards,
> Benjamin
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
[-- Attachment #2: Type: text/html, Size: 3113 bytes --]
next prev parent reply other threads:[~2015-10-13 19:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 14:25 [bitcoin-dev] Liquid Benjamin
2015-10-13 14:27 ` Benjamin
2015-10-13 14:57 ` Tier Nolan
2015-10-13 19:37 ` Daniel Newton [this message]
2015-10-13 20:52 ` Adam Back
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='CAOUBo+9D7LQ-S6Rown_sbxxb9366cQj0c0HcU72B=4sBmmS0rg@mail.gmail.com' \
--to=djpnewton@gmail.com \
--cc=benjamin.l.cordes@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.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