Author

Topic: MyriadCoins.com - Make the bet you want (Read 7994 times)

legendary
Activity: 1176
Merit: 1005
October 03, 2012, 03:56:49 AM
#98
I think that would be a more user-friendly design (no need to access the webpage at all, except to nervously check bet results).

This depends on what kind of user you are.  If you already prefer the user interface of satoshidice, you're probably already using that.  It's a good system when you're using a standard Bitcoin client.

However, one of the advantages to MC over SD, particularly for people who use other online gambling sites, is that you can easily pay out to a non-wallet address, like a Seals deposit address, while making the bet from a site that does instant cashouts (like Dragon's Tale).  This bypasses having to mess with a wallet at all, and other than the single confirm, the bet is nearly instant.

This system wouldn't really work with many of these sites, as they generally limit the number of digits allowed after the decimal point.

I could see adding a system like this to MC, but they would, again, require using a Bitcoin client.  I generally only keep Bitcoin in an offline wallet when converting it into "real" money.
legendary
Activity: 2940
Merit: 1333
September 25, 2012, 12:11:03 PM
#97
This seems to be a clone of Satoshi's dice with user defined odds as the point of differentiation.

1) Could you make one consistent address to send wagers to. (like Satoshi's Dice)
2) Could you allow the user to specify the odds of winning using the insignifcant digits of the amount bet (e.g.) say I'm wagering 1 BTC and I want to earn 64.0 BTC if I win. I could send 1.00000640 bitcoins to your single address.
3) You could specify a maximum possible winning payout to avoid jackpot's that break the bank. It would be quite transparent (e.g. no payouts greater than 100.0 BTC).
If I send you, 1.00010000 bitcoins, then you return the 1 bitcoin because the bet payout is too big for you to cover.

I think that would be a more user-friendly design (no need to access the webpage at all, except to nervously check bet results).

It would also be quite easy to verify your payment track record in the blockchain.

A problem with this is that although you can specify how much you risk and how much you want to win, both using the amount you send, you can't tell what the actual odds are going to be without visiting the website.  The odds the site offers you depends not only on the ratio of risk to payout, but also on the percentage of the house wallet that you're trying to win.  There would be no way of later checking what the odds should have been for your bet.  i.e. you won't know how close your chosen number had to be to the randomly picked number for you to have won.

If implemented at all, the scheme you suggest should be in addition to the current system, rather than a replacement of it.
legendary
Activity: 1050
Merit: 1003
September 25, 2012, 03:08:21 AM
#96
This seems to be a clone of Satoshi's dice with user defined odds as the point of differentiation.

1) Could you make one consistent address to send wagers to. (like Satoshi's Dice)
2) Could you allow the user to specify the odds of winning using the insignifcant digits of the amount bet (e.g.) say I'm wagering 1 BTC and I want to earn 64.0 BTC if I win. I could send 1.00000640 bitcoins to your single address.
3) You could specify a maximum possible winning payout to avoid jackpot's that break the bank. It would be quite transparent (e.g. no payouts greater than 100.0 BTC).
If I send you, 1.00010000 bitcoins, then you return the 1 bitcoin because the bet payout is too big for you to cover.

I think that would be a more user-friendly design (no need to access the webpage at all, except to nervously check bet results).

It would also be quite easy to verify your payment track record in the blockchain.
legendary
Activity: 1246
Merit: 1016
Strength in numbers
August 24, 2012, 03:54:34 AM
#95
Myriad has QR codes for the payment addresses now.
legendary
Activity: 1246
Merit: 1016
Strength in numbers
Myriad has been getting Martingaled!

With the current limits and starting at .01 there is room for 10 doublings.

For the small wagers the fee is just 1%.

I am willing to temporarily raise the limits too, I just don't want to leave too much exposed permanently since the site is only lightly tested.
legendary
Activity: 1904
Merit: 1002
That feature shouldn't submit forms.  I actually found the trigger later and fixed it, but thanks anyway.  I should have reported it fixed earlier.

Yeah, I noticed later that I had the feature turned off anyway, and the pre-fetching I was seeing was something facebook explicitly does using javascript.

What was the trigger that was causing the double-submit on some browsers but not on others?

The code that reenabled the submit was adding an onclick since that's how it was originally submitted.  When I changed the submission so that autofill worked, I forgot to update that code, so the onclick was added.  Different browsers handle simultaneous ajax submissions differently.
legendary
Activity: 2940
Merit: 1333
That feature shouldn't submit forms.  I actually found the trigger later and fixed it, but thanks anyway.  I should have reported it fixed earlier.

Yeah, I noticed later that I had the feature turned off anyway, and the pre-fetching I was seeing was something facebook explicitly does using javascript.

What was the trigger that was causing the double-submit on some browsers but not on others?
legendary
Activity: 1904
Merit: 1002
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!  Smiley

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 just noticed that my browser is 'pre-loading' the page it thinks I am going to open next.

Apparently chromium has a setting "Predict network actions to improve page load performance".

I suspect that this feature is what was causing the double-submit.

http://support.google.com/chrome/bin/answer.py?hl=en&answer=1385029

That feature shouldn't submit forms.  I actually found the trigger later and fixed it, but thanks anyway.  I should have reported it fixed earlier.
legendary
Activity: 1176
Merit: 1005
I found this site because they have a promo on http://sealswithclubs.eu where I often hang out. 

All I have to say is great!  The interface is much more user friendly than SatoshiDice and the bet-sizing makes it a perfect way to bet that amount of BTC you have sitting around that is of no use to you, that you don't care if you lose, to gamble it to try to get that amount you want for a tournament buyin or other purpose.

Also, because you specify the payout address at the outset, I can place bets directly from my other gambool places, like Dragon's Tale, and have it pay out immediately to my deposit address.  I assume this was on purpose, but if not, you just captured another niche market.

The house edge is also nice and tiny.

Congratulations!
legendary
Activity: 2940
Merit: 1333
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!  Smiley

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 just noticed that my browser is 'pre-loading' the page it thinks I am going to open next.

Apparently chromium has a setting "Predict network actions to improve page load performance".

I suspect that this feature is what was causing the double-submit.

http://support.google.com/chrome/bin/answer.py?hl=en&answer=1385029
legendary
Activity: 1246
Merit: 1016
Strength in numbers
Suggestion (from the competition, but whatever): I often use my phone to pay things and scan QR codes from my computer.  To do that I end up having to take your address and pasting it into blockchain.info to get a QR code.

Also, there is a URI standard for QR codes that can specify the amount as well:
https://en.bitcoin.it/wiki/URI_Scheme

Example:
bitcoin:1NS17iag9jJgTHD1VXjvLCEnZuQ3rJED9L?amount=20.3X8

Just tested and works with Blockchain android app.  You can use this to specify the amount as well which makes it easier for users like me.  I just scan and hit send.


That is a good idea, thanks.
sr. member
Activity: 392
Merit: 251
Suggestion (from the competition, but whatever): I often use my phone to pay things and scan QR codes from my computer.  To do that I end up having to take your address and pasting it into blockchain.info to get a QR code.

Also, there is a URI standard for QR codes that can specify the amount as well:
https://en.bitcoin.it/wiki/URI_Scheme

Example:
bitcoin:1NS17iag9jJgTHD1VXjvLCEnZuQ3rJED9L?amount=20.3X8

Just tested and works with Blockchain android app.  You can use this to specify the amount as well which makes it easier for users like me.  I just scan and hit send.
legendary
Activity: 1246
Merit: 1016
Strength in numbers
I just raised limits by about 5x. You can bet .01BTC to win 19.70BTC right now.
legendary
Activity: 2940
Merit: 1333
Ha sorry, it didn't occur to me to pay her directly for some reason.

I think that's a good method for doing multiple bets.

I can't believe they are really down 700, that's crazy. I wonder if it was bad luck back when they had a higher max or if there is some problem.

Since all their bets go via a few publicly known bitcoin addresses, it's possible to work out how well they're doing simply by looking at the blockchain.

etotheipi wrote a script to do exactly that, and periodically publishes its output in the first post of this thread:
  https://bitcointalksearch.org/topic/satoshi-dice-statistical-analysis-80312

As of June 11th they were 695.26123453 BTC down, including over 100 BTC paid in transaction fees.

Some have speculated that it's possible to rob them by waiting until you mine a block which includes a payment to yourself, then send a transaction to SatoshiDICE  betting that same output, wait and see if you win or lose.  If you lose, quickly publish the block you mined, and if you win, don't.  That way your bet will be cancelled if you lose.  But you lose the block reward if you don't publish your block, so your winnings had better be more than 50 BTC or it's not worth doing.

I don't know if that's an attack that's actually feasible given how slowly SatoshiDICE has been running recently, or if it's ever been used.  I know at times they've been quite a lot up, so maybe it's just a high-variance game that they're temporarily losing.
legendary
Activity: 1246
Merit: 1016
Strength in numbers
Ha sorry, it didn't occur to me to pay her directly for some reason.

I think that's a good method for doing multiple bets.

I can't believe they are really down 700, that's crazy. I wonder if it was bad luck back when they had a higher max or if there is some problem.
legendary
Activity: 2940
Merit: 1333
Your word is good for a dozen dimes. Distribute or keep as you like. Thanks for sharing the game with people and keep the feedback coming.

That took me a while to work out.  She hadn't received the dime, and the address I was playing with hadn't either.  They I remembered I have a donation address in my signature...  Thanks a lot!  Smiley

Keeping the address active for the same wager briefly crossed my mind, but since we reserve funds to be sure we can pay them I don't know how that would work. How do you reckon SD does it? Unlimited loss risk? And go manual when the hot wallet runs out?

edit: ohh, what about a "play the same bet again" button to make it reserve the funds one more time?

The last time I looked, SatoshiDICE was 700 BTC down overall since they started operations.  Their maximum bets get set to a maximum of 5 BTC across the board recently, even the ones which you're pretty sure to win and which pay very little.  I don't know if that's just a feature of how martingale betting looks to the house - a series of small losses with the occasional monster win.  But if max bet is now 5 BTC, there won't be any monster wins for the house, so I don't know.

How about on the first page, having a '+' button which adds 3 box boxes, for "bet", "win" and "guess" each time it's clicked, up to a maximum of 10 bets or so.  Each time it's clicked the hash changes as a new predetermined number is added to the secret.  The paranoid user can keep a list of all the hashes and see that sha256(junk date nnn1) = first hash, sha256(junk date nnn1 nnn2) = 2nd hash, etc. and the less paranoid but still careful user just needs to check that sha256(junk date nnn1 ... nnnN) = final hash.  You only ever store a database entry for the final hash, along with the "junk date nnn1 ... nnnN" secret.  The user has to pay for all the bets at once, to a single address, and gets the results all at once on a single page.  You count this big bet as if it were N single bets, so if you usually allow a user to have 10 pending bets, you only allow them one of these 10 bet combinations.
legendary
Activity: 1246
Merit: 1016
Strength in numbers
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

Keeping the address active for the same wager briefly crossed my mind, but since we reserve funds to be sure we can pay them I don't know how that would work. How do you reckon SD does it? Unlimited loss risk? And go manual when the hot wallet runs out?

edit: ohh, what about a "play the same bet again" button to make it reserve the funds one more time?
legendary
Activity: 1246
Merit: 1016
Strength in numbers
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...  Smiley

Your word is good for a dozen dimes. Distribute or keep as you like. Thanks for sharing the game with people and keep the feedback coming.
legendary
Activity: 2940
Merit: 1333
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
legendary
Activity: 2940
Merit: 1333
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.
legendary
Activity: 2940
Merit: 1333
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...  Smiley
legendary
Activity: 2940
Merit: 1333
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.
legendary
Activity: 2940
Merit: 1333
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?
legendary
Activity: 2940
Merit: 1333
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!  Smiley

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?
legendary
Activity: 1904
Merit: 1002
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!  Smiley

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.
legendary
Activity: 2940
Merit: 1333
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!  Smiley

You know I'll let you know if I see the error again...
legendary
Activity: 1904
Merit: 1002
Make sure you refresh to get the latest javascript, but it should prevent duplicate submissions now.
legendary
Activity: 1904
Merit: 1002
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 Tongue.

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:

Code:
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

Cleared you IP records again.  Since the first request creates the game, the second request sees that game as well.  Anyway, I'm off to javascript land, be back soon.
legendary
Activity: 2940
Merit: 1333
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.
legendary
Activity: 1904
Merit: 1002
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 Tongue.

I'm clicking.  Once.

Thanks... I only bring up the double clicking because I've seen it too many times.  Facepalm.

Heck, I'm going to go ahead and patch up the javascript to prevent the extra submission.  I'll let you now when it is uploaded.
legendary
Activity: 2940
Merit: 1333
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 Tongue.

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:

Code:
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
legendary
Activity: 1904
Merit: 1002

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:

Code:
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?

Yes, the null.php is fine.  The actual form is hooked up to load that in a hidden iframe, whereas the actual submission is handled by javascript (it needs to clean up a few things).  I had to make it actually submit the form the old fashion way to get it to remember the autocomplete values.  It seems browsers only save them on a regular form submission, not an ajax submission, so null.php just ignores it's parameters and prints "Okay".  Not the most efficient way to do things, but sometimes the standards box you in.
legendary
Activity: 2940
Merit: 1333
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 Tongue.

I'm clicking.  Once.
legendary
Activity: 1904
Merit: 1002

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.

Right, I fixed a bug earlier that was causing what you saw.  I have no clue what could be causing the issue for dooglus 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 Tongue.  I'll leave it alone for now in case you guys want to play with it more, but i have a patch for the javascript that will ignore the second response that I'll upload in the morning.  It needs put in place anyway since double clicking and double enters will cause the behavior.  In fact, I should be able to rework it a little to prevent the second request from being made, and still ignoring extra responses in case a duplicate request somehow gets made.

As for a workaround if you guys or anyone else sees this tonight and wants to play, if you hit refresh the game will be perfectly fine to play.
legendary
Activity: 2940
Merit: 1333

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:

Code:
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?
legendary
Activity: 1246
Merit: 1016
Strength in numbers

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.
legendary
Activity: 2940
Merit: 1333
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.
legendary
Activity: 1904
Merit: 1002
Mine is a little newer, but shouldn't be majorly different:
18.0.1025.168 (Developer Build 134367 Linux) Built on Ubuntu 11.10, running on LinuxMint 12

Thanks again for all the effort, I'll probably hang around long enough to see how your new experiment turns out before calling it a night.
legendary
Activity: 2940
Merit: 1333
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.
legendary
Activity: 1904
Merit: 1002
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.
legendary
Activity: 2940
Merit: 1333
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!
legendary
Activity: 1904
Merit: 1002
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?

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.
legendary
Activity: 2940
Merit: 1333
I've seen the 'tampered' message without clicking anywhere near the hash.  So that was a red herring.
legendary
Activity: 2940
Merit: 1333
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?
legendary
Activity: 1246
Merit: 1016
Strength in numbers
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.
legendary
Activity: 2940
Merit: 1333
If you're okay with revealing your email, send it to [email protected]

Sent.  An email, that is.
legendary
Activity: 1904
Merit: 1002
OK, it took me a while to figure out how to stop my browser saying it accepted gzipped pages from your server, but now I can capture the packets in uncompressed form.

The problem now is I have too many outstanding games, and so can't reproduce the error, I think.

Can you cancel them for me?  All the ones to my deposit address will be mine...

Can't cancel them, but I deleted the ip records, so you should be good to go.  The available balance (and thus the bet/win limits) will be a little lower until the other games time out, but that shouldn't matter for your testing.
legendary
Activity: 2940
Merit: 1333
OK, it took me a while to figure out how to stop my browser saying it accepted gzipped pages from your server, but now I can capture the packets in uncompressed form.

The problem now is I have too many outstanding games, and so can't reproduce the error, I think.

Can you cancel them for me?  All the ones to my deposit address will be mine...
legendary
Activity: 1904
Merit: 1002
I followed you steps exactly other than waiting 5 minutes and couldn't reproduce.  I've reloaded the page and I will wait before trying again.  If it's not too much trouble the HTTP packets might be helpful.  It might be better to email it than to flood this thread.  If you're okay with revealing your email, send it to [email protected], otherwise a PM will do.
legendary
Activity: 2940
Merit: 1333
I think every time I've double-clicked the hash, I've seen the error, and every time I haven't, I haven't.  Seems odd though.

I just saw the error again without clicking anywhere near the hash.
legendary
Activity: 2940
Merit: 1333
I just reproduced the error again, and took screenshots as I did.

I started with a 5-minute old hash:



Then I clicked the game logo to generate a new hash, filled in the details, double-clicked the hash, and hit control-c.  All ready to click the 'place ...' button:



Then I clicked the 'place ...' button I saw the error message:



Notice that the hash is still selected in that final image.  I only selected it once, and it stayed selected.

I think every time I've double-clicked the hash, I've seen the error, and every time I haven't, I haven't.  Seems odd though.

This all happened in the space of a minute or so.

Would it help if I did it again and grabbed the HTTP packets that hit the network for you?
legendary
Activity: 2940
Merit: 1333
We could possibly show the hashes for games from the user's IP, but those might not necessarily be their games.  We have no way of identifying individual users, other than possibly when they use the same payout address.

I see.  I assumed you would be using a session cookie or something to track my activity on the site.

I tried control-f5 but it doesn't seem to do anything at all.

I monitored the squid logs when I hit control-r, f5, etc.  Here's what happened - it seems to be the same for each, except for control-f5 which as I say did nothing:

I notice that control-shift-r gives different messages, so maybe that's the equivalent of what you asked for.

Code:
[control-r]
1339553565.370    968 127.0.0.1 TCP_MISS/200 2830 GET http://myriadcoins.com/game.php - DIRECT/96.127.133.59 text/html
1339553566.442   1059 127.0.0.1 TCP_REFRESH_UNMODIFIED/304 291 GET http://myriadcoins.com/resources/stylesheet.css - DIRECT/96.127.133.59 -
1339553566.772   1388 127.0.0.1 TCP_REFRESH_UNMODIFIED/304 293 GET http://myriadcoins.com/resources/jquery.min.js - DIRECT/96.127.133.59 -
1339553566.772   1388 127.0.0.1 TCP_REFRESH_UNMODIFIED/304 292 GET http://myriadcoins.com/resources/modernizr-2.5.3.min.js - DIRECT/96.127.133.59 -
1339553566.944   1561 127.0.0.1 TCP_MISS/200 6448 GET http://myriadcoins.com/js_parser.php? - DIRECT/96.127.133.59 text/javascript
1339553567.163    207 127.0.0.1 TCP_REFRESH_UNMODIFIED/304 269 GET http://myriadcoins.com/resources/myriadcoins-logo.png - DIRECT/96.127.133.59 -
1339553567.343    160 127.0.0.1 TCP_MISS/404 581 GET http://myriadcoins.com/favicon.png - DIRECT/96.127.133.59 text/html

[f5]
1339553586.905   2601 127.0.0.1 TCP_MISS/200 2830 GET http://myriadcoins.com/game.php - DIRECT/96.127.133.59 text/html
1339553587.102    184 127.0.0.1 TCP_REFRESH_UNMODIFIED/304 291 GET http://myriadcoins.com/resources/stylesheet.css - DIRECT/96.127.133.59 -
1339553587.262    344 127.0.0.1 TCP_REFRESH_UNMODIFIED/304 292 GET http://myriadcoins.com/resources/modernizr-2.5.3.min.js - DIRECT/96.127.133.59 -
1339553587.344    426 127.0.0.1 TCP_REFRESH_UNMODIFIED/304 293 GET http://myriadcoins.com/resources/jquery.min.js - DIRECT/96.127.133.59 -
1339553587.464    545 127.0.0.1 TCP_MISS/200 6448 GET http://myriadcoins.com/js_parser.php? - DIRECT/96.127.133.59 text/javascript
1339553587.633    156 127.0.0.1 TCP_REFRESH_UNMODIFIED/304 269 GET http://myriadcoins.com/resources/myriadcoins-logo.png - DIRECT/96.127.133.59 -
1339553587.842    164 127.0.0.1 TCP_MISS/404 581 GET http://myriadcoins.com/favicon.png - DIRECT/96.127.133.59 text/html

[control-f5]

[control-shift-r]
1339553610.015    350 127.0.0.1 TCP_MISS/200 2831 GET http://myriadcoins.com/game.php - DIRECT/96.127.133.59 text/html
1339553610.182    150 127.0.0.1 TCP_CLIENT_REFRESH_MISS/200 805 GET http://myriadcoins.com/resources/stylesheet.css - DIRECT/96.127.133.59 text/css
1339553610.763    730 127.0.0.1 TCP_MISS/200 6448 GET http://myriadcoins.com/js_parser.php? - DIRECT/96.127.133.59 text/javascript
1339553610.784    751 127.0.0.1 TCP_CLIENT_REFRESH_MISS/200 6506 GET http://myriadcoins.com/resources/modernizr-2.5.3.min.js - DIRECT/96.127.133.59 application/javascript
1339553611.142   1110 127.0.0.1 TCP_CLIENT_REFRESH_MISS/200 32482 GET http://myriadcoins.com/resources/jquery.min.js - DIRECT/96.127.133.59 application/javascript
1339553611.516    319 127.0.0.1 TCP_CLIENT_REFRESH_MISS/200 14706 GET http://myriadcoins.com/resources/myriadcoins-logo.png - DIRECT/96.127.133.59 image/png
1339553611.763    234 127.0.0.1 TCP_MISS/404 581 GET http://myriadcoins.com/favicon.png - DIRECT/96.127.133.59 text/html
legendary
Activity: 1904
Merit: 1002
Before the game is recorded in the DB, it the hash is recomputed to make sure everything matches up.  If the recomputed hash doesn't match the displayed hash, you get the tampering error.  I'm having a hard time imagining how what you've described happened.  If you open another tab with a new game, it can mess up the site's guess/salt that is stored in the server-side session, but then refreshing wouldn't have fixed it.  Was this a fresh game, or had it sat around for a while?  Was it submitted previously and had a different error?  Was there anything else you did that might provide a hint?

See my post immediately before yours.  I had the error happen 3 times in a row, on 3 different hashes.  The first time may have been over an hour old, I'm not sure.  But the 2nd and 3rd were newly generated.

I ended up sending BTC to the address it told me, and it worked fine.  But that may have been my 4th attempt, which didn't show the error.

Is it possible that my double-clicking the hash at the bottom of the game page then control-c'ing to copy it is causing something bad?

Quote
Here's a list of unpaid hashes with the same payout address as the one hash you posted:

521b684fc9e8f31020c35ed15d25e07fe7f0c2881970769b616acab41fdacb6f
135f4c3a60b4d8c8fe5215e48c517cac5652cb47c9022b8e67b058d79761c191
e94182f8f76f6ae7b8351efe45580eb40b9d59c8b6b7efea442aa784e43d1222

Yes, it is safe to pay for the tampered ones.  The games look to be fine on the server side.  Still, we need to figure out why this is happening.

It might be good to let the user see their list of unpaid games for themselves, and possible let them cancel them.  Otherwise they have to wait 2 (?) hours for them to expire if they create too many when playing around.  Unless there's a good reason not to, of course.

Quote
Can you try a Ctl-F5?  We made some changes to the javascript and you might be caching an old copy.

Will do.

We could possibly show the hashes for games from the user's IP, but those might not necessarily be their games.  We have no way of identifying individual users, other than possibly when they use the same payout address.
legendary
Activity: 2940
Merit: 1333
Before the game is recorded in the DB, it the hash is recomputed to make sure everything matches up.  If the recomputed hash doesn't match the displayed hash, you get the tampering error.  I'm having a hard time imagining how what you've described happened.  If you open another tab with a new game, it can mess up the site's guess/salt that is stored in the server-side session, but then refreshing wouldn't have fixed it.  Was this a fresh game, or had it sat around for a while?  Was it submitted previously and had a different error?  Was there anything else you did that might provide a hint?

See my post immediately before yours.  I had the error happen 3 times in a row, on 3 different hashes.  The first time may have been over an hour old, I'm not sure.  But the 2nd and 3rd were newly generated.

I ended up sending BTC to the address it told me, and it worked fine.  But that may have been my 4th attempt, which didn't show the error.

Is it possible that my double-clicking the hash at the bottom of the game page then control-c'ing to copy it is causing something bad?

Quote
Here's a list of unpaid hashes with the same payout address as the one hash you posted:

521b684fc9e8f31020c35ed15d25e07fe7f0c2881970769b616acab41fdacb6f
135f4c3a60b4d8c8fe5215e48c517cac5652cb47c9022b8e67b058d79761c191
e94182f8f76f6ae7b8351efe45580eb40b9d59c8b6b7efea442aa784e43d1222

Yes, it is safe to pay for the tampered ones.  The games look to be fine on the server side.  Still, we need to figure out why this is happening.

It might be good to let the user see their list of unpaid games for themselves, and possible let them cancel them.  Otherwise they have to wait 2 (?) hours for them to expire if they create too many when playing around.  Unless there's a good reason not to, of course.

Quote
Can you try a Ctl-F5?  We made some changes to the javascript and you might be caching an old copy.
[/quote[

Will do.
legendary
Activity: 1904
Merit: 1002
Can you try a Ctl-F5?  We made some changes to the javascript and you might be caching an old copy.
legendary
Activity: 1904
Merit: 1002
No wanting to risk it, I clicked the banner to get a new hash, put my deposit address, changed the bets to 0.10 and 0.20, input my guess, copy/pasted the hash into a text editor and hit 'place your wager'.  Again it told me something had been tampered with.

I tried again, and again got the 'tampered with' error message.

I tried a 4th time, not copy/pasting the hash, and that time it worked.

Then when I tried a 5th time, trying to find out if I could narrow down exactly what caused the problem, it told me it was sick of me and that I should go away.  Or something.

("Too many outstanding games from your IP address. Please pay for a game or wait for one to time out")

Can I find a list of outstanding games, so I can pay for one?  Is it safe to pay for the "tampered with" ones?

Here's a list of unpaid hashes with the same payout address as the one hash you posted:

521b684fc9e8f31020c35ed15d25e07fe7f0c2881970769b616acab41fdacb6f
135f4c3a60b4d8c8fe5215e48c517cac5652cb47c9022b8e67b058d79761c191
e94182f8f76f6ae7b8351efe45580eb40b9d59c8b6b7efea442aa784e43d1222

Yes, it is safe to pay for the tampered ones.  The games look to be fine on the server side.  Still, we need to figure out why this is happening.
legendary
Activity: 1904
Merit: 1002
Before the game is recorded in the DB, it the hash is recomputed to make sure everything matches up.  If the recomputed hash doesn't match the displayed hash, you get the tampering error.  I'm having a hard time imagining how what you've described happened.  If you open another tab with a new game, it can mess up the site's guess/salt that is stored in the server-side session, but then refreshing wouldn't have fixed it.  Was this a fresh game, or had it sat around for a while?  Was it submitted previously and had a different error?  Was there anything else you did that might provide a hint?
legendary
Activity: 2940
Merit: 1333
Not wanting to risk it, I clicked the banner to get a new hash, put my deposit address, changed the bets to 0.10 and 0.20, input my guess, copy/pasted the hash into a text editor and hit 'place your wager'.  Again it told me something had been tampered with.

I tried again, and again got the 'tampered with' error message.

I tried a 4th time, not copy/pasting the hash, and that time it worked.

Then when I tried a 5th time, trying to find out if I could narrow down exactly what caused the problem, it told me it was sick of me and that I should go away.  Or something.

("Too many outstanding games from your IP address. Please pay for a game or wait for one to time out")

Can I find a list of outstanding games, so I can pay for one?  Is it safe to pay for the "tampered with" ones?
legendary
Activity: 2940
Merit: 1333
I just got an error message when I hit the 'place your wager' button:



I hit the refresh button in the browser, and it appeared to fix itself:



What does that 'tampered with' error message mean?  And is it safe to proceed with the bet after refreshing the page?
legendary
Activity: 2940
Merit: 1333
The balance is actually about 20BTC right now, with bets that win 20% being the max, but like you say the 4BTC is all that matters for brute forcing. If you ever lose a bet you'll be able to bet at least a little bit more the next time, unless someone has reserved some of the balance in between.

But, yeah, I just changed it to an hour. Should be good enough.

Great.  2 minutes was just too short, and I found myself exceeding the 15 minutes sometimes too, if I got distracted writing a forum post part way through betting.

An hour should be good though.  And nobody would mind a couple extra base64 characters in their secret either, just to be on the safe side.
legendary
Activity: 1246
Merit: 1016
Strength in numbers
Yes, smart. That's the way.

I was looking at the feasibility of brute-forcing your hash last night.

You use a 10 character base64 'junk', so even if I can predict the exact time, and guess the right preselected 0-9999 number, I still have to run an expected (64^10)/2 = half a million million million hashes to see if I'm right.

The entire bitcoin network currently hashes at 12 Thash/s.  So if I could convince them all to help me win your 4 BTC wallet balance, it would take us about 13 hours to brute force one of your hashes (given that I already guessed the time and preselected number correctly).

So I think it's pretty safe to increase the time the user has to make his guess a little.  Smiley

The bets will get bigger!

The balance is actually about 20BTC right now, with bets that win 20% being the max, but like you say the 4BTC is all that matters for brute forcing. If you ever lose a bet you'll be able to bet at least a little bit more the next time, unless someone has reserved some of the balance in between.

But, yeah, I just changed it to an hour. Should be good enough.
legendary
Activity: 2940
Merit: 1333
Yes, smart. That's the way.

I was looking at the feasibility of brute-forcing your hash last night.

You use a 10 character base64 'junk', so even if I can predict the exact time, and guess the right preselected 0-9999 number, I still have to run an expected (64^10)/2 = half a million million million hashes to see if I'm right.

The entire bitcoin network currently hashes at 12 Thash/s.  So if I could convince them all to help me win your 4 BTC wallet balance, it would take us about 13 hours to brute force one of your hashes (given that I already guessed the time and preselected number correctly).

So I think it's pretty safe to increase the time the user has to make his guess a little.  Smiley
legendary
Activity: 1246
Merit: 1016
Strength in numbers
I don't intend other wagers to be showing, I'll look into hashing the id. Simple hashing won't be enough, maybe the hash of the payment address or something. And if you visit a non existent id's page it should just take you to a new game.

Ah, I meant the hash that you already show.  The hash of the secret.  Or maybe a prefix of it if you want to keep the URL reasonably short.

So instead of visiting ?id=34, I visit ?hash=2490b823498e


Yes, smart. That's the way.
legendary
Activity: 2940
Merit: 1333
I don't intend other wagers to be showing, I'll look into hashing the id. Simple hashing won't be enough, maybe the hash of the payment address or something. And if you visit a non existent id's page it should just take you to a new game.

Ah, I meant the hash that you already show.  The hash of the secret.  Or maybe a prefix of it if you want to keep the URL reasonably short.

So instead of visiting ?id=34, I visit ?hash=2490b823498e

I changed "After you pay, click here to see if you won" to "Click here to refresh the status of this game." because that link is still useful after the result shows, it will tell you you've been paid eventually. Seems good?

Yup.  Nice work.  Smiley
legendary
Activity: 1246
Merit: 1016
Strength in numbers
legendary
Activity: 1246
Merit: 1016
Strength in numbers
How about an option to not have to specify an address for winnings, but instead have me check a box to agree that you'll return winnings to one of the addresses I pay from?

Right now no bitcoin magic is happening so that would be for version 2.0.

But even them I'm hesitant, I'd need that WARNING showing prominently and still people will mess up. The "Send back to yourself market" is pretty well served too.
legendary
Activity: 1246
Merit: 1016
Strength in numbers
Yes dooglus, I love it, don't stop.

Changed 'confirmations' to 'confirmation'. I dropped the payment address from the after game messages. Logo links now.

I don't intend other wagers to be showing, I'll look into hashing the id. Simple hashing won't be enough, maybe the hash of the payment address or something. And if you visit a non existent id's page it should just take you to a new game.

I changed "After you pay, click here to see if you won" to "Click here to refresh the status of this game." because that link is still useful after the result shows, it will tell you you've been paid eventually. Seems good?
legendary
Activity: 2940
Merit: 1333
I hope you're OK with all the criticism.  I like the game and the site, and complain only in the hope of helping you make it better.

That said:

Quote
Payment will be sent to [address] after 1 confirmations.

Confirmation should be singular.

Quote
You have a 49.50% chance of winning. In order to win, your guess must be within 2475 of our chosen number. Numbers do wrap around.

I'd like to see my guess in that line each time its shown.  The page which I refresh while waiting for the result doesn't show my guess at all until the result is known.  I'd like to see a range "our selection will need to be over 8012 or under 4120 for you to win" or some such.

Is it intentional that I can look through other people's bets?  http://myriadcoins.com/game.php?id=29 isn't mine.  Someone bet 0.40 to win 0.43, and lost, despite having a 92% chance of winning.  When they win, I see their wallet address too (like in http://myriadcoins.com/game.php?id=27).  Instead of a sequence number, you could use ?id= - then I'd only be able to look at bets I made myself.

If I pick a bad id number, I see NaN: http://myriadcoins.com/game.php?id=27122343 gives:

Quote
You have a NaN% chance of winning. In order to win, your guess must be within NaN of our chosen number

Quote
Thank you for sending 0.01BTC to 1FxeR2E8pBD2RdqCscjxLWJyhjZrSjigaB!

Would anyone ever care to see the deposit address again?  It's a throwaway address.  Maybe it's useful for matching up which bets correspond with which wallet entries, I don't know.

I'd like to be able to click on the logo at the top of any page to return to the front page.  Currently it doesn't do anything.
legendary
Activity: 2940
Merit: 1333
How about an option to not have to specify an address for winnings, but instead have me check a box to agree that you'll return winnings to one of the addresses I pay from?
legendary
Activity: 2940
Merit: 1333
Using a copy of the input element from your form also remembers my input.  Perhaps something in one of the javascript libraries you're using is turning it off.

Now this is interesting:

I reloaded your page, and now the wallet address box has some history in it.  But only the things that I typed into the form I made locally using your input element's HTML code.

So I think the problem lies with your submit button not updating the input element's history, and not with the input element itself.

So I've managed to get your page to remember my wallet address by doing the following:

1. make a file with this in:

Code:




2. visit the file in a web browser

3. type my wallet address in the box and hit return

4. that's all - now my wallet address is available in your page's element's history
sr. member
Activity: 328
Merit: 250
Guessed 7777 and won Smiley
legendary
Activity: 1246
Merit: 1016
Strength in numbers
Quote
Thank you for sending 0.20BTC to [address]! You have won 0.40BTC! Payment will be sent to [address] after 2 confirmations.

How about not waiting for confirmations, but using the output of the transaction I paid you with as an input of your payment to me.  Then you can do fast payouts like a little-known dice game does.

That might happen eventually, but I'm not sure what/how modifications need to be made to send 0 confirm inputs and to select coins. For now I dropped it to 1 confirm though.
legendary
Activity: 2940
Merit: 1333
Quote
Thank you for sending 0.20BTC to [address]! You have won 0.40BTC! Payment will be sent to [address] after 2 confirmations.

How about not waiting for confirmations, but using the output of the transaction I paid you with as an input of your payment to me.  Then you can do fast payouts like a little-known dice game does.
legendary
Activity: 2940
Merit: 1333
Right, I know what you mean. I thought browsers did it on their own (it seems they even do it cross sites sometimes right?) but I guess it needs to be enabled. Me or notme will straighten it out. :-)

I think maybe it just has to not be disabled...  The following remembers my input:

Code:




Using a copy of the input element from your form also remembers my input.  Perhaps something in one of the javascript libraries you're using is turning it off.
legendary
Activity: 2940
Merit: 1333
Quote
Thank you for sending 0.20BTC to [address]! You have won 0.40BTC! Payment will be sent to [address] after 2 confirmations.
Guess: 1260, Number: 1287, Distance: 27, Max Distance: 2475
sha256('Bx6hf13x752012-06-12 01:35:26 1287') = d6582cc734b8dc577681723a1b902536c8ff9ce36661653bd7ff2bcb0a14cd92
After you pay, click here to see if you won!

Note that it is still saying "After you pay, click here to see if you won!" even after it has told me that I won.
legendary
Activity: 1246
Merit: 1016
Strength in numbers
Dimes coming to you and the 3400 guesser!

Received.  Thanks.  Exactly covers my two losing bets.  Smiley

Let me see about the remembering.

I'm using Chromium 18.0.1025.151 (Developer Build 130497 Linux) Ubuntu 12.04 if it's important.

Usually input fields automatically keep a history of what I've typed into them, but the wallet address one doesn't.  The 'Subject:' box at the top of this page I'm using to compose the message, for instance, if I blank it out and type 'R', I get a big list of previous subject lines I replied to.

Right, I know what you mean. I thought browsers did it on their own (it seems they even do it cross sites sometimes right?) but I guess it needs to be enabled. Me or notme will straighten it out. :-)
legendary
Activity: 2940
Merit: 1333
Dimes coming to you and the 3400 guesser!

Received.  Thanks.  Exactly covers my two losing bets.  Smiley

Let me see about the remembering.

I'm using Chromium 18.0.1025.151 (Developer Build 130497 Linux) Ubuntu 12.04 if it's important.

Usually input fields automatically keep a history of what I've typed into them, but the wallet address one doesn't.  The 'Subject:' box at the top of this page I'm using to compose the message, for instance, if I blank it out and type 'R', I get a big list of previous subject lines I replied to.
legendary
Activity: 1246
Merit: 1016
Strength in numbers
I went to bet 40 BTC to win 42 BTC (then changed my mind before submitting).

"You have a 85.87% chance of winning. In order to win, your guess must be within 4294 of our chosen number."

If I guess 4294, then everything from 0000 to 8588 is within 4294 of my guess.  That's 8589 winning guesses out of 10k, or 85.89%.

You report 85.87%, which makes me think that you're not counting 0 and 8588 as being winning numbers.  That's going to piss somebody off one day...

Either that or the displayed percentage is just a little out.

Hmm, let me investigate.
legendary
Activity: 2940
Merit: 1333
I went to bet 40 BTC to win 42 BTC (then changed my mind before submitting).

"You have a 85.87% chance of winning. In order to win, your guess must be within 4294 of our chosen number."

If I guess 4294, then everything from 0000 to 8588 is within 4294 of my guess.  That's 8589 winning guesses out of 10k, or 85.89%.

You report 85.87%, which makes me think that you're not counting 0 and 8588 as being winning numbers.  That's going to piss somebody off one day...

Either that or the displayed percentage is just a little out.
legendary
Activity: 1246
Merit: 1016
Strength in numbers
It just told me: "Hash or timestamp has been tampered with.
To keep things fair, games are only valid for 2 minutes, please generate a new hash."

I didn't tamper with anything.

I did hang around longer than 10 minutes though, looking at the odds it offered me.

I'm guessing the 2 minute limit is to prevent me brute-forcing the hash to find out what the number is.  How about making the 'junk' an extra character or two longer, and having the games valid for an hour instead.  2 minutes arguably isn't long enough for a new user to find their wallet address, copy it into the form, get familiar with how the site works, decide what numbers to type into the boxes, etc.

And instead of making me click a link to "generate a new hash", how about just generating a new one right there and then.

Also, I keep having to re-type my wallet address.  The input field isn't remembering the one I used last time, like input fields usually remember things.  I keep having to go back to my wallet and copy/paste it each time.

Oh, and where's that dime you promised me?  Wink

Dimes coming to you and the 3400 guesser!

Yeah, I will increase it, I think 15 min for now. I can't just make a new hash silently since that would defeat the promise, I think there has to be notification/action.

Let me see about the remembering.


legendary
Activity: 1246
Merit: 1016
Strength in numbers
I'm not sure about having the odds get worse the more I bet.

That encourages me to split my bet into 10 smaller bets to get better odds.

I slide the fee like that so I can offer larger wagers than I'd want to take if the fee was flat.

Splitting your bet up does help me since you are not likely to win (or lose) them all and so my variance is less and I can invest less capital.

When I load up the wallet everything should be about 10x bigger (and maybe more later on). Meaning 10x higher caps and the same odds for 10x higher wagers than currently. Hopefully in less than a day.
legendary
Activity: 2940
Merit: 1333
It just told me: "Hash or timestamp has been tampered with.
To keep things fair, games are only valid for 2 minutes, please generate a new hash."

I didn't tamper with anything.

I did hang around longer than 10 minutes though, looking at the odds it offered me.

I'm guessing the 2 minute limit is to prevent me brute-forcing the hash to find out what the number is.  How about making the 'junk' an extra character or two longer, and having the games valid for an hour instead.  2 minutes arguably isn't long enough for a new user to find their wallet address, copy it into the form, get familiar with how the site works, decide what numbers to type into the boxes, etc.

And instead of making me click a link to "generate a new hash", how about just generating a new one right there and then.

Also, I keep having to re-type my wallet address.  The input field isn't remembering the one I used last time, like input fields usually remember things.  I keep having to go back to my wallet and copy/paste it each time.

Oh, and where's that dime you promised me?  Wink
full member
Activity: 206
Merit: 100
Guessed 3400 and won!
legendary
Activity: 2940
Merit: 1333
I'm not sure about having the odds get worse the more I bet.

That encourages me to split my bet into 10 smaller bets to get better odds.
hero member
Activity: 686
Merit: 500
Wat
I guessed 9001 lol
legendary
Activity: 1246
Merit: 1016
Strength in numbers
The (?) after the hash at the bottom of the page is underlined, making it look like it is a hyperlink.  That caused me to click on it, which in turn prevented the tooltip from popping up.

It appears that I'm meant to just hover over it, not click it.  Removing the underline would help prevent people clicking on it I think.
The string that was hashed for me was:

Code:
bw4lv6Q8B52012-06-11 23:56:548930

I would suggest putting spaces in there between the junk, the date, and the guess, just to make it more legible.

Thanks dooglus. Keep it coming.
legendary
Activity: 2940
Merit: 1333
The (?) after the hash at the bottom of the page is underlined, making it look like it is a hyperlink.  That caused me to click on it, which in turn prevented the tooltip from popping up.

It appears that I'm meant to just hover over it, not click it.  Removing the underline would help prevent people clicking on it I think.
legendary
Activity: 2940
Merit: 1333
The string that was hashed for me was:

Code:
bw4lv6Q8B52012-06-11 23:56:548930

I would suggest putting spaces in there between the junk, the date, and the guess, just to make it more legible.
legendary
Activity: 1904
Merit: 1002
Please give feedback! And ask questions if anything is unclear.

Is 9999 'within 10 of' 0001?

ie. do the numbers wrap around?

Numbers do wrap around.  Bitcoin transactions are checked once per minute, so it may take a minute to recognize your payment.
legendary
Activity: 2940
Merit: 1333
June 11, 2012, 11:06:08 PM
#9
Please give feedback! And ask questions if anything is unclear.

Is 9999 'within 10 of' 0001?

ie. do the numbers wrap around?

Edit: I can answer that now.  I lost my bet, with "Guess: 3536, Number: 8930, Distance: 4606, Max Distance: 3536".

8930 - 3536 = 5394
13536 - 8930 = 4606

So they do wrap around - the reported distance is the shorter of the two.  It would be worth mentioning that (more prominently, if I missed it).
legendary
Activity: 2940
Merit: 1333
June 11, 2012, 11:03:33 PM
#8
I sent 0.05 BTC, and guessed 3536.

I'm clicking "After you pay, click here to see if you won!" but the same page keeps coming up over and over.  Is it waiting for confirmations, or did something go wrong?

Edit: it took over 5 minutes to let me know if I won, but did eventually tell me.  "Guess: 3536, Number: 8930, Distance: 4606, Max Distance: 3536".  I lost my 70.71 shot...

It says the game will be valid until Mon Jun 11 2012 22:56:54 GMT-0700 (PDT) and it's currently only Mon Jun 11 21:03:06 PDT 2012, so it's valid for almost 2 more hours.

Quote
Set your wager amount and choose your win rate. Guess close enough to the predetermined number to win!
Send 0.05BTC to 18gEEmSuQse6oaK8EnfBo3umZgCwRb1TAK for a 70.71% chance to win 0.07BTC.
This game will be valid until: Mon Jun 11 2012 22:56:54 GMT-0700 (PDT).
Refresh Game
Start new game!
 
BET AMOUNT
 0.05 BTC
WIN AMOUNT
 0.07 BTC

You have a 70.71% chance of winning. In order to win, your guess must be within 3536 of our chosen number.
legendary
Activity: 1246
Merit: 1016
Strength in numbers
June 11, 2012, 05:04:28 PM
#7
I just changed it to say, "After you pay, click here to see if you won!"
legendary
Activity: 1246
Merit: 1016
Strength in numbers
June 11, 2012, 05:01:28 PM
#6
I'm assuming I didn't win? How do I get notified of a win/loss?

A few seconds after you pay, click the refresh link.
hero member
Activity: 784
Merit: 1000
0xFB0D8D1534241423
June 11, 2012, 04:52:39 PM
#5
I'm assuming I didn't win? How do I get notified of a win/loss?
legendary
Activity: 1246
Merit: 1016
Strength in numbers
June 11, 2012, 04:51:33 PM
#4
Uh-oh. I'm pretty sure I bet on the number being 6000, but I'm not positive. Me and my memory, I tell ya Undecided
Sent coins to 13e8q1PtDNAXPGci7v5Jpz53FXLEwY5RTV and the hash of the bet was d8212b6ef695128b4014910df1e632706279bb22ac5b769f0876a0343f5e8346


Cool, sent a dime.
hero member
Activity: 784
Merit: 1000
0xFB0D8D1534241423
June 11, 2012, 04:36:33 PM
#3
Uh-oh. I'm pretty sure I bet on the number being 6000, but I'm not positive. Me and my memory, I tell ya Undecided
Sent coins to 13e8q1PtDNAXPGci7v5Jpz53FXLEwY5RTV and the hash of the bet was d8212b6ef695128b4014910df1e632706279bb22ac5b769f0876a0343f5e8346
legendary
Activity: 1246
Merit: 1016
Strength in numbers
June 11, 2012, 04:23:26 PM
#2
Bump for the free dimes offer.
legendary
Activity: 1246
Merit: 1016
Strength in numbers
June 09, 2012, 09:58:10 PM
#1
Myriad offers flexible bets. You enter the amount you want to bet and the amount you want sent if you win and it offers you odds. You can accept the wager by sending payment.

The max bet, win amount and effective fee (lower odds than 'fair') depend on how much is in the wallet.

We're testing with real money, but a smaller wallet for now. Because the effective fee is determined by the percent of the wallet you are trying to win the fee will be higher now for the same wager compared to after the wallet is fully loaded up.

The games are cryptographically provably fair. We use sha256 to hash [junk, timestamp, our guess] when you first hit the site. After the wager is completed we reveal [junk, timestamp, our guess] and you can check that the guess is the one we committed to at the time you came to the site.

Since wins are determined by how close your guess is to ours you don't need to worry about how we select our guess.

Please give feedback! And ask questions if anything is unclear.

MyriadCoins.com

Max bet has been raised! Right now you can bet .01 to win 19.70!
Jump to: