We conduct regular AMA sessions on our official Telegram channel. Join us to ask questions and get the latest news and updates from trade.io.
Telegram: https://t.me/TradeToken
Marcin, Hello everybody!
Q. Are we still on time to get FX, API and App by end of the year (i.e. less than 4 weeks from now)?
OK, heavy topics just from the beginning,
Let's start with FX: We have an internal commitment for a specific date: Dec. 27th and dedicated team works tirelessly to make it happen. No delays or unexpected events so far, we are on track although it is very tight timeframe, but...Please note this is Phase 1 of a 2 Phase launch. Phase 1 being FX being available to trade.io exchange clients only and crypto only deposits. Phase 2 which we’re expecting completion in early Q1 of 2019 will have stand-alone sites for our FCA & OffShore Entities, TIO Markets UK Ltd. & TIO Markets Ltd... These stand-alone entities will allow clients to register directly from the site and will allow funding in crypto and a variety of fiat methods. Additionally, there will be a complete affiliate program offering top-tier CPA programs with state of the art tracking software.
So, back to the topic, mobile experience next:
So, you already know we work on a couple of mobile products: iOS and Android mobile native trading applications and also on the mobile-friendly version of our exchange website. The most significant changes related to the mobile-friendly website are planned for the release this Monday and there will be most likely 1-2 subsequent releases improving some smaller UI experience defects on the subsequent Mondays…
As for the mobile native apps: iOS is planned to be dev-complete and ready for internal testing next week. We are planning to involve some of our dedicated community members in the Beta testing phase as soon as the app code is signed off by our security experts after the review of the potential security holes…
As for the Android, it will come around 2 weeks later, but we still believe we will be dev ready this year. It means that the iOS version should be released to the public by the end of this year and Android in early January after all the alpha, beta and security tests are concluded.
Q. Hey Marcin, recently I saw something new in trade.io exchange. It had smooth and have many tuning actions for it. It is ok. But I think our developing speed in trade.io should more rapidly. Update maybe more twice of week and finally result must be perfect. Do use end users are tester for this new main functions: FX, app.
A. I disagree, for now. With the size of our team, once-a-week releases seem to be balanced. We can focus the whole 1 week on the delivery and one day on the shipment. If we are going to ship more often we will produce less in this time. Some companies practice daily shipment -- it might be something we will consider some time in 2019, but at this moment it does not really make sense here.
Marcin: “You asked about API too, let me finish with your first question please. Some of our institutional partners and liquidity providers already use our API interface since a couple of months, but this was not yet the API we intended to open for the general consumption…”
Xalat: “Exactly. Volume is mostly driven by bots, hence APIs are important”
Marcin: “We have dedicated team who worked on the trading API and also market data feeds API that we could offer widely. The API is ready, we are now conducting functional tests, load tests and security penetration tests on it…”
Q: When can we start using the exchange from the algo-trading tools that would require robust API access?
A. The plan is to have all the test steps concluded early next week and if no serious defects found we should be able to release it in the production environment in another 1-2 weeks, i.e prior to the end of this year. We’ve take meticulous care and time to ensure we’ll be offering one of if not the best API solution available, and hope to attract quite a few institutions with its robust functionality.
Q. What kind of query/minute can we expect as limits? In market fetching and throwing orders please?
A. We are targeting to be able to sustain 100 txs/s for now with our current load tests. But some further scalability improvements are also in making (bit the delivery date early next year).
Q. Any news on the fiat trading platform?
A. We are in the technical preparation phase of this project, as the business discussions already concluded. No specific release date yet, but it should not take too long (definitely early Q1).
Q. Are you planning for bug bounty programs or acknowledgements for reporting security vulnerabilities?
A. No formalized bounty program planned so far, but fair security vulnerability disclosures of serious security issues to [security@trade.io](mailto:security@trade.io) will be definitely appreciated and rewarded.
Q. Would different platforms have different websites with various measures of KYC procedures, or will there be a uniform account system behind?
A. Can't answer to this yet, compliance related topics to Phase 2 are not 100% ironed out yet.
Q. Do you user’s end users as tester for this new main functions: FX, app.
A. We have a dedicated QA team, so this is for the manual tests. But we are also concluding work on our. A automation extensive tests suite. It should make our future deploys much smoother and of higher quality, more issues should be discovered before the actual change is deployed to the live servers.
Q. Will we start seeing more ERC20 tokens soon? They don't require as much work as the separate blockchains if I've understood correctly?
A. Correct, another 4-5 is going to be added next week.
Q. Would the market maker bot start working again after the upcoming of APIs?
A. Market maker already works, using our private api, no plans to change it in the near future. But the new api will be used by the other 3rd party partners and potentially by other market makers.
Q. Marcin what is your plan in relation to the Bitcoin Cash split?
A. Generally, exchanges took a side either on the SV or ABC fork. Our initial plan before the fork even happened was to support one or the other depending on which chain would prevail, but we never took any side... Right now it is clear both forks are here to stay, hence the decision is to support both. Before we open the deposits and withdrawal options we need to implement replay attack protection to our internal wallet addresses, as the respective forks did not implement it as part of their own code changes.
It is not really something that we wanted to do, as we preferred to focus on the new coins implementation, but as the fork happened we have no option, we took some of our engineering’s off from the other chains integration and work related to the replay attack protection is ongoing. We will most likely resume trading next week, and open deposits and withdrawals for both forked chains in the following week. Though don’t treat it yet a firm commitment.
Q. Besides the new stuff, how is the rework of the older code coming along?
A. We are not dumping anything, nothing like that. But more automated tests and more code coverage clearly shows where the defects are and where the team focus has to be put. It is an ongoing process, what will in fact never ends (refactoring of the code is part of the development process).
No comments:
Post a Comment