Topic: SatoshiDICE.com - The World's Most Popular Bitcoin Game - page 252. (Read 495688 times)
please check out this TX - seems stuck : 5698d78fecc195af9e8d9ff6c53a3a5f1e84c32222c0d2692f804478939a1d20
http://www.satoshidice.com/lookup.php?tx=5698d78fecc195af9e8d9ff6c53a3a5f1e84c32222c0d2692f804478939a1d20
Is is possible you could add a JSON feed of the Bet Addresses, Winning Odds, Min & Max Bets etc?
I've made a bet of 0.50 BTC and it won. The details are here : http://satoshidice.com/full.php?tx=32907ecb2832a90bc4decc9946f58289df49986174f10266427858edf6d2187d
The transaction is still waiting under the unconfirmed list at SatoshiDice site. I'm waiting for my winnings since 2 days. Please help.
The transaction is still waiting under the unconfirmed list at SatoshiDice site. I'm waiting for my winnings since 2 days. Please help.
Maybe this has been up before, but what's the point having hundreds of recent bets on the front page? It often jams my opera making the site (and my laptop) pretty much unusable. For Satoshi's sake, I hope the page is not dynamic... 
I have actually thought the same thing. Especially with CloudFlare they are losing a lot of the benifit.
Maybe this has been up before, but what's the point having hundreds of recent bets on the front page? It often jams my opera making the site (and my laptop) pretty much unusable. For Satoshi's sake, I hope the page is not dynamic...
OK, yep, I see that mine was committed in 184674 and your payment was after that (committed in block 184675)
So the answer is the actual 0.0005 issue.
Anyway, as I said, in my case that txn had no fee according to bitcoind's rules (I let bitcoind decide as it pleases)
So I guess people have to be sure to enforce the fee and not let bitrcoind produce zero fee txn, or simply just wait for their txn to commit.
Thanks for the info.
So the answer is the actual 0.0005 issue.
Anyway, as I said, in my case that txn had no fee according to bitcoind's rules (I let bitcoind decide as it pleases)
So I guess people have to be sure to enforce the fee and not let bitrcoind produce zero fee txn, or simply just wait for their txn to commit.
Thanks for the info.
Yep got the 'lose' 
Thanks for processing it ... but now it has happened again.
http://blockchain.info/tx-index/9312926/b41bd7c28ca69f47eff448e48e76b37e02a03577f49389c9a61e1fc28b7865d6
This time there was certainly no orphan (I didn't check last time)
The block before it (184665) was fine and the block after it (184666) was also ok ... even though it ended in 666
One common thing between these 2 was that the bitcoind decided to send no fee but did send a fee with all the others that went through immediately.
Thanks for processing it ... but now it has happened again.
http://blockchain.info/tx-index/9312926/b41bd7c28ca69f47eff448e48e76b37e02a03577f49389c9a61e1fc28b7865d6
This time there was certainly no orphan (I didn't check last time)
The block before it (184665) was fine and the block after it (184666) was also ok ... even though it ended in 666
One common thing between these 2 was that the bitcoind decided to send no fee but did send a fee with all the others that went through immediately.
Looks like it was processed fine with the payment in the next block. However, it wan't processed until it was confirmed because the software ignores unconfirmed transactions with a fee less than 0.0005.
...
It looks like the software saw that TX but there was some bug relating to it being included in an orphan chain as well as the main chain. I'll look into that. In the mean time, it is processing now.
Yep got the 'lose' It looks like the software saw that TX but there was some bug relating to it being included in an orphan chain as well as the main chain. I'll look into that. In the mean time, it is processing now.
Thanks for processing it ... but now it has happened again.
http://blockchain.info/tx-index/9312926/b41bd7c28ca69f47eff448e48e76b37e02a03577f49389c9a61e1fc28b7865d6
This time there was certainly no orphan (I didn't check last time)
The block before it (184665) was fine and the block after it (184666) was also ok ... even though it ended in 666
One common thing between these 2 was that the bitcoind decided to send no fee but did send a fee with all the others that went through immediately.
Meanwhile ...
This txn somehow managed to not make it onto the site (it has 4 commits at the moment)
Maybe it was having my name in the address was the problem?
http://blockchain.info/tx-index/9235557/e520c1639bc201bbe245527ca30d9f6553f419741bfc707d3478761a4f24469b
Could an SD person please process it ...
This txn somehow managed to not make it onto the site (it has 4 commits at the moment)
Maybe it was having my name in the address was the problem?
http://blockchain.info/tx-index/9235557/e520c1639bc201bbe245527ca30d9f6553f419741bfc707d3478761a4f24469b
Could an SD person please process it ...
It looks like the software saw that TX but there was some bug relating to it being included in an orphan chain as well as the main chain. I'll look into that. In the mean time, it is processing now.
Meanwhile ...
This txn somehow managed to not make it onto the site (it has 4 commits at the moment)
Maybe it was having my name in the address was the problem?
http://blockchain.info/tx-index/9235557/e520c1639bc201bbe245527ca30d9f6553f419741bfc707d3478761a4f24469b
Could an SD person please process it ...
This txn somehow managed to not make it onto the site (it has 4 commits at the moment)
Maybe it was having my name in the address was the problem?
http://blockchain.info/tx-index/9235557/e520c1639bc201bbe245527ca30d9f6553f419741bfc707d3478761a4f24469b
Could an SD person please process it ...
Kano,
It is my understanding that SD will pick up TXs that are not listed on their website, but are in the blockchain, eventually.
Yes I do suspect they will fix it but by now I'd guess it will be manual ... thus why I reported it to start with since it got passed being committed already in the block chain.
Meanwhile ...
This txn somehow managed to not make it onto the site (it has 4 commits at the moment)
Maybe it was having my name in the address was the problem?
http://blockchain.info/tx-index/9235557/e520c1639bc201bbe245527ca30d9f6553f419741bfc707d3478761a4f24469b
Could an SD person please process it ...
This txn somehow managed to not make it onto the site (it has 4 commits at the moment)
Maybe it was having my name in the address was the problem?
http://blockchain.info/tx-index/9235557/e520c1639bc201bbe245527ca30d9f6553f419741bfc707d3478761a4f24469b
Could an SD person please process it ...
Kano,
It is my understanding that SD will pick up TXs that are not listed on their website, but are in the blockchain, eventually.
Meanwhile ...
This txn somehow managed to not make it onto the site (it has 4 commits at the moment)
Maybe it was having my name in the address was the problem?
http://blockchain.info/tx-index/9235557/e520c1639bc201bbe245527ca30d9f6553f419741bfc707d3478761a4f24469b
Could an SD person please process it ...
This txn somehow managed to not make it onto the site (it has 4 commits at the moment)
Maybe it was having my name in the address was the problem?
http://blockchain.info/tx-index/9235557/e520c1639bc201bbe245527ca30d9f6553f419741bfc707d3478761a4f24469b
Could an SD person please process it ...
And we have set a new record for us today. We have had over 30,000 bets today and still a good chunk of an hour left in the day (GMT days).
And, if anyone wishes to know the repercussions of that ... yes it is causing quite a stink:
- https://bitcointalksearch.org/topic/huge-increase-in-satoshidice-spam-over-the-past-day-87444
Each of the nodes I connect to have been modified to hold hundreds of connections. Likewise, I've tried restarting without connecting to them, rescanning, etc... If it's a matter of starting it differently, rescanning, or redownloading the block chain, you can assume I have already tried it.
Ok, let's eliminate some possible problems.
Have you tried using your existing wallet.dat with the stock client (v0.6.2) that connects to peers (using the default manner)?
My bitcoind runs 24/7, and has 4 specific other nodes that I run, which it connects to... T
I think that's your problem right there.
When you shut down the client, it forgets about these invalid and unconfirmed transactions sent long, long ago from SatoshiDICE but since forgotten on by everyone else since they never confirmed. But then when you start your client back up, it learns of these again from these other four (polluted) nodes of yours.
Why not try a normal startup to the outside world, or with -connect= to a well connected node.
Each of the nodes I connect to have been modified to hold hundreds of connections. Likewise, I've tried restarting without connecting to them, rescanning, etc... If it's a matter of starting it differently, rescanning, or redownloading the block chain, you can assume I have already tried it.
And we have set a new record for us today. We have had over 30,000 bets today and still a good chunk of an hour left in the day (GMT days).
Previous high was 19,000 on June 4th.
Previous high was 19,000 on June 4th.
Congrats!
At this point it's going to be a LOT of blocks before you're caught up.
The problem you are having is that Satoshidice ignores any transaction with a fee of less than 0.0005 until it is confirmed. Based on my experience that many of these never confirm and we would rather not tie up outputs on them if they are doomed.
For example, blockchain.info shows that last one as "Estimated: Never": http://blockchain.info/tx-index/8969893/ff6a2dedc9fd31194806ba8aec7236d32cd4666a5b77fcdc7e01d38bb3cb3b72
Oh...didn't think about checking the fees since the client suggested to add a fee to some and not to others. I thought the defaults were ok.For example, blockchain.info shows that last one as "Estimated: Never": http://blockchain.info/tx-index/8969893/ff6a2dedc9fd31194806ba8aec7236d32cd4666a5b77fcdc7e01d38bb3cb3b72
I changed the settings to always include a fee and now it works great!
Thanks
And enjoy my bitcoins I'll end up losing on your site!
And we have set a new record for us today. We have had over 30,000 bets today and still a good chunk of an hour left in the day (GMT days).
Previous high was 19,000 on June 4th.
Previous high was 19,000 on June 4th.
It seems to be better now, I had three bets reply right away.
But some bets just seems to get stuck.
Take the following for instance fb6553405beb57ba270df9814adcfc63b94e6a5be5546b2e519255b0ed557fc8
Look at both the bet tx and the payment tx: it took around 20 minutes.
Now I have another bet which satoshidice hasn't picked up yet: ff6a2dedc9fd31194806ba8aec7236d32cd4666a5b77fcdc7e01d38bb3cb3b72
That one shows up on blockchain.info, but not on the satoshidice website. on the home page when I look at processing status I see that that the last processing pass is from 22:52 with age 4 (that is the number of tx left to process?)
I hope you manage to resolve those problems too
But some bets just seems to get stuck.
Take the following for instance fb6553405beb57ba270df9814adcfc63b94e6a5be5546b2e519255b0ed557fc8
Look at both the bet tx and the payment tx: it took around 20 minutes.
Now I have another bet which satoshidice hasn't picked up yet: ff6a2dedc9fd31194806ba8aec7236d32cd4666a5b77fcdc7e01d38bb3cb3b72
That one shows up on blockchain.info, but not on the satoshidice website. on the home page when I look at processing status I see that that the last processing pass is from 22:52 with age 4 (that is the number of tx left to process?)
I hope you manage to resolve those problems too
The problem you are having is that Satoshidice ignores any transaction with a fee of less than 0.0005 until it is confirmed. Based on my experience that many of these never confirm and we would rather not tie up outputs on them if they are doomed.
For example, blockchain.info shows that last one as "Estimated: Never": http://blockchain.info/tx-index/8969893/ff6a2dedc9fd31194806ba8aec7236d32cd4666a5b77fcdc7e01d38bb3cb3b72
Sorry, that was a database change I made. I make it use transactions in a more conservative way which ended up being a good bit slower so it was having trouble keeping up with people's bets. It should be much better now. I really need to track some metrics of bet to result time so that this sort of issue is more obvious to us.
It seems to be better now, I had three bets reply right away.But some bets just seems to get stuck.
Take the following for instance fb6553405beb57ba270df9814adcfc63b94e6a5be5546b2e519255b0ed557fc8
Look at both the bet tx and the payment tx: it took around 20 minutes.
Now I have another bet which satoshidice hasn't picked up yet: ff6a2dedc9fd31194806ba8aec7236d32cd4666a5b77fcdc7e01d38bb3cb3b72
That one shows up on blockchain.info, but not on the satoshidice website. on the home page when I look at processing status I see that that the last processing pass is from 22:52 with age 4 (that is the number of tx left to process?)
I hope you manage to resolve those problems too
Jump to: