I need your explainations, admin!
your system selected wrong value times to calculated my bet ,
http://secondstrade.com/tx.jsp?tx=a9101c0b4f01f62671bc4f48cf09f68bcbff4666715331dab0d6c36872eaacd7with this value times of Start date and Real end date above , it must be
Betting start seed : 15:33:33+384.68+1+1.11585
Betting start seed convert SHA256: 1972706b592dc80886d6d7e8ec205b0ff9208ec777bf521f14ba3e118715698e
Betting expire seed : 15:33:38+384.67+0+1.11585
Betting expire seed convert SHA256: dac64a5b14d1bc4e99a67f4db479143f7d7a5d50d25c56e5e1ad027fb8403b5e
And I must win base on your explaination in this post
as i explained at the before post,
seed value is generated every second regardless bet.
when bet comes, seed of the time will be selected as start seed value.
way of expire seed value is a same. different point is using the real end date.
so, the generated seed value at 17:55:00.306 is 17:54:59, seed value of 17:55:00 is not generated yet.
if you see the past milliseconds data , you will know the way.
below is the sample milliseconds data of the past.
Betting Transaction id : 0ef48ac525a2e2b0e945404feaaeb7ff4c43718626a80bfcfa8e232a55a92bde
Betting address : 1Ju5QeBcm1ETQ1s7xPbZ8SbYDJhym4jyQa
Betting asset : SECONDS5 DOWN
Betting BTC : 0.00319293
Start date : 2016-01-20T03:28:37.347Start date(miliseconds) : 1453260517347
Prediction end date : 2016-01-20T03:28:42.347
Prediction end date(miliseconds) : 1453260522347
Real end date : 2016-01-20T03:28:42.900
Real end date(miliseconds) : 1453260522900
Betting price : 6
Betting expire price : 7
B
etting start seed : 03:28:36:740+388.51+3+1.09432Betting start seed convert SHA256: 6c6ac0f15b4787794a5bafbfe7ecf7a8a3d2bd520d03360158daf3433409e742
Betting expire seed : 03:28:42:750+388.5+1+1.09432
Betting expire seed convert SHA256: aaa70276ca9c0239d657ec38127405dd6dc3cf5e3fb41b062fbe247a38f9d1cc
Result : LOSE
Sorry buddy
P.S
we have plan adding millisecond time of generating seed value.