 Show Posts
|
|
Pages: [1]
|
|
username: cclairejune8
thanks
|
|
|
|
|
what can you say about that last post, is it still normal? i knew it, something's fishy going on here!!
oh my god admin, when will this be perfect?
sad thing about errors were you either end up to a normal transactions behind those errors or a refund that takes days
of waiting and waiting and waiting. i wasnt refunded so my case was worst of all. lol to myself, im like an idiot who waits for nothing.....
|
|
|
|
hi? everyone ?
we deleted millisecond of seed value on dice game (5 seconds, 7seconds,Odd-Even) now.
please refer to the invest.
thank you.
thanks that these milis where gone, hopefully for the better, behind the fact that im also part of who fights for a fair gaming here, my bitcoins were still not on my position. admin, i ask you to ps return what i ask for. changing these rules means that you also admit the errors were caused by that. refund me 1 btc will be enough to finish all this. im tired of waiting, i wanna play again when you pay me, right away.. |
|
|
|
|
on the other hand, i will wait forever then until admin will calm down and admit that he should return my 1.5 bitcoins.
i will ask the advice in every forum talking bitcoins, and will soon see you personally on this actions..
how about we will talk in person all of us, we can afford a flight to admins place and country, this would a slap on our fce to crypto world that even a simple idea of how time was kept, we have no knowledge on it and yet continue on this...
|
|
|
|
|
i will be satisfied of such explanations if i will be refunded on my 1.5 btc request which was a very small amount compared to what we will be dealing in future because my team and i will continue gambling here and will not stop until you admin will got this perfect, that s the way we support our admin, if in that case he or you respect what we asked JUST A SIMPLE 1.5 BITCOINS REFUNDS . IM STILL WAITING ON THOSE RIGHT DECISIONS as we the supporter of your site!! god bless us all
|
|
|
|
|
im next if you're all done,
mine was denied by admin but i did submit explanations for reconsiderations,
hope admin will study why my requests were legitimate for refunds.
|
|
|
|
hi again,
i would like to clarify on what you said.
at the time of my betting, bet that were requested payout to reduced to refunds.
you said through a post that these seven transactions have different time in
mili secends and during that time your start ad expire seed sha 256 convert
included miliseconds on it. right? in these cases, i want you to explain on
your post that you say this:
''If Start date different with millisecond, the result can be different.
This is normal process. Thank you.''
thats right! i agree on that, as a matter of fact, your system converted txids
by this format:
Betting start seed : 12:33:31:373+225.41+5+1.12609.
the ''373'' was the mili sec on all txids
using a sha 256 calculator?generator, they all end up identically on
Betting start seed convert SHA256:
''ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258''
and thats because they have the same start date mili seconds used which was ''373''
when this miliseconds were changed, the seed convert sha 256 result will change too.
so.. if the start seed convert 256 of all seven txids is:
''ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258'', it is
because they were generated by sha 256 using this value:
Betting start seed : 12:33:31:373+225.41+5+1.12609
and even one single character will be added, changed or erased, it will never have
''ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258'', as result.
it would be other that that.
due to this reasons above, i will challenge you to post at bitcointalk.org even one of
these txids, to show to us, that will have a different start miliseconds than''373''
that will come up to same Betting start seed convert SHA256 to:
''ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258'',
im sure in any possible way of having a solution that you cant.
im done explaining admin, and i want you to pay me the refund that ive requested
1.5 BITCOINS in all
thanks
as you can see on 4 notice of http://secondstrade.com/notice.html there is a batch program that deal with incoming orders at a same time every seconds. because start date times of the all 7 are different, real end date also will be different. so, although 7 transaction have same betting start seed, the betting expire seed of the next 3 transaction was deal with by the next second process with differing 4 transaction. it was very normal. it can not be refunded. thank you. at 12:33:31:373 on that day was the time 7 bets were recognized, so they belong to the same batch, a reminder to us all that these batch program rule of yours were added on times that there were too many refunds requested on different players. that these program of yours were hidden to us and your the only one who knows this bogus program of batching. the volume of transactions on your site were too small to segregate bets to batches. to show to everyone that you insisted that these 7 transactions were different in their start date which were not true, for this purpose, look closely the time your syatem used, time where identical, if its really not, then an error occur and its a refund case.. 1--cd1e79cce21a481a77d4bd3374a29803c05698275752a70c2b149d20355fbd50 w Betting start seed : 12:33:31:373+225.41+5+1.12609 2--59b042e01cc1d2731a31ff83e26a346a2f8ed61f1fc389ef90554b3b8cf81f05 w Betting start seed : 12:33:31:373+225.41+5+1.12609 3--139ea51372cd85168edac4663b4ea7f7319d4212d12f8c6021a005fb1cf555ab w Betting start seed : 12:33:31:373+225.41+5+1.12609 4--d75c7ce0f62b36c87f5e6909a47dada605e1a93deed714b53ad236d57376eac0 w Betting start seed : 12:33:31:373+225.41+5+1.12609 5-- 42d2b5160270dce1d3612af0d17d0741495bd4d7dc1f55f5eff60756f45f1bd0 L Betting start seed : 12:33:31:373+225.41+5+1.12609 6 -59dc2ebd494123c80d77d18d85517b80212b7c17a7023ccfd0d7a77ac4d2ea32 L Betting start seed : 12:33:31:373+225.41+5+1.12609 7-- 6d88d873ee116c06a0528afcdfbe830cb0f7c866f10dc39be939c57e5d60db3b L Betting start seed : 12:33:31:373+225.41+5+1.12609 if you insist that last 3 txids belong to other date than 12:33:31:373 on that day, then this whole process were all lies and manipulations. 12:33:31:373 on that day was used on all txids. if this were error on your system if times were different so the rule will be applied, RULE 5. Every bet due to system itself problem will be refunded. pperform the refunds as requested. 1.5 bitcoins, thanks |
|
|
|
|
hi again,
i would like to clarify on what you said.
at the time of my betting, bet that were requested payout to reduced to refunds.
you said through a post that these seven transactions have different time in
mili secends and during that time your start ad expire seed sha 256 convert
included miliseconds on it. right? in these cases, i want you to explain on
your post that you say this:
''If Start date different with millisecond, the result can be different.
This is normal process. Thank you.''
thats right! i agree on that, as a matter of fact, your system converted txids
by this format:
Betting start seed : 12:33:31:373+225.41+5+1.12609.
the ''373'' was the mili sec on all txids
using a sha 256 calculator?generator, they all end up identically on
Betting start seed convert SHA256:
''ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258''
and thats because they have the same start date mili seconds used which was ''373''
when this miliseconds were changed, the seed convert sha 256 result will change too.
so.. if the start seed convert 256 of all seven txids is:
''ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258'', it is
because they were generated by sha 256 using this value:
Betting start seed : 12:33:31:373+225.41+5+1.12609
and even one single character will be added, changed or erased, it will never have
''ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258'', as result.
it would be other that that.
due to this reasons above, i will challenge you to post at bitcointalk.org even one of
these txids, to show to us, that will have a different start miliseconds than''373''
that will come up to same Betting start seed convert SHA256 to:
''ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258'',
im sure in any possible way of having a solution that you cant.
im done explaining admin, and i want you to pay me the refund that ive requested
1.5 BITCOINS in all
thanks
|
|
|
|
in addition to my posts, all 7 transactions do have the same start seed value generated by sha 256.
this value is ''ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258''
if the txids with the same sha 256 generation on the same bet type should always be in the exact the same end seed value as generated by sha256.
1--cd1e79cce21a481a77d4bd3374a29803c05698275752a70c2b149d20355fbd50 w
2--59b042e01cc1d2731a31ff83e26a346a2f8ed61f1fc389ef90554b3b8cf81f05 w
3--139ea51372cd85168edac4663b4ea7f7319d4212d12f8c6021a005fb1cf555ab w
4--d75c7ce0f62b36c87f5e6909a47dada605e1a93deed714b53ad236d57376eac0 w
5-- 42d2b5160270dce1d3612af0d17d0741495bd4d7dc1f55f5eff60756f45f1bd0 L
6 -59dc2ebd494123c80d77d18d85517b80212b7c17a7023ccfd0d7a77ac4d2ea32 L
7-- 6d88d873ee116c06a0528afcdfbe830cb0f7c866f10dc39be939c57e5d60db3b L
all txid have the same seed value on sha 256 which is the value below
''ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258''
in conclusion, they should have the same and exact result.
i have a mssg to you admin in chat scrollback regarding my request that i wouuld like to have an agreement to change the payout request to a refund request as i read most of the thread that errors are only have to end to refunds if the error was due to system of yours. its only possible if you will also agree being the admin, 2.7 btc will now be reduced to 1.5 btc refunds request. kindly resolve this cases to move on.... |
|
|
|
|
in addition to my posts, all 7 transactions do have the same start seed value generated by sha 256.
this value is ''ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258''
if the txids with the same sha 256 generation on the same bet type should always be in the exact the same end seed value as generated by sha256.
1--cd1e79cce21a481a77d4bd3374a29803c05698275752a70c2b149d20355fbd50 w
2--59b042e01cc1d2731a31ff83e26a346a2f8ed61f1fc389ef90554b3b8cf81f05 w
3--139ea51372cd85168edac4663b4ea7f7319d4212d12f8c6021a005fb1cf555ab w
4--d75c7ce0f62b36c87f5e6909a47dada605e1a93deed714b53ad236d57376eac0 w
5-- 42d2b5160270dce1d3612af0d17d0741495bd4d7dc1f55f5eff60756f45f1bd0 L
6 -59dc2ebd494123c80d77d18d85517b80212b7c17a7023ccfd0d7a77ac4d2ea32 L
7-- 6d88d873ee116c06a0528afcdfbe830cb0f7c866f10dc39be939c57e5d60db3b L
all txid have the same seed value on sha 256 which is the value below
''ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258''
in conclusion, they should have the same and exact result.
|
|
|
|
due to no sleep while reading older posts and comparing those to mine, i accidentally paste differently as do it manually transferring it from my table-type records to your format. but its an honest mistake that doesn't chance the sense of the requests and results of your seeds were untouched. these were the corrected reposts i'm still waiting for you to pay me out. i apologist for the previous post.
-------------------------WIN
Betting Transaction id : cd1e79cce21a481a77d4bd3374a29803c05698275752a70c2b149d20355fbd50
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.49927
Betting price : 2
Betting expire price : 0
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:36:595+225.41+7+1.12629
Betting expire seed convert SHA256: 0dc3a9f403294f99cfdbe4ebc616745dc032f2c41d35fa664d42b9bcee708a12
Betting Transaction id : 59b042e01cc1d2731a31ff83e26a346a2f8ed61f1fc389ef90554b3b8cf81f05
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 0
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:36:595+225.41+7+1.12629
Betting expire seed convert SHA256: 0dc3a9f403294f99cfdbe4ebc616745dc032f2c41d35fa664d42b9bcee708a12
Betting Transaction id : 139ea51372cd85168edac4663b4ea7f7319d4212d12f8c6021a005fb1cf555ab
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 0
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:36:595+225.41+7+1.12629
Betting expire seed convert SHA256: 0dc3a9f403294f99cfdbe4ebc616745dc032f2c41d35fa664d42b9bcee708a12
Betting Transaction id : d75c7ce0f62b36c87f5e6909a47dada605e1a93deed714b53ad236d57376eac0
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 0
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:36:595+225.41+7+1.12629
Betting expire seed convert SHA256: 0dc3a9f403294f99cfdbe4ebc616745dc032f2c41d35fa664d42b9bcee708a12
----------------------------------------------LOST
Betting Transaction id : 42d2b5160270dce1d3612af0d17d0741495bd4d7dc1f55f5eff60756f45f1bd0
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 9
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:37:622+225.41+0+1.12632
Betting expire seed convert SHA256: 932b6b6233b7c8b5ccc29df61432dffade0d579b8eac1422f5666a6a7915a221
Betting Transaction id : 59dc2ebd494123c80d77d18d85517b80212b7c17a7023ccfd0d7a77ac4d2ea32
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 9
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:37:622+225.41+0+1.12632
Betting expire seed convert SHA256: 932b6b6233b7c8b5ccc29df61432dffade0d579b8eac1422f5666a6a7915a221
Betting Transaction id : 6d88d873ee116c06a0528afcdfbe830cb0f7c866f10dc39be939c57e5d60db3b
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 9
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:37:622+225.41+0+1.12632
Betting expire seed convert SHA256: 932b6b6233b7c8b5ccc29df61432dffade0d579b8eac1422f5666a6a7915a221
i know that you have a wide range of understanding, and continue to fullfill such request.
thank you.
hi? these transactions have different start date, so the betting expire seed of first 4 transactions and the next 3 transactions are also different. so the result of these all transactions is normal. this is not a refund case. below are your betting results. -------------------------WIN Betting Transaction id : cd1e79cce21a481a77d4bd3374a29803c05698275752a70c2b149d20355fbd50 Start date : 2015-08-27T12:33:31 Start date(miliseconds) : 1440678811400 ------------------------ Betting Transaction id : 59b042e01cc1d2731a31ff83e26a346a2f8ed61f1fc389ef90554b3b8cf81f05 Start date : 2015-08-27T12:33:31 Start date(miliseconds) : 1440678811472 ------------------------ Betting Transaction id : 139ea51372cd85168edac4663b4ea7f7319d4212d12f8c6021a005fb1cf555ab Start date : 2015-08-27T12:33:31 Start date(miliseconds) : 1440678811543 ------------------------ Betting Transaction id : d75c7ce0f62b36c87f5e6909a47dada605e1a93deed714b53ad236d57376eac0 Start date : 2015-08-27T12:33:31 Start date(miliseconds) : 1440678811619 覧覧覧覧覧覧覧覧覧覧覧有OST Betting Transaction id : 42d2b5160270dce1d3612af0d17d0741495bd4d7dc1f55f5eff60756f45f1bd0 Start date : 2015-08-27T12:33:31 Start date(milliseconds) : 1440678811718 覧覧覧覧覧覧 Betting Transaction id : 59dc2ebd494123c80d77d18d85517b80212b7c17a7023ccfd0d7a77ac4d2ea32 Start date : 2015-08-27T12:33:31 Start date(milliseconds) : 1440678811801 覧覧覧覧覧覧 Betting Transaction id : 6d88d873ee116c06a0528afcdfbe830cb0f7c866f10dc39be939c57e5d60db3b Start date : 2015-08-27T12:33:31 Start date(milliseconds) : 1440678811872 i will request for you to reconsider checking again to let you know that you were wrong if you tell that those three do have different start seed sha 256 generated. lets say that you were right on that you just said that these three transactions have different on those first four, i will ask you now to tell here in bitcointalk.org obout what would be the correct start seed value and the sha256 generated of them namely the txid below. 1-- 42d2b5160270dce1d3612af0d17d0741495bd4d7dc1f55f5eff60756f45f1bd0 2- -59dc2ebd494123c80d77d18d85517b80212b7c17a7023ccfd0d7a77ac4d2ea32 3-- 6d88d873ee116c06a0528afcdfbe830cb0f7c866f10dc39be939c57e5d60db3b be careful on this decision on telling that the seed of the last three above were different, your name and site are on the line here. i insist that you check these multiple times to avoid complications. i beg you to recheck admin secondstrade.com |
|
|
|
|
im confident, always be, since i started to gamble here. its normal to have errors on every sites. bugs, delays etc., may brought us all here. lucky for us to have support thats responsive and reasonable enough to go back checking on txids that were in past or months ago.
even i did posted something here with a little bit of mistake, i never change the value of the original shs256 generated result of that. no point of making edition as i know that the main records were on admins position. i did apologies to him on that.
let me show to all what was that posting error. here it was below
original results:
Betting Transaction id : 42d2b5160270dce1d3612af0d17d0741495bd4d7dc1f55f5eff60756f45f1bd0
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Start date : 2015-08-27T12:33:31
Start date(milliseconds) : 1440678811718
Prediction end date : 2015-08-27T12:33:36
Prediction end date(milliseconds) : 1440678816735
Real end date : 2015-08-27T12:33:37
Real end date(milliseconds) : 1440678817712
Betting price : 2
expire price: 9
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:37:622+225.41+0+1.12632
Betting expire seed convert SHA256: 932b6b6233b7c8b5ccc29df61432dffade0d579b8eac1422f5666a6a7915a221
Result : LOSE
Sorry buddy Sad
my old post was :
Betting Transaction id : 42d2b5160270dce1d3612af0d17d0741495bd4d7dc1f55f5eff60756f45f1bd0
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 9
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:36:595+225.41+7+1.12629
Betting expire seed convert SHA256: 932b6b6233b7c8b5ccc29df61432dffade0d579b8eac1422f5666a6a7915a221
my request was to pay me out of the transactions that happens to be 7 of them with identical start seed value, in which first four were winning while remaining 3 got lose. they picked up and went to a differenet end price so oviously as payout of those were never got into my wallet address 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE, im still witing for a payout until now.
0.5 per bet x 1.8 payout x 3 bets is 2.7 bitcoins were expected on txids
1-- 42d2b5160270dce1d3612af0d17d0741495bd4d7dc1f55f5eff60756f45f1bd0
2- -59dc2ebd494123c80d77d18d85517b80212b7c17a7023ccfd0d7a77ac4d2ea32
3-- 6d88d873ee116c06a0528afcdfbe830cb0f7c866f10dc39be939c57e5d60db3b
for the main reason of payout request to remind us all is that they should have the value to these four txids below that were winning as they have identical start seed value sha256 generated.
1--cd1e79cce21a481a77d4bd3374a29803c05698275752a70c2b149d20355fbd50
2--59b042e01cc1d2731a31ff83e26a346a2f8ed61f1fc389ef90554b3b8cf81f05
3--139ea51372cd85168edac4663b4ea7f7319d4212d12f8c6021a005fb1cf555ab
4--d75c7ce0f62b36c87f5e6909a47dada605e1a93deed714b53ad236d57376eac0
i wanna hear what will be admins answers to these as he said he finish checking on my address.
thats all
note:
that marked red number seven was the error on my previous post that was corrected already.
|
|
|
|
|
due to no sleep while reading older posts and comparing those to mine, i accidentally paste differently as do it manually transferring it from my table-type records to your format. but its an honest mistake that doesn't chance the sense of the requests and results of your seeds were untouched. these were the corrected reposts i'm still waiting for you to pay me out. i apologist for the previous post.
-------------------------WIN
Betting Transaction id : cd1e79cce21a481a77d4bd3374a29803c05698275752a70c2b149d20355fbd50
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.49927
Betting price : 2
Betting expire price : 0
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:36:595+225.41+7+1.12629
Betting expire seed convert SHA256: 0dc3a9f403294f99cfdbe4ebc616745dc032f2c41d35fa664d42b9bcee708a12
Betting Transaction id : 59b042e01cc1d2731a31ff83e26a346a2f8ed61f1fc389ef90554b3b8cf81f05
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 0
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:36:595+225.41+7+1.12629
Betting expire seed convert SHA256: 0dc3a9f403294f99cfdbe4ebc616745dc032f2c41d35fa664d42b9bcee708a12
Betting Transaction id : 139ea51372cd85168edac4663b4ea7f7319d4212d12f8c6021a005fb1cf555ab
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 0
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:36:595+225.41+7+1.12629
Betting expire seed convert SHA256: 0dc3a9f403294f99cfdbe4ebc616745dc032f2c41d35fa664d42b9bcee708a12
Betting Transaction id : d75c7ce0f62b36c87f5e6909a47dada605e1a93deed714b53ad236d57376eac0
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 0
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:36:595+225.41+7+1.12629
Betting expire seed convert SHA256: 0dc3a9f403294f99cfdbe4ebc616745dc032f2c41d35fa664d42b9bcee708a12
----------------------------------------------LOST
Betting Transaction id : 42d2b5160270dce1d3612af0d17d0741495bd4d7dc1f55f5eff60756f45f1bd0
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 9
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:37:622+225.41+0+1.12632
Betting expire seed convert SHA256: 932b6b6233b7c8b5ccc29df61432dffade0d579b8eac1422f5666a6a7915a221
Betting Transaction id : 59dc2ebd494123c80d77d18d85517b80212b7c17a7023ccfd0d7a77ac4d2ea32
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 9
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:37:622+225.41+0+1.12632
Betting expire seed convert SHA256: 932b6b6233b7c8b5ccc29df61432dffade0d579b8eac1422f5666a6a7915a221
Betting Transaction id : 6d88d873ee116c06a0528afcdfbe830cb0f7c866f10dc39be939c57e5d60db3b
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 9
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:37:622+225.41+0+1.12632
Betting expire seed convert SHA256: 932b6b6233b7c8b5ccc29df61432dffade0d579b8eac1422f5666a6a7915a221
i know that you have a wide range of understanding, and continue to fullfill such request.
thank you.
|
|
|
|
HI..
i noticed that there's an outrage player accusing you admin of something that negatively affects trust.
but instead of examining on to his complain, I decided to look upon my files containing copies of my transactions that I am also secondstrade 5secondsdown gambler who's going under a program on how to have control of my gambling after losing about 27 or more bitcoins here. responsible gambling was it.
my bitcoin wallet address used on betting s seconds down was 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE,
what i have noticed was theres some txid's, 7 of them in particular that were unusual. first of all this where received by seconds trade and registered to be with in his position after having 7 bets at the same time exactly.
as a matter of fact they have the same Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117f.
and if that were the case they should have the same Betting expire seed convert SHA256: 0dc3a9f403294f99cfdbe4ebc61674. at first four transaction they have identical results of course they were accepted at exact same time, then what happen after that was tragic. 3 consecutive lose bets came up but they even have the exact start time and start seed convert SHA256 of those first four that where winning bets.
syatem give different end seed convert sha 256 that after i noticed it now makes me so disappointed,
i lose all money on my gambling, it dosent matter now, what matters were i would like a full payout of the transactions that were obviously change resulting to a disaster damaging my bet and start losing it all.
here are the transaction id follows by secondstrade website's gave me as to verify bets were made.
win (4 bets)
cd1e79cce21a481a77d4bd3374a29803c05698275752a70c2b149d20355fbd50
59b042e01cc1d2731a31ff83e26a346a2f8ed61f1fc389ef90554b3b8cf81f05
139ea51372cd85168edac4663b4ea7f7319d4212d12f8c6021a005fb1cf555ab
d75c7ce0f62b36c87f5e6909a47dada605e1a93deed714b53ad236d57376eac0
lose ( 3 bets)
42d2b5160270dce1d3612af0d17d0741495bd4d7dc1f55f5eff60756f45f1bd0
59dc2ebd494123c80d77d18d85517b80212b7c17a7023ccfd0d7a77ac4d2ea32
6d88d873ee116c06a0528afcdfbe830cb0f7c866f10dc39be939c57e5d60db3b
3 lose bets that i would like to have full payout admin of secondstrade with 0.5 bitcoin each
0.5 x 3 x 1.8 = 2.7 bitcoins of payout you should send back to my wallet as requested.
-------------------------WIN
Betting Transaction id : cd1e79cce21a481a77d4bd3374a29803c05698275752a70c2b149d20355fbd50
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.49927
Betting price : 2
Betting expire price : 0
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:36:595+225.41+7+1.12629
Betting expire seed convert SHA256: 0dc3a9f403294f99cfdbe4ebc616745dc032f2c41d35fa664d42b9bcee708a12
Betting Transaction id : 59b042e01cc1d2731a31ff83e26a346a2f8ed61f1fc389ef90554b3b8cf81f05
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 0
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:36:595+225.41+7+1.12629
Betting expire seed convert SHA256: 0dc3a9f403294f99cfdbe4ebc616745dc032f2c41d35fa664d42b9bcee708a12
Betting Transaction id : 139ea51372cd85168edac4663b4ea7f7319d4212d12f8c6021a005fb1cf555ab
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 0
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:36:595+225.41+7+1.12629
Betting expire seed convert SHA256: 0dc3a9f403294f99cfdbe4ebc616745dc032f2c41d35fa664d42b9bcee708a12
Betting Transaction id : d75c7ce0f62b36c87f5e6909a47dada605e1a93deed714b53ad236d57376eac0
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 0
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:36:595+225.41+7+1.12629
Betting expire seed convert SHA256: 0dc3a9f403294f99cfdbe4ebc616745dc032f2c41d35fa664d42b9bcee708a12
----------------------------------------------LOST
Betting Transaction id : 42d2b5160270dce1d3612af0d17d0741495bd4d7dc1f55f5eff60756f45f1bd0
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 9
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:36:595+225.41+7+1.12629
Betting expire seed convert SHA256: 932b6b6233b7c8b5ccc29df61432dffade0d579b8eac1422f5666a6a7915a221
Betting Transaction id : 59dc2ebd494123c80d77d18d85517b80212b7c17a7023ccfd0d7a77ac4d2ea32
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 9
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:37:622+225.41+0+1.12632
Betting expire seed convert SHA256: 932b6b6233b7c8b5ccc29df61432dffade0d579b8eac1422f5666a6a7915a221
Betting Transaction id : 6d88d873ee116c06a0528afcdfbe830cb0f7c866f10dc39be939c57e5d60db3b
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 9
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:37:622+225.41+0+1.12632
Betting expire seed convert SHA256: 932b6b6233b7c8b5ccc29df61432dffade0d579b8eac1422f5666a6a7915a221
I repeat payout request of 2.7 bitcoins seriously requested as soon as posible admin.
this will proves that you really are fair and can always be trusted if you will soon make the pay out for all i ask
remember that I lose a lot of money but thats my destiny so im just claiming what was rightfully mine.
will you please reply to me here,
god bless you.
We are checking it now. So please wait some more. really appreciate that.. these were different from the request of others. i am asking for a PAYOUT, i believe that there's no need to check it deeper. bets were not even consecutively received by your system, they came in at the exactly the same time. if those first four bets i've sent have won it, as we were based on sha 256 generated, identical start seed should have identical end seed generation. if they were not, it violates probably fair gaming as its all in 5 sec down bet. Im not accusing you secondstrade that you did it or change it manually, who ever made that program might miss it or even if someone else manipulated it personally, the responsibility will always be yours. im saying this because as i read all post before posting mine, i feel and i believe that your a good man and every request were answered. there were players that were mad due to disappointment but you remain calm and respectful on every words. you maintain professionalism on your work. payouts on the other hand will be sent to my wallet after six confirmations and should have receive it long time ago. i asking you to prioritized this PAYOUT as early as possible, that's my request. 0.5 per bet x 1.8 payout x 3 bets is 2.7 bitcoins were expected as early as possible hoping that im having myself a ''well - explained request''. thank you secondstrade.com |
|
|
|
|
i don't care what you call it grownassman!! you cant just say anything that has no connection on your bet and you just making discussions turn complicated.
admin will correct this and you shut up coz its non of your business!!!
go find your own complain with txid in it.
|
|
|
|
|
HI..
i noticed that there's an outrage player accusing you admin of something that negatively affects trust.
but instead of examining on to his complain, I decided to look upon my files containing copies of my transactions that I am also secondstrade 5secondsdown gambler who's going under a program on how to have control of my gambling after losing about 27 or more bitcoins here. responsible gambling was it.
my bitcoin wallet address used on betting s seconds down was 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE,
what i have noticed was theres some txid's, 7 of them in particular that were unusual. first of all this where received by seconds trade and registered to be with in his position after having 7 bets at the same time exactly.
as a matter of fact they have the same Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117f.
and if that were the case they should have the same Betting expire seed convert SHA256: 0dc3a9f403294f99cfdbe4ebc61674. at first four transaction they have identical results of course they were accepted at exact same time, then what happen after that was tragic. 3 consecutive lose bets came up but they even have the exact start time and start seed convert SHA256 of those first four that where winning bets.
syatem give different end seed convert sha 256 that after i noticed it now makes me so disappointed,
i lose all money on my gambling, it dosent matter now, what matters were i would like a full payout of the transactions that were obviously change resulting to a disaster damaging my bet and start losing it all.
here are the transaction id follows by secondstrade website's gave me as to verify bets were made.
win (4 bets)
cd1e79cce21a481a77d4bd3374a29803c05698275752a70c2b149d20355fbd50
59b042e01cc1d2731a31ff83e26a346a2f8ed61f1fc389ef90554b3b8cf81f05
139ea51372cd85168edac4663b4ea7f7319d4212d12f8c6021a005fb1cf555ab
d75c7ce0f62b36c87f5e6909a47dada605e1a93deed714b53ad236d57376eac0
lose ( 3 bets)
42d2b5160270dce1d3612af0d17d0741495bd4d7dc1f55f5eff60756f45f1bd0
59dc2ebd494123c80d77d18d85517b80212b7c17a7023ccfd0d7a77ac4d2ea32
6d88d873ee116c06a0528afcdfbe830cb0f7c866f10dc39be939c57e5d60db3b
3 lose bets that i would like to have full payout admin of secondstrade with 0.5 bitcoin each
0.5 x 3 x 1.8 = 2.7 bitcoins of payout you should send back to my wallet as requested.
-------------------------WIN
Betting Transaction id : cd1e79cce21a481a77d4bd3374a29803c05698275752a70c2b149d20355fbd50
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.49927
Betting price : 2
Betting expire price : 0
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:36:595+225.41+7+1.12629
Betting expire seed convert SHA256: 0dc3a9f403294f99cfdbe4ebc616745dc032f2c41d35fa664d42b9bcee708a12
Betting Transaction id : 59b042e01cc1d2731a31ff83e26a346a2f8ed61f1fc389ef90554b3b8cf81f05
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 0
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:36:595+225.41+7+1.12629
Betting expire seed convert SHA256: 0dc3a9f403294f99cfdbe4ebc616745dc032f2c41d35fa664d42b9bcee708a12
Betting Transaction id : 139ea51372cd85168edac4663b4ea7f7319d4212d12f8c6021a005fb1cf555ab
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 0
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:36:595+225.41+7+1.12629
Betting expire seed convert SHA256: 0dc3a9f403294f99cfdbe4ebc616745dc032f2c41d35fa664d42b9bcee708a12
Betting Transaction id : d75c7ce0f62b36c87f5e6909a47dada605e1a93deed714b53ad236d57376eac0
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 0
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:36:595+225.41+7+1.12629
Betting expire seed convert SHA256: 0dc3a9f403294f99cfdbe4ebc616745dc032f2c41d35fa664d42b9bcee708a12
----------------------------------------------LOST
Betting Transaction id : 42d2b5160270dce1d3612af0d17d0741495bd4d7dc1f55f5eff60756f45f1bd0
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 9
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:36:595+225.41+7+1.12629
Betting expire seed convert SHA256: 932b6b6233b7c8b5ccc29df61432dffade0d579b8eac1422f5666a6a7915a221
Betting Transaction id : 59dc2ebd494123c80d77d18d85517b80212b7c17a7023ccfd0d7a77ac4d2ea32
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 9
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:37:622+225.41+0+1.12632
Betting expire seed convert SHA256: 932b6b6233b7c8b5ccc29df61432dffade0d579b8eac1422f5666a6a7915a221
Betting Transaction id : 6d88d873ee116c06a0528afcdfbe830cb0f7c866f10dc39be939c57e5d60db3b
Betting address : 15UExtKxSJmNxxFDZvB6CiYcqVHqAK1MLE
Betting asset : SECONDS5 DOWN
Betting BTC : 0.5
Betting price : 2
Betting expire price : 9
Betting start seed : 12:33:31:373+225.41+5+1.12609
Betting start seed convert SHA256: ace26f313f3ff6a8097cc31cd4117fe1eeec86c2e78fd17e59074a06d1d2c258
Betting expire seed : 12:33:37:622+225.41+0+1.12632
Betting expire seed convert SHA256: 932b6b6233b7c8b5ccc29df61432dffade0d579b8eac1422f5666a6a7915a221
I repeat payout request of 2.7 bitcoins seriously requested as soon as posible admin.
this will proves that you really are fair and can always be trusted if you will soon make the pay out for all i ask
remember that I lose a lot of money but thats my destiny so im just claiming what was rightfully mine.
will you please reply to me here,
god bless you.
|
|
|
|
|
