From: Peter Todd <pete@petertodd•org>
To: Dan Carter <carterd@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Decentralized digital asset exchange with honest pricing and market depth
Date: Fri, 14 Feb 2014 00:20:36 -0500 [thread overview]
Message-ID: <20140214052036.GE31437@savin> (raw)
In-Reply-To: <ldg7qs$6rn$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]
On Wed, Feb 12, 2014 at 08:34:48AM -0800, Dan Carter wrote:
> I'm not sure how well this would work.
>
> Sure it would provide honest historical pricing, but those who wait for
> publication confirmation may be at a disadvantage -- to get the best
> deal possible Bob would connect to as many nodes as he could, examine
> the stream of unconfirmed asks coming in and sign the best ones before
> someone else does. The network would gravitate towards an O(n^2) fully
> connected network, because being fully connected means one is fully
> aware of all unconfirmed asks at any moment so one can make the best
> judgement and buy before someone else does.
>
> The seller needs a guarantee that all bidders can act on the ask
> transaction simultaneously. Maybe the partial ask transaction could be
> time-locked with a network propagation delay, there would be multiple
> bidder responses and the winner is chosen by lottery (and fee priority)
> by the bitcoin/alt-coin miner who confirms the atomic transaction in
> their block. That would eliminate the advantage to being fully
> connected as it would no longer matter that one can act first, so you
> have a more sane network.
You're assuming the seller cares about fairness - why should they? They
offered a price for an asset and someone bought it; exactly which buyer
willing to buy at that price was able to complete the trade is
irrelevant to them. What they do care about is being sure that at
whatever given price they offered 100% of the buyers willing to buy at
that price actually see the offer in a reasonable amount of time - at
the best price the seller will get there will be only a single buyer
after all so you need that solid proof that said buyer was actually able
to get the offer.
--
'peter'[:-1]@petertodd.org
0000000000000000c34e2307bf2d8e1de9db0351acfe7320a08826a5de3c146a
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 685 bytes --]
prev parent reply other threads:[~2014-02-14 5:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-09 18:04 Peter Todd
2014-02-09 20:44 ` Peter Todd
2014-02-10 19:32 ` Peter Todd
2014-02-11 17:59 ` Troy Benjegerdes
2014-02-14 5:21 ` Peter Todd
2014-02-17 5:47 ` Troy Benjegerdes
2014-02-27 23:48 ` Jorge Timón
2014-02-28 1:37 ` Peter Todd
2014-02-28 17:49 ` Jorge Timón
2014-03-01 17:45 ` Troy Benjegerdes
2014-03-01 18:22 ` Jeff Garzik
2014-03-01 18:28 ` Mark Friedenbach
2014-03-01 18:33 ` Jeff Garzik
2014-03-02 18:08 ` Troy Benjegerdes
2014-03-02 19:03 ` Jorge Timón
2014-02-12 16:34 ` Dan Carter
2014-02-14 5:20 ` Peter Todd [this message]
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=20140214052036.GE31437@savin \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=carterd@gmail$(echo .)com \
/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