|
fireduck
|
 |
June 13, 2012, 11:10:34 PM |
|
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.
|
Bitrated user: fireduck.
|
|
|
titeuf_87
Member
 Offline
Activity: 111
Merit: 10
|
|
June 13, 2012, 11:15:04 PM |
|
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. 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! |
15kfBM3TQ4PGzL7cKncU3su2pH7ZJmiLtr
|
|
|
|
dlasher
|
|
June 14, 2012, 01:41:48 AM |
|
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.
Congrats! At this point it's going to be a LOT of blocks before you're caught up. |
|
|
|
|
|
geebus
|
|
June 14, 2012, 02:02:07 AM |
|
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. |
Feel like donating to me? BTC Address: 14eUVSgBSzLpHXGAfbN9BojXTWvTb91SHJ
|
|
|
Stephen Gornick
Legendary
Offline
Activity: 2506
Merit: 1010
|
|
June 14, 2012, 07:34:10 PM |
|
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)? |
|
|
|
Stephen Gornick
Legendary
Offline
Activity: 2506
Merit: 1010
|
|
June 14, 2012, 07:36:30 PM |
|
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: - http://bitcointalk.org/index.php?topic=87444.0 |
|
|
|
|
|
|
ErebusBat
|
|
June 15, 2012, 01:26:41 PM |
|
Kano, It is my understanding that SD will pick up TXs that are not listed on their website, but are in the blockchain, eventually. |
|
|
|
kano
Legendary
Offline
Activity: 4620
Merit: 1851
Linux since 1997 RedHat 4
|
|
June 15, 2012, 01:48:10 PM |
|
Kano, It is my understanding that SD will pick up TXs that are not listed on their website, but are in the blockchain, eventually. Txn has 49 commits now 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. |
|
|
|
|
fireduck
|
|
June 15, 2012, 01:58:03 PM |
|
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. |
Bitrated user: fireduck.
|
|
|
kano
Legendary
Offline
Activity: 4620
Merit: 1851
Linux since 1997 RedHat 4
|
|
June 15, 2012, 03:17:05 PM |
|
...
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' Thanks for processing it ... but now it has happened again. http://blockchain.info/tx-index/9312926/b41bd7c28ca69f47eff448e48e76b37e02a03577f49389c9a61e1fc28b7865d6This 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. |
|
|
|
|
fireduck
|
|
June 15, 2012, 04:47:27 PM |
|
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. |
Bitrated user: fireduck.
|
|
|
kano
Legendary
Offline
Activity: 4620
Merit: 1851
Linux since 1997 RedHat 4
|
|
June 15, 2012, 11:20:36 PM |
|
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.
|
|
|
|
|
GCInc.
|
|
June 16, 2012, 11:10:56 AM |
|
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...  |
|
|
|
|
ErebusBat
|
|
June 16, 2012, 12:24:07 PM |
|
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. |
|
|
|
|
|
|
piuk
|
|
June 21, 2012, 06:27:24 PM |
|
Is is possible you could add a JSON feed of the Bet Addresses, Winning Odds, Min & Max Bets etc?
|
|
|
|
|
|
|
fireduck
|
|
June 22, 2012, 02:06:41 PM |
|
House edge is about to be temporarily raised to 3% from 1.5%.
|
Bitrated user: fireduck.
|
|
|
|
ErebusBat
|
|
June 22, 2012, 06:44:27 PM |
|
House edge is about to be temporarily raised to 3% from 1.5%.
For how long and what purpose? |
|
|
|
|
