Binance MegaFest: It Happened Again. Show Me the Server Record.
I gave Binance the benefit of the doubt the first time.
Today, the same thing happened again, and I recorded it.
I earned my Spins through the campaign requirements. At the daily reset, the interface showed my available Spins and allowed me to press GO.
I pressed GO.
Again: Error 110006.
Binance has already explained to me that the reward pool can be exhausted while the frontend continues showing the previous state, and that actual availability is determined when the backend processes the request.
Fine. Then I have a more specific question:
If this campaign is first-come, first-served, whose request actually reached the server first?
The published Terms say rewards are distributed FCFS until the $500,000 pool is exhausted. They also say remaining Spins can still be available even after the daily pool is exhausted. �
Binance
But where does it explain:
• The server-side queue/ordering mechanism?
• The timestamp when my request was received?
• The timestamp when it was processed?
• The exact time the pool became exhausted?
• My request's position in that processing sequence?
• What exact server event triggered 110006?
If Binance says:
“Your request was processed after the pool was exhausted.”
Then I am asking for the objective record supporting that statement.
I am not asking for another user's identity or private information.I am asking Binance to provide an anonymized technical explanation of my own request.
And another question:
Where is it written that the interface can continue showing GO/available Spins after the reward pool has already been exhausted?
The campaign announcement tells users:
“Click the GO button to use your spins and reveal your reward instantly.”
Binance
Binance Support previously confirmed to me that the specific frontend behavior was not explicitly described in the published Terms.
So please don't just tell participants:
“That's how the system works.”
Tell us where that mechanism was disclosed and what server-side evidence supports the outcome.2 days
I gave Binance the benefit of the doubt the first time.
Today, the same thing happened again, and I recorded it.
I earned my Spins through the campaign requirements. At the daily reset, the interface showed my available Spins and allowed me to press GO.
I pressed GO.
Again: Error 110006.
Binance has already explained to me that the reward pool can be exhausted while the frontend continues showing the previous state, and that actual availability is determined when the backend processes the request.
Fine. Then I have a more specific question:
If this campaign is first-come, first-served, whose request actually reached the server first?
The published Terms say rewards are distributed FCFS until the $500,000 pool is exhausted. They also say remaining Spins can still be available even after the daily pool is exhausted. �
Binance
But where does it explain:
• The server-side queue/ordering mechanism?
• The timestamp when my request was received?
• The timestamp when it was processed?
• The exact time the pool became exhausted?
• My request's position in that processing sequence?
• What exact server event triggered 110006?
If Binance says:
“Your request was processed after the pool was exhausted.”
Then I am asking for the objective record supporting that statement.
I am not asking for another user's identity or private information.I am asking Binance to provide an anonymized technical explanation of my own request.
And another question:
Where is it written that the interface can continue showing GO/available Spins after the reward pool has already been exhausted?
The campaign announcement tells users:
“Click the GO button to use your spins and reveal your reward instantly.”
Binance
Binance Support previously confirmed to me that the specific frontend behavior was not explicitly described in the published Terms.
So please don't just tell participants:
“That's how the system works.”
Tell us where that mechanism was disclosed and what server-side evidence supports the outcome.2 days
