|
After she made and lost 10 0.01 BTC bets:
> i found it tedious and not much fun, tbh
> not sure if that would have changed had i won though
> its too much work putting the numbers in over and over
> i mean, it saves the wallet to deposit into and u only have to type first number and it remembers
> but always a diff wallet to pay it
|
|
|
|
|
I asked for comments on the site:
> i could be able to put in a bunch of small ones at one time on the same page
> like have 5 boxes instead of 1
> and play em all at once
I realise there's only 1 pre-selected number, but thought I'd pass on the suggestion. She wants to make lots of small bets with a single payment instead of the repeating the multi-step betting process over and over.
|
|
|
|
She's thinking now that the reason it wasn't updating was because it was saying "double check your amounts" because the numbers were too high... She's made her first bet, 0.01 to win the max, with a 0.24% chance of winning. Not surprisingly she lost. She guessed 6942, and would like her free dime please, and is a newbie so can't post here. Should she post in the newbie forum, or is my word good enough? I think she plans to make the same bet 9 more times now...  |
|
|
|
I tried showing the site to a friend. Got this comment:
"so it doesnt change anything when i play with the numbers, that i can see"
She was editing the bet amount, but not tabbing or clicking out of the box. The percentage only updates when you leave the box. How about having it update on each keystroke (onkeyup) rather than waiting for me to leave the box?
It turns out the percentage chance isn't updating even if she does tab between boxes. I don't know why that would be - she'll not have javascript disabled. And another problem: she tried betting 0.01 to win the maximum, and got an error: > it says win amt must be between 0.05 and 3.9179 Chris: and was it? > I put 3.92 cuz thats what it said on the side So it's reporting the max bet as 3.92 when it's really 3.9179, and rejecting 3.92 when you submit the bet. |
|
|
|
|
I tried showing the site to a friend. Got this comment:
"so it doesnt change anything when i play with the numbers, that i can see"
She was editing the bet amount, but not tabbing or clicking out of the box. The percentage only updates when you leave the box. How about having it update on each keystroke (onkeyup) rather than waiting for me to leave the box?
|
|
|
|
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: 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. |
|
|
|
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: 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. |
|
|
|
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+. |
|
|
|
Make sure you refresh to get the latest javascript, but it should prevent duplicate submissions now.
Looks fine from the one trial I did. Good job! You know I'll let you know if I see the error again... Awesome... now I can sleep. I still wish I knew why your system wanted to send two requests, but at least we stopped it. I have Windows 7 on this laptop still I think - I could try it there. I also have a machine with the previous Ubuntu (11.10) on it. I can't think what it might be though - I tried 3 completely different browsers and got the same result from all 3. Can you think of anything I can run here that would help diagnose why it's sending duplicate requests? |
|
|
|
Make sure you refresh to get the latest javascript, but it should prevent duplicate submissions now.
Looks fine from the one trial I did. Good job! You know I'll let you know if I see the error again... |
|
|
|
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. |
|
|
|
|
It's odd that the "Too many outstanding games from your IP address. Please pay for a game or wait for one to time out" message also goes away when I refresh. Is it the 2nd POST that's getting that message, because it's trying to make a 2nd game?
I just got the "tampered" and "too many" messages, hit refresh and got a payment address, sent BTC to that address, and won. So it seems like both messages can be ignored.
|
|
|
|
unless his keyboard is stuttering and sending two enters. I can reproduce if I hit enter twice quickly. Double clicking could also trigger it. If that's the case, shame on you dooglus, never double click on the internet  . I'm clicking. Once. I just tried tabbing to the button and hitting the space bar instead of clicking it. I got the error again, but also the 'too many' message, even though I just paid & lost: An error has occurred:
Hash or timestamp has been tampered with.
Too many outstanding games from your IP address. Please pay for a game or wait for one to time out
|
|
|
|
unless his keyboard is stuttering and sending two enters. I can reproduce if I hit enter twice quickly. Double clicking could also trigger it. If that's the case, shame on you dooglus, never double click on the internet . I'm clicking. Once. |
|
|
|
Can you reproduce the "tampered" error freemoney?
I got it like 3 times in a row earlier (emailed you about it) while reusing an address and then didn't get it when I tried a new address. Now I can't make it happen. I use the same address every time, and currently see the error almost every time. I'd guess 6 out of the last 7 times I tried, I saw it. For the record, I saw the error in chromium without squid, and in firefox without squid. I'm not sure what other browsers I have. I don't want to install all the Qt stuff I'll need to get Konqueror working. Maybe 'epiphany' (the basic GNOME browser) will work - I'll try it. [time passes] The 'tampered' error showed up in epiphany too. I notice that in addition to the two 'create game' POSTS, there's also a 'null' one: POST /create_game.php HTTP/1.1
POST /null.php HTTP/1.1
POST /create_game.php HTTP/1.1
Is that something you know about and expect to see? |
|
|
|
so I'll post this, restart chromium, test, and report back
The bug still happens without squid. The packets now contain gzipped responses, but I'll email you them anyway. I'll also try in firefox. |
|
|
|
Looking at your captured packets, I see no problems with 1-3, but it appears 4 and 5 are mixed up and missing some data.
4a should be a match for 5b, although 5b has two responses and 4a is only one request.
4b is the appropriate response for 5a.
That said, the request in 4a should never have happened, it is identical to 3a. A double request would indeed cause the "tampered" error, but I'm stumped as to why it would have occurred. It also explains why refreshing it fixes it, since as you can see in 3b, the game was successfully submitted and refreshing it just reloads it from the database. I'm unable to reproduce the extra request here. I'm also using Chromium, as you seem to be. Do you also get the same behavior in other browsers? I don't know much about squid, but is it possible it is duplicating the request?
Can you reproduce the "tampered" error freemoney?
I'll leave the site be for now, but I'm going to bed soon. If either of you find more info let me know, otherwise I will put a fix in place in the morning that will not replace the text after the second request. That way only the first submission's response will be displayed, and you'll see the regular text instead of the error. Not ideal, but if I can't reproduce the extra request, it it's hard to eliminate it.
Thank you very much dooglus for providing all this debugging info. It was very helpful.
I renamed the files manually and may have messed them up. I thought I got it right, but maybe not. I'll try connecting directly to the internet, rather than going via squid and see if that fixes the problem... (it seems chromium doesn't have any way of changing proxy settings except from the command line, so I'll post this, restart chromium, test, and report back). It's "18.0.1025.151 (Developer Build 130497 Linux) Ubuntu 12.04" by the way. |
|
|
|
The difference between the win amount and the bet amount is reserved out of the available balance until a payment is confirmed or the game times out, without regard to whether or not the game is a winner.
Good to know! |
|
|
|
|
I've seen the 'tampered' message without clicking anywhere near the hash. So that was a red herring.
|
|
|
|
I changed the games to not expire for 8 hours, I was only thinking about delayed payments like from Seals or similar. Forgot that people could get locked longer that way. Change to whatever you like while testing notme.
You seem to only allow me 5 or so "games" in progress at a time. Is that because you've committed the coins to me at the time I click "place bet" and don't want to over-commit? Do you commit coins even if it's a losing bet for me? Can I use this to tell in advance whether it's a losing bet, and then decide whether to play? |
|
|
|
|
Show Posts
