Decentralized app which rely on centralized services, this way it is not safe for players nor investor.
You should postpone your ICO 'till you solve those issues which RHvar pointed out.
What we have here is some competitors saying wrong things and bad information about us.
We expect this of course. When do competitors say good things.
Everyone who reads this forum can really see that. So it's fine.
They did disclose they are from competitor games, so it is OK.
I'm not a competitor. I have no affiliation with any site.
So please, just answer my question.
Is this true or false:
Participants in the vdice smart contract bear a small amount of risk from the
‘house’ being a bad actor, and from a bad actor internal to Oraclize.
You paste images on social media. You spread lies generally.
So dishonest.This was answered to the satisfaction of people much, much smarter than you, above.
Maybe spend some time learning to understand the answer, instead of trolling
Once again, in response to your question:-
----
1- "Replay Risk"
the very reason why the authenticated JSON-RPC APIs of random.org are used, is because of the "requestsLeft" field which is returned by each API call response (
https://api.random.org/json-rpc/1/signing ). This field content is tied to the API credentials specified in the query and is there to indicate how many requests are left in a given day.
If we check all the TLSNotary proofs published on the blockchain (which contain the whole API response!), an independent auditor can verify whether any subsequent number in the "requestsLeft" fields is missing - when that happens, the auditor has a good indicator that something wrong happened (either on the Oraclize side - which sent more requests than expected - or by any external party knowing that specific API key (vDice itself & random.org)). Of course this doesn't say much about the intent in itself (can just be some failure in the HTTP request, which had to be sent again), but in general it provides some level of security against replay attacks.
----
2- "setConfig"
Oraclize are updating on-chain contracts in the coming days to support this. It's here for forward-compatibility and enables arbitrary Oraclize flags to be enabled/disabled. The very reason why the vDice contract needs it is to enable the "zero-confirmation query precomputation" feature.
----
What the hell?
I quoted the third part audit that
you posted.
It's a simple question that you
still have not answered.
The reason you haven't answered it is because:
If you lie and claim it's false: you would be disputing the results of the third party audit that you've been spamming all over the place.
If you answer honestly, it would be even more obvious to more people that you either don't understand the concept of decentralization or you're a scammer.
By the way, it was quite a shock when I saw your linkdin after all these blogs and press releases popping up that you deny paying for or writing yourself (assuming this is Jason, the CEO. It could be Barney, the " Social Media expert who spends all his time on the internet and is new to the blockchain"
Even more shocking is that your simple dice site, which isn't even provably fair, is a piece of crap. Players can't verify rolls, it can take an hour to complete a single bet, and you've barely had 7k bets a month after launching.
mikeyb @mikeyb Nov 07 08:17
@vDice_io_twitter What is the best way to validate/verify a bet? Doesn't seem like there is any info on easily replicating results.
vDice.io @vDice_io_twitter Nov 07 09:27
Sure, that documentation is available through the support desk
Just click the support tab on the site and contact them
We'll get it live to the site as soon as we can
Most of our devs front and back are focused on the ICO at the moment
As you can imagine
mikeyb @mikeyb Nov 07 09:46
Yeah but these are certainly things investors will want to see (like me, who is testing the system before investing)
mikeyb @mikeyb Nov 07 09:55
And is it normal for it to take 30+ minutes for results on bets? Or is that due to the geth/parity swap?
vDice.io @vDice_io_twitter Nov 07 10:52
Hi Mikey
Understood
I can leave a note for them to add this on the crowdsale site
But it's best if you send them a message through the support tab
I assume you mean when the results on bets are showing up in the UI
And yeah, our front-end guys are upgrading the code for the custom APIs that power the UI
As a result of the switch from geth to parity
You should find that the bets themselves are being processed by the smart contract infrastructure in the standard timeframes
mikeyb @mikeyb Nov 07 11:22
I am referring to the processing of the bet/game/round. When I send a transaction, it is taking over 30 minutes to send back to me either the winnings or 1 wei.
https://i.gyazo.com/d133979710b4dd05c57b5335f2fae1e1.pnghttps://i.gyazo.com/6a468ce34f2fea71328c84ca1c32f871.pngroughly an hour to process and return the results
I have submitted support ticket, but the response is pretty slow. Really wanting to talk with someone in realtime so I dont play support tag until the ICO starts
It's time to come clean Jason. Or is it Barney?
