<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Axon Trade on Medium]]></title>
        <description><![CDATA[Stories by Axon Trade on Medium]]></description>
        <link>https://medium.com/@axontrade?source=rss-858fabf45e6e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dEqlfyXzbEFp87QCa6is4g.png</url>
            <title>Stories by Axon Trade on Medium</title>
            <link>https://medium.com/@axontrade?source=rss-858fabf45e6e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 07:09:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@axontrade/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Optimization techniques for FIX-based trading applications]]></title>
            <link>https://medium.com/axontrade/optimization-techniques-for-fix-based-trading-applications-axon-trade-95be610e3bf5?source=rss-858fabf45e6e------2</link>
            <guid isPermaLink="false">https://medium.com/p/95be610e3bf5</guid>
            <category><![CDATA[algorithmic-trading]]></category>
            <category><![CDATA[crypto-trading]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[hft]]></category>
            <category><![CDATA[high-frequency-trading]]></category>
            <dc:creator><![CDATA[Axon Trade]]></dc:creator>
            <pubDate>Thu, 30 Mar 2023 18:13:00 GMT</pubDate>
            <atom:updated>2023-08-02T18:27:28.937Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*rD8HochDgRV1Y-quTLv-Og.png" /></figure><p>Our team has about 20 years of experience with <a href="https://xtrd.io/home/product/fix-api/">FIX API</a>, with the last six years primarily in crypto (or digital assets, if you will).</p><p>During this period, we accumulated particular experience and knowledge of what is good and what is not when it comes to using FIX protocol. Some of our know-how I will share in this short article.</p><p>These techniques are general and can be applied to digital assets, FX, equities, etc. It also will work (with some exceptions) with REST/WebSockets APIs.</p><h3>General optimization methods</h3><h4>Never run on operating system default settings</h4><p>By default, your OS is pre-configured to run on average hardware profile, and it has no idea how much memory (and what type) you have, what sort of network cards you’ll use, what storage devices are installed, and how they are configured. We don’t know much about Windows or Mac OS, but Linux offers a great set of different configuration mechanisms for tuning. It’s like a free lunch — you can get additional performance by configuring your hardware correctly.</p><p>Tune your 10Gbps NICs for better performance</p><h4>Increase TCP/IP buffers</h4><p>For example, the default buffer size for Linux is 8kb. This value works perfectly for web browsing but might create problems for applications that work with market data intensively.</p><h4>If possible, consider changing threads priorities</h4><p>Again, Linux-specific — you can increase threads priority for specific processes.<br>In addition to this — bind your application to specific CPU cores (threads affinity)</p><h4>If possible, choose the proper disk scheduler</h4><p>Again… Linux has multiple disk I/O schedulers, each with its benefits and drawbacks.<br>If you run on SSD/NVME then consider using . ( <a href="https://access.redhat.com/solutions/109223">https://access.redhat.com/solutions/109223</a>)</p><h4>Keep the number of threads as low as possible</h4><p>This tip is more on the software development side rather than system configuration.<br>Try to reduce the number of working threads to a bare minimum — context switching comes with a price, and with two or three threads it might be ignored. But with hundreds or thousands of threads competing for resources, the overall impact becomes meaningful.</p><h3>Market Data sessions optimization</h3><h4>Increase receiving buffers</h4><p>Pretty straightforward.</p><h4>Properly plan your processing architecture</h4><p>Make an informed decision on how and where to process market data — update books, run calculations, send orders, or do anything else.</p><p>if these operations take some time, performing them in a separate thread is a good idea. This way, you can ensure that a FIX engine is busy emptying, receiving buffers, and not being part of the Monte Carlo calculation. Otherwise, there is a chance that you will become what we call a “slow consumer” and will be disconnected. Do not try to subscribe to all Binance, Coinbase, OKX, and Deribit instruments, and keep complex processing in a single thread.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*bFBXj34gMONSb2V5aqAQuA.png" /></figure><p>On the contrary, if the number of instruments is low, algo is pretty straightforward (e.g. price checks), properly debugged, and profiled, you can always save extra time on context switching by placing your business logic inside FIX messages handlers. For example, the <a href="https://medium.com/@serg.gulko/latency-arbitrage-on-crypto-markets-using-xtrd-oems-bc9b6d548d09">latency arbitrage system</a> we built some time ago works precisely like this.</p><h4>Turn off logging for market data sessions unless it is required</h4><p>If you are not in the business of reselling historical market data, then turn off logging provided by FIX engines. Yes, we optimize market data streams, and our FIX-based feeds contain fewer data(in bytes) than native OKX, Huobi, ByBit, or GATE.IO formats. But it still will keep your disk system busy. And it takes some space too. A lot of space.</p><h3>Trading sessions optimization</h3><h4>Increase receiving and sending buffers</h4><p>Unlike market data sessions, where you mainly receive data, trading sessions have usually utilized both ways. This means that both sending and receiving buffers should be adequately increased.</p><h4>Never turn off logging for trading sessions</h4><p>Based on our experience, we always keep logging on for trading sessions. To mitigate I/O penalty, use asynchronous logging adapters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*p2iFp7KNtCW58Tbv18SqsA.jpeg" /></figure><p>If your FIX engine doesn’t have such a thing from scratch, it’s usually a good idea to invest some time to build it by yourself.</p><h4>Use pre-cached messages</h4><p>Use pre-cached messages instead of creating e.g. NewOrderSingle or ExecutionReports (in our case) every time you need it.</p><p>If your FIX engine supports this, run warm-up procedures before hitting the gas with actual trading. Sometimes developers use lazy-load initialization, and creating particular objects might happen only when you send an actual message. Pity if this message is your NewOrderSingle when you are chasing a price.</p><h4>Use pre-cached timestamps</h4><p>If you profile your code, you will be surprised at how long it takes to transform timestamps from long (data format) into strings. It might be beneficial to pre-populate formatted strings into memory. This task is challenging (populate, update), but the performance gain is significant.</p><p><em>Originally published at </em><a href="https://axon.trade/optimization-techniques-for-fix-based-trading-applications/"><em>https://axon.trade</em></a><em> on March 30, 2023.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95be610e3bf5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axontrade/optimization-techniques-for-fix-based-trading-applications-axon-trade-95be610e3bf5">Optimization techniques for FIX-based trading applications</a> was originally published in <a href="https://medium.com/axontrade">axontrade</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Latency arbitrage on crypto markets using Axon Trade OEMS]]></title>
            <link>https://medium.com/axontrade/latency-arbitrage-on-crypto-markets-using-axon-trade-oems-axon-trade-a6f84695e532?source=rss-858fabf45e6e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6f84695e532</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[algorithmic-trading]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[high-frequency-trading]]></category>
            <category><![CDATA[crypto-trading]]></category>
            <dc:creator><![CDATA[Axon Trade]]></dc:creator>
            <pubDate>Wed, 02 Nov 2022 15:55:53 GMT</pubDate>
            <atom:updated>2023-08-02T18:28:00.916Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*3w7PyxUQCBUou8MCqMUdtg.png" /></figure><p>In addition to our order and execution management system for crypto trading, our company provides integration and custom software development services. In this article, I would like to showcase one such project — a latency arbitrage trading system.</p><p>The main concept besides latency arbitrage is straightforward. Due to some market fragmentation, different market conditions, jurisdictions, and even trading hours, the selling price for an asset (BID) on one exchange could be lower than the buy price on another (ASK). This means you can buy in one place and sell in another, pocketing the difference.</p><p>Latency arb is very similar to what market-makers do, except for the fact that they prefer to rest somewhere in the order book. In our case, the system performs as a pure taker, scooping liquidity from the top of books. As a measure of self-protection, we only used LIMIT orders with minimal resting time (so if an order was not filled, we had to cancel it).</p><p>“Simplicity on paper” comes with a price during implementation — everything should be fast. VERY FAST. Price discrepancies appear for just a moment, and you have a limited amount of time to do the following:</p><ul><li>Receive market data</li><li>Detect arb opportunity</li><li>Shoot two orders (to BUY on one exchange and to SELL on another) at the same time</li></ul><p>Do not forget about error handling because bad things always happen. For example, one leg gets filled, and the second — is either rejected, partially filled, or stuck in a book.</p><p>For obvious reasons, we choose Axon Trade OEMS for digital asset trading as a market data source and an entry point for all orders. This allows changing trading pairs and exchanges easily without adjusting any of the trading logic.</p><p>Here is a simplified application architecture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BkvtzaJWFyTeYysxFMZ_xA.png" /></figure><p>Our end goal was to keep the number of elements as low as possible, so we came up with the following topology:</p><ul><li>Two independent FIX sessions — one for market data, one for trading</li><li>Trading FIX session connected to <strong>BuySideOMS</strong>, a component to manage order stages</li><li><strong>BuySideOMS</strong> acts as a hub to receive trading commands and return execution confirmations to the business logic component</li><li><strong>Brain</strong> is more like a complex events processing (CEP) loop that decides what the next step would be based on current market conditions (received through market data FIX session) and order statuses.</li><li>To control and monitor the <strong>Brain</strong> behavior, we added a REST-based API and a user interface on top of it; the main trick here is that REST API is set aside from the central communication circle — <strong>Brain</strong>/<strong>OMS</strong>/Market Data Session/Trading Session.</li></ul><p>During development, our team faced several challenges:</p><ul><li>Market data processing procedures</li><li>Error handling</li><li>Asset settlement and rebalancing across exchanges</li></ul><p>Axon Trade market data dissemination services don’t apply any throttling or batching to outgoing data. This means a recipient must process the data at an extremely high speed to avoid the situation called “slow consumer” when messages start to pile up in outgoing buffers causing memory overuse. Our servers react simply to it — slow sessions will be terminated after some time. An approach to solve this problem is complex and might include the following:</p><ul><li>Reduce network travel time by locating as much as possible close to our servers</li><li>Increase operation system network buffers on your side — never, never run on a default operating system settings.</li><li>Increase the buffer size on the FIX engine. Most FIX engines allow manually setting the size of a queue</li><li>Avoid mixing market data processing and business logic in the same thread unless the logic is super simple</li></ul><p>As long as there is no centralized clearing in crypto (yes, 2022…), you have to maintain a sizable inventory on both exchanges and settle as infrequently as you can. Your main enemy here is the exchange’s trading and withdrawal fees. Withdrawal fees might include direct fees, applied by exchange, and network fees, so watch out for this. From a distance, these numbers might look small, but the profit from arb is also not that big, so you have to perform multiple successful trades. If you do not have enough inventory, you have to rebalance it, and this is the point where withdrawal commissions can erode your trading profit. If you have big books on both sides, you can enjoy the ride!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mdMjFpCfpZGv0jq_qxr1Dg.png" /></figure><p>Asset transfer itself is a challenge. Initially, our client was planning to do crypto vs. fiat arbitrage. To rebalance fiat, we planned to use a solution from a company that is exceptionally aggressive on the marketing side, promoting things they do not have. This is an untrustworthy company, so to speak. Only one step away from production, we realized it had a gap. The solution — switch to stablecoins.</p><p>For crypto rebalancing, we were in a position to buy vs. build. A top candidate here was Fireblocks. It certainly has a working product, but the price(access + API) was far beyond our allowed budget. The solution — we built a simple exchange to exchange rebalance.</p><p>Now pride time (technological, not coming out) — the system was able to hit the top of the book prices on Kraken and OKCoin in most cases, even when located in Equinix NY4 data center. It was a double pride — the trading app we built was fast, and Axon Trade OEMS was blazing fast. During the course of development, we navigated multiple technological, jurisdictional, and organizational challenges that our team successfully resolved.</p><p>As a footnote, does latency arb still exist in crypto? Yes, it does. Can you exploit it? Possibly. But aside from latency arbitrage, many other trading ideas can be implemented on top of Axon Trade OEMS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*286B69644iSL-LXbWWx0RQ.png" /></figure><p>If you have any questions (OEMS itself, custom software development services, etc) — feel free to reach out, and we will do our best to assist you.</p><p><em>Originally published at </em><a href="https://axon.trade/latency-arbitrage-on-crypto-markets-using-axon-trade-oems/"><em>https://axon.trade</em></a><em> on November 2, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6f84695e532" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axontrade/latency-arbitrage-on-crypto-markets-using-axon-trade-oems-axon-trade-a6f84695e532">Latency arbitrage on crypto markets using Axon Trade OEMS</a> was originally published in <a href="https://medium.com/axontrade">axontrade</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MT4/MT4 Crypto bridge by Brokeree/XTRD]]></title>
            <link>https://medium.com/axontrade/mt4-mt4-crypto-bridge-by-brokeree-xtrd-axon-trade-1b3f242f4c9c?source=rss-858fabf45e6e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b3f242f4c9c</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[mt5]]></category>
            <category><![CDATA[mt4]]></category>
            <category><![CDATA[brokerage]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[Axon Trade]]></dc:creator>
            <pubDate>Wed, 02 Nov 2022 14:11:30 GMT</pubDate>
            <atom:updated>2023-08-07T12:52:53.676Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/805/0*IspN50JWYNUcgku9.png" /></figure><p><a href="https://brokeree.com/">Brokeree Solutions</a>, a turnkey solutions developer for multi-asset brokers, has just announced the integration of its flagship Liquidity Bridge with <a href="https://axon.trade/">Axon Trade</a> — orders and execution management system (OEMS) for digital asset trading with a strong focus on low-latency and high-throughput execution.</p><p>Multi-server Liquidity Bridge is a comprehensive solution that combines advanced A/B book order execution, smart liquidity aggregation, and risk management. With this integration, brokers may introduce new crypto instruments for their clients on MetaTrader 4 and 5 platforms via the market data and liquidity provided by Axon Trade.</p><p>“We provide access to major US, Asia, and Europe exchanges. By leveraging our stack, clients can easily increase their liquidity offering by adding new LPs from the management panel without spending weeks for integration followed by neverending maintenance,” said Serg Gulko, CEO of Axon Trade. “I came to the digital asset space from FX and am familiar with the challenges market participants are facing. Our common effort with Brokeree pivoted toward helping MT4/MT5 brokers reduce their costs, increase profit margins, and help them keep the competitive edge by providing new trading instruments to their clients without investing a fortune in R&amp;D.”</p><p>Axon Trade is an institutional-grade OEMS for digital asset trading. It provides a unique combination of services, such as FIX API for digital asset trading, real-time normalized market data feeds, low-latency execution services, and a secure environment inside Equinix data centers.</p><p>“In the liquidity aggregation field, especially in volatile markets such as crypto, it’s crucial to use comprehensive technologies with robust risk-management features. By integrating with brands like Axon Trade, we can deliver our clients with accessible high-grade technology,” shared Brokeree in the press release.</p><p>Brokeree Solutions is a technology company specializing in solutions development for multi-asset brokers running MetaTrader 4 and 5, trading platform servicing, and consultation.</p><p>Established in 2013, the company has developed over 50 products, including liquidity management software, investment systems, and a wide range of plugins to automate and optimize certain internal processes of financial brokerages.</p><p><em>Originally published at </em><a href="https://axon.trade/axon-trade-to-integrate-with-brokeree-solutions/"><em>https://axon.trade</em></a><em> on November 2, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b3f242f4c9c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axontrade/mt4-mt4-crypto-bridge-by-brokeree-xtrd-axon-trade-1b3f242f4c9c">MT4/MT4 Crypto bridge by Brokeree/XTRD</a> was originally published in <a href="https://medium.com/axontrade">axontrade</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Axon Trade OEMS for Crypto]]></title>
            <link>https://medium.com/axontrade/xtrd-oems-for-crypto-b7a5c64fc11?source=rss-858fabf45e6e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7a5c64fc11</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[crypto-trading]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Axon Trade]]></dc:creator>
            <pubDate>Thu, 17 Feb 2022 11:30:36 GMT</pubDate>
            <atom:updated>2023-07-31T16:18:54.940Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*sBe__6rdUVvyl1iinOeaTg.png" /></figure><p><em>Article by Serg Gulko, Co-Founder &amp; CEO at Axon Trade</em></p><p>In this article, I would like to address the most common questions we received about Axon Trade OEMS for digital assets trading.</p><h3>What is the OEMS for crypto trading?</h3><p>OEMS, sometimes O/EMS, stands for Order and Execution Management System. Initially, it was two separate software types — OMS and EMS which were merged into a single system over time. We live in a time of consolidation and modern OEMS systems are capable (sometimes) of doing much more than before, including positions management orchestrating the settlement process.</p><p>OEMS is in charge of many things — orders entry and execution through different liquidity providers, analytics, market data streaming and charts, transactions cost analysis, and so on. The system can be accessed by humans as well as programmatically through APIs such as FIX.</p><p>Unlike its peers from established markets like FX, a big part of crypto OEMSs is dedicated to connectivity management. Almost every liquidity provider in the FX space understands FIX; specifications have not changed for years and a TCP/IP connection established on Monday can be disconnected in about one week. This does not happen in crypto which adds some “spice” to the process and extra complexity.</p><h3>How is OEMS different from libraries?</h3><p>There are many different open source and proprietary libraries that can act as a normalization layer between your system and exchange(s). This is really a wrapper from general purposes languages like Java, Python, PHP, or JavaScript into widely used in crypto REST/WebSocket calls. Libraries can help you send orders but leave you alone with more complex problems like different symbols’ names, monitoring session states, and performing systems synchronization. Even accessing trading history can be tricky — some exchanges do not store more than 90 days of orders (and in the most extreme cases — only the last 1000 orders).</p><p>Of course, you can link the database layer, implement your own mechanisms to deal with dead WebSockets, tune connectors code (in many cases, the quality is far from ideal and many things can and should be improved), add accounts support, and so on. Good job! You just built your own OEMS system.</p><p>I see libraries as bricks, while OEMS is an unfinished house. Add hardwood floors, furniture, doors, lights, and a fence — and you’ll get a trading platform, market-making algo, or something different but something that can be used by people. Bricks are important but you can’t live surrounded by just them.</p><p>Disclaimer: in Axon Trade OEMS we do not use any third-party normalization libraries to communicate with crypto exchanges. Everything is built in-house to ensure the best performance.</p><h3>When should I use OEMS for crypto?</h3><p>In most cases, it’s beneficial to integrate ready-to-use OEMS unless you would like to build your own and become a vendor.</p><p>Of course, there are many factors to consider, such as flexibility, functionality, latency, geographical location, support, prices, and even team behind the scene but I can assure you that it’s always possible to find a compromise. There are many solutions on the market, some good, some bad but they can save the most valuable resource — time.</p><h3>What functions are available from the shelf?</h3><p>Different systems offer different sets of functions. Below is what Axon Trade OEMS offers to accelerate crypto trading.</p><h4>Normalized FIX API for trading and market data</h4><p>We use FIX 4.4 for both market data and trading sessions. It means that, for example, quotes from Binance will look the same as quotes from Coinbase Pro. The trading process also will look identical although exchanges are completely different.</p><h4>Simultaneous access to multiple crypto exchanges</h4><p>Axon Trade OEMS is interconnected with major crypto exchanges in the US, Europe, and Asia. All trading operations on different venues can be done through a single TCP/IP connection (or can be spread).</p><h4>Active orders management</h4><p>Information about clients’ orders is replicated and constantly updated on our servers. Each trade confirmation or/and cancellation dynamically changes the representation of orders which we store in memory.</p><h4>Access to trading history</h4><p>We store every order sent through our system and every execution report received. There is no ‘data retention period,’ everything that gets in, remains there. Information about trading activities includes exchange-assigned IDs, timestamps, trade prices and sizes, and also fees paid.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PnTW-0as7rNRVhpw.png" /></figure><h4>Multitenant design</h4><p>Axon Trade OEMS for crypto is designed in a way that allows a single organization to have multiple independent resources, for example, trading desk accounts with their own connections to exchanges, balances, and separated FIX sessions for trading.</p><p>Such separation also helps build trading platforms on top of the Axon Trade stack — accounts are segregated and do not interact with each other.</p><h4>Normalized Symbology</h4><p>There is no common standard for naming convention. Each exchange lives to create something new and unique (and they have a wild imagination), so we built and maintain our own directory that covers spot and derivatives markets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RU89xGZUCIpP9HF8.png" /></figure><h4>Connectivity Management</h4><p>We carefully monitor outgoing connectivity statuses, and if something goes wrong (and this happens relatively often, unfortunately, due to current infrastructure development) we notify clients, disable trading on a particular destination, and start checking once it returns to normal. Once we connect again, we handle complicated synchronization procedures that include checking all open orders, trading history, and position changes.</p><h4>Demo Environment</h4><p>Axon Trade OEMS has a dedicated demo environment that can be used to test integration without putting real money at risk. The Demo Environment fully replicates our production services, including market data streams and management API.</p><h4>Management API</h4><p>In addition, to <a href="https://docs.xtrd.io/#fix-api">FIX API</a> for trading and market data, we offer <a href="https://docs.xtrd.io/#management-api">REST-based API</a> to manage assets of your organizations — accounts, connectivity to exchanges, FIX sessions, and access rights. This API also can be used to fetch trading history, positions, and even open orders.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7a5c64fc11" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axontrade/xtrd-oems-for-crypto-b7a5c64fc11">Axon Trade OEMS for Crypto</a> was originally published in <a href="https://medium.com/axontrade">axontrade</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scalper for Binance Using Axon Trade FIX API]]></title>
            <link>https://medium.com/axontrade/scalper-for-binance-using-axon-trade-fix-api-1edd8d2fbfb3?source=rss-858fabf45e6e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1edd8d2fbfb3</guid>
            <category><![CDATA[binance]]></category>
            <category><![CDATA[algorithmic-trading]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[crypto-trading]]></category>
            <category><![CDATA[high-frequency-trading]]></category>
            <dc:creator><![CDATA[Axon Trade]]></dc:creator>
            <pubDate>Mon, 31 Jan 2022 08:27:53 GMT</pubDate>
            <atom:updated>2023-08-02T18:27:04.914Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*PZkyiG5MdNpOMtESbGh-Nw.png" /></figure><p><em>Binance is one of the largest cryptocurrency exchanges in the world, responsible for $7.7 trillion crypto exchange volume in 2021. It was founded in 2017 by Changpeng Zhao, who previously worked for Blockchain.info and as CTO of OKCoin. </em><strong>Axon Trade Overview</strong> <em>Axon Trade is an institutional-grade OEMS for digital assets trading. We provide access to major crypto exchanges through the unified FIX API.</em></p><p>In this article, we would like to demonstrate how to build a small yet powerful scalping application that trades on the leading cryptocurrency exchange — Binance.</p><p>The bot will be connected to Binance through Axon Trade FIX API to receive real-time normalized market data and to place/cancel orders.</p><p>You can reuse this <a href="https://bitbucket.org/xtrd/xtrd_demos/src/master/renko-scalper/">source code</a> in your projects free of charge.</p><p>Disclaimer: the bot is not a ready-to-use solution because it lacks risk controls and proper positions management. Although our R&amp;D shows promising performance, do not expect to achieve the same results.</p><p>Before we dive into the technical part, it’s worth explaining the logic behind the given trading bot.</p><p>Scalping is a momentum-based trading style where positions hold for minutes or even seconds and then sell for profit (or small loss… a sacrifice to Mr. Market). When performed manually, it requires self-discipline, the ability to handle stress, make quick decisions, and act accordingly.</p><p>Renko chart is one of the technical analysis tools that help reduce market noise and identify market trends more precisely. One of the authors of this article was introduced to Renko about 15 years ago and fell in love with it.</p><p>To construct a single brick on a chart we should perform several simple steps:</p><ul><li>Define a brick size e.g. 10 points</li><li>Define the price type to track. It can be bids, asks, trades, an average between the bid and ask, etc.</li><li>Start tracking prices in real-time</li><li>If the price changed more than 10 points, then form a new Renko brick in the corresponding direction. It is possible that the single price change can form more than one Renko brick.</li></ul><p>Here is our trading logic:</p><ul><li>Wait for a new Renko brick to be formed</li><li>If it is an UP brick, then place a limit order to SELL with a price at the level of UP + 1 brick</li><li>If it is a DOWN brick, then place a limit order to BUY with a price at the level of DOWN — 1 brick</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/598/1*0a46SvCzp66nw9xM4auW5A.png" /></figure><ul><li>Continue monitoring the market for changing course or for execution</li><li>If a newly formed brick changed its direction (this means that the price changed at least 2x of a brick size in the reverse direction), we should cancel our existing limit order and place another one with a new price and reversed direction.</li><li>If the market moved in the direction we predicted, then our order gets executed and we should start over.</li></ul><p>Simply put, it is the good old “buy low, sell high” principle computerized and applied to crypto markets through Axon Trade FIX API.</p><p>The bot itself contains several main components:</p><ul><li>Market data connector</li><li>Trading connector</li><li>Market data processor/Renko generator</li><li>Simple OMS/EMS system</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/1*QKWlTCTrtBwnY5GQgoUjRg.png" /></figure><p>To make this technical-enough material more fun, we decided to build a small user interface to plot Renkos bricks and executions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VYshwTOCFUy28wvj-60v_Q.png" /></figure><p>Since all high-level details of implementation were discussed, let’s get started with the implementation part.</p><p>To build Renko charts we need to establish a connection to a service called Axon Trade MD Feeder. It is responsible for disseminating real-time normalized market data from Binance (and other crypto exchanges) using FIX protocol. In comparison with WebSockets, FIX is faster and more reliable because it runs on top of a pure TCP/IP stack and has no additional intermediary layers.</p><p>Using FIX protocol, you can easily subscribe to receive updates for one or many trading instruments available on Binance such as BTC/USDT, ETH/USDT, and so on. It is possible to specify what sort of information you’ll need — bids, asks, and/or trades. Another big advantage is that market data itself comes in incremental updates. This means that you receive only actual changes of the entire orders book (like 3–4 levels) but not a full book every time. This is not a big issue with Binance which already streams data as a delta (difference between the previous and current state) but can be extremely helpful with other crypto exchanges Axon Trade supports.</p><p>There are three major messages defined by FIX standard and implemented inside Axon Trade that help manage your crypto market data streams — MarketDataRequest, MarketDataSnapshotFullRefresh, and MarketDataIncrementalRefresh. As it is easy to understand from their names, MarketDataRequest is used to manage your subscription (start or stop data streams), MarketDataSnapshotFullRefresh is used by the server to transmit the entire book, and MarketDataIncrementalRefresh is sent by the server when data (price or side) in the particular orders book changed.</p><p>The market data management workflow is simple — once the application established a connection to Axon Trade OEMs over the FIX, it sends MarketDataRequest to subscribe to all updates on BTC/USDT (or another selected symbol) on Binance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/952/1*tizmw4Dusts_K8JWVB8Kmw.png" /></figure><p>If the request was successfully processed, Axon Trade OEMS for digital assets trading responds with a MarketDataSnapshotFullRefresh message that contains all levels for BTC/USDT orders book. The application uses this data to initiate the book and starts waiting for incoming MarketDataIncrementalRefreshes that carry small (and sometimes not very small) delta changes. These changes have to be applied to the book (delete levels, update sizes on a particular level, add new prices). Once a book is updated, the component responsible for Renko’s generation will check if the conditions to create a new brick are met or if the price is still within the interval.</p><p>Now, when we have a working market data connection and Renkos charts, it’s time to start trading on Binance using FIX API.</p><p>FIX specification contains plenty of different messages (commands and responses) that cover pretty much everything in a typical trade lifecycle starting from initiation to ending with trade confirmation and settlement. Axon Trade OEMS system allows managing orders (get all, place, cancel, replace) and viewing positions through the unified FIX API.</p><p>When it comes to trading, there are three major messages — NewOrderSingle, OrderCancelRequest, and ExecutionReport.</p><p>NewOrderSingle is used to initiate an order. The message allows specifying different order characteristics, such as side (e.g. BUY), size, type (e.g. LIMIT), symbol, time in force (e.g. Good Till Cancel), among others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hceVAAJPSdApuOHChGF69w.png" /></figure><p>Below is a textual representation of the raw FIX request to buy 0.001 BTC for USDT at Market on the Binance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/468/1*hVYBYAcfCYwx6CV5ypxfkQ.png" /></figure><p>In many cases, the server interacts with clients over ExecutionReports. This message is used to indicate changes of your orders over time — was it accepted or rejected, canceled, or executed, and if executed, what are the price and size?</p><p>Each message has clear status, a clear ID, and a timestamp associated with it.</p><p>Many exchanges have their own workflows. Axon Trade OEMS for digital assets trading helps normalize these statuses and make them identical across all supported platforms:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/797/1*SUHGI_CUzsNTQFVF-PruzA.png" /></figure><p>Our demo application utilizes only two simple commands — NewOrderSingle (to place a new order) and OrderCancelRequest (to cancel an order we don’t need anymore).</p><p>Another useful command is OrderCancelRequest. It is used to initiate the cancellation of a pending order or the outstanding amount of a partially filled order.</p><p>Below is a sample of FIX-based OrderCancelRequest to cancel a pending order on Binance:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/478/1*HrW-MNdx9byK5rm7ZZlPPQ.png" /></figure><p>Our demo application will send requests to open an order (using NewOrderSingle) and to cancel it (using OrderCancelRequest) over the FIX to Binance. The server will notify us (using ExecutionReports) in real-time about any status changes of our order(s).</p><p>In real life, it’s always a good idea to separate business logic that makes decisions about entering or exiting the market from orders management. This component is usually complex and covers a vast array of scenarios of what can happen with orders starting from regular behavior when everything goes as expected and ending with different doomsday scenarios.</p><p>For the sake of simplicity, in this sample, we decided to use oversimplified orders management which also handles incoming market data-related events (OMS.java).</p><p>Below is the video of the working system (replayed with 50х speed):</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F2_jcEIXl90k%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D2_jcEIXl90k&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F2_jcEIXl90k%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d0ced158e0bb759480b8083cea5a4335/href">https://medium.com/media/d0ced158e0bb759480b8083cea5a4335/href</a></iframe><p>Building a successful trading system is a challenging task where you must overcome many obstacles. Our goal is to make sure that the connectivity between your application and target exchange (or exchanges) will not become one of these blocking factors. By using Axon Trade OEMS for digital assets trading, you can easily build a reliable system that can operate around the clock. Connect to our FIX API to trade on Binance or many other exchanges and/or to receive real-time normalized market data. Focus on your business and let Axon Trade be your ‘pipes and plumbing’ provider!</p><p><em>Originally published at </em><a href="https://axon.trade/renko-based-scalper-for-binance-using-axon-trade-fix-api/"><em>https://axon.trade</em></a><em> on January 31, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1edd8d2fbfb3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axontrade/scalper-for-binance-using-axon-trade-fix-api-1edd8d2fbfb3">Scalper for Binance Using Axon Trade FIX API</a> was originally published in <a href="https://medium.com/axontrade">axontrade</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Improve Execution in Crypto Markets]]></title>
            <link>https://medium.com/axontrade/how-to-improve-execution-in-crypto-markets-ed19c536d6f2?source=rss-858fabf45e6e------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed19c536d6f2</guid>
            <category><![CDATA[crypto-trading]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[hft]]></category>
            <category><![CDATA[high-frequency-trading]]></category>
            <category><![CDATA[algorithmic-trading]]></category>
            <dc:creator><![CDATA[Axon Trade]]></dc:creator>
            <pubDate>Tue, 29 Jun 2021 13:06:02 GMT</pubDate>
            <atom:updated>2023-08-07T12:53:32.595Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*oR0lQvgf4M2MePKHeKXgaA.png" /></figure><p>Among many technical questions we receive, the latency-related group definitely stands out. Having deep HFT roots, I fully share concerns about this topic. Back in the day, building strategies for FX markets, we were choosing one CPU family over the other, preferring to use switches and routers of certain non-mass-market brands, install and tune very specific network cards, and so on. By the way, we replicated all this in the Axon Trade eco-system, that is why our NY4 location is equipped with Aristas and Exablaze servers!</p><p>But, of course, all these optimizations should be made only after your code is tuned to perfection. There is no economical sense of burning thousands of dollars on expensive hardware toys while you might have a bigger problem and it’s closer than you think.</p><p>We’ve been consulting several so-called “crypto-first” prop trading shops who bought absolutely top-of-the-line/high-cost servers and rented private internet lines from Avelacom (by the way, we also use Avelacom for certain destinations) to shave 4–7 ms of network-added latency. But! And here comes the best part — they had plans to use the CCXT library to trade. Don’t get me wrong, CCXT is a great library and I personally do respect the Open Source community but CCXT is not about HFT! So the fund guys win 7 ms by using high-end hardware and private networks but lose sometimes up to 200 ms by using the wrong software.</p><p>Why do I think <a href="https://xtrd.io/">Axon Trade</a> can do any better? One of our main focuses was — and still is — lowering latency in all possible ways. We analyze exchanges’ APIs, measure execution times, and build our connectors in order to notify clients as soon as possible when something happens.</p><p>Let me give you an example. Bittrex has a REST API to submit orders and an event-driven notification channel built on top of the terrible Microsoft SignalR stack. SignalR, in its turn, provides information in “orders” and “executions” channels. Data from the “executions” channel is more informative and useful (at least from our standpoint) but sometimes it comes with 300 (!) ms delay after similar, but less granular, updates in “orders”. What is really funny is that initial responses over the REST API come (sometimes, not always, which makes it even more interesting) faster than confirmations through SignalR. We know all these nuances and our connectors are capable of dealing with such situations. Of course, it creates certain complexity and non-linear logic but this is what we do for living.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*BDZjHv0GDvHGaJggYvm2jg.jpeg" /></figure><p>Another example — when you cancel an order on Binance, you can rely on WebSocket notifications (which is a very convenient way) but in many cases, the REST API gets you a faster response. How fast? 10 ms! So you’ll know that your order has been canceled 10 ms faster and act on it accordingly. In the HFT world 10 ms is almost an eternity.</p><p>Each exchange has such “Easter eggs” and we know many of them. <a href="https://xtrd.io/">Axon Trade</a> combines powerful hardware with a software layer, optimized to “shave” 10 ms here and 45 ms there. If you are committed to win, everything matters — your algo, the way it is coded, servers to run it, the right network to communicate, and a reliable partner to execute. Cut these latencies with Axon Trade, join the club!</p><p><em>Originally published at </em><a href="https://axon.trade/how-to-improve-execution-in-crypto-markets-or-axon-trade-art-of-shaving/"><em>https://axon.trade</em></a><em> on June 29, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed19c536d6f2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axontrade/how-to-improve-execution-in-crypto-markets-ed19c536d6f2">How to Improve Execution in Crypto Markets</a> was originally published in <a href="https://medium.com/axontrade">axontrade</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 5 Quant Trading and Algotrading Blogs]]></title>
            <link>https://medium.com/axontrade/top-5-quant-trading-and-algotrading-blogs-3bd62af850da?source=rss-858fabf45e6e------2</link>
            <guid isPermaLink="false">https://medium.com/p/3bd62af850da</guid>
            <category><![CDATA[quant-trading]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crypto-trading]]></category>
            <category><![CDATA[algorithmic-trading]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[Axon Trade]]></dc:creator>
            <pubDate>Thu, 25 Mar 2021 12:26:59 GMT</pubDate>
            <atom:updated>2023-08-07T12:51:53.116Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RFT5r-lb0k6obrUa.png" /></figure><p>QuantInsti describes itself as a company that provides innovation and solutions to bridge the gap between finance and technology in the changing phase of the industry. It serves individuals, businesses, exchanges, data providers, brokers, and other technology providers to achieve their common goal of excelling in Quant &amp; Algo trading. QuantInsti provides both paid and free services to the industry.</p><p>Free services include webinars, blogs, tutorials, and trading models, algorithmic trading workshops, events, and modules for exchanges and industry. One of the most interesting and useful resources provided by QuantInst for free is their <a href="https://blog.quantinsti.com/">quant &amp; algo trading blog</a>. You can find a great selection of high-quality articles that can be a great source of information on trading for beginners and experienced traders.</p><p><a href="https://hackernoon.com/search?query=algotrading&amp;page=2&amp;configure%5BhitsPerPage%5D=12">Hackernoon</a></p><p>Hacker Noon is one of the most popular blogging platforms “built for technologists to read, write, and publish”. It is an open international community of 15,000+ contributing writers publishing stories and expertise for 3,000,000+ curious and insightful monthly readers.</p><p>Hacker Noon has a relatively small number of articles on algorithmic trading, but all of them are very professionally written — 7 of them are among Hacker Noon top stories, which means that these articles were highly rated among this huge community of IT professionals. Take a look at stories with the “algotrading” tag and see for yourself.</p><p><a href="https://quantpedia.com/blog/">Quantpedia</a></p><p>According to Quantpedia’s website, their mission is “to process financial academic research into a more user-friendly form to help anyone who seeks new quantitative and algorithmic trading strategy ideas”.</p><p>A new blog post for Premium users is created once a new strategy is added into Quantpedia. Members can see all of a strategy’s characteristics and use the Screener and visualization tools to compare it to other Quantpedia strategies. All new academic research papers related to already existing Quantpedia Premium strategies are also published on their blog, but those blog posts are visible only for Premium users. Occasionally, they find academic papers related to common quantitative trading strategies. Such papers are usually described on their <a href="https://quantpedia.com/blog/">free blog</a>.</p><p><a href="https://quantifiableedges.com/blog/">Quantifiable Edges</a></p><p>Quantifiable Edges is a website founded by Rob Hanna, a full-time market professional since 2001. He first began publishing his market views and research in 2003. From 2003 to 2007 his column “Rob Hanna’s Putting It All Together” could be found twice a week on TradingMarkets.com. In 2008 Rob began Quantifiable Edges.</p><p>This resource has been publishing quantitative research, systems, and trading ideas since 2008. Quantifiable Edges also provides unique courses for longer-time market timing and quant-based swing trading, but what you can get for free is a truly great selection of articles written by Rob Hanna himself.</p><p><a href="https://alvarezquanttrading.com/blog/">Alvarez Quant Trading</a></p><p>Cesar Alvarez, the founder of Alvarez Quant Trading, spent nine years as a professional market researcher for Connors Research and TradingMarkets.com. Cesar has been at the forefront of stock market research, having developed a number of successful trading systems now used by numerous investors and fund managers in the United States and internationally.</p><p>Most of his posts are based on the research he is doing for his own personal trading. Check out his <a href="https://alvarezquanttrading.com/blog/">blog</a> where he tests trading ideas that readers and Cesar have. The primary focus is on stocks and ETFs with a hold range of a couple of days to several months. You can get spreadsheets of the results and more. Worth mentioning is that he also posts results that did not work out. “Understanding what does not work is every bit as important as knowing what does” — Alvarez says.</p><p><em>Originally published at </em><a href="https://axon.trade/top-5-quant-trading-and-algotrading-blogs/"><em>https://axon.trade</em></a><em> on March 25, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3bd62af850da" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axontrade/top-5-quant-trading-and-algotrading-blogs-3bd62af850da">Top 5 Quant Trading and Algotrading Blogs</a> was originally published in <a href="https://medium.com/axontrade">axontrade</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coinbase Pro API Review]]></title>
            <link>https://medium.com/axontrade/coinbase-pro-api-review-d3256fbe0147?source=rss-858fabf45e6e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3256fbe0147</guid>
            <category><![CDATA[algorithmic-trading]]></category>
            <category><![CDATA[crypto-trading]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[coinbase]]></category>
            <dc:creator><![CDATA[Axon Trade]]></dc:creator>
            <pubDate>Wed, 10 Feb 2021 08:38:03 GMT</pubDate>
            <atom:updated>2023-08-07T13:37:43.018Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G1Deqtau9gBo8edomdECWg.png" /></figure><p>Like most people, my first impressions are based on visual appeal. Yes, I realize that it might be the wrong approach to judge a book by it’s cover, but it’s hard to beat human nature.</p><p>As part of the crypto exchange integration process at Axon Trade, we usually familiarize ourselves with the exchange’s provided user interface, support systems, communication channels, public documentation, and so on. I remember that the day we started working on Coinbase Pro, I posted a long and exciting speech in the internal employee group chat about my findings.</p><p>After dozens and dozens of clunky, sometimes even absurd GUIs I’ve witnessed, Coinbase Pro was like a breath of fresh air. Everything was so polished, so smooth (no, smooooooth), and worked so intuitively, that I said — “guys, that’s why Coinbase is one of most popular platforms to trade crypto. Yes, fees are high but you enjoy the process. It’s like a switchover from an old Soviet Union “Zhuguli” to Mercedes Benz. Look, they even have a FIX API!”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oa5PKlslCIPE1P9vO-bjGQ.png" /></figure><p>But then we started working with Conbase’s API. First impressions can be deceiving. Below is the list of things that puzzled us (and which we solved).</p><p><strong>Your order is not yours</strong></p><p>The FIX protocol defines a special field called <strong>ClOrdId</strong> (Client Order ID) to carry client-assigned IDs of his/her orders. The client’s OME/EMS (order/execution management system) uses these unique IDs to track each order individually for many reasons. It could be execution, reporting, accounting, or of the above.</p><p>When the server receives and accepts the client’s order, it assigns its own ID to the order (transmitted using field OrderID). This is completely reasonable because you can’t rely on a counterparty to track orders. Your system, your rules, your order IDs.</p><p>Unfortunately, in Coinbase Pro, a client’s order IDs are not really clients’. In accordance with their rules, the field <strong>ClOrdId</strong> should contain a UUID string (something like this 58d1f436–6a53–11eb-9439–0242ac130002).</p><p>Any attempts to send something different — numbers (1,2,3…), strings (my_super_order_1, cool_order_132) or any other forms of IDs will be rejected. This means that your OMS/EMS should discard the existing methodology of client side ID generation (database IDs, timestamps, random strings, and so on) and start using Coinbase Pro rules. Time to rename <strong>ClOrdId</strong> to <strong>CoinbaseClOrdId</strong>!</p><p>Wait, UUID is not that bad for ID management, there are several other exchanges that use it. Why not adopt it and stop complaining?</p><p>Because there is another surprise with <strong>ClOrdIds</strong> on Coinbase Pro! Once an order is confirmed and you received the first ExecutionReport with OrderID, you’ll never see your IDs again. Any following update attempts to extract a list of open orders or trading history — everything will contain only the Coinbase-assigned ID.</p><p>So there are challenges to solve:</p><ul><li>adopt your OMS/EMS to use UUIDs or build a mapper between your native IDs and what you send to Coinbase</li><li>build a matching mechanism that allows identifying orders using only <strong>OrderID</strong> and links it to <strong>ClOrdId</strong>s</li></ul><p>Needless to say, our clients simply don’t know about the twists and turns of this plot. <a href="https://xtrd.io/product/fix-api/">Axon Trade’s FIX API</a> is designed in a way that doesn’t limit you or creates additional obstacles to solve. Your system, your orders, your rules.</p><p>Axon Trade allows the assignment of any type of IDs — numbers or strings. Each ExecutionReport (if successful) contains an <strong>OrderID</strong> (ID in our system, always a number), and an exchange-assigned ID (could be anything) that can be used for cross-checks between internal and exchange systems for a binary, synergistic execution verification and audit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/477/1*1wZJAldwfkgaJahOwwsCJA.jpeg" /></figure><p>As a final word: Coinbase Pro is a fantastic product and a great exchange to trade on — it’s normal that some parts of a very complex offering have minor rough spots.</p><p>Axon Trade’s job is to ensure that our clients’ awareness of integration difficulties only exists from our complaints in articles!</p><p><em>Originally published at </em><a href="https://axon.trade/coinbase-pro-api-review/"><em>https://axon.trade</em></a><em> on February 10, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3256fbe0147" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axontrade/coinbase-pro-api-review-d3256fbe0147">Coinbase Pro API Review</a> was originally published in <a href="https://medium.com/axontrade">axontrade</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Different deployment options]]></title>
            <link>https://medium.com/axontrade/different-deployment-options-8d4ac701dbd5?source=rss-858fabf45e6e------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d4ac701dbd5</guid>
            <category><![CDATA[crypto-trading]]></category>
            <category><![CDATA[digital-asset]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[algorithmic-trading]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[Axon Trade]]></dc:creator>
            <pubDate>Mon, 10 Aug 2020 17:00:38 GMT</pubDate>
            <atom:updated>2023-08-07T13:43:44.064Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/804/0*82S_9FftFkJy3zFz.png" /></figure><p><strong>Colocation</strong></p><p>Colocation is a deployment of physical hardware in the <a href="https://axon.trade/">Axon Trade</a> rackmounts in Equinix NY4, a primary datacenter utilized by major financial companies and stock exchanges. One of the most secure and efficient (in terms of performance and latency) ways to start trading crypto is by leveraging these Axon Trade routing servers at Equinix.</p><p>You can send us your own hardware or rent something from our inventory. Axon Trade can offer 1U or 2U slots with both managed and unmanaged options.</p><p>With a managed option the Axon Trade team will take care of your hardware (monitor, component replacement, backups etc), while unmanaged means that it has to be done by your engineers.</p><p>From our experience, if you want to get the best possible performance — colocation is the only choice. With direct access to hardware and software, you can tune servers to outperform virtual instances offered by cloud providers. Of course, it all comes with a price and depends on your end goals. For example, a Honda is a great car to do pretty much everything — travel, commute to work, help your friend to move to another location but if you need to run a race — consider a Ferrari.</p><p>Pros of dedicated managed hardware:</p><ul><li>Low network latency</li><li>High performance</li><li>High security</li><li>Full control over the hardware</li></ul><p>Cons:</p><ul><li>Cost of hardware</li><li>Cost of hardware maintenance</li></ul><p><strong>Cross-connection</strong></p><p>If your servers are already in Equinix, another great option is cross-connection. With minimal latency, you can communicate with Axon Trade’s servers to consume market data and route orders to major cryptocurrency exchanges in the US, Asia, and Europe.</p><p>Axon Trade’s state-of-the-art network infrastructure based on high-performance Arista switches will deliver FIX messages in and out in no time!</p><p>Pros</p><ul><li>Low network latency</li><li>High security</li><li>Ability to reuse your own hardware</li></ul><p>Cons</p><p><strong>VPN</strong></p><p>If network latency for you is not an issue, we can offer access to our services through encrypted VPN channels. It’s easy to configure and doesn’t necessarily require purchasing expensive hardware.</p><p>With this type of connection, clients are able to access the same resources as cross or direct connection but with a bit higher network latency caused by SSL/TLS encryption.</p><p>This is an ideal set up during the development/integration phase followed by migration to more advanced (and fast) cross-connection or colocation methods. Nevertheless, VPN can still be used for a variety of applications that do not require low latency.</p><p><strong>VPS</strong></p><p>Virtual Private Server (or VPS for short) is a good alternative to the co-location option. Instead of physical servers, your code will be running inside a virtual machine. This is a perfect option when you just want to do a quick test of your ideas.</p><p>Pros</p><ul><li>No long-term obligations</li><li>Hardware knowledge is not required</li><li>Easy to maintain (backup, restore, destroy)</li><li>Less expensive</li></ul><p>Cons</p><ul><li>Less tuning options</li><li>Less performance</li></ul><p>VPS deployment options are available through our partners such as UltraFX VPS.</p><p>Let us know if you would like to try our services with a no-cost, no-obligation trial period!</p><p><em>Originally published at </em><a href="https://axon.trade/different-deployment-options/"><em>https://axon.trade</em></a><em> on August 10, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d4ac701dbd5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axontrade/different-deployment-options-8d4ac701dbd5">Different deployment options</a> was originally published in <a href="https://medium.com/axontrade">axontrade</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Axon Trade’s Fort Knox of Authentication]]></title>
            <link>https://medium.com/axontrade/axon-trades-fort-knox-of-authentication-bf3941062c42?source=rss-858fabf45e6e------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf3941062c42</guid>
            <category><![CDATA[crypto-trading]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[algorithmic-trading]]></category>
            <category><![CDATA[digital-asset]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Axon Trade]]></dc:creator>
            <pubDate>Fri, 24 Jul 2020 12:58:41 GMT</pubDate>
            <atom:updated>2023-08-07T13:49:18.894Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/804/0*BQoFDwQsysel6SLK.png" /></figure><p>When it comes to cybersecurity, especially in the digital asset industry, there is no room for compromises!</p><p>Of course, this is a very hot topic and it’s always easy to talk about it rather than implement it in practice. These are additional procedures to follow, extra techniques to use, more people to hire. We built our systems taking into account the hostile environment where we will operate. Here is a brief overview of what Axon Trade does in order to protect our clients’ digital assets.</p><p><strong>Restricted access</strong>. Our servers are not available over the public internet. In order to trade, clients have to cross-connect with Axon Trade within Equinix IBX data centers. Another option is to set up a VPN tunnel. In both cases, we know who the customer is.</p><p><strong>Isolated environment for clients</strong>. Each client runs their operations within an isolated network segment invisible to other participants. This isolation is controlled by hardware and software layers.</p><p><strong>Components separation</strong>. Axon Trade is built as a modular system (different data buses, routing components, data normalization farm, streamers, databases, monitoring, journaling, and so on) where components are separated by firewalls (if required by business logic). Each component can access only very specific IP addresses and ports. And, of course, no access to the operating environment is available over the public Internet!</p><p><strong>Data encryption</strong>. Despite the fact that components are isolated and covered by firewalls, they “talk” to each other only through encrypted channels. Even internally. That’s the rule!</p><p><strong>No sensitive information stored as a plain text</strong>. We deal with passwords, keys, and other forms of client’s credentials. This information is never stored unencrypted. API calls (yes, we do have REST API for accounts management) never return real data. Logs/journal records are scrambled to avoid unexpected leaks.</p><p><strong>Protected from people’s failure</strong>. Axon Trade uses techniques similar to launch sequences on nuclear submarines — in order to start the system, it required a combined effort of several people. So in case of an unlikely event when one part of the key was compromised, it’s still not enough to obtain access — analogous to a multi-signature wallet concept.</p><p><strong>Authentications and authorization</strong>. The majority of Axon Trade resources require authentication prior to obtaining access. In addition, access to certain resources is limited by a role-based authorization system.</p><p><strong>Journaling and monitoring</strong>. All events, big and small, are carefully monitored and added into a journal. We know who was doing what and when. Of course, this information is carefully stored and backed up via tape on separate geographically distant servers.</p><p>Axon Trade has many more secure controls but we are keeping some of our secrets!</p><p>Let us know if you would like to try our services with a no-cost, no-obligation trial period!</p><p><em>Originally published at </em><a href="https://axon.trade/engineering-axon-trade-fort-knox-of-authentication/"><em>https://axon.trade</em></a><em> on July 24, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf3941062c42" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axontrade/axon-trades-fort-knox-of-authentication-bf3941062c42">Axon Trade’s Fort Knox of Authentication</a> was originally published in <a href="https://medium.com/axontrade">axontrade</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>