The API seems to show that your actual target multiplier was 1.14:
~snip~
It's really weird that the frontend displays 1.13, but it's likely just a rendering bug. It doesn't make a whole lot of sense for Stake to try to cheat over $2 bets. Do you happen to remember what multiplier you were going for at the time?
I am guessing there could be some rounding out error? ~
~ I checked mine all and they seem fine, but here we are with a proof of one guy not getting fair results, so they should make the announcement and defense against this.
How the games actually works there! I have also observed some unusual result while I'm setting the target multiplier from 1.13× to 1.16×. To make it clear, when I'm setting the target multiplier at 1.13
The bet details shows
- Multiplier: 1.13×
- Target :1.12×
The multiplier and target shows correctly in their bet view model if my target multiplier is out of 1.13× to 1.16× range. But their system shows 0.01× less target when I'm inputting the ‘target multiplier’ in that range.
I have also made a video while I was checking this out. If you haven't understood my above statement then see this video to realize it properly:
https://youtu.be/59p-0yjQ88MEdit: I just asked their support and they said, it is a visual glitch and it will be fixed soon
This is a fun one! This problem is actually based on how your browser does its maths, coupled with how we round numbers on the frontend.
We use the following equation to visually ensure all our numbers on limbo are rounded in a visually pleasing manner (to two decimal places.)
const getFloorMultiplier = (num) => (Math.floor(num * 100) / 100).toFixed(2);
With regards to why this showing different to what is expected for the instances expressed:
This fails because the internal floating point representation of 1.13 is very slightly less than 1.13 - multiplying that by 100 doesn't produce 113 but 112.99999999999998578915 and then rounding that down takes it to 1.12.
You can test this by opening your console in the browser (right click anywhere screen > select 'inspect' > choose 'console')
From there you can type in the following:
As you can see we get the following results.
When put all together, this is the result:
If you try with the numbers expressed above, you will find that it also spits out an absurd result for the instance of 1.16 too. Rest assure that this is just visually rendered incorrectly based on your browser and has no actual influence or affect on the result of your bet. I have whipped together a slight edit in the codebase that will consider target multipliers already rounded, which should technically solve the visual discrepancy experienced.
during the race event there was a lot of high rollers and made rains this is a christmas blessing apart from the promotion of stake.
