Sorry for the delay. I'm done with the script. You can redeem a ticket every 24 hours. The winning ticket will be determined by the TX Hash sent from Ad Network. I'm now researching on which Bitcoin Ad Network to use.
To make it transparency, I would like to ask if any of you would like an escrow? The escrow will have the login detail to the Ad Network. So as to check the TX Hash.
Topic: A Bitcoin Site which share it revenue? (Read 1158 times)
Sorry mate, I totally lost track of this. So much going on right now, but it seems that you found a great solution to the problem. I would, personally, go with B, because, well, that seems like the better option IMO.
It is alright. Noted your answer. I will be doing B since it since better.
I'm done with home page (with some FAQs) and a register page (very secure hashing algorithm). Gonna do a login script tomorrow and finally a simple script to redeem tickets. I have around 10 USD worth of Bitcoin to buy a domain and hosting. Any donation would be appreciate, although it is not needed.
Sorry mate, I totally lost track of this. So much going on right now, but it seems that you found a great solution to the problem. I would, personally, go with B, because, well, that seems like the better option IMO.
Hmm.. @bitcoininformation is there any update? Anyway, I came up with another idea to choose who the winner is. Well, since we are rewarding players from advertisement revenue, we will first need to receive our payment. The payment we receive with have a TX Hash. We will then use the TX Hash to determine the winners. I'm thinking of the first 6 digits numbers. Thus, there will be a 'draw' (picking of winners) when we have 999,999 tickets. Well, sometime we might even draw when we have enough BTC. Thus, making the 'game' run faster.
What would you guys (or girls) like?
A: Ticket number from 1 to 999,999 - using AUTO_INCREMENT on SQL.
B: Randomly pick a ticket number from 1 to 999,999 - using mt_rand().
What would you guys (or girls) like?
A: Ticket number from 1 to 999,999 - using AUTO_INCREMENT on SQL.
B: Randomly pick a ticket number from 1 to 999,999 - using mt_rand().
Litte example to show you how bad PHP + rand() is:
Source: https://www.random.org/analysis/
This should have been a completely random "picture".
Source: https://www.random.org/analysis/
This should have been a completely random "picture".
Thanks for pointing it out. I will be noting it.
I am interested in your site please send more details in pm
Hmm.. what other information do you need? All information (almost) is in the first thread..
I am interested in your site please send more details in pm
Litte example to show you how bad PHP + rand() is:
Source: https://www.random.org/analysis/
This should have been a completely random "picture".
Source: https://www.random.org/analysis/
This should have been a completely random "picture".
Alright, noted. I would be great if you can give me some tip on generating a number from a hash.
Send me a PM and I will get back to you as soon as I'm done at work. Going to create a small sample script for you 
Thanks for guiding me to the right path! I would not have know about the rand() function secret.. Anyway, sent you a PM! I will be crediting you once my site is up and running!
Alright, noted. I would be great if you can give me some tip on generating a number from a hash.
Send me a PM and I will get back to you as soon as I'm done at work. Going to create a small sample script for you Alright. Thanks for pointing out that rand() is not random at all.
Hmm.. a hash to generate a number? Sound great! However, I'm thinking to make it somewhat community-based work. I mean.. everyone got to pick a number or two. The most picked number will be chosen to be the winner. Thus, meaning.. when they redeem their tickets, they wont be able to see their ticket ID. The ID will be given using the AUTO_INCREMENT on SQL.
That isn't a smart idea, because it will be abused pretty quickly. Someone could grab a proxy list and start voting for a number they want to vote for (and thus win easily). You should be in control about the number that wins, not the users. Hmm.. a hash to generate a number? Sound great! However, I'm thinking to make it somewhat community-based work. I mean.. everyone got to pick a number or two. The most picked number will be chosen to be the winner. Thus, meaning.. when they redeem their tickets, they wont be able to see their ticket ID. The ID will be given using the AUTO_INCREMENT on SQL.
Rule of the thumb: Never trust the user, ever.
Alright, noted. I would be great if you can give me some tip on generating a number from a hash.
Alright. Thanks for pointing out that rand() is not random at all.
Hmm.. a hash to generate a number? Sound great! However, I'm thinking to make it somewhat community-based work. I mean.. everyone got to pick a number or two. The most picked number will be chosen to be the winner. Thus, meaning.. when they redeem their tickets, they wont be able to see their ticket ID. The ID will be given using the AUTO_INCREMENT on SQL.
That isn't a smart idea, because it will be abused pretty quickly. Someone could grab a proxy list and start voting for a number they want to vote for (and thus win easily). You should be in control about the number that wins, not the users. Hmm.. a hash to generate a number? Sound great! However, I'm thinking to make it somewhat community-based work. I mean.. everyone got to pick a number or two. The most picked number will be chosen to be the winner. Thus, meaning.. when they redeem their tickets, they wont be able to see their ticket ID. The ID will be given using the AUTO_INCREMENT on SQL.
Rule of the thumb: Never trust the user, ever.
First of all, please make something like this. It's sounds like a nice little project. Secondly, don't use rand(), ever. Either use mt_rand() or openssl_random_pseudo_bytes(). rand() isn't random at all.
To proof that you aren't cheating you could publish a hash from which you will generate a number later on. A good hash would be a number that we can verify (for example a block number) and some random stuff that you picked. Just publish what you have done to get the number and show us everything you used.
To proof that you aren't cheating you could publish a hash from which you will generate a number later on. A good hash would be a number that we can verify (for example a block number) and some random stuff that you picked. Just publish what you have done to get the number and show us everything you used.
Alright. Thanks for pointing out that rand() is not random at all.
Hmm.. a hash to generate a number? Sound great! However, I'm thinking to make it somewhat community-based work. I mean.. everyone got to pick a number or two. The most picked number will be chosen to be the winner. Thus, meaning.. when they redeem their tickets, they wont be able to see their ticket ID. The ID will be given using the AUTO_INCREMENT on SQL.
First of all, please make something like this. It's sounds like a nice little project. Secondly, don't use rand(), ever. Either use mt_rand() or openssl_random_pseudo_bytes(). rand() isn't random at all.
To proof that you aren't cheating you could publish a hash from which you will generate a number later on. A good hash would be a number that we can verify (for example a block number) and some random stuff that you picked. Just publish what you have done to get the number and show us everything you used.
To proof that you aren't cheating you could publish a hash from which you will generate a number later on. A good hash would be a number that we can verify (for example a block number) and some random stuff that you picked. Just publish what you have done to get the number and show us everything you used.
i like new project, new sites and new system
i hope you can do your project
its looks profitable.
i hope you can do your project
its looks profitable.
Thanks for the supporting comment! You are welcome to try my project when it is up and running!
i like new project, new sites and new system
i hope you can do your project
its looks profitable.
i hope you can do your project
its looks profitable.
Hi Bitcoiner! So, I came up with an idea last night. A Bitcoin site which pay reward users it revenue. Much like a faucet, however.. it only reward once in a month* and.. only selected people will be able to get those Bitcoin. Those Bitcoin.. of course.. come from the website revenue.
I'm thinking of a ticketing system. Whereas, users can only redeem one ticket per week*. When the time is up, the system will randomly choose some^ ticket number. The lucky person with the ticket number will then be rewarded with some Bitcoin.
The purpose of this new so-called 'faucet' is to let user earn more on faucet. I hate it when getting only a hundred satoshi in faucet.
It will be coded using PHP. I'm still having trouble to let the computer pick a random number. rand() function might work but.. my users wont be trusting me. Any solutions is welcome. Feedback too.
Not sure where to post, move this if you want.
I'm thinking of a ticketing system. Whereas, users can only redeem one ticket per week*. When the time is up, the system will randomly choose some^ ticket number. The lucky person with the ticket number will then be rewarded with some Bitcoin.
The purpose of this new so-called 'faucet' is to let user earn more on faucet. I hate it when getting only a hundred satoshi in faucet.
It will be coded using PHP. I'm still having trouble to let the computer pick a random number. rand() function might work but.. my users wont be trusting me. Any solutions is welcome. Feedback too.
Not sure where to post, move this if you want.
Jump to: