Fimkrypto forum

English discussion => Technical Discussion => Topic started by: eRoh on November 09, 2016, 06:10:59 PM

Title: Network status
Post by: eRoh on November 09, 2016, 06:10:59 PM
Now there seems to be a quite healthy balance in the network, and a clear correlation between effective balance and blocks forged.

For those who interested, the current ratio seems to be about 20-30 blocks forged per a million FIMK per day. If I calculated correctly, that means 0.2% daily "interest rate", i.e. 100-200% yearly profit. :cheers:

Now everybody start forging! :-D

Now that the situation is better, let's not focus on negative things anymore. ;-)

I myself just noticed, that I've been monitoring the network for quite a long time now, and have a good "perstuntuma" (I offer a beer for a good translation) about the overall status. I'll be posting my observations to this thread, if I find something noticeable.
Title: Re: Network status
Post by: Eliphaz Fimk on November 09, 2016, 08:54:09 PM
Your network monitoring has been really helpful!  :thumbup:

Quote
"perstuntuma" (I offer a beer for a good translation)

Kinda hunch.

We owe you one for the FIMK activism anyway :)

Title: Re: Network status
Post by: eRoh on November 09, 2016, 09:02:56 PM
Now there seems to be a quite healthy balance in the network, and a clear correlation between effective balance and blocks forged.

This is what I meant, a snapshot from this evening:
Account   Name   Effective balance   Blocks forged   Blocks/million FIMK   "Fairness" of the forged amount
FIM-6Y9S-3TVG-B28U-CG7MU   Krypto Fin ry forging support   17989122   738   41,02479265   1,168594929
FIM-JS7L-HU5X-XUTT-2GGQH   Warmach's Forging Pool   14873917   517   34,7588332   0,990108507
FIM-QLSC-282V-5GC3-8PJLX   Zero Pool   6946851   218   31,38112506   0,893894186
FIM-XP28-YFNT-ZCNU-GU8WN   Fitcoin   3383381   104   30,73848319   0,875588474
FIM-34B3-PWY5-TMHC-9JYW8      2914791   88   30,19084387   0,859988918
FIM-7V29-9JM3-C9QQ-4QSBQ      2133388   71   33,28039719   0,947995124
FIM-FSNP-9AKV-DN99-34SDS      627087   7   11,16272543   0,317971243
FIM-77P7-WE66-HF3Y-9JU6J      819386   6   7,322556158   0,208583674
FIM-8Z96-4U4J-34WT-34K2Y   Gunnari Liikkuvainen   178581   4   22,39879942   0,638031827
FIM-Q7FH-7V8U-7FJZ-8UE3Q      107949   4   37,05453501   1,055501781
FIM-3896-ZVLA-XKU8-C6XXG   Kati   102336   1   9,771732333   0,278348679
   Total   50076789   1758   35,10608478

Ideally, the "fairness" should be close to 1 for everyone, but because of (intended) randomness of the algorithms, occasional forking and/or downtime there are variations. But as you can see, even small forgers can get a fair share of the cake, if they can keep their servers up and running.

To support the small forgers, I decided to give 10 000 FIMK to each of those forging with less than a million FIMK. Beware, there might be similar rags in the future! And if somebody can convince me that they might start forging and commit to the task, I can make a donation up to 100k. Just private message me, and make your "business plan pitch"!

Your network monitoring has been really helpful!  :thumbup:
We owe you one for the FIMK activism anyway :)

Thanks, my pleasure.

Quote
Kinda hunch.

Sorry, but I really need the vulgarity there. Besides, "perstuntuma" is something a lot more definitive than just a hunch. ;-P
Title: Re: Network status
Post by: Polarpanda on November 10, 2016, 02:12:10 PM
Good points eRoh!

If you look at this account (FIM-YAZR-6U3M-DKAC-GCZTV) you might notice that something drastic changed around 17.Oct.2016. Two+ weeks before that (1-17.Oct) 42 blocks forged. The last three weeks (18.Oct-10.Nov) 12 blocks or 4 blocks in last two weeks. No change in setup or account balance. What's your math on that being fair?
Title: Re: Network status
Post by: warmach on November 10, 2016, 03:05:23 PM

Ideally, the "fairness" should be close to 1 for everyone, but because of (intended) randomness of the algorithms, occasional forking and/or downtime there are variations. But as you can see, even small forgers can get a fair share of the cake, if they can keep their servers up and running.

To support the small forgers, I decided to give 10 000 FIMK to each of those forging with less than a million FIMK. Beware, there might be similar rags in the future! And if somebody can convince me that they might start forging and commit to the task, I can make a donation up to 100k. Just private message me, and make your "business plan pitch"!

I am also willing to help small forgers get their servers up and running.  I have a perl script that is easy to use on a simple Linux setup.  I have setup a FIMK server on a Raspberry Pi.  The RAM requirements make the Pi (512 MB RAM) a little unstable.  Any other small computer or VPS should work.

I've been trying to figure out a way I can help facilitate running a server without the need for the password.  I'm open to any ideas.  The best I've come up with is to forge with an account where we share the password.  The user then leases their balance to this shared account and we auto transfer funds back to their original account.
Title: Re: Network status
Post by: eRoh on November 10, 2016, 05:39:59 PM
If you look at this account (FIM-YAZR-6U3M-DKAC-GCZTV) you might notice that something drastic changed around 17.Oct.2016. Two+ weeks before that (1-17.Oct) 42 blocks forged. The last three weeks (18.Oct-10.Nov) 12 blocks or 4 blocks in last two weeks. No change in setup or account balance. What's your math on that being fair?

Can't say for sure, but I'd suspect that it's been forking off and back on. There have been several disturbances in the network this autumn, including the pools, so that's quite plausible explanation. Maybe you could verify this from your server's logs. It's a good idea to occasionally check last blocks from the browser:
http://localhost:7886/index.html#/activity/fim/blockchain/latest
If that doesn't match lompsa.com (and several of the last ones are your account), you're probably on a fork (even though the server hasn't detected it yet).
Title: Re: Network status
Post by: Polarpanda on November 11, 2016, 02:32:49 PM
Can't say for sure, but I'd suspect that it's been forking off and back on. There have been several disturbances in the network this autumn, including the pools, so that's quite plausible explanation. Maybe you could verify this from your server's logs. It's a good idea to occasionally check last blocks from the browser:
http://localhost:7886/index.html#/activity/fim/blockchain/latest
If that doesn't match lompsa.com (and several of the last ones are your account), you're probably on a fork (even though the server hasn't detected it yet).

It seems to show fork quite often but I don't know if there is much I can do about it.. At least now it seems to find blocks too :-)

2016-11-10 15:14:57 FINE: Average transaction time is 0.089 seconds
2016-11-10 15:14:57 FINE: Got 0 confirmations
2016-11-10 15:14:57 FINE: Downloaded 27 blocks
2016-11-10 15:30:16 FINE: Average transaction time is 0.004 seconds
2016-11-10 15:31:09 FINE: Will process a fork of 1 blocks
2016-11-10 15:31:09 FINE: Rollback from block 11175958811406241642 at height 1434481 to 12959094781219316561 at 1434480
2016-11-10 15:31:09 FINE: Switched to peer's fork
2016-11-10 15:32:50 FINE: Will process a fork of 2 blocks
2016-11-10 15:32:50 FINE: Rollback from block 6756629296191191725 at height 1434483 to 3063505403943391763 at 1434482
2016-11-10 15:32:50 FINE: Switched to peer's fork
2016-11-10 15:45:21 FINE: Average transaction time is 0.002 seconds
2016-11-10 16:02:17 FINE: Average transaction time is 0.003 seconds
2016-11-10 16:03:03 FINE: Will process a fork of 1 blocks
2016-11-10 16:03:03 FINE: Rollback from block 13140701740336670726 at height 1434524 to 9420797745090269543 at 1434523
2016-11-10 16:03:03 FINE: Switched to peer's fork
2016-11-10 16:17:40 FINE: Average transaction time is 0.003 seconds
2016-11-10 16:29:21 FINE: Will process a fork of 2 blocks
2016-11-10 16:29:21 FINE: Rollback from block 10769585445557225113 at height 1434563 to 799173027168879070 at 1434562
2016-11-10 16:29:21 FINE: Switched to peer's fork
2016-11-10 16:35:04 FINE: Average transaction time is 0.001 seconds
2016-11-10 16:35:44 FINE: Will process a fork of 1 blocks
2016-11-10 16:35:44 FINE: Rollback from block 7338914621243365657 at height 1434571 to 8784106841602077884 at 1434570
2016-11-10 16:35:45 FINE: Switched to peer's fork
2016-11-10 16:50:15 FINE: Average transaction time is 0.002 seconds
2016-11-10 17:05:28 FINE: Average transaction time is 0.002 seconds
2016-11-10 17:21:42 FINE: Average transaction time is 0.001 seconds
2016-11-10 17:27:18 FINE: Forger 17142927957740692471 deadline 40 hit 93497274
2016-11-10 17:28:13 FINE: Account 17142927957740692471 generated block 5794734463996886635 at height 1434646 timestamp 93497275 fee 0.0
2016-11-10 17:37:18 FINE: Average transaction time is 0.002 seconds
2016-11-10 17:52:58 FINE: Average transaction time is 0.002 seconds
2016-11-10 18:08:37 FINE: Average transaction time is 0.002 seconds
2016-11-10 18:23:50 FINE: Average transaction time is 0.008 seconds
2016-11-10 18:26:33 FINE: Will process a fork of 2 blocks
2016-11-10 18:26:33 FINE: Rollback from block 10959958016664993258 at height 1434735 to 8782705118632386786 at 1434734
2016-11-10 18:26:33 FINE: Switched to peer's fork
2016-11-10 18:41:36 FINE: Average transaction time is 0.002 seconds
2016-11-10 18:56:59 FINE: Average transaction time is 0.001 seconds
2016-11-10 19:13:03 FINE: Average transaction time is 0.006 seconds
2016-11-10 19:29:06 FINE: Average transaction time is 0.001 seconds
2016-11-10 19:32:43 FINE: Will process a fork of 2 blocks
2016-11-10 19:32:43 FINE: Rollback from block 5549369316525647920 at height 1434822 to 2032089278188381468 at 1434821
2016-11-10 19:32:43 FINE: Switched to peer's fork
2016-11-10 19:46:24 FINE: Average transaction time is 0.002 seconds
2016-11-10 19:48:20 FINE: Will process a fork of 2 blocks
2016-11-10 19:48:20 FINE: Rollback from block 5187832570731367756 at height 1434842 to 5555832947673565528 at 1434841
2016-11-10 19:48:20 FINE: Switched to peer's fork
2016-11-10 20:01:25 FINE: Average transaction time is 0.003 seconds
Title: Re: Network status
Post by: Eliphaz Fimk on November 11, 2016, 10:42:08 PM
Can't say for sure, but I'd suspect that it's been forking off and back on.
From my very limited investigations I also concur this is likely the case. The block resolve algorithms of current generation cryptocurrencies really aren't designed for such a small and unproportional distribution of nodes. Yet, from Dirk's ingenious fork auto-resolution algorithms he developed at the peak of success  ;D the nodes seem to get back running autonomously, which I consider quite a feat and very positive amidst all the unconfortable stuff. AFAIK unique in the crypto sphere.
Title: Re: Network status
Post by: eRoh on January 01, 2017, 12:31:01 PM
To support the small forgers, I decided to give 10 000 FIMK to each of those forging with less than a million FIMK. Beware, there might be similar rags in the future! And if somebody can convince me that they might start forging and commit to the task, I can make a donation up to 100k. Just private message me, and make your "business plan pitch"!

Donation round 2 sent. Let me know, if I missed somebody. Happy New Year!
Title: Re: Network status
Post by: kani on January 03, 2017, 11:28:27 PM
Donation round 2 sent. Let me know, if I missed somebody. Happy New Year!

Great initiative!  Happy New Year!
Title: Re: Network status
Post by: eRoh on January 23, 2018, 04:32:40 PM
Lompsa down?
https://lompsa.com/#/activity/fim/blockchain/latest
Anybody home?
Title: Re: Network status
Post by: Eliphaz Fimk on January 24, 2018, 05:26:20 PM
Lompsa.com centralized frontend java certificate had expired thus the content feed was down for ~24 hrs. In such circumstances the peer-to-peer network and full FIMK nodes work perfectly.
Title: Re: Network status
Post by: eRoh on January 24, 2018, 06:16:44 PM
Lompsa.com centralized frontend java certificate had expired thus the content feed was down for ~24 hrs. In such circumstances the peer-to-peer network and full FIMK nodes work perfectly.

It still is the best/only public block explorer that I know of. Or any others (besides my own nodes of course)?
Title: Re: Network status
Post by: eRoh on August 13, 2018, 11:48:50 AM
FIMK basic income forging over 95% of the blocks:
https://lompsa.com/#/activity/fim/forgers/latest

Should the distribution be more decentralized? Any volunteers?
Title: Re: Network status
Post by: eRoh on August 16, 2018, 10:45:23 AM
FIMK basic income forging over 95% of the blocks:
https://lompsa.com/#/activity/fim/forgers/latest

Should the distribution be more decentralized? Any volunteers?

At least my server has been constantly forking after this "distortion". Any observations? Number of forgers has significantly dropped, people having problems or given up?
Title: Re: Network status
Post by: Eliphaz Fimk on August 22, 2018, 11:00:12 AM
For unknown reason forgers were having serious trouble to join the main chain headed by warmach's pool, dropping off constantly. We decided to take lead with the association's account, improving things somewhat but apparently still maintaining a conflict of at least two powerful chains (if I read eRoh's note properly). It's intended to detach the mega account from forging in the near future, let's see how things then go. In case they don't improve, it might be necessary to adjust your well known nodes config to use the chain of your preference and not jump around the two large chains / fork your own. Warmach may not be aware of the situation, any heads up to him to attend to this is appreciated.
Title: Re: Network status
Post by: eRoh on August 23, 2018, 05:12:45 PM
For unknown reason forgers were having serious trouble to join the main chain headed by warmach's pool, dropping off constantly. We decided to take lead with the association's account, improving things somewhat but apparently still maintaining a conflict of at least two powerful chains (if I read eRoh's note properly). It's intended to detach the mega account from forging in the near future, let's see how things then go. In case they don't improve, it might be necessary to adjust your well known nodes config to use the chain of your preference and not jump around the two large chains / fork your own. Warmach may not be aware of the situation, any heads up to him to attend to this is appreciated.

Any instructions, and/or a blockchain file to download? I have two servers stuck at
2514283   8/3/18, 8:31:33 AM
despite of restoring back to 1st of July (and catching up), so maybe something wrong starting from that block?
Title: Re: Network status
Post by: Zska on September 06, 2018, 11:06:48 PM
1. Are you doing something to fix this fork situation?

2. Seems like you have stopped to pay Perustulo?
Title: Re: Network status
Post by: Zlotnik on October 14, 2018, 06:24:24 PM
What pools still work right now? If i understand properly Warmach's pool is on a fork, right?
Title: Re: Network status
Post by: eRoh on February 10, 2019, 08:49:46 PM
Security certificate of lompsa.com is expired. Could you update it?