From: Ammar Faizi <[email protected]>
To: OKX <[email protected]>
Cc: Alviro Iskandar Setiawan <[email protected]>,
Michael William Jonathan <[email protected]>,
"GNU/Weeb Mailing List" <[email protected]>
Subject: Trailing Stop Bug in OKX: Illogical Variance Ranges
Date: Sun, 24 Nov 2024 01:59:40 +0700 [thread overview]
Message-ID: <CAFBCWQKoaAJ6GFsx59EPW_a6iV25dU_TzF=0YsfJ9pjPCzLq6A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]
Hello,
Could you escalate this ticket to the OKX development team?
This is a technical issue that deserves their immediate attention.
I've stumbled upon a peculiar bug in the trailing stop feature in OKX,
and let's just say it has a flair for drama. Recently, the constant
variance setting started showing an "available range variance" that
defies logic:
0.01 - $current_price
Now, for the NOT/USDT pair, when the price is 0.008061, the range becomes:
0.01 - 0.008061
Yes, you read that correctly; the trailing stop starts at a negative
price. Clearly, NOT/USDT has ambitions of entering the quantum trading
dimension. This results in the starting point of the trailing stop
being at a negative price, which is clearly invalid.
Meanwhile, over in the BNB/USDT pair, we have a more reasonable but
still eyebrow-raising range:
0.01 - 657.3
Although this range is technically usable, it still seems inconsistent
and not entirely logical.
The trailing stop feature is vital for OKX traders, and the current
behavior undermines its utility. Please address this bug promptly, as
traders deserve better than playing "guess the variance range" with
their funds.
I've attached screenshots for you to look over. Feel free to bask in
the glory of this head-scratching math.
[ The bug appeared recently; it seems it started after the recent OKX
maintenance. ]
--
Ammar Faizi
[-- Attachment #2: okx001.png --]
[-- Type: image/png, Size: 17799 bytes --]
[-- Attachment #3: okx002.png --]
[-- Type: image/png, Size: 18201 bytes --]
next reply other threads:[~2024-11-23 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[email protected]>
2024-11-23 18:59 ` Ammar Faizi [this message]
2024-11-23 19:00 ` OKX Team Request Received #6448571 OKX
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFBCWQKoaAJ6GFsx59EPW_a6iV25dU_TzF=0YsfJ9pjPCzLq6A@mail.gmail.com' \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox