That just means Ukto is working on the new API and it should be available soon enough. Hence why he made me one key to test.

No. Should be released soon. Usually it should be out within the first 2 weeks of the month. No exact schedule tho.

Actually I was updating it manually not long ago. Now I got an API key. It's still not public tho. As soon as it is, I'll release a new version.

It will be back, don't worry. No sure what Scrat is doing exactly tho.

Nope. Not interested in paying more. If people want to switch, I'll just buyback their bonds as per contract.

Eh, well I don't know how many thousands times you rolled but 11 losses streaks are to be expected with so many rolls. Although if it was less than 10 thousand, I guess that's indeed unlucky.

What odds are you playing at?

 

By the way:
That should be 10 USD per BTC I believe.

Eh, as long as it's addressed promptly, that's quite fine.

I wouldn't be so sure of who it is. This forum is reputed for getting a lot of trolling going on. Some people lost money, of course some will end up looking for suspicious things.

If we wanted to accuse you of anything, we'd do it openly. We haven't, but it did cross our minds. Nothing surprising and we're not the only ones, you made about half the posts on that thread! (I might be exaggerating there... maybe 1/3rd to 1/4th). You even often have two posts in a row!

But as someone pointed out (and even made a website example about how PrimeDice could make all rolls a loss if they wanted) and since some users lost money and you've been bumping the thread so much, expect to get a lot of these. Anything even remotely shady gets attacked.

If I were Stunna, I'd just freeze betting right now until the client seed becomes easily changeable. There's currently no way to do so without editing the page's source code. Until that's done/unless people know about this/do it manually, there is nothing provably fair about PrimeDice. Client seed is the same on each roll and thus PrimeDice knows the secret seed, the client seed, and can serve whichever server seed they want for the next roll. PrimeDice could choose the outcome for each roll unless the user knows about it and changes the secret on each roll. I don't think Stunna is abusing it, but that's serious enough to not just be a top priority of things to do. No betting should be allowed until that's resolved. (Would spare PrimeDice a lot of bad press. Will only get worse if betting is being allowed while situation isn't resolved. And you don't want to attract yourself some permanent trolls.)

Ah, sorry if it is seen as advertising, I was just arguing a bit against what you said about always losing on Coinroll.

You can get under the verification page the database dumps of bets/deposits/withdrawals/accounts

The provably fair system is based on the blockchain tx and all betting history is provided so it can be checked that rolls match the site's secret, the last tx id of user and the nonce (incremented by one on each bet). It's almost as easily auditable as SatoshiDice bets, but without the need for a Bitcoin transaction on each roll.

Coinroll has been following more or less closely the 1% house edge. Bets do remain provably fair and the whole list of bets is public. Rolls are based on the account's last tx ID. Although when looking at individual users, some are average, some are very lucky and some are very unlucky. But for those with a very large amount of bets (thousands), it starts getting quite close to 1% edge.

I don't quite see the difference for the multiplier thing. Other than being presented differently (Under X/65,535 for CR or Over x/100 for PD)... works exactly the same way. To me PrimeDice and Coinroll are essentially clones.

Coinroll's provably fair system is better tho.

Considering the kind of users which regularly pops around this forum, proof of being who you claim to be would probably go a long way in getting answers.

I think for some reason the amount was automatically returned to the sender instead of the cashout address.

Session had expired and addresses changes on each login with a cashout address. Previous one being an invalid deposit address... Something like that.

Each share represents 1/1'000'000th of profits. They are effectively all currently issued. That 1 or 500'000 are outstanding bears no impact for holders. Non outstanding shares are the owners' shares. They can be used as seen fit.

Would definitely pay to see that coming to fruition.

Thank you for releasing this script. As promised, I tipped you.

We took over in December and have been pretty hard pressed expenses wise in the beginning.

1. Not much. We used to rent them. We now have owned servers co-located in New York. We don't have the means to move around. As for server prices, they are published along specs in monthly statements.
2. If you haven't seen our previous website, it was a plain black header/footer with black on white text and a little bit of color. We had no budget for a new design and had to produce one. There is still improvements to come to the current website.
3. Some of our clients are already receiving discounts in exchange of a prominent banner/ad. We're also the most widely advertised servers for Bitcoin service around the community. We don't usually have to pay for this. We're the most known around.

We pretty much already are, I believe.

Yes, we will have a reviews/clients section eventually.

Short story:
Only the bets archive/history seems to have the wrong nonces (repeated) as viewed in archive or on the website. The lucky numbers appear to be the one that would have been generated with the correct nonce (not skipped like on the archived bets).

Ex:
https://coinroll.it/bet/26c991a300e6
Shows nonce 41875 & lucky number 45957 (Which can be generated with nonce 41874)
https://coinroll.it/bet/916f4107ff33
Shows nonce 41875 & lucky number 25074 (Which can be generated with nonce 41875)

Well that is an issue if historic bets are to be verified with a script. Although if it only impacts the archive, correcting the issue should be easy.