We thank you for your concern, but everything is under control. Suprnova, the pool you cited, has found multiple confirmed blocks after that bad batch. We are also preparing for a hard fork that will change the mining difficulty regulator from KGW to DGW that should stop the issue of difficulty changes. This can occur when a large mining pool hops on and off the Belacoin blockchain. Under the Kimoto Gravity Well, the difficulty retargets after every block. With DGW, the difficulty retarget will follow more of an average, so there will not be as much variation in the mining difficulty.
I said ok, that happened on low diff, but diff now was 1500 - 1800, and again someone jump with big big Hashrate, and guess what !!??
All Orphans again !!!!!! And again I lost my money....so definitely I'm out with mining this coin until you fix that problem !!
78514910 BELA 2017-05-02 10:32:10 Credit Orphaned 679399 35.88652804
78514870 BELA 2017-05-02 10:32:08 Credit Orphaned 679398 39.42368871
78514823 BELA 2017-05-02 10:32:06 Credit Orphaned 679397 36.70752550
78514484 BELA 2017-05-02 10:27:59 Credit Orphaned 679395 37.54002380
78514437 BELA 2017-05-02 10:27:57 Credit Orphaned 679394 37.92257662
and yesterday....
78390786 BELA 2017-05-01 02:05:11 Credit Orphaned 678362 47.81157720
78390779 BELA 2017-05-01 02:05:09 Credit Orphaned 678361 47.34842992
78390772 BELA 2017-05-01 02:05:07 Credit Orphaned 678360 47.52771543
78390306 BELA 2017-05-01 01:55:17 Credit Orphaned 678351 47.93435648
78390299 BELA 2017-05-01 01:55:15 Credit Orphaned 678342 48.11797716
78390294 BELA 2017-05-01 01:55:13 Credit Orphaned 678340 48.76631909
78390288 BELA 2017-05-01 01:55:11 Credit Orphaned 678335 48.81996251
78390282 BELA 2017-05-01 01:55:09 Credit Orphaned 678320 49.16439382
78390278 BELA 2017-05-01 01:55:07 Credit Orphaned 678319 48.76861305
78390273 BELA 2017-05-01 01:55:05 Credit Orphaned 678316 47.66077448
78390271 BELA 2017-05-01 01:55:03 Credit Orphaned 678303 50.00000000
78390270 BELA 2017-05-01 01:55:01 Credit Orphaned 678302 50.00000000
78390267 BELA 2017-05-01 01:54:59 Credit Orphaned 678301 49.56843403
78390264 BELA 2017-05-01 01:54:57 Credit Orphaned 678294 49.53886693
78390263 BELA 2017-05-01 01:54:55 Credit Orphaned 678290 50.00000000
78390260 BELA 2017-05-01 01:54:53 Credit Orphaned 678289 49.28336152
78390257 BELA 2017-05-01 01:54:51 Credit Orphaned 678285 49.81419676
78390254 BELA 2017-05-01 01:54:49 Credit Orphaned 678284 49.43277818
78390251 BELA 2017-05-01 01:54:47 Credit Orphaned 678282 49.48793732
78390248 BELA 2017-05-01 01:54:45 Credit Orphaned 678275 49.63988920
78390244 BELA 2017-05-01 01:54:43 Credit Orphaned 678274 47.28222566
78390240 BELA 2017-05-01 01:54:41 Credit Orphaned 678272 47.78849220
78389670 BELA 2017-05-01 01:44:12 Credit Orphaned 678270 48.08073597
78389666 BELA 2017-05-01 01:44:10 Credit Orphaned 678268 48.51082153
78389664 BELA 2017-05-01 01:44:08 Credit Orphaned 678267 49.20634921
78389660 BELA 2017-05-01 01:44:06 Credit Orphaned 678266 47.79935691
So in less than 24 hours mining Bella, I lost 0.11 BTC...what a beautiful day !!!
Fix network, stop attacks !!
And as you said:
"but
everything is under control. Suprnova, the pool you cited, has found
multiple confirmed blocks after that bad batch."
Really ?
Did you even checked Suprnova ?
679242 Confirmed sonicmayhem 05/02/2017 03:11:58 1,796.0606 50.0011 117,706,628 114,403,136 97.19
679085 Confirmed stankonia 05/01/2017 22:03:47 1,826.2322 50.0000 119,683,951 153,364,840 128.14
678827 Confirmed anonymous 05/01/2017 12:29:35 2,189.4790 50.0000 143,489,697 525,232,764 366.04
678541 Confirmed sonicmayhem 05/01/2017 03:50:44 2,269.4605 50.0000 148,731,362 67,798,178 45.58
678535 Confirmed anonymous 05/01/2017 03:01:07 2,542.0434 50.0140 166,595,355 98,707,717 59.25
678336 Orphan stankonia 04/30/2017 23:50:58 93.0131 50.0000 6,095,707 7,324,042 120.15
678277 Orphan Kidryce 04/30/2017 23:43:20 151.9336 50.0000 9,957,118 183,283,503 1,840.73
678120 Orphan yavuzc78 04/30/2017 11:54:46 489.6238 50.0000 32,087,986 18,857,587 58.77
678117 Orphan yavuzc78 04/30/2017 11:53:56 501.8534 50.0000 32,889,466 4,356,384 13.25
678116 Orphan yavuzc78 04/30/2017 11:53:07 505.9549 50.0000 33,158,263 64,013,881 193.06
678094 Confirmed yavuzc78 04/30/2017 11:48:17 594.9059 50.0000 38,987,753 20,463,968 52.49
after that, they found 1 hey ONE block today and 4 yesterday !!!!!
someone is mining with all 200 MH/s
and the only one who is mining with such big Hashrate is the attacker !
And you still don't see that you have a problem ?
My suggestion is, resend my post to some expert, I can see that you don't understand to read the network and understand why that happened !
mining difficulty regulator will not fix that, Orphans doesn't become immediately but after 50 - 60 confs, what means that someone cross our blocks, someone is on his own fork and when forward us, our network, then he open the ports and our blocks became Orphans, and that is the problem what you have here, so you will not fix that with changing difficulty regulator