<?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: Towards a unified exchange protocol</title>
	<atom:link href="http://trilema.com/2012/towards-a-unified-exchange-protocol/feed/" rel="self" type="application/rss+xml" />
	<link>http://trilema.com/2012/towards-a-unified-exchange-protocol/</link>
	<description>Moving targets for a fast crowd.</description>
	<pubDate>Sun, 21 Jun 2026 08:15:07 +0000</pubDate>
	<generator>http://polimedia.us</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: A Review of the Bitcoin Category on trilema.com &#171; Ossa Sepia</title>
		<link>http://trilema.com/2012/towards-a-unified-exchange-protocol/#comment-148175</link>
		<dc:creator>A Review of the Bitcoin Category on trilema.com &#171; Ossa Sepia</dc:creator>
		<pubDate>Sun, 29 Mar 2020 08:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://trilema.com/?p=43770#comment-148175</guid>
		<description>[...] a unified protocol for BTC security exchanges based on MPEx's set of commands. [...]</description>
		<content:encoded><![CDATA[<p>[...] a unified protocol for BTC security exchanges based on MPEx's set of commands. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mircea Popescu</title>
		<link>http://trilema.com/2012/towards-a-unified-exchange-protocol/#comment-90297</link>
		<dc:creator>Mircea Popescu</dc:creator>
		<pubDate>Mon, 05 Nov 2012 18:24:20 +0000</pubDate>
		<guid isPermaLink="false">http://trilema.com/?p=43770#comment-90297</guid>
		<description>Sadly wordpress automatically puts unicode quotes in. All quotes are to be simple quotes of course.</description>
		<content:encoded><![CDATA[<p>Sadly wordpress automatically puts unicode quotes in. All quotes are to be simple quotes of course.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jurov</title>
		<link>http://trilema.com/2012/towards-a-unified-exchange-protocol/#comment-90290</link>
		<dc:creator>jurov</dc:creator>
		<pubDate>Mon, 05 Nov 2012 13:14:08 +0000</pubDate>
		<guid isPermaLink="false">http://trilema.com/?p=43770#comment-90290</guid>
		<description>Please get rid of the unicode quotes: “” I was thinking it's obvious, but my subcontractor did indeed blindly copy them :/</description>
		<content:encoded><![CDATA[<p>Please get rid of the unicode quotes: “” I was thinking it's obvious, but my subcontractor did indeed blindly copy them :/</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mircea Popescu</title>
		<link>http://trilema.com/2012/towards-a-unified-exchange-protocol/#comment-90269</link>
		<dc:creator>Mircea Popescu</dc:creator>
		<pubDate>Sat, 03 Nov 2012 20:12:08 +0000</pubDate>
		<guid isPermaLink="false">http://trilema.com/?p=43770#comment-90269</guid>
		<description>Well, mostly not use FIX because FIX is a mess. &lt;a href=https://bitcointalk.org/index.php?topic=122006.msg1314598#msg1314598 &gt;This thread&lt;/a&gt; on BTCtalk is related.

The "everything is a string" protects the protocol from the variable implementations of integers on different platforms. A string can be safely read by 8 bit, 16 bit, 32 bit and 64 bit platforms.

The perspective is quite intentionally BTC-centric. If someone wants to make a LTC-centric exchange they can either adapt the protocol or make a new one. This is BTC-UFX, not ???-UFX.

There are no return values for BUY/SELL etc because the execution side and the order relay side are independent. At the time the exchange accepts an order it does not yet know if/how it will be executed. This is as it should be.

The exchanges are free to use their own time. As long as they maintain the same timezones in their own STATJSON responses all is well.

Ideally exchanges would switch to at least asset-denomination that is compatible, for sure.</description>
		<content:encoded><![CDATA[<p>Well, mostly not use FIX because FIX is a mess. <a href=https://bitcointalk.org/index.php?topic=122006.msg1314598#msg1314598 >This thread</a> on BTCtalk is related.</p>
<p>The "everything is a string" protects the protocol from the variable implementations of integers on different platforms. A string can be safely read by 8 bit, 16 bit, 32 bit and 64 bit platforms.</p>
<p>The perspective is quite intentionally BTC-centric. If someone wants to make a LTC-centric exchange they can either adapt the protocol or make a new one. This is BTC-UFX, not ???-UFX.</p>
<p>There are no return values for BUY/SELL etc because the execution side and the order relay side are independent. At the time the exchange accepts an order it does not yet know if/how it will be executed. This is as it should be.</p>
<p>The exchanges are free to use their own time. As long as they maintain the same timezones in their own STATJSON responses all is well.</p>
<p>Ideally exchanges would switch to at least asset-denomination that is compatible, for sure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jurov</title>
		<link>http://trilema.com/2012/towards-a-unified-exchange-protocol/#comment-90268</link>
		<dc:creator>jurov</dc:creator>
		<pubDate>Sat, 03 Nov 2012 19:55:52 +0000</pubDate>
		<guid isPermaLink="false">http://trilema.com/?p=43770#comment-90268</guid>
		<description>Thanks for documenting the interface. However, I see following problematic points:

Before trying to create new standard, one should consider existing ones and make clear that they are inaccurate and why. You have mentioned FIX protocol yourself, why not use it instead? 

Technical merits should be reasonably justified, for example you decided to use only a "everything is a string" subset of JSON and with embedded checksums. This adds additional effort necessary to emit/parse JSON data -&#62; risk of bugs/incompatibilities that need to be outweighed by benefits, and more possible solutions considered.

There is no extension mechanism outlined, for example exchange may want to provide ability to buy/sell the same asset in litecoins. 

Specification of BUY,SELL,CANCEL,EXERCISE,etc. return value is missing. I can from practice say it is very important for client to be able to reliably check how much items were actually accepted for the order, whether cancel was accepted and what was the exact result of exercise.

Above 2 points could easily be solved by adopting JSONRPC or similar existing protocol.

All dates should be specified as UTC or formatted with timezone.

And, on broader note, this interface should be adopted by multiple exchanges, much wanted function will be possiblity to move assets between them. Maybe it would be even beneficial in long term for MPEx to fund research in this direction.</description>
		<content:encoded><![CDATA[<p>Thanks for documenting the interface. However, I see following problematic points:</p>
<p>Before trying to create new standard, one should consider existing ones and make clear that they are inaccurate and why. You have mentioned FIX protocol yourself, why not use it instead? </p>
<p>Technical merits should be reasonably justified, for example you decided to use only a "everything is a string" subset of JSON and with embedded checksums. This adds additional effort necessary to emit/parse JSON data -&gt; risk of bugs/incompatibilities that need to be outweighed by benefits, and more possible solutions considered.</p>
<p>There is no extension mechanism outlined, for example exchange may want to provide ability to buy/sell the same asset in litecoins. </p>
<p>Specification of BUY,SELL,CANCEL,EXERCISE,etc. return value is missing. I can from practice say it is very important for client to be able to reliably check how much items were actually accepted for the order, whether cancel was accepted and what was the exact result of exercise.</p>
<p>Above 2 points could easily be solved by adopting JSONRPC or similar existing protocol.</p>
<p>All dates should be specified as UTC or formatted with timezone.</p>
<p>And, on broader note, this interface should be adopted by multiple exchanges, much wanted function will be possiblity to move assets between them. Maybe it would be even beneficial in long term for MPEx to fund research in this direction.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
