The daemon was down. Our game script checks the transaction by querying the daemon and checking new transactions made to the addresses of bets. So when it was started all bets which were in queue were played randomly. Your bet id was assigned by script randomly that time. Its not based on the time or date. The new transactions/queued bets are assigned bet id randomly.
That does not explain why I cannot lookup the bet that played all bets including recent bets have shown up in the log, I have tried the options part of your site where it says to put in your Bitcoin address but it does not lookup a transaction history and nothing occurs.
If I could see a transaction hash, I would believe it played but nothing so far has seemed to have happened the burden is on the operator to prove it played. If you can show me a transaction log that confirms that the bet was recognized by the daemon and provided an outcome this would be resolved. Can you verifibly prove that the daemon has assigned a random transaction when it was restarted.
If not the fault lies on the operator as no evidence can be provided that it does work and is provably fair, what it shows is that the daemon made an error on my bet. I'll rephrase it looking at the logs to prove the error.
It does not show up in recent bets with any result on the recent bets, if what you stated is true the BET ID should have randomly assigned me a transaction that can be looked up, which it did not. Second your claim is that the bets are not based on time and date, however other transactions are shown on the chain momentarily after being placed, and have been recognized by the Daemon within Seconds of playing on your site.
imgurlThe Bet was played on 2015-10-14 10:08:58 the daemon was restarted at 2015-10-14 22:05:41 with this bet from 1QEsT7QXG3pQVou9gZHACC8udY4T9Gt6NY for 0.003 BTC.
It can be verified in the blockchain to have played on 1RUBY with a sending and recieving address for transactions starting from 22:15:31 on when 1QEsT7QXG3pQVou9gZHACC8udY4T9Gt6NY makes a bet on the 1RUBY/Promo line and it shows the relevant transactions in the recent bets on the page But it conclusively does not include my transaction which was missed.
A curious transaction seems to occur on 22:09 which includes my inputs and sends it to 1Q before the user begins betting on the line.
This should prove that the daemon DID NOT PLAY my bet and the script did not assign it randomly, rather it scooped the amount in the wallet did not assign it an ID and then started with new deposits to the address.
I feel their is grounds for a refund on this bet given the consistency between the bet logs, lack of user id and the facts presented.
