Topic: Provably fair BTC lottery (Read 2281 times)
The application.
Are you selling the application? or the website?
We are actually planning to lauch a casino with lottery as well. Will be nice to see how this goes.
This software is for sale. It is active at http://bitthingy.net/btc_lottery/public/ There is no money in the pool, and no bonuses paid out. It is up merely to demonstrate how the software works.
Purchase includes all software, and 5 hours of support to get the site up and running. It does not include the domain. Serious offers and inquiries only.
*******************************************************************************
Description:
Bitcoin lottery with a progressive pool, bonus free rolls, and bonus payouts. Players sign up with a bitcoin address, and are provided a deposit address. A daemon sweeps the accounts periodically to check for deposits. Once the daemon detects an available balance, the player will be able to play a pick-3 lottery. The daemon also sends notification to an off-site host that sweeps the wallet.
In addition to the gaming board, there is a small API to retrieve previous draws, as well as current pool information.
For every draw there is a 1:10 chance of winning a free roll, a 1:20 chance of winning a bonus payout, and a 1/6 chance of getting a small advertisement. This provides an addition revenue vector. The bonus engine can be modified to add other kinds of bonuses, such as coupons, and also modified to change the winning percentages.
The current configuration is a 40/60 split between the house and the pool. House money is used for bonus payouts. This is also configurable.
Components:
Game app - This is built on Laravel, and holds all of the code related to the game, including the front end and the daemon. Laravel is a php-based framework, and the app is built on a MySql database. The front-end is vanilla Javascript and jQuery. Most of the graphics were nabbed of off the Internet and are in the public domain. My own minor artwork is included.
Admin app - This is also built on Laravel, and serves to handle some of the automated tasks needed to manage the accounts. This is meant to add a layer of security. In the event that the game server is compromised, there are no funds available on the game site to steal. The app also includes a MySql database for the eventuality that the admin server is compromised. The admin app uses the Blockchain API for wallet transfers. No need to run a local wallet.
Scripts - various scripts for building the database, and testing payout and bonus algorithm.
Security:
No personally identifiable information is stored on the game host. Only public addresses are stored in the database, so there are no private keys that can be stolen. Transactions take place in the database only; there are no actual funds being transferred. There is currently no way to refund player accounts, and that was intentional design choice. The game is set up so that the players get a precise number of plays, with no funds left over, and thus no reason to request a refund.
Purchase includes all software, and 5 hours of support to get the site up and running. It does not include the domain. Serious offers and inquiries only.
*******************************************************************************
Description:
Bitcoin lottery with a progressive pool, bonus free rolls, and bonus payouts. Players sign up with a bitcoin address, and are provided a deposit address. A daemon sweeps the accounts periodically to check for deposits. Once the daemon detects an available balance, the player will be able to play a pick-3 lottery. The daemon also sends notification to an off-site host that sweeps the wallet.
In addition to the gaming board, there is a small API to retrieve previous draws, as well as current pool information.
For every draw there is a 1:10 chance of winning a free roll, a 1:20 chance of winning a bonus payout, and a 1/6 chance of getting a small advertisement. This provides an addition revenue vector. The bonus engine can be modified to add other kinds of bonuses, such as coupons, and also modified to change the winning percentages.
The current configuration is a 40/60 split between the house and the pool. House money is used for bonus payouts. This is also configurable.
Components:
Game app - This is built on Laravel, and holds all of the code related to the game, including the front end and the daemon. Laravel is a php-based framework, and the app is built on a MySql database. The front-end is vanilla Javascript and jQuery. Most of the graphics were nabbed of off the Internet and are in the public domain. My own minor artwork is included.
Admin app - This is also built on Laravel, and serves to handle some of the automated tasks needed to manage the accounts. This is meant to add a layer of security. In the event that the game server is compromised, there are no funds available on the game site to steal. The app also includes a MySql database for the eventuality that the admin server is compromised. The admin app uses the Blockchain API for wallet transfers. No need to run a local wallet.
Scripts - various scripts for building the database, and testing payout and bonus algorithm.
Security:
No personally identifiable information is stored on the game host. Only public addresses are stored in the database, so there are no private keys that can be stolen. Transactions take place in the database only; there are no actual funds being transferred. There is currently no way to refund player accounts, and that was intentional design choice. The game is set up so that the players get a precise number of plays, with no funds left over, and thus no reason to request a refund.
give to know when fully finished
Yes. I can't run it.
Looks great! Are you for sure selling?
As is, 4BTC. The game logic is solid, the back-end is solid, and the daemon required to synchronize the blockchain with accounts is complete. There is no admin panel to handle site configurations yet, and the bonus engine is not yet implemented. The bonus engine is going to generate things like free rolls, small btc payouts, or occasional ads. If I get those both completed, then I would probably ask 6btc. I have 100+ hours of development, and it is up and running, so obviously not vaporware. I would keep the domain name.
well I think and let you know.
As is, 4BTC. The game logic is solid, the back-end is solid, and the daemon required to synchronize the blockchain with accounts is complete. There is no admin panel to handle site configurations yet, and the bonus engine is not yet implemented. The bonus engine is going to generate things like free rolls, small btc payouts, or occasional ads. If I get those both completed, then I would probably ask 6btc. I have 100+ hours of development, and it is up and running, so obviously not vaporware. I would keep the domain name.
Actually, I would very much like to sell it. I can't legally run a game from where I live, so it isn't going to help me at all.
what price?
Actually, I would very much like to sell it. I can't legally run a game from where I live, so it isn't going to help me at all.
do not want to sell your lottery?
Cool. Thanks for the bug report.
I also forgot to mention that there is an api of sorts to return all plays to date in JSON format:
http://bitthingy.net/btc_lottery/public/draws
I also forgot to mention that there is an api of sorts to return all plays to date in JSON format:
http://bitthingy.net/btc_lottery/public/draws
When balance is finish and you play again, with zero balance, it goes into a continuous loop, searching for a solution and you cannot exit.
Hope this helped. Tips appreciated.
Hope this helped. Tips appreciated.
Play is a bit sluggish and the How to play option is not working.
The P of Pool are to small .... If you look quickly, it looks like Fool.
The P of Pool are to small .... If you look quickly, it looks like Fool.
Hi! Thanks for the feedback. I think you are right. I need to adjust the font in the graphic.
Play may seem sluggish due to the hashing function that must take place on the back end. The winning numbers are not stored on site, so the submissions have to be hashed each time. In order to prevent brute force attacks on the server, the algorithm is designed to take a few seconds before returning the result.
Play is a bit sluggish and the How to play option is not working.
The P of Pool are to small .... If you look quickly, it looks like Fool.
The P of Pool are to small .... If you look quickly, it looks like Fool.
Thank you to those who volunteered for testing. I decided to go ahead and open the site to anyone that wants to participate in testing. The winner of this testing round will win .1BTC.
https://blockchain.info/address/1BWs8Uso1BLcTNiofsacFgo6QByEBVNZWe
No email address, or any other information is required, or saved, by the application.
bitthingy.net/btc_lottery/public
There are roughly 40 slots available, and I will add more as needed. To register, simply provide a BTC wallet address, and select enter. I would recommend generating a new single use address. If there are slots available, you will have .1BTC of game credit to use, at .001BTC per play.
Please let me know if something breaks, or if you have questions.
[email protected]
https://blockchain.info/address/1BWs8Uso1BLcTNiofsacFgo6QByEBVNZWe
No email address, or any other information is required, or saved, by the application.
bitthingy.net/btc_lottery/public
There are roughly 40 slots available, and I will add more as needed. To register, simply provide a BTC wallet address, and select enter. I would recommend generating a new single use address. If there are slots available, you will have .1BTC of game credit to use, at .001BTC per play.
Please let me know if something breaks, or if you have questions.
[email protected]
Do you mean like issue tickets, and then hold a drawing, like a paper lottery?
Yeah, like power ball style, or a pick 3/pick 4. Or actual scratch tickets loaded with BTC if you win. Would be a cool gift and way to get people to use BTc if they win!
Do you mean like issue tickets, and then hold a drawing, like a paper lottery?
What about actual bitcoin lottery tickets? Can this be done?
Jump to: