Quote from: gmiwenht on January 11, 2013, 05:35:39 AM

Quote from: evoorhees on January 11, 2013, 01:09:38 AM

Quote from: gmiwenht on January 11, 2013, 12:15:23 AM

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:

Quote from: fireduck on December 03, 2012, 11:20:28 PM

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