this is one of the reasons why i doubted secondstrade.
the wallet address 3M4pL5fqMsHYiCunNwfp6Ned9A2hVEMHTE
place a bet on seconds trade down and have won its bet.
txid of the bet is
63b6a5734afa06e29e417a0f73f188b41efa1b07a2ccd95b1d3502ec9f71bf24
check this out
http://secondstrade.com/tx.jsp?tx=63b6a5734afa06e29e417a0f73f188b41efa1b07a2ccd95b1d3502ec9f71bf24Betting Transaction id : 63b6a5734afa06e29e417a0f73f188b41efa1b07a2ccd95b1d3502ec9f71bf24
Betting address : 39rXZdDf4CPqWrXAWRweKzXoJ76XFRUxSL
Betting asset : SECONDS5 DOWN
Betting BTC : 0.0499
Start date : 2015-10-14T04:27:03
Start date(miliseconds) : 1444796823529
Prediction end date : 2015-10-14T04:27:08
Prediction end date(miliseconds) : 1444796828536
Real end date : 2015-10-14T04:27:09
Real end date(miliseconds) : 1444796829119
Betting price : 2
Betting expire price : 2
Betting start seed : 4:27:2:968+253.01+9+1.13878
Betting start seed convert SHA256: 2892985e65c16cf384ebd061fec85fba721373303b448bc89ce5f48319c2fcf1
Betting expire seed : 4:27:8:969+253.08+4+1.13878
Betting expire seed convert SHA256: d215eecd758a2316441a96e9f191cddd57fba4f1023851e0279bf3e536396def
Result : WIN
Prize : 1.8
Payout BTC : 0.08982
WIN Payout Transactiond id : b94875a5a767716943ee2972e006dd4f1f5e2ba7b72529da40ec4ee98dc1389c
lol
behind the fact that the wallet address 3M4pL5fqMsHYiCunNwfp6Ned9A2hVEMHTE was the one send the bet and had won,
secondstrade.com recognize the wallet address 39rXZdDf4CPqWrXAWRweKzXoJ76XFRUxSL insteed and send the payout too.
leaving away wallet address 3M4pL5fqMsHYiCunNwfp6Ned9A2hVEMHTE with nothing on expected payout.
what kind of trick secondstrade.com brouhgt to players? you can even check in blockchain
that the said payment was spent by wallet address 39rXZdDf4CPqWrXAWRweKzXoJ76XFRUxSL,
the who secondstrade recognize to receive payout since it didnt make any bet on secondstrade down.
not even a single bet since and that's unacceptable.
hi? it have some misunderstanding. i think 39rXZdDf4CPqWrXAWRweKzXoJ76XFRUxSL is also yours.
evidence 1. you sent it by the way Pay to script hash (P2SH) transactions (
https://en.bitcoin.it/wiki/Pay_to_script_hash).
Bitcoin P2SH addresses always start with 3 not 1. your address is start with 3. and 39rXZdDf4CPqWrXAWRweKzXoJ76XFRUxSL also is start with 3.
any address of secondstrade is not start with 3.
evidence 2. All transaction is connected with chain.
you can see the transaction prior to
https://www.blocktrail.com/BTC/tx/63b6a5734afa06e29e417a0f73f188b41efa1b07a2ccd95b1d3502ec9f71bf24?txinIdx=0 the transaction is
https://www.blocktrail.com/BTC/tx/66e5c22415d7fb05fb5eeb331ea5ba84274b60c7a505cac6ae9184306d70aa1b?txoutIdx=1on this transaction,
3PMCzumhQZvkWaqiWQoa8Q4fxmLEQempJ7(0.48615359) ->
39rXZdDf4CPqWrXAWRweKzXoJ76XFRUxSL(0.43610717)
3M4pL5fqMsHYiCunNwfp6Ned9A2hVEMHTE(0.05000000)
at this time, 39rXZdDf4CPqWrXAWRweKzXoJ76XFRUxSL is appeared. until that time, this transaction is no any relation with secondstrade.
we don't know why is the address showed different with other block explorer yet. we will check it .
but the address is also yours.
thank you.
this information below was from your instructions by clicking "HOW TO PLAY"
How to check the result of the past betting
if you want to show the result of your bet, as soon as you bet, you can show by clicking Transaction bar on the left side.
but there are only 20 transactions.
so if you want to know the result of above 20 transactions, you can use
http://secondstrade.com/tx.jsp?tx="your betting id".
if your transaction id is "262729c0deb5b570ab7846c76a82d2a845b04117998dd3f9df1e381f24558e4b" ,
you have to only enter
http://secondstrade.com/tx.jsp?tx=262729c0deb5b570ab7846c76a82d2a845b04117998dd3f9df1e381f24558e4bon the internet address bar like below
What happen was btc wallet address 3M4pL5fqMsHYiCunNwfp6Ned9A2hVEMHTE place a bet on 5seconds down with a txid
63b6a5734afa06e29e417a0f73f188b41efa1b07a2ccd95b1d3502ec9f71bf24. according to your instruction on how to check bet
is to enter
http://secondstrade.com/tx.jsp?tx="your betting id" so this will now
http://secondstrade.com/tx.jsp?tx=63b6a5734afa06e29e417a0f73f188b41efa1b07a2ccd95b1d3502ec9f71bf24 and when checking i noticed that a
different wallet with address 39rXZdDf4CPqWrXAWRweKzXoJ76XFRUxSL appears replacing the real wallet 3M4pL5fqMsHYiCunNwfp6Ned9A2hVEMHTE that actually who bet. this will now look like this.
Betting Transaction id : 63b6a5734afa06e29e417a0f73f188b41efa1b07a2ccd95b1d3502ec9f71bf24
Betting address : 39rXZdDf4CPqWrXAWRweKzXoJ76XFRUxSL
Betting asset : SECONDS5 DOWN
Betting BTC : 0.0499
Start date : 2015-10-14T04:27:03
Start date(miliseconds) : 1444796823529
Prediction end date : 2015-10-14T04:27:08
Prediction end date(miliseconds) : 1444796828536
Real end date : 2015-10-14T04:27:09
Real end date(miliseconds) : 1444796829119
Betting price : 2
Betting expire price : 2
Betting start seed : 4:27:2:968+253.01+9+1.13878
Betting start seed convert SHA256: 2892985e65c16cf384ebd061fec85fba721373303b448bc89ce5f48319c2fcf1
Betting expire seed : 4:27:8:969+253.08+4+1.13878
Betting expire seed convert SHA256: d215eecd758a2316441a96e9f191cddd57fba4f1023851e0279bf3e536396def
Result : WIN
Prize : 1.8
Payout BTC : 0.08982
WIN Payout Transactiond id : b94875a5a767716943ee2972e006dd4f1f5e2ba7b72529da40ec4ee98dc1389c
lol
this error leaves the wallet address 3M4pL5fqMsHYiCunNwfp6Ned9A2hVEMHTE with nothing.
showing a transaction prior to the bet made dosent prove that two wallets where owned by single person and even they do, secondstrade should never send to any address by just predicting that someones wallet address belongs to anybody. the nature of btc was somebody have to send somebody whoever we are were sending anonymously.
saying this two wallet was owned by a single person is irrelevant. even a million times those two wallets transacted each other
secondstrade has no envolvement to that and showing that as to be the evidence is ridiculous. payment should reach to the exact wallet address used in placing a winning bet, correct me if im wrong on that.
i personaly requested secondstrade.com to refund the bet including winning to this syastem error of his
thanks for your reply on above's
Show Posts
