Bitcoin Forum

Hello guys

Is born BtcLucky.com a new way to play fun and safe with more than 98% chance of winning!

In addition 64000x Win your bet ... UP TO 1000 Bitcoin OF WINNING! Many games all related to our world! You will find the famous game of dice, the amazing jackpot, the lottery and much more! What are you waiting for??? Come and play with us! WIN NEVER BEEN SO EASY!
Now there's only dice game but next week will be implemented the jackpot, the lottery game and much more!

Try it yourself: send bitcoin minimum 0,001 and maximum 5 bitcoins to this address
1LuckyoLb6EBLbrbzKWU2N9MSmMuHSNBwZ
you have a 73.2422% chance of winning, if you win you will be instantly credited to the address from where you submitted your bet multiplied 1.340x! If lose will be credited the 0.005% of your bet.

You will find all explanation of how the extraction of "Lucky Number" on the" Verification" page of the site and you will discover that it is impossible to tamper the Lucky number and that is random and 100%!

Why play with us? In the field of dice games we are the ones with the highest percentage of winning and the higher multipliers payment, therefore more likely and more winning!
Check by comparing with other sites that you already know!

BtcLucky.com accept the multi bets!!! Try it now!!

Every week will be implemented totally new games, lots of news waiting for you!

And remember WIN NEVER BEEN SO EASY!!

http://www.btclucky.com

Good game!

/dadosovr

tomorrow will be implemented the jackpot and the jackpot ref!!

It's strange.  I bet 0.003 on lt32768 and I get 0.0018 back...
Was it an overpaid loss, or an underpaid win? A bug?

Also, I'm missing something like satoshidice's check-form
  http://satoshidice.com/lookup.php?tx=&limit=100&min_bet=0
to look up the result of the bet and the actual lucky number.

I think that you do somthing wrong, i now bet on the lessthan 32768 and i win..check  http://btclucky.com/it/last_bet.php

With Internet Explorer the site have some bug now, i'm now solving this for all users that use ie!

What did I do wrong with this tx?
  https://blockchain.info/tx/77b1176af2513a10da7a26b5ce421241d573dcc6c68c6c31c22c8df443ea6a83
It doesn't even show up on last bets.

This is, what I believed to be the payout-tx:
   5c9e7ab5acf6ba5c33d74f28cdbbbaeeacdf36fb3e56cf4e0aa9d678ab8e8c7c
The address 16sX9or9oThFiCs2SQcMriXubPqinw3P1F got previously funded
from some 1Lucky... addresses, so I guessed it's related. Also, as I see now,
it's the same address that paid *your* win.

Also, transferring bitcoins to some address hardly has any relation
to which browser I use. (btw., it's not IE, anyway)

It's not likely that I play again without a plausible explanation of what happened.

Ok, now I know, what went wrong:

My bet transaction had three outputs, only the third of which was the bet.

I replaced my bet-transaction id into the URL behind the "Log"-link of some other bet, giving:
  http://www.btclucky.com/games_log/77b1176af2513a10da7a26b5ce421241d573dcc6c68c6c31c22c8df443ea6a83.log


Instead of dealing with the *third* output of my transaction, it examined the *second*
output, then obviously didn't recognize that address, and did something bogus.

Compare yourself with the details of my bet transaction:
  https://blockchain.info/tx/77b1176af2513a10da7a26b5ce421241d573dcc6c68c6c31c22c8df443ea6a83

It mistakenly tried to handle the 15erNPoS... output instead of the 1LuckyrM48Faa9nK725mX7J5X7FSeFqTar output.

Now there aren't any problem try!

I just tested it :)
It works well, I won and lost ;D

i hope tha you win more than lost :D

You think its fixed? I don't think so. ;-)

Anyway, thanks for the faucet.
(I won't overuse it. promised. But others might.)

Try it and discover that is all fixed ;)

if you send an amount less than the min bet (as written on the table), the game does not work!

Nope, not yet fixed:
My bet: https://blockchain.info/tx/c0bb0d8a56e35699efd4c38a35f27532aabeacd6290c79616c7f793fbe36bfc1
Your log: http://www.btclucky.com/games_log/c0bb0d8a56e35699efd4c38a35f27532aabeacd6290c79616c7f793fbe36bfc1.log

PS: For my testing work, I've so far earned about 0.32 BTC.
   That is a rather cheap fee for someone to do system testing for you,
   but I'd really like some *working* alternative to satoshidice, so I'll
   continue trying your site, and earning some peanuts from it, until
   you really fix it.

PS: yeah, the satoshi-bet didn't work, but the hole is still there.

OK OK try try

Are you satisfied?

Yes, at least now this simple trick didn't work any more. Bravo! :-)

Will try more tricks in the next few days and report back, when I find something.

If you think that for saving you from greater losses I deserve
an extra donation, then you know where to send it to :-)

some thanks ... But you could report it without me out of his head with blockchain and stealing some btc :) thanks anyway

In a few hour will be implemented the jackpot platinum gold silver and bronze!!!! ;)

BtcLUcky accept now the multi bet!!!!

There seems to have been a problem recently with a large stack of transactions failing
due to a double-spend far upstream. (see also https://bitcointalk.org/index.php?topic=127531.0 )

For the following bet:
  http://www.btclucky.com/games_log/6e58604678d59a541f2a7d5ea4c0b096405091e0360255cf68703ad6fb82dea2.log
the bet itself still confirmed fine:
  http://blockchain.info/tx-index/34271677/6e58604678d59a541f2a7d5ea4c0b096405091e0360255cf68703ad6fb82dea2
but the payout of 0.01230400 was voided due to bad (double-spend derived) funds:
  http://blockchain.info/search?search=8a8bd0bc0f5230adfc12a8f95cfe16f9d73c6fd5f5390d2627525a379efbc066
     shows: "Sorry we could not find any blocks or transactions matching this hash"

Unless your software does it automatically, I'd request a manual correction.

PS: Among my own bets, there was one voided, as well (and so was its payout), and one
is still waiting for confirmation but has no reason not to get confirmed any time soon.

Unfortunately this website is dodgy.

See also this discussion (in Italian): https://bitcointalk.org/index.php?topic=124274.msg1354469#msg1354469

Thanks for the pointer.  I google-translate-skimmed my way through it.

I don't know about errors with lucky#, but with respect to the voided payouts,
I believe that DadoSovr is victim to a higher degree than being a scammer.

I have seen two dice-games since satoshi-dice, btcdice and btclucky and both of them
were/are vulnerable to starving bets (that is: bets that propagate, but wont ever be confirmed).
Satoshidice is the only one essentially immune to such bets, in that it ties the payouts to the
bets: If then the bet becomes invalid, then so does the payout.

Now I guess, someone seems to have kind of "flooded" btclucky with starving bets,
and got non-starving returns.
Those starving funds were instead paid out to later players. Those, that now complain...

Confirmed: currently there’s every indication that they are thieves.

https://bitcointalk.org/index.php?topic=129070.0

WoW BtcLucky.com has increased the bet max...WOW ARE AMAZING!!! You can win over 200 Bitcoin!!!!!

Lol.

On my approximative Italian I gather from the linked original that this is a situation very much akin to the bitdaytrade debacle. Specifically, the Davide Sovrano / DadoSovr character pretended to have written code which he didn't (giangel84 would appear the real author (https://bitcointalk.org/index.php?topic=124274.msg1359685#msg1359685), probably freelancer working for hire), then was hit quite massively by the same doublespend problem that hit S.DICE. Unlike their model, bitlucky failed to even comprehend the problem let alone take precautions, and as a result a number of dissatisfied bettors started a riot (Stemby chief among them). The owner disappeared ("abandoned the project, the wallet and the support email").

It was a problem in the code. Not the double spending thing

In any case Davide Sovrano (DadoSovr) is a thief.

Ah? Ok then.

So what about the doublespending thing? Seems to me they'd be equally open to it, is this correct?

Yes, in theory, because the site works like the original SatoshiDice: it accepts 0-confirmation transactions.

Ciao!