FUUCK ME **** ★No.1 BITCOIN BINARY OPTIONS ★HIGHEST REWARD 190%★1%

[adaseb]

Anybody knows what happens if a payment is sent without a miners reward? Does it still count as a valid trade or is it delayed until confirmed?

[joksim299]

Anybody knows what happens if a payment is sent without a miners reward? Does it still count as a valid trade or is it delayed until confirmed?

I think that it is valid entry and payout is delayed until it is confirmed.

[adaseb]

Anybody knows what happens if a payment is sent without a miners reward? Does it still count as a valid trade or is it delayed until confirmed?

I think that it is valid entry and payout is delayed until it is confirmed.

So as long as 10000 Sats is sent as a miners reward it should eventually count as a bet?

[adaseb]

There I think is a bug somewhere regarding the USDCHF bets.

Here is the transaction ID:
https://blockchain.info/tx/73d006fabdfc5057092ddd5e1c6bfae58a9517599a68d8b5969391d63d3c4b65


This bet was suppose to be registered at 21:59:34 according to the blockchain but it was first delayed for 2 minutes (see the photo attached as 'correct bet') and later it was requoted a losing time and losing value. 0.97225 was the winning bet but was requotted to 0.97234 which ended up being a loss.

The broker I used to verify the quotes is Dukascopy.

1) Why are the bets delayed so long? 2 minute delay is unacceptable.

2) Why do winnings bets get requoted to become losing bets?






EDIT------------------------------------------------

This isn't my bet but someone placed an EURUSD bet Up at 22:25:04

https://blockchain.info/tx/efc9fa256a5aa545f52f6e3639cbb4c0010b2d0aeee499589d378bb153340576


This bet however wasn't registered on the site until 1 minute and 4 seconds later.

http://secondstrade.com/tx.jsp?tx=efc9fa256a5aa545f52f6e3639cbb4c0010b2d0aeee499589d378bb153340576


This one turned out to be a winner.


This same user placed a similar bet about 10 minutes prior.

https://blockchain.info/tx/7d91d2df3824fb792f264cfaa9a8c18dad1d32eeb8524221bb7ec774eb9aaafd

BTC was sent at 22:16:54 and it was registered at your website 2 seconds later at 22:16:56

http://secondstrade.com/tx.jsp?tx=7d91d2df3824fb792f264cfaa9a8c18dad1d32eeb8524221bb7ec774eb9aaafd



So why is it that some bets aren't delayed, while others are delayed by up to 2 minutes and why are some bets requotted?

[secondstrade.com]

There I think is a bug somewhere regarding the USDCHF bets.

Here is the transaction ID:
https://blockchain.info/tx/73d006fabdfc5057092ddd5e1c6bfae58a9517599a68d8b5969391d63d3c4b65


This bet was suppose to be registered at 21:59:34 according to the blockchain but it was first delayed for 2 minutes (see the photo attached as 'correct bet') and later it was requoted a losing time and losing value. 0.97225 was the winning bet but was requotted to 0.97234 which ended up being a loss.

The broker I used to verify the quotes is Dukascopy.

1) Why are the bets delayed so long? 2 minute delay is unacceptable.

2) Why do winnings bets get requoted to become losing bets?


EDIT------------------------------------------------

This isn't my bet but someone placed an EURUSD bet Up at 22:25:04

https://blockchain.info/tx/efc9fa256a5aa545f52f6e3639cbb4c0010b2d0aeee499589d378bb153340576


This bet however wasn't registered on the site until 1 minute and 4 seconds later.

http://secondstrade.com/tx.jsp?tx=efc9fa256a5aa545f52f6e3639cbb4c0010b2d0aeee499589d378bb153340576


This one turned out to be a winner.


This same user placed a similar bet about 10 minutes prior.

https://blockchain.info/tx/7d91d2df3824fb792f264cfaa9a8c18dad1d32eeb8524221bb7ec774eb9aaafd

BTC was sent at 22:16:54 and it was registered at your website 2 seconds later at 22:16:56

http://secondstrade.com/tx.jsp?tx=7d91d2df3824fb792f264cfaa9a8c18dad1d32eeb8524221bb7ec774eb9aaafd



So why is it that some bets aren't delayed, while others are delayed by up to 2 minutes and why are some bets requotted?

hi?
1)
Bet time is when the payment transaction is received by our wallets.
In most cases, the time is less than a second.
However, due to the problem of bit coin network itself may take a long time.

There may be a variety of reasons. We'll check it  more detail.
2)
The result of the game is determined by the price of this bet time and  the price of expiry time .
which is not requoted.  if the expiry time is 1 minute ,  the price will be price of  1 minutes after betting time

thank you.

[adaseb]

There I think is a bug somewhere regarding the USDCHF bets.

Here is the transaction ID:
https://blockchain.info/tx/73d006fabdfc5057092ddd5e1c6bfae58a9517599a68d8b5969391d63d3c4b65


This bet was suppose to be registered at 21:59:34 according to the blockchain but it was first delayed for 2 minutes (see the photo attached as 'correct bet') and later it was requoted a losing time and losing value. 0.97225 was the winning bet but was requotted to 0.97234 which ended up being a loss.

The broker I used to verify the quotes is Dukascopy.

1) Why are the bets delayed so long? 2 minute delay is unacceptable.

2) Why do winnings bets get requoted to become losing bets?


EDIT------------------------------------------------

This isn't my bet but someone placed an EURUSD bet Up at 22:25:04

https://blockchain.info/tx/efc9fa256a5aa545f52f6e3639cbb4c0010b2d0aeee499589d378bb153340576


This bet however wasn't registered on the site until 1 minute and 4 seconds later.

http://secondstrade.com/tx.jsp?tx=efc9fa256a5aa545f52f6e3639cbb4c0010b2d0aeee499589d378bb153340576


This one turned out to be a winner.


This same user placed a similar bet about 10 minutes prior.

https://blockchain.info/tx/7d91d2df3824fb792f264cfaa9a8c18dad1d32eeb8524221bb7ec774eb9aaafd

BTC was sent at 22:16:54 and it was registered at your website 2 seconds later at 22:16:56

http://secondstrade.com/tx.jsp?tx=7d91d2df3824fb792f264cfaa9a8c18dad1d32eeb8524221bb7ec774eb9aaafd



So why is it that some bets aren't delayed, while others are delayed by up to 2 minutes and why are some bets requotted?

hi?
1)
Bet time is when the payment transaction is received by our wallets.
In most cases, the time is less than a second.
However, due to the problem of bit coin network itself may take a long time.

There may be a variety of reasons. We'll check it  more detail.
2)
The result of the game is determined by the price of this bet time and  the price of expiry time .
which is not requoted.  if the expiry time is 1 minute ,  the price will be price of  1 minutes after betting time

thank you.

Did you even read/look at what I posted?

The bet was registered at 22:01:31, and then another bet was registered at 22:02:23, there was only 1 transaction for USDCHF in that timeframe.

So there are 2 bets but only 1 transaction. This is clearly a bug.

I'm not talking about the delay, I know its normal for there to be delays.

[ndnh]

Did you even read/look at what I posted?

The bet was registered at 22:01:31, and then another bet was registered at 22:02:23, there was only 1 transaction for USDCHF in that timeframe.

So there are 2 bets but only 1 transaction. This is clearly a bug.

I'm not talking about the delay, I know its normal for there to be delays.

I think either you use bc wallet or the site relies on blockchain.info as the block explorer.

If it does, here is what happened:
1. When you sent a transaction to the secondstrade USDCHF up, two transactions were created (In my bc wallet since 2 days ago many transactions are made twice (both receiving and sending ones) and eventually one will vanish. this error happens only with blockchain.info block explorer which is why I consider it very unreliable.)
2. So both the bets were actually yours.
3. One of the transactions, the first one of course was accepted by all nodes and was entered into blockchain, while the second was rejected though it would show up in that explorer for a couple of blocks.
4. secondstrade accepted both bets, and played both. But if the second bet was a win, it would wait for a confirmation which would never happen. Making the first original bet the only valid one.

tl'dr there is no problem on the server end, at least regarding this particular event.

[adaseb]

Did you even read/look at what I posted?

The bet was registered at 22:01:31, and then another bet was registered at 22:02:23, there was only 1 transaction for USDCHF in that timeframe.

So there are 2 bets but only 1 transaction. This is clearly a bug.

I'm not talking about the delay, I know its normal for there to be delays.

I think either you use bc wallet or the site relies on blockchain.info as the block explorer.

If it does, here is what happened:
1. When you sent a transaction to the secondstrade USDCHF up, two transactions were created (In my bc wallet since 2 days ago many transactions are made twice (both receiving and sending ones) and eventually one will vanish. this error happens only with blockchain.info block explorer which is why I consider it very unreliable.)
2. So both the bets were actually yours.
3. One of the transactions, the first one of course was accepted by all nodes and was entered into blockchain, while the second was rejected though it would show up in that explorer for a couple of blocks.
4. secondstrade accepted both bets, and played both. But if the second bet was a win, it would wait for a confirmation which would never happen. Making the first original bet the only valid one.

tl'dr there is no problem on the server end, at least regarding this particular event.

No I use the Bitcoin Core - Wallet on my desktop. I read a few posts earlier that the blockchain online wallet is not reliable.

What if the first bet is a win but the second bet is a lose?

[coinableS]

Did you even read/look at what I posted?

The bet was registered at 22:01:31, and then another bet was registered at 22:02:23, there was only 1 transaction for USDCHF in that timeframe.

So there are 2 bets but only 1 transaction. This is clearly a bug.

I'm not talking about the delay, I know its normal for there to be delays.

I think either you use bc wallet or the site relies on blockchain.info as the block explorer.

If it does, here is what happened:
1. When you sent a transaction to the secondstrade USDCHF up, two transactions were created (In my bc wallet since 2 days ago many transactions are made twice (both receiving and sending ones) and eventually one will vanish. this error happens only with blockchain.info block explorer which is why I consider it very unreliable.)
2. So both the bets were actually yours.
3. One of the transactions, the first one of course was accepted by all nodes and was entered into blockchain, while the second was rejected though it would show up in that explorer for a couple of blocks.
4. secondstrade accepted both bets, and played both. But if the second bet was a win, it would wait for a confirmation which would never happen. Making the first original bet the only valid one.

tl'dr there is no problem on the server end, at least regarding this particular event.

No I use the Bitcoin Core - Wallet on my desktop. I read a few posts earlier that the blockchain online wallet is not reliable.

What if the first bet is a win but the second bet is a lose?

Same thing happened to me, it's the malleability attack. The only one that should matter is the transaction that gets confirmed. I lost my bet so I can't tell you for sure though, haha    Anyways I'm going to hold off on playing during this attack.

[ndnh]

What if the first bet is a win but the second bet is a lose?

Usually it is the first tx (the one that appeared first before being pushed down to second on the pic) that is valid and the one that goes through. Whatever happens to the first bet or with the txid that shows up in your wallet (in bc wallet both show up) is the real one. If it wins, it is a win, if it is a lose, it is a lose. Ignore the other one.

Edit: Whatever happens to the one labelled "correct bet". The other one (top one on the image) is the one that was created and rejected as duplicate.

In fact, if you check other sites like Directbet many bets got two bets from a single tx. It is there in many sites and not just in secondstrade. Hopefully it is been there since just 2 days and it should go away soon.


Edit2: Updated my info.
Any one of the two could be confirmed or rejected. The transaction resulting from the malleability attack is also capable of being confirmed, but only one would of course.

[adaseb]

What if the first bet is a win but the second bet is a lose?

Usually it is the first tx (the one that appeared first before being pushed down to second on the pic) that is valid and the one that goes through. Whatever happens to the first bet or with the txid that shows up in your wallet (in bc wallet both show up) is the real one. If it wins, it is a win, if it is a lose, it is a lose. Ignore the other one.

Edit: Whatever happens to the one labelled "correct bet". The other one (top one on the image) is the one that was created and rejected as duplicate.

In fact, if you check other sites like Directbet many bets got two bets from a single tx. It is there in many sites and not just in secondstrade. Hopefully it is been there since just 2 days and it should go away soon.

However this isn't my case. The 2nd bet "loser" is the one that counted and the 1st bet "winner" I never got paid for.

When I look up the trans ID it is directed to the 2nd bet.

So there is nothing that the admin can do to prevent this? Since its a bitcoin node problem?

[ndnh]

However this isn't my case. The 2nd bet "loser" is the one that counted and the 1st bet "winner" I never got paid for.

When I look up the trans ID it is directed to the 2nd bet.

So there is nothing that the admin can do to prevent this? Since its a bitcoin node problem?

hehe sorry. It could happen both ways. But all the three times I experienced it was when the txid I created got confirmed and the fake tx got rejected, so I assumed it is incapable of being getting confirmed.

Edited that post.

I don't know if it can be prevented by switching to another API, since block explorers like btc.blockr.io (the one I use) either doesn't show it or immediately rejects it after 1 conf. Most likely nope.

[ndnh]

Quoting a post here, because it answers some questions.

First I would like to clarify that this problem is not in our system but rather a general Bitcoin network problem where duplicated conflicted transactions are being broadcasted.

You will notice that one of the transaction will confirm by the Bitcoin network normally and the other one will be canceled.

Simply ignore the duplicated canceled transaction. It will never confirm by the Bitcoin network and no funds will be deducted from your wallet for it.
Consequently no payout will be issued for the duplicated canceled bet transfer.

So the bottom line is, you can continue and bet normally and ignore the unreal duplicated conflicted transactions.

[secondstrade.com]

Quoting a post here, because it answers some questions.

First I would like to clarify that this problem is not in our system but rather a general Bitcoin network problem where duplicated conflicted transactions are being broadcasted.

You will notice that one of the transaction will confirm by the Bitcoin network normally and the other one will be canceled.

Simply ignore the duplicated canceled transaction. It will never confirm by the Bitcoin network and no funds will be deducted from your wallet for it.
Consequently no payout will be issued for the duplicated canceled bet transfer.

So the bottom line is, you can continue and bet normally and ignore the unreal duplicated conflicted transactions.

thank you for your good answer.

[lemipawa]

I just won 50,000 Satoshis in this game 
The game is very easy. The only troubel with this game is the confirmation of the transaction which is not the sites fault but over all, game is nice 
http://secondstrade.com/tx.jsp?tx=8bcd4a5c9d2765274b0e0ee19bf67fa1560663ecfc2485cd82ecaebafd5e4850

[secondstrade.com]

I just won 50,000 Satoshis in this game 
The game is very easy. The only troubel with this game is the confirmation of the transaction which is not the sites fault but over all, game is nice 
http://secondstrade.com/tx.jsp?tx=8bcd4a5c9d2765274b0e0ee19bf67fa1560663ecfc2485cd82ecaebafd5e4850

thank you for your good comment. we will  keep trying to make the better site.
and congratulation your win.
thank you.

[adaseb]

I've been placing multiple bets and haven't gotten the error since. Regarding execution time about 20% of all my bets are executed about 30-60 seconds later then they should be which results in losing results.

Anyway to fix this error?

[secondstrade.com]

I've been placing multiple bets and haven't gotten the error since. Regarding execution time about 20% of all my bets are executed about 30-60 seconds later then they should be which results in losing results.

Anyway to fix this error?

hi?  if you use wallet of blockchain.info, there are these dalay issues.
so, we recommend Bitcoin-QT/Bitcoind, MultiBit, Armory, Electrum, Android bitcoin wallet.

thank you.

[lemipawa]

Hi secondstrade
Can you check this 2 transactions please
Looks like they are stuck waiting for confirmation but upon looking at the transaction ID, they already have 5 confirmations as I write this post and no payment yet from your site

http://secondstrade.com/tx.jsp?tx=35cc2c1be93e547cbcd9f916f202fb0c92fdd4f86d878b54d977127056c98813
http://secondstrade.com/tx.jsp?tx=f2c9f8493efa300ba25ad7ff713fc77b4c35ec03ce38dde5f81273c2ad4fb001

[everaja]

Hi secondstrade
Can you check this 2 transactions please
Looks like they are stuck waiting for confirmation but upon looking at the transaction ID, they already have 5 confirmations as I write this post and no payment yet from your site

http://secondstrade.com/tx.jsp?tx=35cc2c1be93e547cbcd9f916f202fb0c92fdd4f86d878b54d977127056c98813
http://secondstrade.com/tx.jsp?tx=f2c9f8493efa300ba25ad7ff713fc77b4c35ec03ce38dde5f81273c2ad4fb001

I guess the payout has already been released by Secondstrade:
1. https://blockchain.info/tx/56b4a0a551c4870891a6473919b96884f21b34e3f34786f138bf5cbd302b7df4
2. https://blockchain.info/tx/9c0a194399ee5690caf0a74ddf8462ea494175c024b6ba3a2689e41af8d5c18b

It generally takes few minutes to send the transaction when the hot wallet is empty ,else Transactions are quick.