SatoshiDICE.com - The World's Most Popular Bitcoin Game

[kano]

What client and version are you using?

[geebus]

What client and version are you using?

Satoshi Client 0.6.2

[Stephen Gornick]

I'm open to suggestions.

I'm thinking that in addition to the invalid transactions (which will never confirm) that you might already have the valid ones that arrived, and just are overlooking because you also see the invalid ones.  [Sorry, re-reading your comment, you mention "many times".  So guess not.]  Those invalid ones are invalid.  They'll never confirm.  Sorry.   But if you got the valid ones, then your only problem is in trying to remove the invalid ones (there's a procedure that will do that).

[Stephen Gornick]

I guess go back to the beginning.

Step 1. Make a backup of wallet.dat

Step 2.  Remove every file in the bitcoin folder except for wallet.dat

Step 3.  Launch bitcoin and let it download all the blocks again.

--------

If that still doesn't give you a solution, then you might try pywallet to export the private keys and import them elsewhere.

[geebus]

I guess go back to the beginning.

Step 1. Make a backup of wallet.dat

Step 2.  Remove every file in the bitcoin folder except for wallet.dat

Step 3.  Launch bitcoin and let it download all the blocks again.

--------

If that still doesn't give you a solution, then you might try pywallet to export the private keys and import them elsewhere.

I've done that (re-download block chain), but those transactions still show.

I can't seem to figure out how to export keys, or import them back (in bulk) into a new wallet using pywallet. Know of a tutorial anywhere?

[Stephen Gornick]

If that still doesn't give you a solution, then you might try pywallet to export the private keys and import them elsewhere.

I've done that (re-download block chain), but those transactions still show.

With a clean memory pool after restarting and them not existing in any blocks in the blockchain, I don't understand how it would even know about those transactions to show them anymore even.

To get a look by someone who might know the details of how this can happen, would you consider posting this issue in the Technical Support board?
 - http://bitcointalk.org/index.php?board=4.0

[homer]

Sounds like geebus is seeing the same problem I am.  Sure wish I knew what was going on exactly.  I've tried doing all the things he listed, and still missing bitcoins.

[titeuf_87]

I realize satoshidice is sometimes slow... but for the past few days I always had to wait at least five minutes before I even know if I won or not. Often times it's even longer.

Is this just me? Or that happens to others too?

[arklan]

from my incredibly limited experience, that was the case for me, particularly when betting on the <32000. the <64000 paid out near instantly.

[Raoul Duke]

Since last night I'm waiting hours before I even know if I win or not.

One question: Can we use a sendmany transaction to bet in several numbers and save on transaction fees?

[Retard]

Since last night I'm waiting hours before I even know if I win or not.

One question: Can we use a sendmany transaction to bet in several numbers and save on transaction fees?

dito

-.-

[dooglus]

The receive transactions I have in my wallet do not appear on blockchain.info or blockexplorer.com, and the transactions for SatoshiDICE's payments to me do not appear in my wallet anywhere (I have checked, multiple times).

The thing is, the transactions on the SD site have been confirmed.  For example, your first bet was paid out here:

http://blockexplorer.com/tx/d2768db6562c0231da78188c282748b0b4219064792221ff6e32266ca07f01c1

The problem is probably that you have a conflicting transaction in your wallet which prevents this real transaction from showing up.

I think you'll need to remove the bad transactions from your wallet so the real ones can show up.

I've found pywallet's web interface to be great for doing that.

With a clean memory pool after restarting and them not existing in any blocks in the blockchain, I don't understand how it would even know about those transactions to show them anymore even.

The wallet.dat file holds transactions as well as private keys.  That's why you sometimes need '-rescan' - it tells bitcoin to not assume that it knows about all the transactions from old blocks, but to rescan the blockchain and add any relevant transactions to the wallet.

In this case we have too many transactions in the wallet and need to remove the bad ones.  Jeremy had a similar issue recently - I'll link you to his thread:

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

[dooglus]

Since last night I'm waiting hours before I even know if I win or not.

One question: Can we use a sendmany transaction to bet in several numbers and save on transaction fees?

Yes you can.  See the first point on http://www.satoshidice.com/advanced.php.

[dlasher]

Slow doesn't begin to describe it. I've seen bets today sit (6) hours before returning......


Perhaps someone wasn't ready for this kind of popularity?

[Raoul Duke]

Also, look at this one: http://satoshidice.com/lookup.php?tx=d361a475d14d5e7c85bbb62571f660aee98f7aff5517441d6922fa9cc3a5daee

A sendmany transaction that processed the bets with 45min between each

[kano]

No idea if it is the reason, coz it depends on how the SatoshiDICE server works, however:

In bitcoind, an unconfirmed transaction may be lost if bitcoind restarts.
Unconfirmed transactions from other bitcoinds are stored in a memory pool so are lost when bitcoind stops.
Or, if for some reason the 0-confirm transaction didn't make it to the bitcoind (networks aren't perfect) it wont know about it (though rare)
This also means that if bitcoind wasn't running when the transaction was sent out, it won't know about it until either it ends up in a block, or some other 0-confirm transaction requires it and bitcoind requests it from another bitcoind.
i.e. it will eventually get the transaction back again since probably every other bitcoind still has it and eventually a block will include it.
But bitcoind may not find out about it until it lands in a block (which can be more than an hour on some rare occasions - or longer if some pools are ignoring processing the transaction)

[Raoul Duke]

Transaction ID: 1e11a050fd5a1d18fd63890f9ab4e60c9ce2231ad149d9b36cfee9edbce34b9b

Sent 2 hours ago, 14 confirmations so far. No record on SatoshiDice...

[geebus]

No idea if it is the reason, coz it depends on how the SatoshiDICE server works, however:

In bitcoind, an unconfirmed transaction may be lost if bitcoind restarts.
Unconfirmed transactions from other bitcoinds are stored in a memory pool so are lost when bitcoind stops.
Or, if for some reason the 0-confirm transaction didn't make it to the bitcoind (networks aren't perfect) it wont know about it (though rare)
This also means that if bitcoind wasn't running when the transaction was sent out, it won't know about it until either it ends up in a block, or some other 0-confirm transaction requires it and bitcoind requests it from another bitcoind.
i.e. it will eventually get the transaction back again since probably every other bitcoind still has it and eventually a block will include it.
But bitcoind may not find out about it until it lands in a block (which can be more than an hour on some rare occasions - or longer if some pools are ignoring processing the transaction)

My bitcoind runs 24/7, and has 4 specific other nodes that I run, which it connects to... This wallet is only used for Satoshidice, so no other TX's (aside from the one I funded the wallet with) exist.

Neither a rescan, nor a re-download of the blockchain resolved the issue.

I'm currently rebuilding the wallet by exporting all the private keys from it and re-importing them 1-by-1 into a new wallet... it will take a few days to run, since there are ~2100 private keys and it averages 45 seconds per key to import. I'll let you know how it works out.

[dooglus]

My bitcoind runs 24/7, and has 4 specific other nodes that I run, which it connects to... This wallet is only used for Satoshidice, so no other TX's (aside from the one I funded the wallet with) exist.

Neither a rescan, nor a re-download of the blockchain resolved the issue.

I'm currently rebuilding the wallet by exporting all the private keys from it and re-importing them 1-by-1 into a new wallet... it will take a few days to run, since there are ~2100 private keys and it averages 45 seconds per key to import. I'll let you know how it works out.

That will work, but it would be a lot quicker to just remove the bad transactions from your wallet using PyWallet.

Why don't you try exporting the keys you used in the faulty transactions first and importing them into your new wallet - then you'll see that the bets have been paid out, and that it's just bad transactions in your wallet that prevent you from seeing them.

[geebus]

My bitcoind runs 24/7, and has 4 specific other nodes that I run, which it connects to... This wallet is only used for Satoshidice, so no other TX's (aside from the one I funded the wallet with) exist.

Neither a rescan, nor a re-download of the blockchain resolved the issue.

I'm currently rebuilding the wallet by exporting all the private keys from it and re-importing them 1-by-1 into a new wallet... it will take a few days to run, since there are ~2100 private keys and it averages 45 seconds per key to import. I'll let you know how it works out.

That will work, but it would be a lot quicker to just remove the bad transactions from your wallet using PyWallet.

Why don't you try exporting the keys you used in the faulty transactions first and importing them into your new wallet - then you'll see that the bets have been paid out, and that it's just bad transactions in your wallet that prevent you from seeing them.

PyWallet errors on wallets that have been opened in Bitcoin-qt v 0.6+