Just letting everyone know that we've been monitoring XMR deposits for the past few days and all is well
You can now deposit as normal! If you have a delay with your XMR deposit, please wait a few minutes and it should go through. Thanks again for everyone's patience and please let me know if you need any support on SD.
I noticed that when btc is deposited into ur site, it take a long while before it reflects after confirmation, my take is that you are trying to programme the person outcome that's why u are delaying. If you know u aint doing that, allow btc to reflect in balance immediately after 1 confirmation
Not sure where you came up with such a theory, but this is hardly the case at all. I'm not sure how many times you've attempted to deposit funds on SD in the past but there are many times where funds are deposited within seconds after 1 confirmation. Let me try and explain how this all works:
The reason why there are times where it can take slightly longer to be credited to your account after seeing 1 confirm on a public blockchain (and by slight, I mean a few minutes afterwards) is because our Bitcoin node needs to pick up the transaction which is separate from other public blockchains. We run our own full node so that we do not have to depend on another service should they ever go down. Running a full node also makes it so that we do not have to trust another service should they be hacked/etc (which is very important for gambling sites), and coming along with this is requirement for us to download all new BTC transactions made. As this is the case, there are going to be times where 1 confirmation on whichever block explorer you checked does not coincide with our node in exact realtime since our server needs to download the new TXes constantly. This is obviously quite resource intensive in conjunction to the other resources required to run a safe and secure dice site, so we don't have it checking every second but rather periodically (by this I mean every few minutes). Another variable that can cause a slight delay in having your funds credited to your SD account are when transactions increase for whatever reason on the network. Please review the following link:
https://blockchain.info/charts/n-transactions?timespan=180daysAs you can see, there are some days where transaction volume on the BTC network are 3x higher than other days which can slow down the network. Lastly, just like any other running node we have a series of checks built into our system to automatically verify all transactions. All nodes build their own transaction pools. Just to give you an idea, here are just a few general checks that need to be ran for each incoming transaction:
1. The transactions syntax and data structure are correct.
2. The input and outputs have values.
3. The transaction is less than the block size of 1 MB.
4. The values must be more than 0 and less than 21 million.
5. None of the inputs have a hash that is equal to 0.
6. The locktime is less than the maximum allowed number.
7. The transaction size is greater than or equal to 100 bytes.
8. The number of signatures is less than the signature limit.
9. The unlocking script can only push numbers onto the stack.
10. The locking script must match is standard format.
11. A matching transaction must exist.
12. If a transaction is missing move the transaction to the orphan transaction pool.
13. If the transaction is a coinbase transaction then it must have a maturity of 100 confirmations.
14. For each input the output must exist and not have been spent.
15. Check that each input value is in the required range.
16. Reject if the input value is less than the output value.
17. Reject if the transaction value is to low to get into an empty block.
18. The unlocking scripts for each input must be verified against the output locking scripts.
As you can see, there are quite a bit of moving pieces when it comes to validating Bitcoin transactions and must be done for every incoming TX. Since we handle a significant amount of BTC daily, we must ensure that every transaction is verified properly the first time. Everything I've discussed here is automated and done programmatically so there isn't some person sitting there reviewing your transactions coming in. That just wouldn't be feasible or reasonable in any situation. With all of this being said, your take on SD "programming the persons outcome" just doesn't make sense. Furthermore, if this were the case we wouldn't have players winning 6+BTC in a single day...Our system is set up to be fair from beginning to end, and we have no interest in "rigging" any part of the gambling experience. After all, that's the whole point of any casino having a house edge built in, is to make things fair yet generate profit for the casino operator. After all, we (nor any other casino) are non-profit organizations.
Hopefully this dispels any misconceived "theories" you may have about why deposits can sometimes take slightly longer, and I also hope that the information I provided you above helps you understand better how transactions are handled by Bitcoin nodes. Again, I can assure you that we have no interest in figuring out the outcome of anything prior to the user playing. If you still think this is the case, there is a simple solution: Roll 5 or more times with no wager, then change the server seed and change the client seed manually to anything you'd like. You can easily validate the rolls once you change your seed again as the previously used server seed will be revealed to you by clicking on any bet ID from that set.
We are indeed a provably fair gambling site, so every roll can be validated which requires the server seed along with the client seed. Feel free to let me know if you have any further questions about this subject
