MyriadCoins.com - Make the bet you want

[FreeMoney]

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... 

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.

[FreeMoney]

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?

[dooglus]

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! 

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.

[FreeMoney]

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.

[dooglus]

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://bitcointalk.org/index.php?topic=80312.0

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.

[FreeMoney]

I just raised limits by about 5x. You can bet .01BTC to win 19.70BTC right now.

[fireduck]

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.

[FreeMoney]

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.

[dooglus]

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

[darkmule]

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!

[notme]

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 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.

[dooglus]

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?

[notme]

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.

[FreeMoney]

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.

[FreeMoney]

Myriad has QR codes for the payment addresses now.

[cunicula]

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.

[dooglus]

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.

[darkmule]

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.