|
The first round is about to end in a few hours (in 7 hours and 15 minutes when this is being posted). DOGE and ETH coins got some bonus from site profit, the current pools are:
BTC: 0.1 BTC (it's the minimum guaranteed)
LTC: 15 LTC (it's the minimum guaranteed)
ETH: 7.75 ETH (2.75 ETH above guaranteed)
DOGE: 477,700 DOGE (127,000 above guaranteed)
So, with only a few hours left, I can only wish you good luck!
After this round finishes, a new round will start automatically. so even if you don't win this time, there will be a new round every single week.
Cheers and good luck,
Ethan
|
|
|
|
where i can see the current minimum deposits ? ty in advance  Elias Ch. Update few secs later : 2 posts in a row , excuse me it was not intentional . We accept every deposit transaction, there is minimum. Cheers, Ethan |
|
|
|
|
All right, I've been looking into technical possibilities and I think I know how to split the bet dataset into "current and quickly accessible" and "older, but still accessible". I believe there IS a good solution :-)
Anyway, I'll keep you updated! Cheers,
Ethan
|
|
|
|
|
I've just deployed this code to make browser <-> server communication more lightweight, and I've removed some of bet delays.
Anyway, you should see some bet speed improvement anyway, but the main limitation is still the speed of light, or rather speed the information travels through the universe. Before the browser can place a bet, a confirmation of the previous bet must be received, and if you live in another part of the world this itself could limit you to 2-4 bets per second. Our servers are in Ireland, so the closer you are, the faster your bets should be.
Tell me if you find anything not working as expected, it's been quite a large re-coding.
Cheers :-)
Ethan
|
|
|
|
|
We were never streaming ALL the bets, so this should not be a huge problem...
I'll be deploying new code later today so we'll hopefully see a difference. I couldn't do it yesterday because I've discovered a few bugs and wanted to revise the code again.
Cheers,
Ethan
|
|
|
|
That sounds nice. do i have to change anything on my chat bot to keep working after update?
I don't think so. TCP API is unchanged. Older clients can still connect using JSON encoding, so you should be fine. The client needs to explicitely "ask" for msgpack encoding and the web app will do it. I've tried to test everything as much as I could and I think it will work just GREAT :-) Now, regarding the bet pruning - I got a lot of feedback and most people told us that keeping historical bets is NOT that important. Besides, most sites keep deleting old data anyway. I'll give the idea a few days, maybe I'll find a nice (technical) solution to keep old bets somewhere and keep them accessible, while having the recent data ultra-fast. Thanks and cheers! Ethan |
|
|
|
|
So it seems bet speed is critical... OK, I started to work on optimizing browser <-> server communication and so far I was able to remove 75% of the overhead by switching to more efficient coding (msgpack), compressing keys and removing unnecessary messaging.
Right now everything seems to work. After I do the final code review I'll deploy the changes and remove some of the bet delays.
|
|
|
|
So far it seems that speed is most important... And it's hard to disagree. On the other hand I'd like to keep the older bets accessible somehow, maybe there is a hybrid solution somewhere in the middle. I am thinking about storing historical data on separate drive or even a separate server...
But if it happens to be too complex, then you think we should aim for speed rather than keeping complete bet history?
Personally I dont care much about the bet speed nor bet history. I record my bets locally. It would be great if bet results are broadcasted to all existing sessions for an account so i can record bets placed on mobile on my pc the easy way  Whatever, here a few things I noticed which maybe help to increase the speed for general users: The All bets stream ('Watch Bets') sucks a lot performance out of yolo and is enabled by default. Same with the live updates for competitions. Especially on slow and mobile devices it slows down bets. Thats a client side thing. Even with Watch Bets disabled and non competition running I get like ~450 bets per minute (non delayed) using on-site Autoplayer. Using my self made bot I get like 1k bets per minute. Thats 2 times faster! (* records from times before weekly competitions) jfyi I use a slightly modified version of RGBkey´s API wrapper for NodeJs. Its modified the way I can auth by login instead of api key. I think you can get much more out of yolo just by optimizing the web client! Cheers notYou Good points. This could help for sure! Edit: I have to admit, during the 3 years of adding new features the client <-> server communication got a bit bulky and it might be good to revise and optimize it. Making the messages less bulky would definitely speed things up! |
|
|
|
|
So far it seems that speed is most important... And it's hard to disagree. On the other hand I'd like to keep the older bets accessible somehow, maybe there is a hybrid solution somewhere in the middle. I am thinking about storing historical data on separate drive or even a separate server...
But if it happens to be too complex, then you think we should aim for speed rather than keeping complete bet history?
|
|
|
|
|
Good luck everyone! I hope it will be fun!
Cheers,
Ethan
|
|
|
|
I've just sent the prizes for the first weekly round. The next round has ~0.4 BTC in prize pools (in BTC+LTC+ETH+DOGE) and 10 prizes for each coin (=40 together). Don't miss it! https://yolodice.com/#weeklyCheers, Ethan |
|
|
|
Weekly contests are nice! Maybe it would be better one contest for all coins can't see reason behind separation and four different prize pools One reason is that there might be more opportunities, and more chances for spotting these EV+ spots. The other is that I don't want to compare wagered amounts using exchange ratios, e.g. from LTC to BTC. It's just asking for trouble. The first round of weekly competitions is almost over, last chance people! Cheers, Ethan |
|
|
|
WEEKLY COMPETITIONS Aka "finally something new" :-) We are launching Weekly Competitions - these are just like regular wagering competitions, but running each week, for each coin independently. Here's what they really are: - The competitions start and end at 12 AM (0:00 UTC) every Monday (midnight Sun/Mon) and last exactly 7 days. - Competitions for each coin are separate. - There are only three prizes for the first 3 places for each coin. - The more you wager the higher you are on the leaderboard. To beat another player you have to wager more than them. - The prize pool is dynamic, based on weekly site profit. - Everyone can join, just start placing bets in any coin. - Prizes are sent within 1h after the competitions end. We've launched weekly competitions today, in the middle of the week, so the first round is only 3 days. The next full cycle starts on Monday and.. stay tuned! We'll boost the prize pools to make it fun!Cheers, Ethan |
|
|
|
Is the site down? I'm only getting a spinning wheel when I try to load the site.
Our Let's Encrypt certificate expired and did not renew automatically - I've fixed it as soon as I woke up. Sorry about that, I'll need to manually supervise the renewal next time. Cheers, Ethan |
|
|
|
|
The competition ended with the prize pool over 418 LTC, and the 1. prize was 209 LTC. Quite nice! Congratulations!
|
|
|
|
|
Wow, just logged in and the prize pool in the competition is now over 300 LTC (and the main prize over 150 LTC). Hopefully it will stay this way, making it one of the highest among our competitions so far.
Cheers and good luck!
Ethan
|
|
|
|
|
Good luck everyone!
Cheers,
Ethan
|
|
|
|
why support is not responding ? I was stolen the account where my balance beat , and your moderators cannot help me , do you help your player who trust you? all moderators knew my account that stole me , and yesterday was online, I told you and your moderators but didn’t do , I sent a screen in support and moderator , where I showed you how I sent the money , but chiefly your moderators themselves knew that my account was beating and stole me and the moderators did not help me . I know you are here now and do not answer me I’m getting sick for 2 days and someone doesn’t help me. My account was stolen from me where the balance struck and now they don’t even answer me. No admin. I saved in support but there is no answer. and when my account was stolen, they beat online and I told all the admin and moderators but didn't
Firstly, please do not spam posts in this forum, or your messages will probably be reported. Secondly, your support ticket is only 18 hours old, so it's not fair to say you've been waiting for 2+ days. As far as I know, Ethan told me just now (in the last hour) that he already reached out to you. Sending messages to Moderators about this kind of stuff does not help, because they cannot do anything about it. All account access/recovery stuff is done by Ethan when he is online. Indeed we cleared everything in a Chat discussion. Cheers, Ethan |
|
|
|
|
It happened. Someone had a lucky strike and nullified most of our LTC bankroll. Yep, this can happen.
Until we refill LTC bankroll, the max bet profit will probably ridiculously low.
To have a piece of mind after this loss we lowered max bet profit for other coins a bit, and these are rounded now so that the amounts don't change with every bet.
Congratulations to the winner(s), it was a fair game.
Cheers,
Ethan
|
|
|
|
|
The competition just ended, I think it was the most wagered Dogecoin competition we had, with the highest prize pool. We ended up with the prize pool of over 4,400,000 DOGE, and the main prize was ~ 1,320,000 DOGE.
Congratulations everyone and thanks for the fun!
Cheers,
Ethan
|
|
|
|
|
Show Posts
