@jostorres We are about to modify our Wolf Race pretty soon, offer bigger rewards in a longer time perspective or lower rewards in like 2 hours period. We should have it ready to release in a few days.

@arisatox Dicebot is a bit hard to manage for us because every update we make to our needs updating dicebot. Once we release our API to the public we will start versioning every update we make so it should fix all the issues with the dicebot.

@Darker45 Thank you for appreciating our hard work! It's been around 8 months of being live! In terms of auto bet settings, we are already working on adding some new small details that enable more possibilities to program it

@bakasabo Please reach out to us on the live chat support or via support@wolf.bet, we will be happy to help you. Happy New Year to you too!

Results published Prizes sent!


A huge thanks to everyone who joined another Lucky Number contest edition! We promise to get back with another contest as soon as possible. Happy 2020

The endpoint you have found is public just to be able to log in and receive a token for private endpoints. Anyway, this endpoint, as well as the others, will be published in the API documentation for our platform soon.

Transmission via the HTTPS protocol is encrypted with an SSL certificate, so nobody overhears the data being sent.
The CSRF token is used for forms embedded in web pages, not API requests.

We are glad that you also managed to handle the withdrawal endpoint (without published documentation yet) because it means that our platform will be very friendly for all players who want to create their own scripts and strategies.

@victorsspy In the end, a small request from us, it's very easy to create a catchy title that will make people click it. Much harder to build and improve a website every day. We are eager to increase the security of our platform and we already proved it, we also encourage users to activate the 2-factor authentication to make the access almost bulletproof. You can always reach out to us using the official thread on bitcointalk or via our live chat support/ticket system.

Sorry, already picked by ashmodeus

@RHavar to avoid any concerns and misunderstanding we will implement the manual input of the client seed ASAP. Once we do this I will let you know so please test it out again and point any imperfections you find. We don't want any understatement in this matter

@joksim299 We totally understand your concerns, to make it fully transparent we will introduce the manual input of a client seed in a few days!

@RHAvar The client seed in compare to the server seed only looks like hashed, in fact, it is definitely not. As you can notice in a provably fair checker, the client seed is public as well as a nonce. Simple saying the client seed is just a random generated string that works equally to the manually provided string by a user. At the moment we don't allow for user input, but it will be released soon.

@SirLancelot Exactly what you are saying will be introduced next week! Races with bigger prizes but held for a shorter time or a prize pool divided among the larger number of players. We certainly try to A / B test a lot of things we promote but we face limitations also from the development side.

Sorry, 89 was already picked by Souri