Bot not activated

[orsson9]

I have paid the full price (15.5 FTM about 1.07 $ per 1 FTM) however the bot didnt activate for 4 hours. Please contact me.

[mole3421278]

Hello, just to be sure, are you in a state where the trading of futures has been banned? If you don't know, try to open manually a futures position on Binance and check if you are allowed to open it or not. Meanwhile we'll check if there is some other problems.

[mole3421278]

Right now the bot doesn't have problems, so the suggestions are to:

• check if in your state the trading of futures has been banned;
• check if you linked the bot to a valid API key (check in the section "API management" of binance if you gave to the API the permissions it needs).

If the problem sussists try to download and start the twin bot Benzaiboten (if you paid for Daibotuten you have granted the usage also of Benzaiboten, but it is for the spot trading, so if the problem is that your state has the ban on the futures you should be fine with it, but remember to give to Benzaiboten an API key with permissions to operate in the spot zone).

Also, you can share here the transaction of the payment to check if there are problems there.

[orsson9]

Kindly reminder.

czw., 17 mar 2022 o 09:30 Adam Lazar @.***> napisał(a):

Hello

Thank you for contacting me. I double check the following:

• Futures account is working fine, I have currently open positions.
• Permissions for API - Futures and read,

I spotted problems with bot on command line. Got issues with time dispreperency. Synced with ntp and rebooted server, but didn't solve the problem. Don't know if it has any value but bot is printing always the same timestamp on console -> 2022.03.15 15:23:26

Transaction:

https://ftmscan.com/tx/0xcfc900dd71ac6eae3e8e0f34cf763657354ccc77855092ea22c7af104c2539a5

Best Regards

wt., 15 mar 2022 o 19:39 mole @.***> napisał(a):

Right now the bot doesn't have problems, so the suggestions are to:

• check if in your state the trading of futures has been banned;
• check if you linked the bot to a valid API key (check in the section "API management" of binance if you gave to the API the permissions it needs).

If the problem sussists try to download and start the twin bot Benzaiboten (if you paid for Daibotuten you have granted the usage also of Benzaiboten, but it is for the spot trading, so if the problem is that your state has the ban on the futures you should be fine with it, but remember to give to Benzaiboten an API key with permissions to operate in the spot zone).

Also, you can share here the transaction of the payment to check if there are problems there.

— Reply to this email directly, view it on GitHub https://github.com/mole3421278/Daibotuten-futures-trading-optimizer-bot/issues/5#issuecomment-1068333086, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALKJBBYTP36SXSLTDZFSKT3VADKPBANCNFSM5QZOQDBA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: <mole3421278/Daibotuten-futures-trading-optimizer-bot/issues/5/1068333086 @github.com>

[mole3421278]

Hi, thank you for your efforts to find the problem. I'd say the problem is here: "Don't know if it has any value but bot is printing always the same timestamp on console -> 2022.03.15 15:23:26"

The correct behaviour is the following one:

You should see the timestamp changing with the time, so the problem should be in the clock or something related to that.

Try writing this API of binance in the browser multiple times: https://api.binance.com/api/v3/time The correct behaviour that you should see everytime you execute it is a different number, like: {"serverTime":1647684112817} {"serverTime":1647684286951} {"serverTime":1647684301099} and so on. Tell me if you see always the same result.

[mole3421278]

Also, try the following (taken from Stackoverflow): If you are running Windows 10, or Windows 11, do the following:

• Start -> search date and time
• Make sure you have set Set time automatically to On
• In the opened window you have an option Synchronize your clock, and press Sync now.

[mole3421278]

Another thing to check: you paid the fees using FTM from binance or from another exchange or external wallet?

[orsson9]

Hello

For some reason the bot is always printing the same time and date, even after clock sync and system reboot. But when I enter https://api.binance.com/api/v3/time I get a different result every time.

FTM was sent from Binance spot wallet.

Best Regards

[image: timeandDate.png]

sob., 19 mar 2022 o 12:52 mole @.***> napisał(a):

Another thing to check: you paid the fees using FTM from binance or from another exchange or external wallet?

— Reply to this email directly, view it on GitHub https://github.com/mole3421278/Daibotuten-futures-trading-optimizer-bot/issues/5#issuecomment-1072995788, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALKJBB4YX5O3KBPVV3HXBDLVAW5WPANCNFSM5QZOQDBA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: <mole3421278/Daibotuten-futures-trading-optimizer-bot/issues/5/1072995788@ github.com>

[mole3421278]

Can you share a screenshot of the log of the bot?

[mole3421278]

Show also a screenshot of the window of the bot, thank you

[orsson9]

Attaching requested screen. Twitter errors are sometimes visible.

[image: screen.jpg]

sob., 19 mar 2022 o 19:56 mole @.***> napisał(a):

Show also a screenshot of the window of the bot, thank you

— Reply to this email directly, view it on GitHub https://github.com/mole3421278/Daibotuten-futures-trading-optimizer-bot/issues/5#issuecomment-1073063264, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALKJBB2ESBQXUJRTHD6ST3TVAYPNJANCNFSM5QZOQDBA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: <mole3421278/Daibotuten-futures-trading-optimizer-bot/issues/5/1073063264@ github.com>

[mole3421278]

I'm sorry, can't see the image, but only this: "[image: screen.jpg]" Please, load the image on the discussion of GitHub

[orsson9]

[mole3421278]

Thank you. The error regarding twitter is known and due to the connectivity with twitter, that sometimes goes down, nothing scary, it returns to work automatically after a while. Regarding the fees, the suspect is that the transaction has registered a lower value in USDT, so it doesn't count to activate the bot. Write down an address (on the Fantom Network, it's okay the same from which you tried to send the fee) to give you back your FTM and try again with another transaction (you can also change the crypto to use if you want). Thank you

[orsson9]

Thank you.

Coin and network FTM:

0xeb9d2bfa8c26dd0ab5edb86de6073f7099a83087

[mole3421278]

Done https://ftmscan.com/tx/0xa895f9ad2e12380a1b8e74e9ded7d518da19e4374e71ee99b03e7afada49d82a

[mole3421278]

Is the bot active now?

[orsson9]

Unfortunately didn't worked. Now bot is printing 2 dates. ( Both of them are similar to time when I paid transaction)

[mole3421278]

To investigate the problem I'm going to release a new version with more information on the log.

[mole3421278]

Try this new version: https://github.com/mole3421278/Daibotuten-futures-trading-optimizer-bot/releases/tag/v1.5.1 It won't solve the problem, but it can give me useful information to solve the problem. Post here the screenshot of the log generated with this new version. Thank you

[orsson9]

[orsson9]

Didn't spot the new log messages.

[mole3421278]

Okay, so the problem must be in the clock. Go to Binance and tell me the time at which the last transaction happened according to Binance. Thank you.

[orsson9]

Withdrawal Completed 2022-03-20 12:08 (GMT+1)

pon., 21 mar 2022 o 17:56 mole @.***> napisał(a):

Okay, so the problem must be in the clock. Go to Binance and tell me the time at which the last transaction happened according to Binance. Thank you.

— Reply to this email directly, view it on GitHub https://github.com/mole3421278/Daibotuten-futures-trading-optimizer-bot/issues/5#issuecomment-1074157810, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALKJBB6NIWAEOFZAPUISIVTVBCS3JANCNFSM5QZOQDBA . You are receiving this because you authored the thread.Message ID: <mole3421278/Daibotuten-futures-trading-optimizer-bot/issues/5/1074157810@ github.com>

[mole3421278]

Try this new version: https://github.com/mole3421278/Daibotuten-futures-trading-optimizer-bot/releases/tag/v1.5.2 Now the problem should be solved. Let me know, thank you.

[orsson9]

This version is up to date PAID: 18.136647999999997 usdt on 2022-03-20 11:07:04 CHECK: FEE PAID CORRECTLY 2022-03-20 11:27:04 PAID: 18.136647999999997 usdt on 2022-03-20 11:07:04 CHECK: FEE PAID CORRECTLY CHECK: FEES PAID Started to work to trade!

Thank you for all your support.

[mole3421278]

Nice! Closing this issue. if you have any other problem or suggestion do not hesitate to propose it. Good trading.