<?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 Alexey Levin on Medium]]></title>
        <description><![CDATA[Stories by Alexey Levin on Medium]]></description>
        <link>https://medium.com/@Aelay?source=rss-caf01c0fa255------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*smsN5c9mUwka83CZ2n7r0A.jpeg</url>
            <title>Stories by Alexey Levin on Medium</title>
            <link>https://medium.com/@Aelay?source=rss-caf01c0fa255------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 23:57:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Aelay/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[Digitex 2020 kick-off]]></title>
            <link>https://medium.com/smartdec/digitex-2020-kick-off-1409f67fdab7?source=rss-caf01c0fa255------2</link>
            <guid isPermaLink="false">https://medium.com/p/1409f67fdab7</guid>
            <category><![CDATA[news]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[smartdec]]></category>
            <category><![CDATA[digitex-futures]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Alexey Levin]]></dc:creator>
            <pubDate>Fri, 31 Jan 2020 18:16:55 GMT</pubDate>
            <atom:updated>2020-01-31T18:16:55.408Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zf5S3I9lp3dZULeY.png" /></figure><p>Hi everybody, long time, no see!</p><p>The work on Digitex continues, no disturbances.</p><p>Since mid-January we have been busy with planning, while also implementing various urgent tasks.</p><p>During the New Year we worked some extra time, but we are happy with the result — the Trading Battle is Live on the Testnet. This has generated some great positive feedback. The daily volumes on the Testnet reach as high as 5 billion traded contracts.</p><p>Adam will be in Moscow next week to talk about all the procedures on delivering the system to him for the Mainnet Launch.</p><p>We will be providing updates on the process.</p><p>In the following update we will be announcing timelines for the release of the Mainnet version. The preliminary date for this release is 27 April, 2020.</p><p>Stay tuned! 2020 promises to be exciting!</p><blockquote><em>This article was created by </em><a href="https://smartcontracts.smartdec.net/"><em>SmartDec</em></a><em>, a security team specialized in static code analysis, decompilation and secure development.</em></blockquote><blockquote><em>Feel free to use </em><a href="https://tool.smartdec.net/"><em>SmartCheck</em></a><em>, our smart contract security tool for Solidity and Vyper, and follow us on Medium, </em><a href="https://t.me/SmartDec"><em>Telegram</em></a><em> and </em><a href="https://twitter.com/SmartDecTeam"><em>Twitter</em></a><em>. We are also available for </em><a href="https://smartcontracts.smartdec.net/"><em>smart contract development and auditing work</em></a><em>.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*ZLZzssHIjnXRjqVa.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1409f67fdab7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/smartdec/digitex-2020-kick-off-1409f67fdab7">Digitex 2020 kick-off</a> was originally published in <a href="https://medium.com/smartdec">SmartDec Cybersecurity Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Christmas Digitex Update]]></title>
            <link>https://medium.com/smartdec/christmas-digitex-update-3f66db34cd08?source=rss-caf01c0fa255------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f66db34cd08</guid>
            <category><![CDATA[smartdec]]></category>
            <category><![CDATA[news]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[digitex-futures]]></category>
            <dc:creator><![CDATA[Alexey Levin]]></dc:creator>
            <pubDate>Fri, 20 Dec 2019 18:55:42 GMT</pubDate>
            <atom:updated>2020-01-22T09:29:14.674Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WrlVTyEV92cFvRFu.png" /></figure><p>On <strong>November 30</strong>, exactly as planned, the Digitex exchange successfully launched on the testnet. We worked hard and are very pleased with the result. We celebrated the launch and continue to improve the exchange. Now we are developing a work plan for year 2020.</p><p><strong>What we are doing in December:</strong></p><p>From the moment of launch, we have been monitoring the system to be sure that it’s working stable. The last workweeks of the year have been spent on processing the huge volume of feedback from testnet. We have a long list of inquiries from users, a lot are questions or suggestions, many are very helpful or even inspiring. We are sincerely grateful to users for participating in improving the functionality of the system.</p><p>We have prepared the updates that include bug fixes and UI updates. We also would like to use this occasion to remind everybody that these are test tokens that have no real value and will be reset at random times.</p><p>Some of the features that were added to the Digitex Exchange in December:</p><ul><li>the ability to close positions separately (by price), not based on the FILO (first in last out) principle</li><li>the chart of the market depth to the left of the ladder</li><li>the price chart was updated to be as user-friendly as possible</li><li>fixed other minor issues</li><li>now we are working to add functionality that allows holding <strong>tournaments</strong> between users and we plan to finish it this year</li><li>we are also working on experimental zero-knowledge order book verification and some ui redesigns we might also roll them out this year.</li></ul><h3><strong>Let us now highlight the plans for the year 2020</strong></h3><p>The main priority is getting the system ready for the <strong>Mainnet Launch</strong>.</p><p>To achieve this Milestone a number of projects must be completed, here is the tentative list of these projects:</p><h4><strong>1. Adding a much more extensive Back Office and Administrative functionality</strong></h4><p>Before releasing a mainnet-ready version, we need to be sure that the exchange management systems and back office work perfectly.</p><ul><li><strong>Risk management</strong></li></ul><p>This includes such features as controlling position limits, price limits and other limits, tools for setting the parameters for the exchange and markets, such as leverages supported and more.</p><p>A very important part of this project is integration with the insurance fund, which now is only in plans.</p><ul><li><strong>Exchange management</strong></li></ul><p>This includes functionality to safely start and stop the trading and other similar features.</p><ul><li><strong>User management</strong></li></ul><p>E.g. bans and such.</p><h4>2. Additional instrument-related functionality</h4><ul><li><strong>There must be implemented a procedure for global settlement for perpetual instruments and other necessary updates to the instrument.</strong></li></ul><p>You can see that these procedures can be done with a hard reboot on the testnet, but for the mainnet they must be done through a strict secure protocol. The good news that now that the core functionality is in place, adding them is just a matter of careful implementation.</p><ul><li><strong>The Spot Price Oracle must be mainnet-ready.</strong></li></ul><p>Any cases of loss or corruption of data for the spot oracle can be critical on mainnet, as we know, more than one project was hurt by such malfunctions in the past.</p><h4>3. 2FA and other required security features</h4><p>Many of these also were not necessary on the testnet, but must be fully functional before the MainNet.</p><h4>4. <strong>Documentation revamp and formal verification</strong></h4><ol><li>Verify implementation to the spec</li><li>Verify tests with the spec</li><li>All tests pass</li></ol><p>For the testnet the descriptions of markets could be kept in the most convenient way for the fast dev process, on the mainnet these will be published and must provide exact specification of the contract. Adding to that User Guides and similar resources will be put in place.</p><h4>5. Integrating a third-party KYC system</h4><h4>6. <a href="https://en.wikipedia.org/wiki/Fault_tolerance">Fault-tolerance</a>, backup systems and such</h4><ul><li><strong>Backup servers and syncing them. Testing recovery time.</strong></li></ul><p>We need to conduct a study of all possible emergencies (hardware malfunction/disconnects or such). Emergency scenarios must not lead to money loss.</p><h4>7. Extensive Stress- and Load-testing</h4><p>New bottlenecks that are discovered must be taken care of.</p><h4>8. Monitoring module</h4><p>A requirement for the mainnet is a very thorough monitoring of all parts of the system for detecting any problems.</p><h4>9. Multiple independent audits of various nature</h4><ul><li><strong>Internal Security Audit</strong></li></ul><p>Being an infosec-centered firm ourselves, we will conduct an internal security audit running our code-analysis scanner (link) on all the codebase, and manually checking for possibilities of ddos, spam of other attacks on the system.</p><ul><li><strong>External Audits</strong></li></ul><ol><li>Software audit</li><li>Security audit</li></ol><p>Any issues or bugs that are found must be fixed and everything must be re-checked. We are confident in our code, however it would be irresponsible to plan releases before the results of audits are in.</p><h4>10. We are also reviewing our codebase for any technical debt that might consume more time</h4><h3>Now let us go over other plans, completion of which is not a requirement for the MainNet Launch.</h3><h4><strong>1. Tournaments</strong></h4><ul><li>A simple version of tournaments is already in development and soon will be on the testnet.</li><li>A more extensive version of tournaments might be implemented in the future.</li></ul><h4><strong>2. New UI</strong></h4><p>In particular, adaptation of the web front-end for Mobile.</p><h4>3. A separate <strong><em>Mobile App</em></strong> client.</h4><h4>4. More <strong>Tools for the Trader</strong>!</h4><p>Now the system only supports a limited set of functions a trader can utilize (for example, all orders are GTC, stop-loss and make-profit are not shipped yet). All of these features can and will be implemented. A stretch goal here is shipping a tool in which a trader can set up their own bots.</p><h4><strong>5. Public API</strong></h4><p>This would open up the exchange for algorithmic trading giving a huge boost to liquidity.</p><h4>6. Support for <strong>More Instruments.</strong></h4><p>Now the system is running only the first pilot instrument — direct BTC/USD perpetual. The procedure of adding new instruments, among the first — an inverse BTC/USD and an ETH/USD contracts, should be simple and fast. For that, internal tooling must be implemented.</p><h4><strong>7. Spot Markets</strong>.</h4><p>In order to provide the most seamless UX, the user should be able to buy DGTX for ETH on the exchange. Such integration is also on the list of plans.</p><h4><strong>8. Architecture review</strong></h4><p>It would be very valuable to make this a separate full-scope project in order to get rid of any leftover legacy and plan ahead for any redesigns that can give major boosts in performance.</p><h4><strong>9. Analytics</strong></h4><p>Another separate project that will give a lot of value is this one. In order to release features in the most effective manner, the staff should see how many users are on, how many registered, what is their behaviour and such.</p><h4><strong>10. Social Platform</strong></h4><p>There is a visionary idea of adding a lot of social functionality to the exchange, the ability to post technical analysis charts, to do streams and video-calls. Adding all that is a huge project, which however can make the exchange a real jewel.</p><h4><strong>11. Decentralized and non-custodial solutions</strong></h4><p>This December we plan to release to the testnet some experimental solutions that we want to serve as a basis for the future non-custodial tech. However, we have to say that as with all other non-custodial solutions that are fast, everything is still in prototype versions. We don’t know if any of the teams in the space including us will be able to achieve actual production use in a real exchange with real volumes for real money during 2020. However, this might be possible and we will allocate developer time to this.</p><p>As you can see this is quite an extensive list. Not every project on the list will be included in the actual production. Right now we are discussing the priorities for the development and assessing the resources needed for each of these projects. We plan to get back to you with our next communication around the end of January.</p><p><strong>As for immediate plans</strong>, the team is going to have some rest on the new year holidays. And in January we will get back to work!</p><p><strong>In short</strong>, we congratulate everybody again with the successful TestNet Launch and we are already planning for the next Milestone.</p><p><strong>Happy New Year everybody!</strong> We wish everyone to have great rest on Holidays and enter 2020 fresh and productive as we certainly will!</p><blockquote>This article was created by <a href="https://www.smartcontracts.smartdec.net/?source=post_page---------------------------">SmartDec</a>, a security team specialized in static code analysis, decompilation and secure development.</blockquote><blockquote>Feel free to use <a href="https://tool.smartdec.net/?source=post_page---------------------------">SmartCheck</a>, our smart contract security tool for Solidity and Vyper, and follow us on Medium, <a href="https://t.me/SmartDec?source=post_page---------------------------">Telegram</a> and <a href="https://twitter.com/SmartDecTeam?source=post_page---------------------------">Twitter</a>. We are also available for <a href="https://smartcontracts.smartdec.net/?source=post_page---------------------------">smart contract development and auditing work</a>.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/0*i1ylH3KdJAZSyVFH.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f66db34cd08" width="1" height="1" alt=""><hr><p><a href="https://medium.com/smartdec/christmas-digitex-update-3f66db34cd08">Christmas Digitex Update</a> was originally published in <a href="https://medium.com/smartdec">SmartDec Cybersecurity Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SmartDec: Digitex Futures Exchange Development Status Report #10]]></title>
            <link>https://medium.com/smartdec/smartdec-digitex-futures-exchange-development-status-report-10-1e4970cedae5?source=rss-caf01c0fa255------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e4970cedae5</guid>
            <category><![CDATA[news]]></category>
            <category><![CDATA[digitex]]></category>
            <category><![CDATA[testnet]]></category>
            <category><![CDATA[smartdec]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Alexey Levin]]></dc:creator>
            <pubDate>Thu, 14 Nov 2019 16:23:47 GMT</pubDate>
            <atom:updated>2019-11-14T16:23:47.824Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QMXRkw0lv3KlXrGZ8NeYrw.jpeg" /></figure><p>This is the last technical report before the testnet release! The previous report can be found <a href="https://blog.smartdec.net/smartdec-digitex-futures-exchange-development-status-report-9-caa7a1b825b6">here</a>.</p><p>This summer and autumn were an exciting journey.</p><p>In May, we discussed with Adam Todd the possibility of leading the effort for developing the software infrastructure for his Digitex exchange.</p><p>In particular, from the very beginning Adam asked us to be extremely transparent about the development, and we agreed to publish regular reports about how we are proceeding. You can take a look back and read all of them in our blog:</p><p><a href="https://blog.smartdec.net/smartdec-plans-to-be-the-developer-for-the-digitex-exchange-38a2dc0f2270">Initial Report</a></p><p><a href="https://blog.smartdec.net/smartdec-digitex-futures-exchange-development-status-c8b8bacafb48">Status Report #1</a></p><p><a href="https://blog.smartdec.net/smartdec-digitex-futures-exchange-development-status-report-2-4dc7d67dcaf1">Status Report #2</a></p><p><a href="https://blog.smartdec.net/smartdec-digitex-futures-exchange-development-status-report-3-f0d1281c553a">Status Report #3</a></p><p><a href="https://blog.smartdec.net/smartdec-digitex-futures-exchange-development-status-report-4-5441a60a099">Status Report #4</a></p><p><a href="https://blog.smartdec.net/smartdec-digitex-futures-exchange-development-status-report-5-d52f5d5d6fda">Status Report #5</a></p><p><a href="https://blog.smartdec.net/digitex-intermediate-report-58396b1a961e">The intermediate report</a></p><p><a href="https://blog.smartdec.net/smartdec-digitex-futures-exchange-development-status-report-6-db7c4024540c">Status report #6</a></p><p><a href="https://blog.smartdec.net/smartdec-digitex-futures-exchange-development-status-report-7-7ab8c8ba97f9">Status report #7</a></p><p><a href="https://blog.smartdec.net/smartdec-digitex-futures-exchange-development-status-report-8-871a640ec4dc">Status report #8</a></p><p><a href="https://blog.smartdec.net/smartdec-digitex-futures-exchange-development-status-report-9-caa7a1b825b6">Status report #9</a></p><p>Now we are publishing the 10th report, our first round number, almost exactly half a year into the project. The next report will be the Testnet Release.</p><p>The first weeks were spent on completing the full audit of the legacy code and the proposal.</p><p>After we were done with that, we took on the development.</p><p>During the summer, we rewrote the matching engine virtually in its entirety. We also implemented extensive infrastructure around the engine, the web back-end, various connector and API libraries and finally, the cherished UI, which was re-designed multiple times (and is being re-designed yet again as we speak, oh, Adam, the perfectionist).</p><p>We have spent some time on assessing the current state of ethereum scalability tech, including plasma, zkSNARKS and such, however, none of the solutions are ready yet for the high-load that a live derivatives exchange demands. Yet, we are keeping tabs on the fast progress in the field and thinking about ways we can integrate these solutions with the exchange when they are ready. By the way, our own Alexander Drygin and Sergey Khokhlov won yet <a href="http://utonhack.com/">another hackathon</a> a few weeks ago with an idea based on zk-tech that might find an application in the Digitex platform. This project is called “Proof of Trade” and solves the problem of proving historical trading performance. We are going to publish the article with a detailed explanation in the near future.</p><p>The Fall was mostly spent on integrational testing, building all the components together, debugging and, finally, continuous stress-testing.</p><p>Stress-testing is a process in which we throw a very high load on the system and watch closely, which part will break first, which part is the bottleneck. Then we think about ways to make that part handle higher throughput, implement them and re-iterate. As a result, the capabilities of the system are constantly growing.</p><p>In the <a href="https://blog.smartdec.net/smartdec-digitex-futures-exchange-development-status-report-9-caa7a1b825b6">last post</a> we wrote that the bottleneck we discovered was created by Daphne and Redis. We have worked on several solutions: we implemented a version that uses Uvicorn instead of Daphne, we also assessed an option of scaling vertically by using more expensive instances on AWS, but, more interestingly, we have implemented a replacement for Daphne in Golang. We are still testing this solution and assessing which one to use during the open testnet phase, but, in fact, we can go with either.</p><p>In the meantime, as we mentioned in the last <a href="https://www.youtube.com/watch?v=gClSPXlAfRg">AMA with Adam and</a>, the Closed AlphaTest has already started. Until now, these were only the very few first testers that are close to the dev team, but over the weekend the plan is to onboard another hundred. As always, first users bring the first feedback, which we have started recording and integrating into the development cycle.</p><p>On the development front, we have the following news.</p><p>The logic of the funding procedure is implemented not only in the engine, but also in the UI. Under the trade list on the trading page user can see the funding rate, payout sum and timer until the next funding.</p><p>We also added logic of closing position to the user interface. The difference between closing a position and ordinary limit/market orders is that closing a position does not require an order margin.</p><p>We added Profit-and-Loss (PNL) in the UI. The PNL value is calculated for the current user’s position and becomes zero after the funding. Also we added calculation of the Unrealized PLN to the ladder interface. UnPNL is displayed in the last column of the ladder from the side that is opposite to the position of the trader. Also we fixed the bug of the Price Oracle, which was crashing sometimes.</p><p>Finally, we want to add that we plan on posting a little less often after the testnet launch. The reports will probably not follow a fixed bi-weekly schedule (but there still will be reports as often as we have enough content to share).</p><p>The reasons are simple, we are constantly distracted from development by writing posts. We take this responsibility seriously, so it takes a lot of time to prepare them. Also, frequent posts become not as informative and mundane. If you want to keep up with the project, instead of reading one thorough report per quarter, you have to parse 6 posts and compile your understanding from them.</p><p>As usual, stay tuned, next post will have the actual details of the Testnet Release. Thank you for monitoring the progress!</p><blockquote><em>This article was created by </em><a href="https://smartcontracts.smartdec.net/"><em>SmartDec</em></a><em>, a security team specialized in static code analysis, decompilation and secure development.</em></blockquote><blockquote><em>Feel free to use </em><a href="https://tool.smartdec.net/"><em>SmartCheck</em></a><em>, our smart contract security tool for Solidity and Vyper, and follow us on Medium, </em><a href="https://t.me/SmartDec"><em>Telegram</em></a><em> and </em><a href="https://twitter.com/SmartDecTeam"><em>Twitter</em></a><em>. We are also available for </em><a href="https://smartcontracts.smartdec.net/"><em>smart contract development and auditing work</em></a><em>.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*KJ6ChW-WZwhXsy14.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e4970cedae5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/smartdec/smartdec-digitex-futures-exchange-development-status-report-10-1e4970cedae5">SmartDec: Digitex Futures Exchange Development Status Report #10</a> was originally published in <a href="https://medium.com/smartdec">SmartDec Cybersecurity Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Digitex Intermediate Report]]></title>
            <link>https://medium.com/smartdec/digitex-intermediate-report-58396b1a961e?source=rss-caf01c0fa255------2</link>
            <guid isPermaLink="false">https://medium.com/p/58396b1a961e</guid>
            <category><![CDATA[smartdec]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[digitex-futures]]></category>
            <category><![CDATA[news]]></category>
            <dc:creator><![CDATA[Alexey Levin]]></dc:creator>
            <pubDate>Thu, 05 Sep 2019 19:49:32 GMT</pubDate>
            <atom:updated>2019-09-05T19:49:32.020Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*goSpY3zMtCwAyL8ihdOX0A.png" /></figure><p>In the <a href="https://blog.smartdec.net/digitex-testnet-release-date-c0bd5f27e26d">last blog post</a>, we promised to give more detail on what has been done since we started working with <a href="https://digitexfutures.com/">Digitex</a>. We collected several notes from our work until now and prepared this report.</p><p>In the beginning, we received the code from the Dublin development team that had been worked on for the launch of a centralized exchange. The project contained the following components: UI, web back-end, several databases, message queue, and the engine itself.</p><p>However, while the code was extensively documented, it was far from a production-ready implementation. The code was untested and not debugged. We still had much work to do.</p><p>Now, let’s go over details.</p><h4><strong>Web-app</strong></h4><p>Web back-end is realized using Django. We started testing and found out that parts of functionality didn’t work and parts were incomplete. For example, one could login with an account that was hardcoded into the database, but could not create a new account through the web front-end. 2FA was there in the interface design images, but not functioning. Password reset was there in code but needed debugging. The ladder interface was there, but only partially functional. There was no functionality to manually place orders not using the ladder interface.</p><p>We have now added 17 user-story images for the UI, have debugged the code, added parts that were missing in the ladder interface and have moved over to extensive testing.</p><h4><strong>Back Office</strong></h4><p>The system did not have Back Office.</p><p>We have gathered the requirements on Back Office from Adam and consulted third party experts who have been developing similar systems, created tech specs, decomposed the problem and chose what can be made using third party plug-ins. In particular, the current plan is to use ZenDesk. Everything that is not a third party component is now in development: graphical designs of pageviews have been made, web designs are being produced, functional parts are close to being available for testing.</p><h4><strong>PostgreSQL database</strong></h4><p>After we made the scheme of the database we received, we made a decision that it needed to be modified heavily, since there were a lot of unused tables in it. Now the scheme is adapted and we have started optimizing the database. Our specialists are performing database setups, creating replication scenarios, and node allocations. All of this is needed for fault tolerance and for maintaining performance characteristics.</p><h4><strong>RabbitMQ message queue</strong></h4><p>After first stress tests our team was rather surprised by the performance of the system. It was not apparent how it could support Adam’s requirements of 10,000 users. We went on to investigate the reasons. It turned out that we had a system realized using HTTP RESTful API endpoint that supported no more than 30 requests of order placement/cancelation per second.</p><p>The reasons for such low performance were:</p><ol><li>The system was initializing connections to redis (the cache database) and to RabbitMQ for every request.</li><li>Two-step method of data transmission from the engine to the HTTP REST API handler, which was also using polling.</li></ol><p>The overall performance was measured for the RabbitMQ. Tests showed that with standard setup RMQ allows transmitting 20k messages per second. Another reason the system had low performance was that for transmission between the kernel and web module message serialization was implemented with custom code. Besides that, only a limited number of message types was supported, which would prohibit future expansion of the scope of the project</p><p>During the course of the work, we have removed the intermediate link for transmitting messages from the kernel to the REST API. We also implemented the support for connecting to the Kernel directly using TCP. This connection supports up to 500,000 basic messages per second (ignoring the business logic). We use Google’s <a href="https://developers.google.com/protocol-buffers/">Protocol Buffers</a> for serialization now.</p><h4><strong>Futures-Engine Kernel</strong></h4><p>We received a realization of the kernel that had 420087 lines of code in C and C++. External components contained 409478 LOC. Investigation into the code showed that a lot of external components were basically unused and could be easily removed. After that, the size of the repo was 10609 LOC, out of which, 1911 lines were tests. So, the actual codebase was 8698 lines of code. Testing and analysis of the code showed that only the simplest cases had been implemented. In order to implement the logic of the engine, the team had to deconstruct all the mathematics behind the exchange operation and futures/perpetuals market and has written most of the corresponding specifications. All of that is added to the realization of the kernel, which is ready for testing.</p><p>In order to perform extensive testing of the kernel, a decision was made to develop special robots-simulations that would imitate some strategies, mimicking users.</p><p>During the analysis, we also noticed an attempt to make the code cross-platform. For the first phase of the realization we abandoned cross-platform capabilities, which allowed us to simplify the development significantly, simplify linking for various objects and simplifying building.</p><p>The current realization of the engine supports around 40,000 transactions per second. One transaction includes order placement, matching, creating a trade and communicating the event to observers in the market, so one transaction can lead to 4 messages from the engine to users.</p><h4><strong>In Conclusion</strong></h4><p>This was a collection of notes we aggregated over the summer. Since then, the development has already moved further. We are now busy with integrational testing, building all components of the exchange together, trying to run them as a whole. The reader should not be mistaken that this means that the exchange is almost ready. There is a long road of taking the first version to the first stable secure version. However, internally, we are pretty excited as we are moving forward.</p><blockquote><em>This article was created by </em><a href="https://smartcontracts.smartdec.net/"><em>SmartDec</em></a><em>, a security team specialized in static code analysis, decompilation and secure development.</em></blockquote><blockquote><em>Feel free to use </em><a href="https://tool.smartdec.net/"><em>SmartCheck</em></a><em>, our smart contract security tool for Solidity and Vyper, and follow us on Medium, </em><a href="https://t.me/SmartDec"><em>Telegram</em></a><em> and </em><a href="https://twitter.com/SmartDecTeam"><em>Twitter</em></a><em>. We are also available for </em><a href="https://smartcontracts.smartdec.net/"><em>smart contract development and auditing work</em></a><em>.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*IUoBlwUiP3i2EMfR.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=58396b1a961e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/smartdec/digitex-intermediate-report-58396b1a961e">Digitex Intermediate Report</a> was originally published in <a href="https://medium.com/smartdec">SmartDec Cybersecurity Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Digitex Testnet Release Date]]></title>
            <link>https://medium.com/smartdec/digitex-testnet-release-date-c0bd5f27e26d?source=rss-caf01c0fa255------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0bd5f27e26d</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[digitex-futures]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[news]]></category>
            <category><![CDATA[smartdec]]></category>
            <dc:creator><![CDATA[Alexey Levin]]></dc:creator>
            <pubDate>Thu, 22 Aug 2019 18:01:02 GMT</pubDate>
            <atom:updated>2019-08-22T18:01:02.350Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4bhOM5vQelWqOE5wAamFxQ.png" /></figure><p>Two months ago we <a href="https://blog.smartdec.net/smartdec-plans-to-be-the-developer-for-the-digitex-exchange-38a2dc0f2270">announced</a> that we are in a conversation with <a href="https://digitexfutures.com/">Digitex</a> on leading the development of the exchange.</p><p>We then committed to performing a review of the suggested system and current implementation from all angles. As the community already knows, since then we have completed this work and, at this point, already started working on the development of the system.</p><p>An enormous amount of progress has been made, yet even more is left to do.</p><p>We will publish the story of this summer’s work, detailing the analysis, bug fixes, changes to the architecture and more in another post, probably with the next bi-weekly update.</p><p>But now, for the news that everybody has been waiting for. We are ready to announce that <strong>we will have a beta version ready for Testnet Launch on November 30th 2019.</strong></p><p>With some optimism, we could expect to have it earlier than that, but we won’t commit to that now.</p><p>Testnet launch means an actual functioning exchange, but on a Testnet (such as <a href="https://ropsten.etherscan.io/">Ropsten</a>, <a href="https://ethereum.stackexchange.com/questions/37465/how-is-rinkeby-different-from-mainnet">Rinkby</a> and others), where the ETH and all tokens are “toy” versions of themselves, not carrying real monetary value. We estimate that the Testnet version will be capable of supporting up to 10,000 users concurrently. As we deploy and integrate all parts of the exchange together and continue stress testing, we will have more precise numbers for the technical capabilities of the system. This initial launch will be a fully centralized version of the exchange.</p><p>Even before the Testnet launch, we will be running closed tests, available for a limited number of users. And after several months of Testnet run and third-party audits, the system should be ready for the Mainnet Launch.</p><p>The plan is for this initial Testnet Launch to support a single market — a DGTX-funded perpetual swap BTCUSD contract. A perpetual contract is a similar instrument to a futures contract, however, it persists and is not terminated after the Funding event — an analog to Settlement. There will also be functionality to simply buy and sell Testnet DGTX for ETH in order to enter the market.</p><blockquote><em>This article was created by </em><a href="https://smartcontracts.smartdec.net/"><em>SmartDec</em></a><em>, a security team specialized in static code analysis, decompilation and secure development.</em></blockquote><blockquote><em>Feel free to use </em><a href="https://tool.smartdec.net/"><em>SmartCheck</em></a><em>, our smart contract security tool for Solidity and Vyper, and follow us on Medium, </em><a href="https://t.me/SmartDec"><em>Telegram</em></a><em> and </em><a href="https://twitter.com/SmartDecTeam"><em>Twitter</em></a><em>. We are also available for </em><a href="https://smartcontracts.smartdec.net/"><em>smart contract development and auditing work</em></a><em>.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*rf_Hb-ScuO6rercf.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0bd5f27e26d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/smartdec/digitex-testnet-release-date-c0bd5f27e26d">Digitex Testnet Release Date</a> was originally published in <a href="https://medium.com/smartdec">SmartDec Cybersecurity Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Volor Flex]]></title>
            <link>https://medium.com/@Aelay/volor-flex-eec0432ada0f?source=rss-caf01c0fa255------2</link>
            <guid isPermaLink="false">https://medium.com/p/eec0432ada0f</guid>
            <dc:creator><![CDATA[Alexey Levin]]></dc:creator>
            <pubDate>Mon, 09 Feb 2015 22:24:55 GMT</pubDate>
            <atom:updated>2015-02-09T22:24:55.523Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Fvisual%3Dtrue%26url%3Dhttp%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F26856894%26show_artwork%3Dtrue&amp;url=https%3A%2F%2Fsoundcloud.com%2Forigamisound%2Fvolor-flex_you-in-me&amp;image=http%3A%2F%2Fi1.sndcdn.com%2Fartworks-000014644626-fsycst-t500x500.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=soundcloud" width="500" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/149e0ab4aa6e49e7b8f5ffe9bd3d07df/href">https://medium.com/media/149e0ab4aa6e49e7b8f5ffe9bd3d07df/href</a></iframe><p>#music #Volor #Flex</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eec0432ada0f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>