Yes, in settings - Security tab - you have withdrawal destination whitelisting
It seems unconvenient. What's the meaning of "whitelisting delay"? delay of withdrawal or delay of adding address to white list? I have a security concern if not using whitelist. I withdraw using API, but ftx api needs 2FA/password to do that, it means that I have to put all these info on my server. Once my server get hacked in, they get everything.
Whitelist delay means that address that is requested to whitelist will take X amount of days to be whitelisted; after its whitelisted then you can withdraw to that address
Hello, we want to do a telegram in Arabic for the project
Then that's unusable. Do you have solutions for my concern above if not using whitelist?
Unfortunately i do not have a solution for that particular problem, try asking on python3 forums
Not a programming problem
It is, you can join @ftx_api_support Unfortunately you need to use withdrawal password and 2fa over api or disable 2fa over api and only use password or use whitelist as well What you seem to want is a way to use 2fa without storing secret over your server, that's s programming problem
I would like to disable 2fa over api, can I? ftx is the only exchange I've ever used, which needs 2fa when withdraw with api.
You can do that on ftx.com/profile -> security You would need to disable ALL withdrawals with 2FA and then you’ll be able to withdraw only using withdrawal password over API or UI
that's not "disable 2fa over api", that's "disable 2fa over withdrawals", still not solve my problem. Most of the other main exchanges use this design(or similar): withdraw whitelist is recommended, when adding to whitelist, mail/sms confirms are requireded, 2fa is required when manually withdraw, not required when withdraw with api. This works without any problem, why does ftx has a design which is so weird, and I don't think it's safer.
For now that’s your only solution or generate the secret and use it over api every time.
Обсуждают сегодня