My open-source verifier now supports Diamond Poker. Check out my post on the Stake forum

It looks like password recovery is borked as well as the seed issue above, which I think is a pretty glaring problem

I'm not worried about the privacy aspect because I believe that will be a short-term thing once more people start using segwit. Maybe you could give users a toggle between deposit addresses being P2WPKH or P2PKH. (I know that would be more work but if people are worried about privacy it might be nice). Plus, segwit addresses should save the site money on fees.

As for the investments, maybe just add it to the trello board as a to-do sometime in the future when there's time to work on it. It's not that serious of an issue I suppose but being charged 35% on the same profits twice or more if you close the investment in the red is pretty rough.

Username: Drain

Joined date: 10.08.2014

When will Stake support SegWit deposit addresses?

Ethan, do you think that you could start tracking investment profit independent of each individual investment? I ask this because right now if it's say the day after commission was taken and my investment is down 3% since commission was taken, I can't close the investment before I get that 3% back otherwise I'll get commissioned on the same profits twice. When the commission is already a pretty large 35% this can really hurt so it essentially traps your money in the site. Will you consider changing this?

EDIT: Also, when will the site support SegWit addresses?

Both jackpots getting near 2 BTC!

Do you have any proof?

I've been thinking, one of the biggest problems with provable fairness is how often people simply don't use it. This is often because of the extra steps required to make sure everything is fair. As I'm sure a lot of you know by now, I like to make sure that everybody has the best experience possible. What if we had a userscript, or chrome extension that automatically did this for us?

One of the biggest holes in nearly every provably fair scheme is the hash of the server seed. Extremely often, it's just not written down/copied anywhere. Most sites don't show you the hash until you open a window or go to a page that displays it. What then? If the site knows that you haven't looked at the hash, then you wouldn't be able to tell whether or not the server seed they revealed to you was the one they were using. Now of course, this isn't perfect, as the site would have no way to guarantee that you won't look at the server seed hash halfway through playing, but it's still possible. The point of provable fairness is to remove all doubt that the site could be altering results.

I propose a chrome extension to do this, as I believe it has the lowest "cost of entry". All a user has to do is simply click the install button and they're protected. A userscript requires too much technical knowledge for most people to set up, although it could work cross-browser. I believe that anybody privacy-conscious enough to use other browsers is also smart enough to copy down their server seed hash.

The extension could be able to do the following, all behind-the-scenes:

• Record new server seed hashes as they are generated, to prevent sites from changing them later and storing them securely in chrome.storage where the website and other extensions can't touch them. (This has the added benefit of being able to sync between different chrome browsers).
• Instantaneously verify all bets made in the past as soon as a new seed is in use and the previous one revealed.
• (Fluff) Have a counter of all bets made by the user that have been verified when you click on the extension icon

Of course, the potential for a malignant extension here is huge. A bad extension that has access to the page would be able to withdraw a user's entire balance to an attacker's address. Such an extension would have to be open-source so that anybody could examine it and make sure nothing bad is going on behind-the-scenes.

I'd love to hear people's thoughts about this, as well as hearing from anybody that doesn't use chrome as their browser so I can get a handle on how many people would be affected before I think about working on this. The great thing about a chrome extension is that it could support any number of websites, without the user needing to add additional extensions or such.

Thanks!

I've added Mines to the verifier now! 5 games are now available. Check the thread on the Stake forum for more info.

I've used the API to create a script that can notify people using the Join app for Android when a bet that wins or loses over a certain amount is made. If anybody else uses this app and is interested, I could consider opening this up to anybody that wanted to receive notifications.

My open-source bet verifier (Stake forum thread) now supports Plinko, in addition to Dice and Roulette. Other game support will come as I have time to work on this. So you can get the idea of the calculation that this tool will save you when verifying your bets, here is the output from a plinko game:



Enjoy!

Competition is over, here are the results:

I forget the URL but that's already high up on the suggestion board under "in progress", I think they're already working on it

I agree, I hope that you're able to combat botters.

Username is RGBKey

Not that many people playing, should be easy to take one of the lower spots for anybody

The verifier now also supports URL parameters and could be linked to directly from YOLOdice if desired, click here for an example

Edit: Here is what it could look like if integrated on the site:

Done!

I could definitely show the intermediate steps on the page