From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WJnyW-0007NF-Ds for bitcoin-development@lists.sourceforge.net; Sat, 01 Mar 2014 17:45:24 +0000 X-ACL-Warn: Received: from nl.grid.coop ([50.7.166.116]) by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1WJnyT-0000R7-4v for bitcoin-development@lists.sourceforge.net; Sat, 01 Mar 2014 17:45:24 +0000 Received: from localhost (localhost [127.0.0.1]) (uid 1000) by nl.grid.coop with local; Sat, 01 Mar 2014 11:45:13 -0600 id 000000000006A341.0000000053121CA9.0000748D Date: Sat, 1 Mar 2014 11:45:13 -0600 From: Troy Benjegerdes To: Jorge =?iso-8859-1?Q?Tim=F3n?= Message-ID: <20140301174513.GP3180@nl.grid.coop> References: <20140209180458.GB20126@savin> <20140209204434.GA11488@savin> <20140210193247.GC17359@savin> <20140211175919.GV3180@nl.grid.coop> <20140214052159.GF31437@savin> <20140217054751.GY3180@nl.grid.coop> <20140228013719.GA5786@savin> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Score: -0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1WJnyT-0000R7-4v Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Decentralized digital asset exchange with honest pricing and market depth X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Mar 2014 17:45:24 -0000 > > You can make the same argument against Bitcoin itself you know... > > > > A Bitmessage-like network would be trivial to front-run via a sybil > > attack. It's the fundemental problem with marketplaces - the data > > they're trying to publish has to be public. > > I don't see the Bitcoin analogy... > Anyway, I still don't think the seller cares, if he sells at the price > he was asking, what would he care about "front running" those parallel > networks. > I've seen many street markets without "public information" and they > work just well. The spot price for ammonia fertilizer, refined gasoline at terminals, and price of tea in china are not 'public information', yet these are some of the largest traded commodities in the world, far exceeding the drop in the bucket that all cryptocoin transactions make. I'd further argue that the *actual* price of corn (cash bid price at elevators and ethanol plants) is not public information either. There is a great deal of money traded in collecting and then distributing the 'cleared price' information. Have a look at http://www.interquote.com/template.cfm?navgroup=aboutlist&urlcode=12&view=1 > >> I don't think this will be a tragedy, because like we discussed on > >> IRC, I don't think the primary goal of markets is price discovery, but > >> trade itself. > >> > >> About historic data, the actual trades are always public, and some > >> kind of "archivers" could collect and maintain old orders for historic > >> bid and asks, etc. > > > > And again, how do you know that record is honest? Fact is without > > proof-of-publication you just don't. > > Well, the trades that appeared in the chain actually occurred. > Buying to yourself at fake prices? Be careful, the miner could just > separate the order and fill it himself. Or anyone paying a higher fee, > for that matter. You just made my long-term strategic argument for investing in my own mining hardware so I can be sure to trade reliably. > Again, you haven't addressed why the seller cares more about "accurate > historic market data" than just his own fees and sell. > > > You mean a reverse nLockTime that makes a transaction invalid after a > > certain amount of time - that's dangerous in a reorg unfortunately as it > > can make transactions permenantly invalid. People who take money from buyers and sellers care most about 'accurate historic market data'. I just want to exchange my corn for e85, fertilizer, and electricity, and audit the code that runs accounting for the exchange. I really don't give a shit if there is 'accurate historic market data' as long as **MY** personal trade data is accurate and I got a good enough price, and I know who I'm dealing with. I know someone smarter than me and with more money, market leverage, and political connections **WILL** game the system and distort the market data history so they can take more money from buyers and sellers without actually doing some usefull market function. As long as use buyers and sellers can see the code, and have a good eye for knowing when someone's pushing the market around, we can just put our orders in and relieve some speculators of their money. Just get me working code for cross-chain trades, and we'll work on the accurate historic data problem later. ---------------------------------------------------------------------------- Troy Benjegerdes 'da hozer' hozer@hozed.org 7 elements earth::water::air::fire::mind::spirit::soul grid.coop Never pick a fight with someone who buys ink by the barrel, nor try buy a hacker who makes money by the megahash