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

[legitnick]

What the fuck is wrong with SD lately?? It has been completely unplayable for the past week or so... I would make successive bets, and then it just stops responding and doesn't return result until next confirmation. And yes, I am including 0.001 tx fee. Also, I often get orphaned transactions that take hours to confirm with no payout. Martingales are not fun if it takes hours to stack them. If something doesn't get fixed soon, then SD is pretty much dead to me.

Hi,

Can you provide a few of your transaction links? I'll look into it. Wallet is healthy so there shouldn't be any abnormal complications going on.

Same thing happened to me, had 200+ bets stuck at UNKOWN for 3+ days

[1714277127]

1714277127

[1714277127]

1714277127

[1714277127]

1714277127

[1714277127]

1714277127

[1714277127]

1714277127

[deepceleron]

What the fuck is wrong with SD lately?? It has been completely unplayable for the past week or so... I would make successive bets, and then it just stops responding and doesn't return result until next confirmation. And yes, I am including 0.001 tx fee. Also, I often get orphaned transactions that take hours to confirm with no payout. Martingales are not fun if it takes hours to stack them. If something doesn't get fixed soon, then SD is pretty much dead to me.

Hi,

Can you provide a few of your transaction links? I'll look into it. Wallet is healthy so there shouldn't be any abnormal complications going on.

example address:

1LovexaZcNCW3Ebm2MehyUwJ5tnQ1sWTPz

this happens constantly, and is happening right now
e.g. https://blockchain.info/tx/1bd59ce48440964fb1e1521532e2369bb4d498978b865ae1883d5914f943aca9

this tx was pushed at 13:25 and no response as of yet (13:42). the response will come as soon as it gets 1 confirmation (i just know this because it happens all the time)

EDIT: now 13:55, tx still not confirmed and no response. but i made other plays and gotten replies instantly (from the same address, 48%)

Seems like the system is working as it should:

So, some recent problems I've been working on:
...
2) We were running out of available funds, which means we would pay with pending funds which can lead to a very poor user experience.  I've made a change such that once the available funds drops below a certain point Satoshidice will only process bets that meet our isLegit() check.  This check passes if the transaction is confirmed or if the transaction and all its UNCONFIRMED parents are known by Satoshidice and have a fee of at least 0.0005 BTC and if the depth of unconfirmed parents is less than 8.  This can lead to a delay, but I think it makes sense when available funds are running low to use them on the transactions most likely to confirm soon first.

You haven't paid an adequate minimum fee, you must be sending with a non-standard client. Double-spend prevention logic dictates that nobody accept your transaction until it is confirmed by being included in a block:

Jan. 11, 2013, 6:03 a.m. ab81954c2bc897ac3d4a867d5da7f8974e816ed207c4cb760b5cb778438491e3
This is a low priority transaction.
This transaction includes 0.00100000 BTC as fee.
size: 2600 bytes
priority: 6,172,266
input: 26.21158766 BTC

    0.00700000 BTC from a9539b2699b0605c3160c25219cdff23eae3d9562331bfbe473dd48420fe5f8b:0 (1LovexaZcNCW3Ebm2MehyUwJ5tnQ1sWTPz)
    1.04280096 BTC from cd4a322dc9b5e0425a2fbe55366a2f1561c74ff9acc446c69336e55dce54dc68:0 (1LovexaZcNCW3Ebm2MehyUwJ5tnQ1sWTPz)
    0.01950000 BTC from fb5f7e8b0123bab2894d76ee38afabc93117c1dcf190c3cc751e86d292e43857:0 (1LovexaZcNCW3Ebm2MehyUwJ5tnQ1sWTPz)
    0.01950000 BTC from 8d1a09c859d0b787ff0f79fa4e56f31351697d2cde4e2f86a7dbbf41e0bb3356:0 (1LovexaZcNCW3Ebm2MehyUwJ5tnQ1sWTPz)
    0.05950000 BTC from 56070b9229e5ded860bd655e56f152a2225ca97e5ebae6c7b9b5e35aebb0c611:0 (1LovexaZcNCW3Ebm2MehyUwJ5tnQ1sWTPz)
    0.80554270 BTC from a27523b18229d08309d646cd3a64cf732f4c1c3195b36dd9a9d1991708d8d860:1 (1LovexaZcNCW3Ebm2MehyUwJ5tnQ1sWTPz)
    0.07950000 BTC from e244a524a3cf6ca234a3978df2398c8f67df76eaefa13b2d15f1839c6e8f7e0a:0 (1LovexaZcNCW3Ebm2MehyUwJ5tnQ1sWTPz)
    0.03950000 BTC from 9dd4fc1f3b5873409442bd88335ba4b25cf485f76b27630507436602cddef147:0 (1LovexaZcNCW3Ebm2MehyUwJ5tnQ1sWTPz)
    0.01950000 BTC from f36f563b1c34e15547121c1c4d1862e9b845bc9129ef0a0278f22800e5ec980e:0 (1LovexaZcNCW3Ebm2MehyUwJ5tnQ1sWTPz)
    0.02728400 BTC from 36c46aff2a74b936918d140d229ab63b524664b56173fa114c5d26ab23154e21:1 (1LovexaZcNCW3Ebm2MehyUwJ5tnQ1sWTPz)
    16.03028400 BTC from 43482273585c8bb1b397e084bfda021cd68cb45665691d9821eab1b0ce9c7701:0 (1LovexaZcNCW3Ebm2MehyUwJ5tnQ1sWTPz)
    4.02828400 BTC from e5608820f9dcd65da6bc0c1a117b512ff6aa3db53f811ec7526b90fab93c3940:1 (1LovexaZcNCW3Ebm2MehyUwJ5tnQ1sWTPz)
    0.01950000 BTC from 51fc18bafe74444b1c0a80b3a74c1d49d17e0115e934d293ed302bcb5d6a3554:0 (1LovexaZcNCW3Ebm2MehyUwJ5tnQ1sWTPz)
    4.01389200 BTC from 9902117bf949f7b3118ab9269b6705d4979d5d10d522c76186c8cfd7adb1ffe5:1 (1LovexaZcNCW3Ebm2MehyUwJ5tnQ1sWTPz)

output: 26.21058766 BTC

    26.00000000 BTC to 1dice8EMZmqKvrGE4Qc9bUFf9PX3xaYDp
    0.21058766 BTC to 1LovexaZcNCW3Ebm2MehyUwJ5tnQ1sWTPz

[dooglus]

So, some recent problems I've been working on:
...
2) We were running out of available funds, which means we would pay with pending funds which can lead to a very poor user experience.  I've made a change such that once the available funds drops below a certain point Satoshidice will only process bets that meet our isLegit() check.  This check passes if the transaction is confirmed or if the transaction and all its UNCONFIRMED parents are known by Satoshidice and have a fee of at least 0.0005 BTC and if the depth of unconfirmed parents is less than 8.  This can lead to a delay, but I think it makes sense when available funds are running low to use them on the transactions most likely to confirm soon first.

You haven't paid an adequate minimum fee, you must be sending with a non-standard client. Double-spend prevention logic dictates that nobody accept your transaction until it is confirmed by being included in a block:

Two things:

1) the quote from fireduck doesn't say that he's checking that the fee is big enough according to the network rules, just that he's checking that it is at least 0.0005 BTC

2) http://bitcoincharts.com/bitcoin/txlist/ agrees that the transaction is "low priority", ie. the inputs are too small and/or new to not require a fee, and so the transaction requires a fee of 0.0005 BTC per kB or part kB.  Your transaction is 2.2 kB, so requires a fee of at least 0.0015 BTC according to the satoshi client.

edit: forgot to include screenshot of the transaction from the above link:

[Bowjob]

Is it safe to say that S.Dice won't have unbelievable runs like December?

[legitnick]

Can someone explain why this happened?
http://satoshidice.com/full.php?tx=2fce09ecfebef65564ab9d8e622786b3a882f9542025a7ad1b826ac55b99dc1e

[BRules]

this kind of things happens when someone plays the satoshi dice.

But if you need some more specific explanation, you should explain what you want us to explain to you, as I couldn't find anything weird in this bet.

[legitnick]

this kind of things happens when someone plays the satoshi dice.

But if you need some more specific explanation, you should explain what you want us to explain to you, as I couldn't find anything weird in this bet.

Look at the address used to place the bet and then look at the address that got the payment.

[BRules]

the bet transaction has two inputs

1Dc8P1wvLpsWUCfhutTgLXZiKT17ti9c51 (0.4995 BTC)
1Enb1nB17S2vysY68kQLUwUuHk9jyF5vD6 (1.2018088 BTC)

so the pay transaction used the first address in the bet transaction

1Dc8P1wvLpsWUCfhutTgLXZiKT17ti9c51 - 1.6045784 BTC
1GoK6fv4tZKXFiWL9NuHiwcwsi8JAFiwGK - 0.53863464 BTC

[legitnick]

the bet transaction has two inputs

1Dc8P1wvLpsWUCfhutTgLXZiKT17ti9c51 (0.4995 BTC)
1Enb1nB17S2vysY68kQLUwUuHk9jyF5vD6 (1.2018088 BTC)

so the pay transaction used the first address in the bet transaction

1Dc8P1wvLpsWUCfhutTgLXZiKT17ti9c51 - 1.6045784 BTC
1GoK6fv4tZKXFiWL9NuHiwcwsi8JAFiwGK - 0.53863464 BTC

I know that but in My Wallet it shows me sending 1.7 but only getting 1.6 from the bet won, the .5 seem to have disappeared.

[BRules]

the bet transaction can be accessed in http://blockchain.info/tx/2fce09ecfebef65564ab9d8e622786b3a882f9542025a7ad1b826ac55b99dc1e

you will see that 0.5 was sent to the address 1BAy2hYAo6MwUkinkE3wbb4aHJyBgVm1yH, probably this is one of your address in your wallet

[Herbert]

Seems like the system is working as it should.

I am sorry, but I think this is not the case.

1) The problem persists even though I loaded my wallet up with a lot more bitcoin
2) I am making really really small bets  (<1% of wallet amount)
3) I am including large tx fee (0.005 BTC)
4) This never happened before, but for some reason it happens now

Sorry, but for me SD is unusable. I used to play it all the time, but I can't any more. And that probably means that it is also unusable for a lot of other people.

Which client are you using? Maybe there is a problem with the coinselection...

[legitnick]

Just to chime in here, I also experience delays when betting through blockchain.info, the bets will randomly freeze and then wait until the next block to go through.
I go to SD and look at the tx id of the froze bet and the page just has lists tx in gold at the top of the page but the rest of the page is blank. No info on the bet at all.

Yeah it borked my blockchain.info wallet, I was able to recover it using bitcoin-qt and my 4 lost coins magically appeared but when I tried to send them back to myself the tx wouldn't go through. Here is the tx that won't go through:
Status: 0/unconfirmed
Date: 1/4/2013 14:53
To: 1M7SYxVFwFV8RmurSRTmyCKPyudu7r6M4f
Debit: -4.43 BTC
Transaction fee: -0.0015 BTC
Net amount: -4.4315 BTC
Transaction ID: f7061844eda5da3350273b3fcd8172d8d2ccc77cda88c39bcfaf16daf6b18158

[evoorhees]

Is it safe to say that S.Dice won't have unbelievable runs like December?

Not safe to say that. The results in December were indeed "better than statistically expected" but not by that much. The real reason the results were so good was that tons of btc was bet in December. If there are months with that kind of bet volume in the future, then more returns like that can be anticipated.

[BRules]

satoshi dice isn't paying fees for returning below minimum transactions anymore. but these transactions aren't being relayed as they don't met the free transactions conditions (https://en.bitcoin.it/wiki/Transaction_fees). so, what will happen with these coins?

example:

http://blockchain.info/tx-index/43841974/2dc3e903d6c30fffb8c606ed4dd26d57a3c5436128dd8267c0379467681156d3

[🏰 TradeFortress 🏰]

satoshi dice isn't paying fees for returning below minimum transactions anymore. but these transactions aren't being relayed as they don't met the free transactions conditions (https://en.bitcoin.it/wiki/Transaction_fees). so, what will happen with these coins?

example:

http://blockchain.info/tx-index/43841974/2dc3e903d6c30fffb8c606ed4dd26d57a3c5436128dd8267c0379467681156d3

they will be sent back to satoshiDICE most likely

so you lost up to 14 cents.

[BRules]

this coins aren't mine, it was just an example.

what how exactly the coins will return to satoshidice?

[Carnth]

this coins aren't mine, it was just an example.

what how exactly the coins will return to satoshidice?

Transactions that are never relayed and/or never confirmed eventually end up back in the sender's wallet... as if the transaction never happened. This usually takes a day (or two).

[BRules]

tke for the info. Looks like satoshi dice has starting paying fees again. http://blockchain.info/tx-index/43970685/7d21d9068259204d21961c8401b59c5792ddaa91b33308093bb17eb2e35dae22

[deepceleron]

this coins aren't mine, it was just an example.

what how exactly the coins will return to satoshidice?

Transactions that are never relayed and/or never confirmed eventually end up back in the sender's wallet... as if the transaction never happened. This usually takes a day (or two).

The transaction was relayed - that is how blockchain.info knows about it - it was broadcast around the network. However, as it didn't include the minimum 0.0001 per KB fee for relay through the p2p network, only those that have a direct IP connection to Satoshidice's server or another peer that has relaxed relaying policies would know about it, and the chance that there is a miner with this transaction waiting in their memory pool is low.

Bitcoins don't magically end up back in the wallet if they are not included in a block. The Bitcoin wallet software considers spent coins as spent, and it takes manually removing the transaction through wallet editing tools to restore the balance shown in the wallet - likely SatoshiDice is not going to do this for 0.001 BTC that they consider "sent" (and should have just kept/ignored) so the coins will probably be considered lost.

[Bowjob]

It looks like S.Dice now waits for 1 confirmation before handing out BTC. Is this for real?