Topic: SatoshiDICE.com - The World's Most Popular Bitcoin Game - page 259. (Read 495799 times)

Yeah, a few bets that never confirmed came in last night.  That is fine until we run out of confirmed funds and start paying with pendings that never confirm.

Anyways, everything will get paid eventually.  I'm invalidating payments that aren't going anywhere and recreating them with different inputs.

Sorry for the delays.

I made a bunch of bets last night, the winnings showed up in my wallet right aways(blockchain.info), But this morning all my winnings are gone! I'm down almost 2BTC from last night. All my bets were placed with 1RezNoRKTt6UQXiAq6Xd7cLmMbrtdF4dF

Two big winner bets have been PENDING for several hours, and the payment out transactions can no longer be found.

http://www.satoshidice.com/full.php?tx=ca0a7568f4e1a73d1f9193d785e5296bcd307f6af82575586882cc8daff1cca4
http://www.satoshidice.com/full.php?tx=ef9792c0499ba94eef1c92bc7baa111319fcb0edf31c0663db3eecdc4fd5453e

Russian now added!

I understand now lol nm

How exactly do you play..im confused

I'll fix that. Thanks.

Looks like it works again And that I won!

I sent a bet through before seeing the process was down, that wont effect the bet yes? It'll just be processed in time?

Looks like it's down now?
This is a good thing, that way I won't gamble too much...

I also noticed a small graphical issue: on the satoshidice.com website the odds are advertised as 98% breakeven (in the logo), but on the advertising on the bitlotto website it says 99%.

Thanks, got all the missing payments.

http://blockchain.info/tx-index/6841173/9224ec4ca880eab252bd7e568f642c62854b370e66044199bd255aea8ca451eb

Ok, returning from a dive into whatever this insanity is.

http://blockchain.info/tx-index/4611323/5d34b39c5e531e939801ff573553189d9f6ee417b1ce053dbb29d6474c263619

Take a look at this, a normal transaction.
In the script inputs section there are two elements:
3045022100a22956219bfb38b6f89eeaecd7c1bf3626efbd13fb53a4bf694f613cfcb493c202206 dbe153a64cc05f017a0e4e3070780ae1ce00ca22c45699c1f825a1da0e7cbbc01 04550138da91fd693ac9865af4d3412d5f03f776a50e852f348b270402946e5079ce3a8a6b5cb40 2a181439151e1453da6d75b515c86ddf9f34206dffeff32a46e

The second one, that starts with 0455 is the public key.  It is pretty important.

Now take a look at our favorite transaction:
http://blockchain.info/tx-index/6712457/a96a3cc6284df89c4d670722e6c2705b7d3709673be8e7207c53e02f35220d45

It just has one element:
30450220239628fbc434ac378f1f0f52d02ec0004e8d0ae930467eee649daabaf210e409022100b 3d836a99f48b9bec9136c77efc4dd9721924ab291df4fca33006095ad2d04a101

Now this is probably valid.  Blockexplorer and Blockchain.info seem to understand it but my BitcoinJ implementation does not.  In fact, it misunderstands is so hard that it isn't know it is misunderstanding it and hashes the entire input script as if it is the public key.  So that produces an address so my software goes on fine and pays that address, which no one has the key to.

I have my software now ignoring any such transactions that it sees.  This isn't optimal but at least it prevents them from being paid to the wrong address.

I hope in the next few days some people in the BitcoinJ development circle can shed some light and I can put in a real solution.

In the mean time I will pay out nelisky separately to make that right and run a program to see if there were any more of these.

I think this was caused because the output in question was fresh from a mined block and had the output in the older OP_CHECKSIG style.

http://blockchain.info/tx-index/6313254/55eacb8699a780561ca42012a3ea47e2eab100d01f89a18749666a94bc88938e

However, I could easily be misunderstanding what is going on there.

Aren't we all glad you're a junior member and most people will ignore that comment ...

After over 3000 bets, I haven't seen a single blip.  Every bet has had an answer.  I wouldn't worry about a few errant half-cents.

Transaction: a96a3cc6284df89c4d670722e6c2705b7d3709673be8e7207c53e02f35220d45
  UpdateTime: Thu May 24 14:56:48 PDT 2012
  Inputs:
    in:0 <- 55eacb8699a780561ca42012a3ea47e2eab100d01f89a18749666a94bc88938e:1
      1K6UuRxtomeyGhYsTCXq9HdRDQVMDPQeEe
      [72]30450220239628fbc434ac378f1f0f52d02ec0004e8d0ae930467eee649daabaf210e409022100b 3d836a99f48b9bec9136c77efc4dd9721924ab291df4fca33006095ad2d04a101

So Blockexplorer and blockchain.info say 1MgH8iNkdZrDW8rsfzifDzsqJnCjBVyRBV
My software says 1K6UuRxtomeyGhYsTCXq9HdRDQVMDPQeEe

The input script is identical. Very strange.

Well - to state the obvious - it will be easy for you to find out how often it messed up the target address - simply check the blockchain (that everyone has) with simple code independent of the code that does the work at the moment

Though, the fact that anyone else can do it would probably suggest you need to check the chain yourself asap ...

This is really strange and I don't see what could have gone wrong at first glance.  I have shutdown processing until I have a coherent answer.

For now, just hope that they will fix the mistake.
Eventually, maybe also stop betting as well - gambling is evil

Indeed, if you look at your bet:
http://satoshidice.com/full.php?tx=a96a3cc6284df89c4d670722e6c2705b7d3709673be8e7207c53e02f35220d45
.. the output address does not match any input at all.

Ok, so I checked the transactions and there was one which I actually won -> a96a3cc6284df89c4d670722e6c2705b7d3709673be8e7207c53e02f35220d45

Thing is, the pay out address, it is not mine. I'm using the bitcoin-qt client at version 0.6.2.2, so I'm pretty sure that's not the problem. Where did satoshidice come up with the address? It is not mentioned in the bet tx at all. So, all in all, I placed 7 bets and received 4 payouts for losing, so I'm missing 2 loosing payouts and one win.

What should I do? Stop betting?