Week 3 (14.04-20.04)
BitcoinTalk User ID: 365389
Instagram username: life.for.nerzul
Instagram  URL: https://www.instagram.com/life.for.nerzul/
Number of Instagram Friends: 6457

Please list links of Post:
1.https://www.instagram.com/p/BhwCLVigPBZ/?taken-by=life.for.nerzul
2.
Please list links of Repost:
1 https://www.instagram.com/p/BhoLFVvAdVV/?taken-by=life.for.nerzul
2 https://www.instagram.com/p/BhqlcAOga4i/?taken-by=life.for.nerzul
3 https://www.instagram.com/p/BhtMmSXgTy6/?taken-by=life.for.nerzul
4 https://www.instagram.com/p/BhygJzZAEVJ/?taken-by=life.for.nerzul

Week 3 (14.04-20.04)
BitcoinTalk User ID: 365389
Twitter username: @CryptoHellFire
Twitter URL: https://twitter.com/CryptoHellFire
Number of Twitter Friends: 3873

Please list links of Tweets:
1. https://twitter.com/CryptoHellFire/status/985826993198567424
2. https://twitter.com/CryptoHellFire/status/986165237878591488
3. https://twitter.com/CryptoHellFire/status/986532644501540864
Please list links of Retweets:
1. https://twitter.com/Egretia_io/status/986829883396501504
2  https://twitter.com/Egretia_io/status/987213771201482752

###TWITTER WEEK 3###
Twitter user URL:https://twitter.com/CryptoHellFire
https://twitter.com/CryptoHellFire/status/984397490333147136
https://twitter.com/CryptoHellFire/status/984740810494181376
https://twitter.com/CryptoHellFire/status/985823455231856640
https://twitter.com/CryptoHellFire/status/986166428620480512

Campaign : Twitter
Twitter Username: @CryptoHellFire
Spreadsheet No:1220
Twitter Account:https://twitter.com/CryptoHellFire
Week#:6 (11/04-17/04)
Twitter Links:
1.11.04.2018 https://twitter.com/CryptoHellFire/status/984086087776849920
2.12.04.2018 https://twitter.com/CryptoHellFire/status/984393296234602496
3.13.04.2018 https://twitter.com/CryptoHellFire/status/984741673606447104
4.16.04.2018 https://twitter.com/CryptoHellFire/status/985822606984208385

Week 2 (07.04-13.04)
BitcoinTalk User ID: 365389
Instagram username: life.for.nerzul
Instagram  URL: https://www.instagram.com/life.for.nerzul/
Number of Instagram Friends: 6457

Please list links of Post:
1. https://www.instagram.com/p/Bhd77MagZDs/?&taken-by=life.for.nerzul
2. https://www.instagram.com/p/BhhPRyoAuUr/?taken-by=life.for.nerzul
Please list links of Repost:
1 https://www.instagram.com/p/BhZK0V1HIPH/?taken-by=life.for.nerzul
2 https://www.instagram.com/p/Bhbgfymna0E/?taken-by=life.for.nerzul
3 https://www.instagram.com/p/BhgcR9-g4PZ/?taken-by=life.for.nerzul

Week 2 (07.04-13.04)
BitcoinTalk User ID: 365389
Twitter username: @CryptoHellFire
Twitter URL: https://twitter.com/CryptoHellFire
Number of Twitter Friends: 3873

Please list links of Tweets:
1. https://twitter.com/CryptoHellFire/status/984389513471516672
2. https://twitter.com/CryptoHellFire/status/984737750623641600
3. https://twitter.com/CryptoHellFire/status/984849752431976453
Please list links of Retweets:
1. https://twitter.com/Egretia_io/status/983434459134521344
2  https://twitter.com/Egretia_io/status/983948925454430208

Promising. But you must carefully choose an investment object. Only blockchain and infrastructure projects. Only strong team and funds like hashed in backers.

Mar 03 1645 ~ Mar 05 1545   4 x S7@4.73   47 hours x 4 units = total 188 hours      s702 s703 s704 s705
Mar 06 1640 ~ Mar 07 1041   4 x S7@4.73   16 hours x 4 units = total 64 hours              s702 s703 s704 s705
Mar 27 0830 ~ 1800      8 x S7      9.5 hours x 8 units = total 76 hours      all
Apr 04 1930 ~ Apr 06 1100   3 x S7@4.73   39.5 hours x 3 units = total 118.5 hours           s7f s7g s7h
Apr 11 0715 ~ 1735      8 x S7      10 hours x 8 units = total 80 hours              all
Apr 15 0616 ~ 1050      1 x S7@4.73   4.5 hours                               s7f
Apr 18 1117 ~ 1331      1 x S7@4.66   2 hours                          s7a
Apr 21 2256 ~ Apr 22 0830   1 x S7@4.73   9.5 hours                               s7e
Apr 22 0956 ~ 1200      1 x S7@4.73   2 hours                          s7d

====================

May 09 1345 ~ 1925      1 x S7@4.73   5.5 hours !!!                       s7b 1/3 hashrates
May 13 1340 ~ May 14 1055   1 x S7@4.73   21 hours                               s7g
May 16 1615 ~ May 17 0235   1 x S7@4.73   10 hours                               s7b
May 17 0930 ~ 1325      1 x S7@4.73   4 hours                          s7b


s7a is a 4.66 others are 4.73, didn't take records before Mar 03 and i stopped taking record aftrer May 17 as i'm too tired with this hosting.
i claimed downtime that's why i rec'd compensation of total 3.0926 (included the 1.6688 rec'd on Jan 30 for online delay)

EDIT: network engineer is not a coder, network engineer always troubleshoot with span port and packet analyzer doesn't mean he is capable in developing a protocol suite by himself

People say China miners must mine at China pool and this is not true, GFW increase latency not blocking any well known bitcoin ports e.g. 3333, 8333, 9332, 9333 etc.
People (indeed li said) i mine at pools outside China causing problems and this is not true at all, i'm connecting Slush pool via their CN node that is 100% China pool.
I'm a CxIE with 20xxx number I know internet well, you people always been misled by the Chinese, GFW is simply a hardware firewall with deep packet inspection functionality that's all.

Spent 7 btc for a 4.66 and 23 btc for the 4.73, paid total 7.2149 hosting fees, 3.0926 compensation rec'd, adding up all payouts from pools and what so called 0.92 buy back money finally i realize i loss 11 btc for this fucking hosting, the biggest loss i ever seen since i started mining in 2014, wtf

The root problem i believe is they (li and partners) has recently adding too many miners in the DC causing too high temperature and power overload, as i said before everytime we hv power outage BW will drop a hugh amount of hashrates at same time, whenever BW adding more hashrates we will suffer as well. Don't we see BW has added 30P more hashrates since last Monday?

Another 4.73 is getting crazy today, he is forcing people to leave the game, SHAME.

Li if you decided to leave the hosting business let me here to counter propose you another option, i.e. transfer all my miners to BW B16 hashrates with 1:1 ratio

Li i believe you hv replaced the bad power supply miner is running fine for 5 hours by now.
If you say we hv to pick option 1 or 2 no other options i would say you are now ripping off people, 4.73 miners been online only 100 days and i spent appr 23 BTC  for the miners you can figure out how much i gonna loss. Don't blame S7 or GFW all problems i hv were caused by your infrastructure issues, your grid power, your power supply.
Back in 2015 Umisoo sold their customer base to Bitmaintech and transferred all the hosted miners to Hashnest with 1:1 ratio, though it was not a fair trade at least they gave me a chance to sell off my hashrates on market at a reasonable price.

Li your power supply is hving big problem it turn on / off by itself every few minutes, get it fixed quick otherwise my S7 will be blown up. Crazy problem everyday...read email pls...



All my S7 connected to Slush with no problem except this 4.73

Li you hv power problem today and made one of my 4.73 competely dead, mind you to read email pls
Interestingly only 4.73 were affected by the power surge not 4.66.

i hv 1 x 4.73 down since Apr 21 14:56 UTC

Li what is otc market?

what the hell power transformer problem again and again? all S7 down since 0715 Beijing time today, 4.66 and 4.73.
as usual bw.com hashrates dropped from 81.63P to 68P at same time.

miners back online finally, 39.6 hours x 3 units = total 118.5 total downtime.

also i noticed that Li has recently changed his internet access from China Telecom x.x.x.70 to China Unicom x.x.x.223, my pool stats is showing a lot reject and miner fallback in the past 3 hours, ping test from my proxy to Unicom ip got almost 10% packet drop with 120ms turnaround avg ,anyway 120ms is OK but severe packet drop must degrade hashing performance, not sure if anyone seeing the same

3 miners down for 36 hours, still counting...

Li how come power outage always occur at around 1700 Beijing time? is it a coincidence or what?