Bitcoin Forum
November 20, 2018, 10:37:22 PM *
News: Latest Bitcoin Core release: 0.17.0 [Torrent].
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 [20] 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 ... 274 »
  Print  
Author Topic: SatoshiDICE.com - The World's Most Popular Bitcoin Game  (Read 474384 times)
geebus
Sr. Member
****
Offline Offline

Activity: 258
Merit: 250



View Profile WWW
June 13, 2012, 05:18:56 AM
 #381

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+

Feel like donating to me? BTC Address: 14eUVSgBSzLpHXGAfbN9BojXTWvTb91SHJ
1542753442
Hero Member
*
Offline Offline

Posts: 1542753442

View Profile Personal Message (Offline)

Ignore
1542753442
Reply with quote  #2

1542753442
Report to moderator
1542753442
Hero Member
*
Offline Offline

Posts: 1542753442

View Profile Personal Message (Offline)

Ignore
1542753442
Reply with quote  #2

1542753442
Report to moderator
1542753442
Hero Member
*
Offline Offline

Posts: 1542753442

View Profile Personal Message (Offline)

Ignore
1542753442
Reply with quote  #2

1542753442
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1542753442
Hero Member
*
Offline Offline

Posts: 1542753442

View Profile Personal Message (Offline)

Ignore
1542753442
Reply with quote  #2

1542753442
Report to moderator
dooglus
Legendary
*
Offline Offline

Activity: 2548
Merit: 1125



View Profile
June 13, 2012, 05:20:01 AM
 #382

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

Not for me it doesn't.

Maybe you need a newer PyWallet.

Just-Dice                 ██             
          ██████████         
      ██████████████████     
  ██████████████████████████ 
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
    ██████████████████████   
        ██████████████       
            ██████           
   Play or Invest                 ██             
          ██████████         
      ██████████████████     
  ██████████████████████████ 
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
    ██████████████████████   
        ██████████████       
            ██████           
   1% House Edge
Gladamas
Sr. Member
****
Offline Offline

Activity: 294
Merit: 250


Bitcoin today is what the internet was in 1998.


View Profile
June 13, 2012, 05:51:21 AM
 #383

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

Not for me it doesn't.

Maybe you need a newer PyWallet.

No, pywallet won't work with Bitcoin-qt 0.6+, nor will it work with encrypted wallets.

1GLADMZ5tL4HkS6BAWPfJLeZJCDHAd9Fr3 - LQ6Zx8v7fHVBiDX5Lmhbp6oEDB7dUFjANu
GPG 0xF219D5BB3C467E12 - Litecoin Forum
fireduck
Sr. Member
****
Offline Offline

Activity: 390
Merit: 251



View Profile
June 13, 2012, 05:59:24 AM
 #384

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?

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.

Bitrated user: fireduck.
dooglus
Legendary
*
Offline Offline

Activity: 2548
Merit: 1125



View Profile
June 13, 2012, 06:16:45 AM
 #385

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

Not for me it doesn't.

Maybe you need a newer PyWallet.

No, pywallet won't work with Bitcoin-qt 0.6+, nor will it work with encrypted wallets.

Are you sure?  I used it just a few days ago, and I've not had anything older than bitcoin-qt 0.6 for a long time.

Maybe I didn't encrypt the wallet I used it with, but I created it using bitcoin-qt 0.6+.

Just-Dice                 ██             
          ██████████         
      ██████████████████     
  ██████████████████████████ 
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
    ██████████████████████   
        ██████████████       
            ██████           
   Play or Invest                 ██             
          ██████████         
      ██████████████████     
  ██████████████████████████ 
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
    ██████████████████████   
        ██████████████       
            ██████           
   1% House Edge
dlasher
Sr. Member
****
Offline Offline

Activity: 466
Merit: 250



View Profile WWW
June 13, 2012, 06:59:37 AM
 #386

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.


Yes. Please.
geebus
Sr. Member
****
Offline Offline

Activity: 258
Merit: 250



View Profile WWW
June 13, 2012, 07:11:01 AM
 #387

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

Not for me it doesn't.

Maybe you need a newer PyWallet.

No, pywallet won't work with Bitcoin-qt 0.6+, nor will it work with encrypted wallets.

Are you sure?  I used it just a few days ago, and I've not had anything older than bitcoin-qt 0.6 for a long time.

Maybe I didn't encrypt the wallet I used it with, but I created it using bitcoin-qt 0.6+.

Yeah, I tried it last night and it just throws a bunch of errors on my 0.6+ wallet, but worked fine on a 0.5.x wallet.

Feel like donating to me? BTC Address: 14eUVSgBSzLpHXGAfbN9BojXTWvTb91SHJ
dooglus
Legendary
*
Offline Offline

Activity: 2548
Merit: 1125



View Profile
June 13, 2012, 07:34:22 AM
 #388

Yeah, I tried it last night and it just throws a bunch of errors on my 0.6+ wallet, but worked fine on a 0.5.x wallet.

I just tried it on my encrypted 0.6.2 wallet.  The web interface tells me "deleted 1 transaction" and if I try again, "delete 0 transactions", but when I load the wallet up into the client, the transaction is still showing.  Possibly because it's already confirmed though.  I'll try with an unconfirmed transaction...

[time passes]

Yes, it works with bitcoin 0.6.2 and an encrypted wallet.

I made a transaction in my wallet, then quit bitcoin-qt and ran:

Code:
python pywallet.py --web

in a terminal, then visited http://localhost:8989/ in my web browser, scrolled down to where it says:
  Delete a key from your wallet:
copy/pasted the new unconfirmed transaction ID into the 'key' field, and clicked 'delete'.

It told me: "tx:[...] has been successfully deleted from /home/.../.bitcoin/wallet.dat, resulting in 1 deleted item".

I would guess that maybe you have some problems with your 0.6+ wallet, and so exporting and re-importing the keys is probably the best thing to do anyway.

Then when I ran bitcoin-qt again, the transaction was no longer showing at all.  It's still on blockchain.info as an unconfirmed transaction, and I'm sure it will eventually confirm, at which point I will see it in my wallet again.

Just-Dice                 ██             
          ██████████         
      ██████████████████     
  ██████████████████████████ 
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
    ██████████████████████   
        ██████████████       
            ██████           
   Play or Invest                 ██             
          ██████████         
      ██████████████████     
  ██████████████████████████ 
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
    ██████████████████████   
        ██████████████       
            ██████           
   1% House Edge
geebus
Sr. Member
****
Offline Offline

Activity: 258
Merit: 250



View Profile WWW
June 13, 2012, 08:06:36 AM
 #389

I would guess that maybe you have some problems with your 0.6+ wallet, and so exporting and re-importing the keys is probably the best thing to do anyway.

Then when I ran bitcoin-qt again, the transaction was no longer showing at all.  It's still on blockchain.info as an unconfirmed transaction, and I'm sure it will eventually confirm, at which point I will see it in my wallet again.

My issue is that these transactions do not exist in the blockchain and were generated during a split. The transactions that are showing on blockchain.info do not appear in my wallet... weird issue. I imagine that rebuilding a new wallet from the private keys should fix it though, since it re-verifies every transaction for every private key imported.

Feel like donating to me? BTC Address: 14eUVSgBSzLpHXGAfbN9BojXTWvTb91SHJ
dooglus
Legendary
*
Offline Offline

Activity: 2548
Merit: 1125



View Profile
June 13, 2012, 08:10:38 AM
 #390

My issue is that these transactions do not exist in the blockchain and were generated during a split. The transactions that are showing on blockchain.info do not appear in my wallet... weird issue. I imagine that rebuilding a new wallet from the private keys should fix it though, since it re-verifies every transaction for every private key imported.

I just realised - you're importing the keys and rescanning the whole blockchain for each one aren't you.  No wonder it's taking so long.

If you want to speed it up, and are comfortable building bitcoin-qt from source, comment out these two lines in src/rpcdump.cpp then rebuild:

Code:
        pwalletMain->ScanForWalletTransactions(pindexGenesisBlock, true);
        pwalletMain->ReacceptWalletTransactions();

Then you'll be able to import all your private keys very quickly, like less than a second each.  Then run a single 'bitcoin-qt -rescan' at the end and you're done.

There's no need to rescan the wallet separately for every key you import, but that's what bitcoin-qt does.

Just-Dice                 ██             
          ██████████         
      ██████████████████     
  ██████████████████████████ 
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
    ██████████████████████   
        ██████████████       
            ██████           
   Play or Invest                 ██             
          ██████████         
      ██████████████████     
  ██████████████████████████ 
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
    ██████████████████████   
        ██████████████       
            ██████           
   1% House Edge
Stephen Gornick
Legendary
*
Offline Offline

Activity: 2506
Merit: 1001


View Profile
June 13, 2012, 08:13:16 AM
 #391

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.

Unichange.me

            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █


Raoul Duke
aka psy
Legendary
*
Offline Offline

Activity: 1456
Merit: 1000



View Profile
June 13, 2012, 01:29:21 PM
 #392

Just to confirm what dooglus said. pywallet does indeed works with wallets from the 0.6.2 Satoshi client.
I tested it 2 days ago to delete all transactions from my wallet and do a rescan to take a doubt I was having and it indeed worked.

dlasher
Sr. Member
****
Offline Offline

Activity: 466
Merit: 250



View Profile WWW
June 13, 2012, 04:57:17 PM
 #393


bets ground to a halt again.. right around 10-11am EST... 

fireduck
Sr. Member
****
Offline Offline

Activity: 390
Merit: 251



View Profile
June 13, 2012, 05:20:09 PM
 #394


bets ground to a halt again.. right around 10-11am EST... 



Over 21,000 bets already today.  Everything seems to be flowing fine now except for about 600 unknowns which I am working on clearing up now.  They should be gone in the next 4 hours or so.

Bitrated user: fireduck.
dlasher
Sr. Member
****
Offline Offline

Activity: 466
Merit: 250



View Profile WWW
June 13, 2012, 05:48:08 PM
 #395

Over 21,000 bets already today.  Everything seems to be flowing fine now except for about 600 unknowns which I am working on clearing up now.  They should be gone in the next 4 hours or so.


Would be useful to have some sort of "average bet delay in seconds" near the top of the main page...
fireduck
Sr. Member
****
Offline Offline

Activity: 390
Merit: 251



View Profile
June 13, 2012, 05:54:06 PM
 #396

Would be useful to have some sort of "average bet delay in seconds" near the top of the main page...

Agreed.  I'll work on that. 

Bitrated user: fireduck.
ErebusBat
Hero Member
*****
Offline Offline

Activity: 560
Merit: 500

I am the one who knocks


View Profile
June 13, 2012, 07:30:38 PM
 #397

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.

Have you seen graphite?
http://graphite.wikidot.com/

This page has a REALLY good example of how to see if your deploys messed anything up:
http://codeascraft.etsy.com/2010/12/08/track-every-release/

░▒▓█ Coinroll.it - 1% House Edge Dice Game █▓▒░ • Coinroll Thread • *FREE* 100 BTC Raffle

Signup for CEX.io BitFury exchange and get GHS Instantly!  Don't wait for shipping, mine NOW!
dlasher
Sr. Member
****
Offline Offline

Activity: 466
Merit: 250



View Profile WWW
June 13, 2012, 10:36:27 PM
 #398


lots and lots of unconfirmed... something -stopped- about 5:30 EST.

Block had a lot of transactions in it, then... little:

http://www.blockchain.info/block-index/236637/000000000000066930aefb95e7ff55034ceabb569a7e5aca1257fa3920933f84



fireduck
Sr. Member
****
Offline Offline

Activity: 390
Merit: 251



View Profile
June 13, 2012, 10:39:09 PM
 #399


lots and lots of unconfirmed... something -stopped- about 5:30 EST.

Block had a lot of transactions in it, then... little:

http://www.blockchain.info/block-index/236637/000000000000066930aefb95e7ff55034ceabb569a7e5aca1257fa3920933f84


Right now we have about 4500 unconfirmed.  I have yet to figure out any coherent way of predicting when the miners will pick these up.


Bitrated user: fireduck.
titeuf_87
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
June 13, 2012, 10:55:34 PM
 #400

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  Smiley

15kfBM3TQ4PGzL7cKncU3su2pH7ZJmiLtr
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 [20] 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 ... 274 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!