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

Status: 1163 confirmations
Date: 11/23/2012 07:37
To: satoshidice.com lessthan 00004 15990.789 1dice2pxmRZrtqBVzixvWnxsMa7wN2GCK
Debit: -0.001 BTC
To: satoshidice.com lessthan 32000 2.031 1dice8EMZmqKvrGE4Qc9bUFf9PX3xaYDp
Debit: -0.01 BTC
Transaction fee: -0.0005 BTC
Net amount: -0.0115 BTC
Transaction ID: b80ee0c2d01f40731a48bf0f5ca97004602a4357da4e2fd9fb3dac43b77818e0

also, I upgraded my client...


20:23:55
getrawtransaction 89f3bc7de8aaef8a5c1b8daf90e108d349652a61e8a9e6d191e199c898c59fd7
20:23:55
0100000002e01878b743ac3dfbd92f4eda57432a600470a95c0fbf481a73401fd0c2e00eb802000 0008b483045022100907513102947367004ba4c51d9aa08d03cf3c92c8ac00dbc51f30a112159cc c5022033aaccf45fcd877c840d6852bd609bfb7f28182cd88e6a50ae735f7e984556760141048cc 0b94178715f03ed3d0bceb368191d0fdd7fc16d806567f6f2c45aecafb8f53e5ef849564072189b 9b4f8bfe1564da776567ba359cfb0c05e839bcf65371abffffffff046df3556bcb311bdea374dcf c10ec5df0a482a717637c4437be5f8f762efcc0010000008b483045022069bc91b6d1e6fe49e394 28528d1509a7b2f65438021006d28dce9c409b435bc1022100fbccbb18850eb674cdf4d802ee313 7a8e8fa35c9add8684ca7b50b7419b2b6e00141047b02ab271ff84e97ffd3982ef941de9befd9a6 a59711475d38eeea9f769b29eabc5327d16662f0000986ac04bad7fd060f840ead8801d9dc1be1c c57d2df4d7bffffffff0238d01d00000000001976a914017a78851dd062a2ab4a72e2065612362f ac725b88acdd6c1d05000000001976a914e04d22e13420d48e8ea69ac8b7abfb229b9d6bf188ac0 0000000

If a bet is confirmed, it will eventually be paid out.

If a bet never confirms, it will eventually disappear.

So it really depends which half of the bet/payment it is that's "stuck".

What exactly happens to all of the unconfirmed transactions? Will they get stuck or will they eventually confirm?

I expect you have an old version of the client.  Get the current version and you'll see the debug window option in the help menu.

And I don't see that transaction anywhere.  What's the transaction id for your corresponding bet transaction?  You can find it by right-clicking the bet in your client and selecting 'show transaction details' and then can copy/paste the txid.

You won't lose coins even if their server is hit by a meteorite. Every bet is stored in the blockchain.

Ah, I see.

There hasnt been any major problem where people lose coins due to errors or anything, has there?

Thanks for the info

Sometimes someone flooding SD with a lot of small bets. And the others have to wait until the game chews all these txs. I wish they do anything to speed-up their engine. Necessity to wait 5-10 seconds after each bet kills the fun.

Is satoshi dice working properly for everyone else today?

Seems slow to send and receive. And I think a few may be stuck

Now, I can show my ignorance.  I'm using the standard client and 'debug' isn't an option in the help menu.  In any case, here is everything I know about the unconfirmed transaction.  The bet went thru and I even won, but the transaction from satoshidice to me is the one that is unconfirmed.

Status: 0/unconfirmed
Date: 11/23/2012 07:40
Credit: 0.01953848 BTC
Net amount: +0.01953848 BTC
Transaction ID: 89f3bc7de8aaef8a5c1b8daf90e108d349652a61e8a9e6d191e199c898c59fd7

Like I said before, it's not a big deal. But I'm learning a lot about how all this works by troubleshooting an issue.

If that is indeed what happened, then wouldn't the client automatically be resending the transactions on a regular basis?

You can force it to try resending a transaction.

Go to the debug console (Help > Debug window > Console) then:

  * getrawtransaction transaction-id-to-resend
  * sendrawtransaction big-long-hex-string-from-the-above

From https://bitcointalksearch.org/topic/m.1298954:

I don't know what would have caused your transactions never to confirm.  Could you have double-spent some of your coins maybe?  If you have another copy of the same wallet on a different computer that can happen.

I can look into the details for you if you do the following:

* copy the transaction ID of one of the unconfirmed bets
* on the Help menu, click 'Debug window'
* select the 'console' tab
* type getrawtransaction xxxxxxx (where xxxxxxx is the transaction ID you copied above)
* post the result

That will allow me to see the transaction, even though either your client or the bitcoin network as a whole is rejecting it.

On my end, I'll open the debug console the same way, but will run this instead:

* decoderawtransaction yyyyyyy (where yyyyyyy is the result of your getrawtransaction that you post)

You can try it to see what information you're revealing.  It's exactly the same information as if the transaction you tried to make had ended up being sent.

Satoshidice has been getting large amounts of bets these past 20 minutes.

I've looked deeper.  The transaction IDs are not in the blockchain.  They simply show as unconfirmed in my wallet.  Is this what happens with orphan transactions?  It's only .019 btc so not a big deal.  I'm redownloading the blk files so it'll be sometime tomorrow before it'll let me get to the trans IDs, but I'm sure it'll only confirm what I've already discovered.

I don't see any bets from 4 days ago in the blockchain that haven't got corresponding payments from SatoshiDice.

I suspenct that either your bet never got into the blockchain, or you've been paid already.

Can you post the transaction IDs?

Do I need to post something about my stuck transactions, or is it something that just fixes itself if I wait long enough?  I've got two been unconfirmed for 4 days.

See message I sent to your inbox.

[Edit:


and details from my reply cleared as requested.]

Problem solved.

Yeah, we don't handle freshly mined coins very well.

Those are processed now.  I had to put in their return addresses by hand.  The version of bitcoinj we use can't figure them out coherently.