Bitcoin Forum
June 27, 2024, 08:25:28 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 [55] 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 ... 506 »
  Print  
Author Topic: DirectBet – LIVE Sportsbook & Racebook. Now Accepting Ether !  (Read 759679 times)
MoneyGod
Sr. Member
****
Offline Offline

Activity: 406
Merit: 250



View Profile
July 04, 2014, 07:19:40 PM
 #1081

I lost a bet french
many opportunities for french tonight, may not have been lucky to French  Sad
But today was Day for Germans they play very good even referee was harsh for them but still they play good and manage to win

ts11111
Member
**
Offline Offline

Activity: 117
Merit: 10


View Profile
July 04, 2014, 07:19:58 PM
 #1082

They are middle men. They get their odds from Cloudbet & Bet365

That's not true.

Quote
They confirm bets when it is advantageous to them. They have all the power and control. When they see a bet come in, they can confirm it at whatever odds they want (if flexible odds selected).

When you use the "Flexible Odds" betting option we confirm your bet at the current available odds. As soon as we receive your bet transfer, we immediately make a single inquiry to the current odds, and these odds are set as the confirmed odds for the bet. Most of the times, if you send out the bet immediately, the odds will be the same as they were by the time you ordered the bet, but in other times the odds might be higher or lower.

What you are claiming here is not true. If you like, I can show you dozens of your bets where the confirmed odds were much higher than the odds were at the time that you ordered the bet. This will demonstrate to you that we confirm bets in a fairly manner.

We are very surprised by your claim. We explained to you in the past via e-mail how we confirm bets and you kept betting frequently on our website ever since then.
To us, that's an indication that our automated betting system has treated your fairly.

You are blatantly lying to justify not confirming my Fischer bet at 5.6.

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.

Rating Place
Legendary
*
Offline Offline

Activity: 3780
Merit: 1060


View Profile
July 04, 2014, 08:11:46 PM
 #1083

Quote
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-wallet

You will not have these delays when using the official wallet.

DirectBet is lying here too. I placed 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.



DirectBet (OP)
Legendary
*
Offline Offline

Activity: 1288
Merit: 1010



View Profile WWW
July 04, 2014, 08:17:59 PM
 #1084

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
Hero Member
*****
Offline Offline

Activity: 882
Merit: 500


View Profile
July 04, 2014, 08:20:26 PM
 #1085

Quote
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-wallet

You 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 Offline

Activity: 117
Merit: 10


View Profile
July 04, 2014, 08:26:22 PM
 #1086

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 Offline

Activity: 3780
Merit: 1060


View Profile
July 04, 2014, 08:28:43 PM
 #1087

Here's my bet that was sent at 17:45 but DirectBet said 17:52.

Quote
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 Offline

Activity: 117
Merit: 10


View Profile
July 04, 2014, 08:31:59 PM
 #1088

Here's my bet that was sent at 17:45 but DirectBet said 17:52.

Quote
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 Offline

Activity: 3780
Merit: 1060


View Profile
July 04, 2014, 08:36:38 PM
 #1089

Here's my bet that was sent at 17:45 but DirectBet said 17:52.

Quote
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 Offline

Activity: 1288
Merit: 1010



View Profile WWW
July 04, 2014, 08:38:25 PM
 #1090

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/f33f82da7e486509b45ab23b965b5ae789c5ae64cf1a08230249235562420fdc

When 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 :

Quote
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-wallet

You will not have these delays when using the official wallet.

uknohowwedo
Full Member
***
Offline Offline

Activity: 166
Merit: 100


View Profile
July 04, 2014, 08:39:41 PM
 #1091

wow really? im never using DB again if they dont fix this for you ts111 thats bogus
Rating Place
Legendary
*
Offline Offline

Activity: 3780
Merit: 1060


View Profile
July 04, 2014, 08:42:33 PM
 #1092

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
Sr. Member
****
Offline Offline

Activity: 252
Merit: 250


View Profile
July 04, 2014, 08:43:15 PM
 #1093

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 Offline

Activity: 117
Merit: 10


View Profile
July 04, 2014, 09:04:43 PM
 #1094

And just like that, DB disappears.

May be time to organize a boycott  Wink
DirectBet (OP)
Legendary
*
Offline Offline

Activity: 1288
Merit: 1010



View Profile WWW
July 04, 2014, 09:07:04 PM
 #1095

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 Offline

Activity: 117
Merit: 10


View Profile
July 04, 2014, 09:10:02 PM
 #1096

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 Offline

Activity: 3780
Merit: 1060


View Profile
July 04, 2014, 09:20:13 PM
 #1097

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 Offline

Activity: 117
Merit: 10


View Profile
July 04, 2014, 09:25:56 PM
 #1098

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 Offline

Activity: 117
Merit: 10


View Profile
July 04, 2014, 10:06:51 PM
 #1099

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 Offline

Activity: 1288
Merit: 1010



View Profile WWW
July 04, 2014, 10:13:58 PM
 #1100

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/f33f82da7e486509b45ab23b965b5ae789c5ae64cf1a08230249235562420fdc

As 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.

Quote
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.

Pages: « 1 ... 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 [55] 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 ... 506 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!