1. Forums
2. FAQ
3. A request for help: Link Fcoin reported an error, saying that it does not support ETH_USDT transactions, right?

A request for help: Link Fcoin reported an error, saying that it does not support ETH_USDT transactions, right?

Author: Old cat likes fish, Created: 2018-06-14 20:42:21, Updated: 2018-06-14 20:53:55

---

---

• Is it a problem with the FCOIN interface?
• Does it support ES6 syntax? It seems to retest yes, but the actual bot running the report syntax parse error
• WeChat service numbers quantified by the inventor can query policy status, and is there an API or method to report some custom status?
• The newcomer asks, can you build a stock exchange on your own?
• Can the matplotlib graph in the status bar reference other web pages in real time?
• Binance retest and real-time buy functions are incompatible
• Is it possible to convert the bit event mode for interfaces that support websockets?
• Please instruct me, the following error occurs when the code is running in main AttributeError: ooOooo000oOO instance has no attribute '__getitem__'
• Feedback from: FCoin market interface bug
• Report: FCoin's api seems to be a bit unstable, see log
• Can I add a currency that is not on the list to the review?
• Suggested LogReset to delete only erroneous logs
• How do you solve the issue of IP binding when you create a private key?
• The robot's hard drive has been running for a long time, but it has failed to connect.
• Is it possible to adjust the parameters while the robot is running?
• A large number of order not found errors occurred using the okx futures interface
• JS error on the bot page
• okex called the exchang.IO function returns 10000 error, how to fix it, thank you
• Historical data
• How can I get the OKEX futures price index?

---

rj03houWhy can't I find fcoin on the backtesting platform?

Old cat likes fishOkay, I'll give it a try, thank you.

ZeroUpdating the host

Old cat likes fishOdin, feedback on a small bug, FCoin, call IO (("mode", 2) will be reported when wrong, Futures_OP 4: argument error @Zero