DirectBet (OP)
Legendary
Offline
Activity: 1288
Merit: 1010
|
|
July 04, 2014, 08:17:59 PM |
|
You say it was never at 5.6, but I ordered it and it automatically populated the current odds of 5.6
Check my screenshot - I have never ordered a bet and typed in 5.6 as my desired odds.
Even after you received the bet, it showed as "pending" and "open for additional betting". Message said "bet will be confirmed shortly", so I checked the odds and sure enough they were at 5.6. Yet still not confirmed. Why wasn't that automatic? You sat there and allowed Fischer to complete the break and then dropped the odds to 2.8. Then, and only then, did my bet go from "pending" to "negotiate".
Secondly, to test my hypothesis that you copy lines from Cloudbet and Bet365 - I checked the Cubs/Nationals odds today in the 5th inning and sure enough, your lines were identical to Cloudbet.
We do not confirm bets manually. All bets are processed automatically by our automated betting system. We do not copy lines from Cloudbet or Bet365. Please stop spreading false information. You are right, when you ordered the bet, the odds were 5.6. By the time your bet transfer was received, the odds were reduced to 4.6 due to developments in the game. During in-play, odds might fluctuate widely. You had an option to lower the minimum required odds and get your bet confirmed but you elected to cancel the bet. Per your request, your bet was then canceled and refunded and therefore no payout is due.
|
|
|
|
tins
|
|
July 04, 2014, 08:20:26 PM |
|
You get an instant notification when your bet is rejected and it is then refunded after there is 1 confirmation in the Bitcoin network for your initial bet transfer. So while the refund is transferred a few minutes later, you know right away whether your bet was confirmed or not. I'm sorry that your bet arrived in a few minutes delay and hope that you will understand that this was not our fault. Your wallet provider delayed the broadcasting of your bet transfer as I've showed you in my previous post. We process bets as soon as they are received. We have no way to tell whether your transfer arrived in a delay or whether you intentionally wanted to send it some time after you ordered the bet on our website. In the future, if you decide to bet at DirectBet again, we recommend that for time sensitive bets and for fastest instant Bitcoin delivery, you use the official Bitcoin Core client or its lighter version Multibit. These wallets can be downloaded from https://bitcoin.org/en/choose-your-walletYou will not have these delays when using the official wallet. DirectBet is lying here too. I place an order at 17:45. I received a bitcoin address and sent the money at 17:45. DirectBet acknowledged that I sent it at 17:45. Now he is saying that he didn't know. He accepted it 7 minutes later. There is no reason for us to wait 7 minutes before knowing if DirectBet is going to accept the bet. You already said that you used 'Firm Odds' and that by the time that the transaction went through the odds no longer met the minimum, thus the bet was refunded. Seems pretty straight forward.
|
|
|
|
ts11111
Member
Offline
Activity: 117
Merit: 10
|
|
July 04, 2014, 08:26:22 PM |
|
You say it was never at 5.6, but I ordered it and it automatically populated the current odds of 5.6
Check my screenshot - I have never ordered a bet and typed in 5.6 as my desired odds.
Even after you received the bet, it showed as "pending" and "open for additional betting". Message said "bet will be confirmed shortly", so I checked the odds and sure enough they were at 5.6. Yet still not confirmed. Why wasn't that automatic? You sat there and allowed Fischer to complete the break and then dropped the odds to 2.8. Then, and only then, did my bet go from "pending" to "negotiate".
Secondly, to test my hypothesis that you copy lines from Cloudbet and Bet365 - I checked the Cubs/Nationals odds today in the 5th inning and sure enough, your lines were identical to Cloudbet.
We do not confirm bets manually. All bets are processed automatically by our automated betting system. We do not copy lines from Cloudbet or Bet365. Please stop spreading false information. You are right, when you ordered the bet, the odds were 5.6. By the time your bet transfer was received, the odds were reduced to 4.6 due to developments in the game. During in-play, odds might fluctuate widely. You had an option to lower the minimum required odds and get your bet confirmed but you elected to cancel the bet. Per your request, your bet was then canceled and refunded and therefore no payout is due. LIES!!!! Per your email from last night: "The odds never reached 5.6. 4.6 was the highest until you canceled the bet. It's possible that you didn't refresh the page and saw outdated odds."
|
|
|
|
Rating Place
Legendary
Offline
Activity: 3864
Merit: 1061
|
|
July 04, 2014, 08:28:43 PM |
|
Here's my bet that was sent at 17:45 but DirectBet said 17:52. Size 258 (bytes) Received Time 2014-07-02 17:45:27 Included In Blocks 308912 (2014-07-02 18:12:04 +27 minutes) Confirmations 313 Confirmations Relayed by IP Blockchain.info Visualize View Tree Chart
|
|
|
|
ts11111
Member
Offline
Activity: 117
Merit: 10
|
|
July 04, 2014, 08:31:59 PM |
|
Here's my bet that was sent at 17:45 but DirectBet said 17:52. Size 258 (bytes) Received Time 2014-07-02 17:45:27 Included In Blocks 308912 (2014-07-02 18:12:04 +27 minutes) Confirmations 313 Confirmations Relayed by IP Blockchain.info Visualize View Tree Chart What a joke! This place is all sorts of f'd up. The problem for us is that they hold all of the cards. There is no transparency. The system is inherently flawed. They owe you AND me.
|
|
|
|
Rating Place
Legendary
Offline
Activity: 3864
Merit: 1061
|
|
July 04, 2014, 08:36:38 PM |
|
Here's my bet that was sent at 17:45 but DirectBet said 17:52. Size 258 (bytes) Received Time 2014-07-02 17:45:27 Included In Blocks 308912 (2014-07-02 18:12:04 +27 minutes) Confirmations 313 Confirmations Relayed by IP Blockchain.info Visualize View Tree Chart What a joke! This place is all sorts of f'd up. The problem for us is that they hold all of the cards. There is no transparency. The system is inherently flawed. They owe you AND me. agree. Betting with the deposit books is much easier and safer.
|
|
|
|
DirectBet (OP)
Legendary
Offline
Activity: 1288
Merit: 1010
|
|
July 04, 2014, 08:38:25 PM |
|
DirectBet is lying here too. I place an order at 17:45. I received a bitcoin address and sent the money at 17:45. DirectBet acknowledged that I sent it at 17:45. Now he is saying that he didn't know. He accepted it 7 minutes later. There is no reason for us to wait 7 minutes before knowing if DirectBet is going to accept the bet.
You sent your bet transfer on 17:45 through the Bitcoin web wallet http://blockchain.info/However, Blockchain.info did not broadcast your transfer right away. They delayed it by 7 minutes. This was not our fault, you may want to contact them and ask them why they did not broadcast your bet transfer right away.Here is a proof from a 3rd party block chain explorer that your bet transfer was broadcasted on 17:52 : https://www.biteasy.com/blockchain/transactions/f33f82da7e486509b45ab23b965b5ae789c5ae64cf1a08230249235562420fdcWhen your transfer finally arrived at 17:52, we processed and confirmed it immediately. Your bet was processed and confirmed according to our rules and therefore it will stand. Had your bet won, it would have paid out automatically at the completion of the game. Following is the relevant information from our Rules page : If your bet transfer is delayed by the Bitcoin, Litecoin or Dogecoin network or by your wallet or for any other reason, it will be processed as soon as it is received.
For time sensitive bets and for fastest instant Bitcoin delivery, use the official Bitcoin Core client or its lighter version Multibit. These wallets can be downloaded from https://bitcoin.org/en/choose-your-walletYou will not have these delays when using the official wallet.
|
|
|
|
uknohowwedo
|
|
July 04, 2014, 08:39:41 PM |
|
wow really? im never using DB again if they dont fix this for you ts111 thats bogus
|
|
|
|
Rating Place
Legendary
Offline
Activity: 3864
Merit: 1061
|
|
July 04, 2014, 08:42:33 PM |
|
DirectBet- Your rules allow for a 3 hour delay then you can tell us after the game if a bet is good or not. Your program and rules are flawed if you can't tell us within 1 minute if a bet is good. Deposit books tell us immediately.
|
|
|
|
21pilot
|
|
July 04, 2014, 08:43:15 PM |
|
i can also recommend Electrum wallet for fast and easy confirmations. and always include a transaction fee because this results in a higher priority of your transaction -> it is broadcasted faster to the blockchain
|
|
|
|
ts11111
Member
Offline
Activity: 117
Merit: 10
|
|
July 04, 2014, 09:04:43 PM |
|
And just like that, DB disappears. May be time to organize a boycott
|
|
|
|
DirectBet (OP)
Legendary
Offline
Activity: 1288
Merit: 1010
|
|
July 04, 2014, 09:07:04 PM |
|
DirectBet- Your rules allow for a 3 hour delay then you can tell us after the game if a bet is good or not. Your program and rules are flawed if you can't tell us within 1 minute if a bet is good. Deposit books tell us immediately.
No Peeps, we tell you immediately, within a few seconds, whether your bet is accepted or rejected. If your bet transfer is received after the event is already over, it will get rejected and refunded. The problem with your bet was that your wallet did not send the transfer right away. It held it for 7 minutes, during which we had no way to tell that you sent in your bet.
|
|
|
|
ts11111
Member
Offline
Activity: 117
Merit: 10
|
|
July 04, 2014, 09:10:02 PM |
|
DirectBet- Your rules allow for a 3 hour delay then you can tell us after the game if a bet is good or not. Your program and rules are flawed if you can't tell us within 1 minute if a bet is good. Deposit books tell us immediately.
No Peeps, we tell you immediately, within a few seconds, whether your bet is accepted or rejected.If your bet transfer is received after the event is already over, it will get rejected and refunded. The problem with your bet was that your wallet did not send the transfer right away. It held it for 7 minutes, during which we had no way to tell that you sent in your bet. Bull. Yesterday mine set as "bet received - pending" and "open for additional betting" for over a minute. You waited for Fischer to break, and then my bet went to "negotiate".
|
|
|
|
Rating Place
Legendary
Offline
Activity: 3864
Merit: 1061
|
|
July 04, 2014, 09:20:13 PM |
|
DirectBet- Your rules allow for a 3 hour delay then you can tell us after the game if a bet is good or not. Your program and rules are flawed if you can't tell us within 1 minute if a bet is good. Deposit books tell us immediately.
No Peeps, we tell you immediately, within a few seconds, whether your bet is accepted or rejected. If your bet transfer is received after the event is already over, it will get rejected and refunded. The problem with your bet was that your wallet did not send the transfer right away. It held it for 7 minutes, during which we had no way to tell that you sent in your bet. I showed you multiple times that you received the bet at 17:45, not 17:52. Your post above says that DirectBet can wait until 1 minute before an event concludes to accept or reject even if the bet was placed an hour ago. You don't see the flaw? You are shot taking.
|
|
|
|
ts11111
Member
Offline
Activity: 117
Merit: 10
|
|
July 04, 2014, 09:25:56 PM |
|
DirectBet- Your rules allow for a 3 hour delay then you can tell us after the game if a bet is good or not. Your program and rules are flawed if you can't tell us within 1 minute if a bet is good. Deposit books tell us immediately.
No Peeps, we tell you immediately, within a few seconds, whether your bet is accepted or rejected. If your bet transfer is received after the event is already over, it will get rejected and refunded. The problem with your bet was that your wallet did not send the transfer right away. It held it for 7 minutes, during which we had no way to tell that you sent in your bet. I showed you multiple times that you received the bet at 17:45, not 17:52. Your post above says that DirectBet can wait until 1 minute before an event concludes to accept or reject even if the bet was placed an hour ago. You don't see the flaw? You are shot taking. Peeps - you can't imagine how many times this has happened to me
|
|
|
|
ts11111
Member
Offline
Activity: 117
Merit: 10
|
|
July 04, 2014, 10:06:51 PM |
|
Peeps - you have a site that rates bitcoin betting sites, right? We need more people to know about our problems unless DB steps in to make it right for us. You can post on your site, and I can post this across twitter, facebook and every single bitcoin/gambling forum on the net. Repeatedly.
|
|
|
|
DirectBet (OP)
Legendary
Offline
Activity: 1288
Merit: 1010
|
|
July 04, 2014, 10:13:58 PM |
|
I showed you multiple times that you received the bet at 17:45, not 17:52.
The time stamp that you are quoting, 17:45, is from your wallet BlockChain.info. This is the time that you asked your wallet to transfer the Bitcoin, but it was broadcasted to the Bitcoin network 7 minutes later on 17:52. The reason why you see 17:45 on bloackchain.info is because the transfer was initiated from there (it is your wallet), as is indicated by "Relayed by IP : Blockchain.info". To find the actual time in which your transfer was broadcasted to the Bitcoin network, look at a 3rd party block chain explorer other than your wallet : https://www.biteasy.com/blockchain/transactions/f33f82da7e486509b45ab23b965b5ae789c5ae64cf1a08230249235562420fdcAs you can see, the transfer was delivered on 17:52. Apparently, Blockchain.info was clogged and delayed broadcasting your transfer. This is further evident by the screen shot that I submitted in my earlier post which shows the time stamp in our wallet. Your post above says that DirectBet can wait until 1 minute before an event concludes to accept or reject even if the bet was placed an hour ago. You don't see the flaw? You are shot taking. We don't hold bets under any circumstances. They are processed as soon as they are received and you can verify that using time stamps from the block chain. Even if we wanted to hold bets as you claim, which we certainly don't, we wouldn't have gained any advantage by doing so. That's because your bets are always confirmed at the best available odds upon receipt, which reflects the true probability of the bet outcome. To give an example from your case, when you ordered the bet on our website on 17:45, the odds were 3.3. When your bet transfer arrived 7 minutes later, the bet odds went up to 5.5 to reflect what was happening in the game, and your bet was confirmed at odds of 5.5. For us, it doesn't matter if we confirm your bet at odds of 3.3 on 17:45, or at odds of 5.5 on 17:52. Our expected profit is the same in both cases. If at all, we prefer to confirm bets as quickly as possible to keep our clients satisfied, but sometimes (although rarely), Bitcoin transfers are delayed and there isn't much we can do about it.
|
|
|
|
maok
|
|
July 04, 2014, 10:22:54 PM |
|
... but sometimes (although rarely), Bitcoin transfers are delayed and there isn't much we can do about it.
Yes you can, start taking Quark which is alot faster :-)
|
QRKHn6UK3ToS53V6jD1rYWRYS4mxQ1mako ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ▄▀▄▀▄▀ Quark core wallet updates ▀▄▀▄▀ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
|
|
|
DirectBet (OP)
Legendary
Offline
Activity: 1288
Merit: 1010
|
|
July 04, 2014, 10:24:34 PM |
|
Peeps - you can't imagine how many times this has happened to me
That's because you are using the Coinbase wallet, which frequently delays Bitcoin transfers. We advised you several times to use the official Bitcoin Core client since you are placing time sensitive bets in-play. Unfortunately, you ignored our suggestions and kept using the Coinbase wallet.
|
|
|
|
ts11111
Member
Offline
Activity: 117
Merit: 10
|
|
July 04, 2014, 10:26:59 PM |
|
Peeps - you can't imagine how many times this has happened to me
That's because you are using the Coinbase wallet, which frequently delays Bitcoin transfers. We advised you several times to use the official Bitcoin Core client since you are placing time sensitive bets in-play. Unfortunately, you ignored our suggestions and kept using the Coinbase wallet. Sometimes I use coinbase, but surprisingly I acknowledged your suggestion and DID switch to the core client.....and included txn fees......and still came up with the same issues. I will tell you that they didn't happen quite as often, which was nice. But still happened nonetheless. Please credit my account with the .59 from the Fischer bet.
|
|
|
|
|