Topic: Tools for creating and verifying provably fair games (Read 1111 times)

That is a great idea, I think that besides the API references, there should be "plain English" (non-technical) introductory texts, and more details for advanced users/adopters. Thank you for the clarification of your idea in PM, I would be thankful whether you could publish the details of it by creating an issue on GitHub, so we can have an open discussion about it.


Primedice may not be the only vendor to be implemented. As RGBKey told us about existing open-source implementations, I think there are many implementation opportunities available. I chose Primedice as the first implementation because of their great attitude towards provably fair gaming projects like this.

I made this page about 2 years ago, but the code on the github page might be of some help to you.

http://rgbkey.github.io/verify/

What I see in this area, that we need very accurate, clean to understand and to implement specifications for "provably-fairness".
If you can generalize provably fairness, please try to make such specifications! It's better than code, because to make code and to make reference implementation you can ask software communities.

Specifications, describing entire aspects of communication of parties during some games or some activities, where "provably-fairness" exist.

For example, in cryptography there are well-known buddies Alice, Bob and Victor. There is a load of beardy math behind them. And they love to hang out as true crypto anarchist. They do strange things and draw for us great math problems, having practical purpose in lots of areas of human activities far beyond just numbers and integral arithmetics. Lots of cryptography protocols described and specified using the story. But try to find easy to read and to implement specs, or at least some visualizations. But nobody ever seen Alice at least... *joke*

If a provably-fairness would keep looking as strange as Alice with Bob, we won't get much.

Mentioning Primedice is not a good idea. You contribute to the brand mentioning them, but if you try some boundary cases, then you will see that they are not `so fair'. No, I believe that they aren't scammers or what.

Thank you for the honest reviews and tips!


The packages are mainly targeted for developers who are interested in provably fair technologies. End-users can use the code to verify their bets, while game owners can integrate standardized, peer-reviewable packages for their implementations.


Originally, I was planning to implement the method as described on the official PrimeDice page, but I decided to code a matching implementation with better performance. The code I used should definitely be more commented, though.


That's a great idea indeed, issues should be created for several games (e.g. blackjack and poker, but the latter seems to be hard and comes with compromises), algorithms (e.g. shuffling) and vendors.


Supporting custom random number providers would be a good idea, although implementing a generic interface for them needs further thoughts.

For provably fair, software support isn't alway enough. For example big companies for provably fair system are using Quantis which is a family of hardware random number generators (RNG) which use the fundamentally random nature of quantum optics as a source of true randomness. It's good that you are going to make open source project about provably fair system but it needs improve.

Hello, kripod and everyone here!

What is the practical purpose of such packages? Is it a thing for players or for developers? For casino of for whom?
I prefer your idea, because I'm going to create my own provably fair games. But I can't use your code as is, because it is practically useless for me as a developer.

Another problem, that I will as a developer never trust your implementation, if it would contain such strange code: https://github.com/kripod/provably-fair/blob/master/packages/primedice/src/index.js#L22

The original provably fair dice game just use few bits from hash and converts it into "the hidden" random number, which isn't known to anybody before "dice roll".

Your idea looks very optimistic, when you say that such algorithms could be generalized. The theory behind "provably fair" games takes it's roots from cryptography and math problems called "Mental Poker" and "Coin flipping by telefone". It took years to design and to find proven solution for such problems.

For OpenSource project, if you expect some contributions get done by the community, please create at least the road map of your project, or fill the issues list with features/ideas you want to be implemented, explain your idea and motivation.

Hopefully my answer is helpful ))

Recently, I came across the idea that most provably fair game algorithms could be generalized and implemented as well-tested (and peer-reviewed?) micropackages.

The project can be viewed at https://github.com/kripod/provably-fair

I would appreciate any kind of contributions, including but not limited to feature requests, documentation improvements, and reports about potential security issues.