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
