Update:
1 2013-11-30 1132.29
2 2013-12-04 1111.56
3 2017-01-04 1088.45
4 2013-11-29 1065.36
5 2013-12-03 1050.57
6 2017-01-03 1020.56
7 2017-01-02 1013.00
8 2017-01-05 1005.35
9 2013-12-02 1000.49
10 2013-11-28 998.56
11 2017-01-01 987.47
12 2013-12-05 975.06
13 2017-02-01 970.40
14 2016-12-29 967.02
15 2016-12-28 955.98
16 2016-12-31 955.73
17 2016-12-30 951.07
18 2017-01-31 949.19
19 2013-12-01 945.67
20 2013-12-10 941.56
|
|
|
|
Back in the top 20: Update:
1 2013-11-30 1132.29
2 2013-12-04 1111.56
3 2017-01-04 1088.45
4 2013-11-29 1065.36
5 2013-12-03 1050.57
6 2017-01-03 1020.56
7 2017-01-02 1013.00
8 2017-01-05 1005.35
9 2013-12-02 1000.49
10 2013-11-28 998.56
11 2017-01-01 987.47
12 2013-12-05 975.06
13 2016-12-29 967.02
14 2016-12-28 955.98
15 2016-12-31 955.73
16 2016-12-30 951.07
17 2017-01-31 949.19
18 2013-12-01 945.67
19 2013-12-10 941.56
20 2013-11-27 937.09
|
|
|
|
With today's price action we should be entering top20 territory again!
The price I use is the volume weighted average price of the whole day, from midnight UTC to midnight UTC. That's 4pm Pacific, 7pm Eastern. So today's update (in about 3 hours) may well not break into the top 20, but if the price stays up then tomorrow's will. |
|
|
|
Update:
1 2013-11-30 1132.29
2 2013-12-04 1111.56
3 2017-01-04 1088.45
4 2013-11-29 1065.36
5 2013-12-03 1050.57
6 2017-01-03 1020.56
7 2017-01-02 1013.00
8 2017-01-05 1005.35
9 2013-12-02 1000.49
10 2013-11-28 998.56
11 2017-01-01 987.47
12 2013-12-05 975.06
13 2016-12-29 967.02
14 2016-12-28 955.98
15 2016-12-31 955.73
16 2016-12-30 951.07
17 2013-12-01 945.67
18 2013-12-10 941.56
19 2013-11-27 937.09
20 2014-01-06 936.62
21 2016-12-27 922.42
22 2017-01-23 920.25
23 2017-01-30 917.94
24 2017-01-27 917.86
25 2017-01-28 917.53
|
|
|
|
Update:
1 2013-11-30 1132.29
2 2013-12-04 1111.56
3 2017-01-04 1088.45
4 2013-11-29 1065.36
5 2013-12-03 1050.57
6 2017-01-03 1020.56
7 2017-01-02 1013.00
8 2017-01-05 1005.35
9 2013-12-02 1000.49
10 2013-11-28 998.56
11 2017-01-01 987.47
12 2013-12-05 975.06
13 2016-12-29 967.02
14 2016-12-28 955.98
15 2016-12-31 955.73
16 2016-12-30 951.07
17 2013-12-01 945.67
18 2013-12-10 941.56
19 2013-11-27 937.09
20 2014-01-06 936.62
21 2016-12-27 922.42
22 2017-01-23 920.25
23 2017-01-27 917.86
24 2017-01-28 917.53
25 2017-01-22 916.63
26 2017-01-21 916.08
27 2017-01-29 915.29
28 2017-01-06 914.26
29 2017-01-08 913.92
30 2017-01-26 907.69
|
|
|
|
Update:
1 2013-11-30 1132.29
2 2013-12-04 1111.56
3 2017-01-04 1088.45
4 2013-11-29 1065.36
5 2013-12-03 1050.57
6 2017-01-03 1020.56
7 2017-01-02 1013.00
8 2017-01-05 1005.35
9 2013-12-02 1000.49
10 2013-11-28 998.56
11 2017-01-01 987.47
12 2013-12-05 975.06
13 2016-12-29 967.02
14 2016-12-28 955.98
15 2016-12-31 955.73
16 2016-12-30 951.07
17 2013-12-01 945.67
18 2013-12-10 941.56
19 2013-11-27 937.09
20 2014-01-06 936.62
21 2016-12-27 922.42
22 2017-01-23 920.25
23 2017-01-27 917.86
24 2017-01-28 917.53
25 2017-01-22 916.63
|
|
|
|
Basically the idea is if you're impatient and want your money before it confirms, you'll be able to pay to get it instantly.
What if I deposit without opting in, wait 20 minutes without getting a confirmation and change my mind about opting in. Can I at that point opt in and instantly get 99% of the deposited amount in my balance? Or do I have to decide before I make the transaction whether I want to pay the 1% fee or not? |
|
|
|
Update:
1 2013-11-30 1132.29
2 2013-12-04 1111.56
3 2017-01-04 1088.45
4 2013-11-29 1065.36
5 2013-12-03 1050.57
6 2017-01-03 1020.56
7 2017-01-02 1013.00
8 2017-01-05 1005.35
9 2013-12-02 1000.49
10 2013-11-28 998.56
11 2017-01-01 987.47
12 2013-12-05 975.06
13 2016-12-29 967.02
14 2016-12-28 955.98
15 2016-12-31 955.73
16 2016-12-30 951.07
17 2013-12-01 945.67
18 2013-12-10 941.56
19 2013-11-27 937.09
20 2014-01-06 936.62
21 2016-12-27 922.42
22 2017-01-23 920.25
23 2017-01-27 917.86
24 2017-01-22 916.63
25 2017-01-21 916.08
|
|
|
|
Bitcoin goin hard down then big up is jormal for bitcoin what is really perfect for traders which trade with many kind of cryptocurrencies.
Your jormal. Update:
1 2013-11-30 1132.29
2 2013-12-04 1111.56
3 2017-01-04 1088.45
4 2013-11-29 1065.36
5 2013-12-03 1050.57
6 2017-01-03 1020.56
7 2017-01-02 1013.00
8 2017-01-05 1005.35
9 2013-12-02 1000.49
10 2013-11-28 998.56
11 2017-01-01 987.47
12 2013-12-05 975.06
13 2016-12-29 967.02
14 2016-12-28 955.98
15 2016-12-31 955.73
16 2016-12-30 951.07
17 2013-12-01 945.67
18 2013-12-10 941.56
19 2013-11-27 937.09
20 2014-01-06 936.62
21 2016-12-27 922.42
22 2017-01-23 920.25
23 2017-01-22 916.63
24 2017-01-21 916.08
25 2017-01-06 914.26
26 2017-01-08 913.92
27 2017-01-26 907.69
28 2017-01-24 903.34
29 2017-01-10 902.61
30 2016-12-24 900.20
|
|
|
|
http://khashier.com/ is showing block 1351634 from 2017-01-23 07:28:48 to be the latest block. I see 1356517 blocks in the chain. khashier stopped updating about 3 days ago.
|
|
|
|
Update:
1 2013-11-30 1132.29
2 2013-12-04 1111.56
3 2017-01-04 1088.45
4 2013-11-29 1065.36
5 2013-12-03 1050.57
6 2017-01-03 1020.56
7 2017-01-02 1013.00
8 2017-01-05 1005.35
9 2013-12-02 1000.49
10 2013-11-28 998.56
11 2017-01-01 987.47
12 2013-12-05 975.06
13 2016-12-29 967.02
14 2016-12-28 955.98
15 2016-12-31 955.73
16 2016-12-30 951.07
17 2013-12-01 945.67
18 2013-12-10 941.56
19 2013-11-27 937.09
20 2014-01-06 936.62
21 2016-12-27 922.42
22 2017-01-23 920.25
23 2017-01-22 916.63
24 2017-01-21 916.08
25 2017-01-06 914.26
26 2017-01-08 913.92
27 2017-01-24 903.34
28 2017-01-10 902.61
29 2016-12-24 900.20
30 2016-12-26 898.97
31 2016-12-23 897.77
32 2017-01-19 895.00
33 2013-12-06 894.36
34 2017-01-20 893.82
35 2017-01-25 893.11
|
|
|
|
Mathematically, you have a ~150% chance to have 1 red in 150 rolls on 98.99% win chance.
What does "150% chance" mean? Certain-and-a-half? I think your math is wrong. You have a 1% chance of losing each roll. If you do 150 rolls that doesn't mean you have a 150% chance of losing at least one. The way the calculation works is like this: * you have a 0.99 probability of winning each bet * so you have a 0.99 ^ 150 probability of winning all 150 bets * 0.99 ^ 150 = 0.22145 * so you have a 22.145% chance of winning all 150 bets * so you have a 77.855% chance of losing at least one bet Please note that I do not vouch for yolodice. |
|
|
|
Update:
1 2013-11-30 1132.29
2 2013-12-04 1111.56
3 2017-01-04 1088.45
4 2013-11-29 1065.36
5 2013-12-03 1050.57
6 2017-01-03 1020.56
7 2017-01-02 1013.00
8 2017-01-05 1005.35
9 2013-12-02 1000.49
10 2013-11-28 998.56
11 2017-01-01 987.47
12 2013-12-05 975.06
13 2016-12-29 967.02
14 2016-12-28 955.98
15 2016-12-31 955.73
16 2016-12-30 951.07
17 2013-12-01 945.67
18 2013-12-10 941.56
19 2013-11-27 937.09
20 2014-01-06 936.62
21 2016-12-27 922.42
22 2017-01-23 920.25
23 2017-01-22 916.63
24 2017-01-21 916.08
25 2017-01-06 914.26
26 2017-01-08 913.92
27 2017-01-24 903.34
28 2017-01-10 902.61
29 2016-12-24 900.20
30 2016-12-26 898.97
|
|
|
|
Update:
1 2013-11-30 1132.29
2 2013-12-04 1111.56
3 2017-01-04 1088.45
4 2013-11-29 1065.36
5 2013-12-03 1050.57
6 2017-01-03 1020.56
7 2017-01-02 1013.00
8 2017-01-05 1005.35
9 2013-12-02 1000.49
10 2013-11-28 998.56
11 2017-01-01 987.47
12 2013-12-05 975.06
13 2016-12-29 967.02
14 2016-12-28 955.98
15 2016-12-31 955.73
16 2016-12-30 951.07
17 2013-12-01 945.67
18 2013-12-10 941.56
19 2013-11-27 937.09
20 2014-01-06 936.62
21 2016-12-27 922.42
22 2017-01-23 920.25
23 2017-01-22 916.63
24 2017-01-21 916.08
25 2017-01-06 914.26
|
|
|
|
Nice but, could you help to integrate the code into clam daemon?
By doing this every clam user will be able to use it when necessary.
That's not a bad idea. It could build a new wallet with the private keys it finds in an existing corrupt wallet file. |
|
|
|
Do you pay bug bounties at all? I didn't find a way of cheating, but I did find some factual errors in the FAQ.
Yes, definitely! Site's profit is not stellar yet, but I try my best! I found another one for you:  (1 - 0.01) / m = 0.99 / 2 = 0.495 (not 0.45) Your calculation seems to be using d = 0.10, a 10% house edge. Could that explain why you have a 50 BTC profit from just 725 BTC wagered? Just kidding.  Please note that I do not vouch for yolodice. |
|
|
|
There seems to be a flexible interpretation of the term "20" at play here.
Update:
1 2013-11-30 1132.29
2 2013-12-04 1111.56
3 2017-01-04 1088.45
4 2013-11-29 1065.36
5 2013-12-03 1050.57
6 2017-01-03 1020.56
7 2017-01-02 1013.00
8 2017-01-05 1005.35
9 2013-12-02 1000.49
10 2013-11-28 998.56
11 2017-01-01 987.47
12 2013-12-05 975.06
13 2016-12-29 967.02
14 2016-12-28 955.98
15 2016-12-31 955.73
16 2016-12-30 951.07
17 2013-12-01 945.67
18 2013-12-10 941.56
19 2013-11-27 937.09
20 2014-01-06 936.62
21 2016-12-27 922.42
22 2017-01-22 916.63
23 2017-01-21 916.08
24 2017-01-06 914.26
25 2017-01-08 913.92
|
|
|
|
Update:
1 2013-11-30 1132.29
2 2013-12-04 1111.56
3 2017-01-04 1088.45
4 2013-11-29 1065.36
5 2013-12-03 1050.57
6 2017-01-03 1020.56
7 2017-01-02 1013.00
8 2017-01-05 1005.35
9 2013-12-02 1000.49
10 2013-11-28 998.56
11 2017-01-01 987.47
12 2013-12-05 975.06
13 2016-12-29 967.02
14 2016-12-28 955.98
15 2016-12-31 955.73
16 2016-12-30 951.07
17 2013-12-01 945.67
18 2013-12-10 941.56
19 2013-11-27 937.09
20 2014-01-06 936.62
21 2016-12-27 922.42
22 2017-01-21 916.08
23 2017-01-06 914.26
24 2017-01-08 913.92
25 2017-01-10 902.61
|
|
|
|
Update:
1 2013-11-30 1132.29
2 2013-12-04 1111.56
3 2017-01-04 1088.45
4 2013-11-29 1065.36
5 2013-12-03 1050.57
6 2017-01-03 1020.56
7 2017-01-02 1013.00
8 2017-01-05 1005.35
9 2013-12-02 1000.49
10 2013-11-28 998.56
11 2017-01-01 987.47
12 2013-12-05 975.06
13 2016-12-29 967.02
14 2016-12-28 955.98
15 2016-12-31 955.73
16 2016-12-30 951.07
17 2013-12-01 945.67
18 2013-12-10 941.56
19 2013-11-27 937.09
20 2014-01-06 936.62
21 2016-12-27 922.42
22 2017-01-06 914.26
23 2017-01-08 913.92
24 2017-01-10 902.61
25 2016-12-24 900.20
26 2016-12-26 898.97
27 2016-12-23 897.77
28 2017-01-19 895.00
29 2013-12-06 894.36
30 2017-01-20 893.82
|
|
|
|
A new version of the platform has been deployed.
It's at https://oxt.me/ - you omitted that from your post. I played around for a few minutes, but ended up getting a "too many requests" error that wouldn't go away:  Edit: after a while I was able to carry on exploring, but the "too many requests" message didn't go away. |
|
|
|
|
Show Posts
