Free Progressive Lottery Faucet We just released a free progressive lottery faucet. Rules: - You can play 3 free tickets per day; - For each free ticket played, 20 satoshis will be added to each jackpot; - You will win hitting 2 to 6 numbers; - Your winnings will be sent to your address when your accumulated winnings are greater than 0.0001 BTC; Play it Now
|
|
|
Referral System: We are the first lottery to offer a multi level affiliate program and you will receive profit from three levels below you. This means that you will win a percentage of the house profit when Player A that was registered through your referral link buy tickets (first level). You will also win when Player B that was registered through Player A referral link buy tickets (second level). And also you will when Player C that was registered through Player B referral link buy tickets (third level). The percentage for the first level is 10% of the house profit, the percentage for the second level is 8% and the percentage for the third level is 7%. So lets try an example:Lets suppose you referred 7 players. This means that if every one that you refered buy a basic ticket for 0.001 BTC you will receive 0.000028 BTC. Now lets suppose that every player you referred also referred more 7 players each one. This means that if every one referred in your first and second level buy a basic ticket for 0.001 BTC you will receive 0.0001848 BTC. And once more lets suppose that every player referred in your second level also referred more 7 players each one. This means that if every one referred in your first, second and third level buy a basic ticket for 0.001 BTC you will receive 0.0011452 BTC. And all this is considering only the basic ticket. But that's not all, we also decided that everyone should have a referrer before registering, but we don't want to block registrations of players that reached our site clicking in our ads or through a search engine. So we created a score system. After every draw we will calculate a score for every player that logged in on YABTCL in the last 30 days and the player with the bigger score will be the referrer of the players that didn't reached our site through a referral link and also he will be considered the referrer of all the random tickets bought by players that used one of our fixed addresses until the next draw. Events that raise your score: Investing, buying tickets, creating pools and buying quotas in pools. Events that decrease you score: Wining shares of the jackpots, receiving profits from your investments, receiving revenue from the referrals, divesting and receiving profit from quotas bought in your SAT (Share-a-Ticket) pools. Let's see an example where a player: - Invested 10 BTC (+10);
- Received 1.5 BTC from his investment (-1.5);
- Divested 9 BTC from his investment (-9);
- Bought tickets for a total of 3 BTC (+3);
- Created a SAT Pool for a total of 2 BTC (+2);
- Others players bought quotas in his pool for a total of 1 BTC (-1);
- Received percentages of the revenue from the referrals totalizing 1 BTC (-1);
- Won shares of the jackpots totalizing 1 BTC (-1);
So, the player of the above example will have a score of +1.5 and if this is the highest score between all players at the draw time, all the players registered until the next draw that didn't reach the site through a referral link will be automatically referred by the above player. If you have any questions, don't hesitate to ask.
|
|
|
hey mem, tks for adding our lottery in the games list.
I'm sorry if our provably fair system isn't that easy to understand but it couldn't be simpler as we want transparency to our players and also investors.
And once again, you have a great site. Impartial reviews and also badges, loved it.
Keep up the good work.
|
|
|
When a player register, we warn him about the importance of using an address where he is in control of its private key, because we have imposed some security measures that some actions require you to sign a message with one of your registered addresses.
one reason that we implemented this kind of security is to kinda force the user to have a address where he controls a private key to avoid problems like having all your money in "online wallets" like MTGox and inputs.io.
Today one player contacted me that he had money in one account of our lottery, but the address he used to register was an address of the defunct inputs.io and, as our lottery requires a message signing to withdraw to a new address, he was not being able to withdraw.
Luckly, the user did not forgot his password and I asked some informations that confirmed that he was really the owner of the lottery account.
So, I'm here to kinda beg you to have an address where you control the private key to avoid losing funds on our lottery and more important, losing all your money when something happen to the "online wallet" where your funds were.
Regards.
|
|
|
Just one quick example is the JS that fetches the txid hash, I noted in the code you embedded the addresses. Thats fine, not an issue at all - but Id suggest perhaps updating the js so it fetches the file and explodes it.
Its a minor minor detail, but I had to look at the code to figure out where the file was being pulled from, only to see that for each draw you post updated JS with the file contents embedded.
I think you didn't get how exactly this script works. I didn't use different JS for different draws and I also didn't use the tickets file on it. What this script do is: - verify if the txid was passed as a request parameter. - if yes, get the content from the URL: https://blockchain.info/rawtx/<txid>- get the address and value from each transaction output and also the time the transaction reached the BlockChain.info servers - do the calculations to transform the outputs in the SHA256 hash of the tickest file. as you can see on the draws details, the URL to this script is always the same, the only thing that changes is the request patameter (txid). And the reason that I embedded the addresses in the JS is because I won't change the address that represent the parts of the SHA256 hash, this means that: 1P7XU93VPfF3UWiA1BTPqeq3fCay98nHLj will always contain the representation of the first 6 characters set of the tickets file hash. 12BDqs7PbiME8o8prgrq44F5G6t2XWWNDu will always contain the representation of the second 6 characters set of the tickets file hash, and so on... hope this is clear.
|
|
|
As they don't put the txids of the bets in the results, you can't prove that payment occurred, thereby giving the operators the possibility to play for free, which goes back to my previous point.
Disagree with you here, at their help page there's an explanation of the revenue distribution of their lottery: We take 4% to the house; From the remainder, we reserve 6% to the next 6 hits jackpot, this means, after someone hit the jackpot for 6 hits, the acumulated amount in this reserve will be used to next 6 hits jackpot; And the remainder we split it into the following: 17% to the jackpot for 6 hits; 17% to the jackpot for 5 hits; 16% to the jackpot for 4 hits; 25% to the jackpot for 3 hits; 25% to the jackpot for 2 hits.
so, as the tickets are listed before the draw, you can calculate how much a jackpot worth in a draw. So, they won't be able to put a free ticket without risking to be caught cheating. You're right BRules. When we had the idea to make a bitcoin lottery, we decided that the lottery should be as most transparent as possible, only this way we can have confidence from our players. but this discussion made me realize that we should put the jackpot value in the draw details, this way will be easier to the users to follow the jackpots.
|
|
|
hi all,
mem, you said: "What I have realized from reviewing yabtcl is that its not enough for sites to simply describe their provably fair system they need to walk through an example."
So, I'm not clear if you're talking about my site.
In every draw, we have an explanation about the provably fair system using the values used in that draw. Do you think we need to improve it? What do you missed in the explanation?
Now, let me explain the technical details how we timestamp the SHA256 hash with a bitcoin transaction.
The SHA256 hash has a total of 64 characters, so we split the hash in 10 parts of 6 characters.
We also defined a specific address to each hashpart.
So, after getting the SHA256 hash of the file, we divide the 64 characters into 11 parts and transform each part into a decimal number. The decimal number got in each part will be the amount of satoshis needed to be sent to the address representing that part. As nowadays a bitcoin transaction output need to have at least 5430 satoshis, we add this amount to each part and then create a bitcoin transaction to timestamp the SHA256 of the file.
Hope it is clear.
Any question, just ask.
And tks again for reviewing our lottery.
|
|
|
changes in the revenue distribution (the house fee remains the same):
We take 4% to the house; From the remainder, we reserve 6% to the next 6 hits jackpot, this means, after someone hit the jackpot for 6 hits, the acumulated amount in this reserve will be used to next 6 hits jackpot; And the remainder we split it into the following: 17% to the jackpot for 6 hits; 17% to the jackpot for 5 hits; 16% to the jackpot for 4 hits; 25% to the jackpot for 3 hits; 25% to the jackpot for 2 hits.
|
|
|
Now you can play without registering using the following addresses to buy random tickets: Numbers In Ticket | Address | Price | 6 | 1QHw2pnQeoHy5ApyvgPAiF9bJjs5Y3np5x | 0.001 BTC | 7 | 1N1eDvqQSQZD45x2UXx2FhrCSz9j8mYe7m | 0.007 BTC | 8 | 1FAVeXkMGkWrqaLbbY2wTTryegWGDeQkX2 | 0.028 BTC | 9 | 1Gp27P5aXzuezGPmdeqhJpaufRJAWrEWLY | 0.084 BTC | 10 | 1KMAWshsM1rh2ryPvAav8BtZjGj9i2HPp6 | 0.210 BTC | 11 | 1CytPDfxydx356YvQk5JW1zBbCt2ThrK1 | 0.462 BTC | 12 | 1JRsp4r4YSBT6jpHzTwGdAzzs9p27jTrnb | 0.924 BTC | 13 | 1Bhc5eizPt41bzJhrqh16BT2kJc63J67Kp | 1.716 BTC | 14 | 12LQ8SYxvhLyycTWrRzJLaz3ynXTHHEF6w | 3.003 BTC | 15 | 1Cpqtg5xvvX2MQsF1xRdsR1NGHW4tZhu5K | 5.005 BTC | 16 | 1HPyNdyTxjNL8DXUezbsojQQUMN72sANG7 | 8.008 BTC | click here for more detailsGood Luck all
|
|
|
And our lucky winner is howeth
There were 6 tickets in the last draw and howeth was the only one who won the jackpot for 2 numbers and also his ticket was the chosen one to win the 0.025 BTC.
Congratulations.
|
|
|
i need the same thing, i have an account blockchain.info, but i cant chat. maybe it is from another site. anyone knows which site ?
just click on the "Chat" link and you will be redirected to www.btc-e.com
|
|
|
The transaction is too small (less than 5430 satoshi's)
Actually, the sum of the transaction outputs can be higher than 5430 satoshis, but if one of the outputs has less than 5430 satoshis the transaction will be considered non stardard
|
|
|
And our lucky winner is BRules, he/she won 0.1 BTC playing a ticket by 0.001 BTC.
Well, actually he/she wasn't that lucky as only he/she played a ticket in the last draw.
For the next draw I will raffle 0.025 BTC between the players that bought tickets. The rules are on my previous post.
good luck all
|
|
|
A transaction with an output less than 0.00005430 is also a non standart transaction and this is also an obstacle to your transaction be confirmed
|
|
|
all this can be acomplished with the RPC calls
get how many confirmations a transaction has: gettransaction <txid>
generation addresses: getnewaddress [account]
If you type "help" in the console on bitcoin gui interface, you will get a list of all commands available via RPC, and if you type "help <command>" you will get a explanation about the specific command.
|
|
|
In my opinion, the best way to receive payments is with the Bitcoin Core client. so you don't need to depend on third parties servers to receive payment
|
|
|
Yes. It's the same way from the older versions. From https://bitcoin.org/bin/0.9.0/README.txtHow to Upgrade --------------
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), uninstall all earlier versions of Bitcoin, then run the installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux).
If you are upgrading from version 0.7.2 or earlier, the first time you run 0.9.0 your blockchain files will be re-indexed, which will take anywhere from 30 minutes to several hours, depending on the speed of your machine.
On Windows, do not forget to uninstall all earlier versions of the Bitcoin client first, especially if you are switching to the 64-bit version.
Windows 64-bit installer -------------------------
New in 0.9.0 is the Windows 64-bit version of the client. There have been frequent reports of users running out of virtual memory on 32-bit systems during the initial sync. Because of this it is recommended to install the 64-bit version if your system supports it.
NOTE: Release candidate 2 Windows binaries are not code-signed; use PGP and the SHA256SUMS.asc file to make sure your binaries are correct. In the final 0.9.0 release, Windows setup.exe binaries will be code-signed.
|
|
|
you can't use -datadir on the configuration file: From https://en.bitcoin.it/wiki/Running_Bitcoin#Bitcoin.conf_Configuration_FileBitcoin.conf Configuration File
All command-line options (except for -datadir and -conf) may be specified in a configuration file, and all configuration file options may also be specified on the command line. Command-line options override values set in the configuration file.
|
|
|
As I could understand from your message, you want to just send a message to the person that send you some coins.
So, let me tell you that you can't send message to others bitcoin users. Maybe you think that this is possible because in the portal blockchain.info some transactions have messages in it, but this is a feature especific in that portal and bitcoin protocol doesn't support it.
Furthermore, if someone send you coins from an exchange, their coins isn't being sent from their address but from the exchange addresses, so they will never receive your transaction back.
So, in my opinion you should forget about this. Or if you really want to do this you will need to use the blockchain.info API
|
|
|
|