<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: MPEx and the HFT problem</title>
	<atom:link href="http://trilema.com/2012/mpex-and-the-hft-problem/feed/" rel="self" type="application/rss+xml" />
	<link>http://trilema.com/2012/mpex-and-the-hft-problem/</link>
	<description>Moving targets for a fast crowd.</description>
	<pubDate>Mon, 27 Apr 2026 17:54:51 +0000</pubDate>
	<generator>http://polimedia.us</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: MPEx vs. The Play Bitcoin Exchanges &#124; When Bitcoin Met Pete</title>
		<link>http://trilema.com/2012/mpex-and-the-hft-problem/#comment-99759</link>
		<dc:creator>MPEx vs. The Play Bitcoin Exchanges &#124; When Bitcoin Met Pete</dc:creator>
		<pubDate>Sun, 11 May 2014 21:28:52 +0000</pubDate>
		<guid isPermaLink="false">http://trilema.com/?p=44818#comment-99759</guid>
		<description>[...] has MPEx solved high-frequency trading, the bane of the NYSE, NASDAQ, etc.? By not allowing instantaneous cancellation of orders. Simple. [&#8617;]MPOE-PR lit up the Bitcointalk forum like no one else. She recently retired as [...]</description>
		<content:encoded><![CDATA[<p>[...] has MPEx solved high-frequency trading, the bane of the NYSE, NASDAQ, etc.? By not allowing instantaneous cancellation of orders. Simple. [&#8617;]MPOE-PR lit up the Bitcointalk forum like no one else. She recently retired as [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: smickles</title>
		<link>http://trilema.com/2012/mpex-and-the-hft-problem/#comment-91080</link>
		<dc:creator>smickles</dc:creator>
		<pubDate>Fri, 21 Dec 2012 20:31:55 +0000</pubDate>
		<guid isPermaLink="false">http://trilema.com/?p=44818#comment-91080</guid>
		<description>I place my orders in all possible universes at once, thus avoiding the problem :D</description>
		<content:encoded><![CDATA[<p>I place my orders in all possible universes at once, thus avoiding the problem :D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mircea Popescu</title>
		<link>http://trilema.com/2012/mpex-and-the-hft-problem/#comment-90989</link>
		<dc:creator>Mircea Popescu</dc:creator>
		<pubDate>Sun, 16 Dec 2012 11:39:31 +0000</pubDate>
		<guid isPermaLink="false">http://trilema.com/?p=44818#comment-90989</guid>
		<description>&lt;blockquote&gt;but I presume calling STAT is akin to observing the system, whereupon the state collapses into one single result.&lt;/blockquote&gt;

This :D</description>
		<content:encoded><![CDATA[<blockquote><p>but I presume calling STAT is akin to observing the system, whereupon the state collapses into one single result.</p></blockquote>
<p>This :D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jurov</title>
		<link>http://trilema.com/2012/mpex-and-the-hft-problem/#comment-90988</link>
		<dc:creator>jurov</dc:creator>
		<pubDate>Sun, 16 Dec 2012 11:30:59 +0000</pubDate>
		<guid isPermaLink="false">http://trilema.com/?p=44818#comment-90988</guid>
		<description>Hahaha, I can attest that wannabe-MPEx-HFT's life is quite difficult, despite there is almost no competition. Not just the cancellation, but whole order lifetime entails dealing with fuzzy quantum phenomena, one has to wait after placing the order it till it can be observed in STAT. I think I have seen balances updated first, then in next stat appeared the transaction itself (although this happens very rarely). Oh and entangled pairs of phantom orders/transactions, too. Only thing missing so far is is superposition of states , but I presume calling STAT is akin to observing the system, whereupon the state collapses into one single result. Maybe MPEx should offer end-to-end quantum access to the engine, enabling users to submit orders with precisely defined wavefunction, instead of pretending above behavior is a bug and trying to fix it in vain or rationalize it backwardly.</description>
		<content:encoded><![CDATA[<p>Hahaha, I can attest that wannabe-MPEx-HFT's life is quite difficult, despite there is almost no competition. Not just the cancellation, but whole order lifetime entails dealing with fuzzy quantum phenomena, one has to wait after placing the order it till it can be observed in STAT. I think I have seen balances updated first, then in next stat appeared the transaction itself (although this happens very rarely). Oh and entangled pairs of phantom orders/transactions, too. Only thing missing so far is is superposition of states , but I presume calling STAT is akin to observing the system, whereupon the state collapses into one single result. Maybe MPEx should offer end-to-end quantum access to the engine, enabling users to submit orders with precisely defined wavefunction, instead of pretending above behavior is a bug and trying to fix it in vain or rationalize it backwardly.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
