From: Tier Nolan <tier.nolan@gmail•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP clearing house addresses
Date: Mon, 8 Aug 2016 10:56:24 +0100 [thread overview]
Message-ID: <CAE-z3OXkvZdr2AqQyySdZWmtpoED8yp=K1HXfNSc5pd9anLh3w@mail.gmail.com> (raw)
In-Reply-To: <CAAEDBiF1F1FkBXWQn_JgE0cr-aeVRAi29ETow0Sg95DO2MBGWQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]
On Mon, Aug 8, 2016 at 1:48 AM, Matthew Roberts <matthew@roberts•pm> wrote:
> Not everyone who uses centralized exchanges are there to obtain the
> currency though. A large portion are speculators who need to be able to
> enter and exit complex positions in milliseconds and don't care about
> decentralization, security, and often even the asset that they're buying.
>
Centralized exchanges also allow for things like limit orders. You don't
even have to be logged in and they can execute trades. This couldn't be
done with channels.
> Try telling everyone who currently uses Btc-e to go do their margin
> trading over lightning channels, for example.
>
Using channels and a centralized exchange gets many of the benefits of a
distributed exchange.
The channel allows instant funding while allowing the customer to have full
control over the funds. The customer could fund the channel and then move
money to the exchange when needed.
Even margin account holders might like the fact that it is clear which
funds are under their direct control and which funds are held by the
exchange.
If they are using bitcoin funds as collateral for a margin trade, then
inherently the exchange has to have control over those funds. A 2 of 3
system where the customer, exchange and a 3rd party arbitration agency
holds keys might be acceptable to the exchange.
[-- Attachment #2: Type: text/html, Size: 2046 bytes --]
next prev parent reply other threads:[~2016-08-08 9:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 18:16 Matthew Roberts
2016-08-03 21:13 ` Troy Benjegerdes
2016-08-03 23:55 ` Tier Nolan
2016-08-04 2:07 ` Matthew Roberts
2016-08-04 3:27 ` Luke Dashjr
2016-08-04 3:49 ` Andrew Johnson
2016-08-04 4:53 ` Matthew Roberts
2016-08-04 12:43 ` Erik Aronesty
2016-08-06 10:39 ` s7r
2016-08-06 11:13 ` Tier Nolan
2016-08-07 5:35 ` Matthew Roberts
2016-08-07 22:59 ` Erik Aronesty
2016-08-08 0:48 ` Matthew Roberts
2016-08-08 9:56 ` Tier Nolan [this message]
2016-08-08 10:09 ` Erik Aronesty
2016-08-08 11:01 ` Tier Nolan
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='CAE-z3OXkvZdr2AqQyySdZWmtpoED8yp=K1HXfNSc5pd9anLh3w@mail.gmail.com' \
--to=tier.nolan@gmail$(echo .)com \
--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