Skip to main content

about Gridcoin

Search This Blog

Posting also here from now on...

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

The recent events have shown that a backup is always nice.
I've added now the downvoted stuff in this blog also...

From now on I will post also to here, in addition to here.

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Comments

Post a Comment

Popular Posts

Which BOINC projects were affected most by the "magnitude zero" events ?

link to image I looked at the BOINC projects + users that were "victims" of the last magnitude zero events. As you can see, users from these 3 BOINC projects have "suffered" the most from the mag zero and its effects, in total 10 days (237h): Numberfields (w13) Rosetta (w15) SETI (w16) And also: Citizen science grid (w3) Einstein (w6) LHC (w9) VGTU (w22) World community grid (w23) The least affected was: Amicable Numbers (W1) Some side effects to be investigated: the users who were affected most: did they or plan they to switch projects b/c they saw for other projects there were magnitudes? how deterring are these troublesome superblock events for new users, outsiders ? I'll add later more to the table (amount users, ...) See also: Gridcoin + its troublesome superblocks (in the last 4 weeks)

Gridcoin + its troublesome superblocks (in the last 4 weeks)

The average superblock creation time was about 47h (median = 36h). I am not counting the to-come-superblock now, for which we wait already for 44h (K) link to image The current dev team definitely needs help, ... and it looks like the poll on the " 32 million GRC expense " (poll title: Developer Reimbursement 6 Month Package , vote until July 29) will be ACK'd (and yes, I know that the term " 32 million GRC expense " might cause disbehaviour in some, but I have not a satisfying answer on my question that it will NOT be 32 mio GRC, or whatever the highest limit may be) Unfinished thoughts: What can be seen is that the 3.5.9.1 and 3.5.9.2 versions did not seem to fix the situation. And the current, long waiting time (46h) for the next superblock (K) seems to indicate 3.5.9.3 + 3.5.9.4 did not help either . We have to wait and see. Why didn't we have a mandatory version since over 3 months (last mandatory: April 2, version 3.5.8

Coincidence? 4-5 days after each release a forking situation?

One user asks here: " Is it common for other coins to have fork "situations" once a week or is that unique to Gridcoin? " Well, see e.g. "Forks happen all the time, you could say with every new block. With every cryptocoin that is out there, and the clients notice this soon and bring you back on track." and more in the prelude here . But... I looked at the data (since we have since >4 weeks superblock troubles ) (link on steemit ) and saw this: 4-5 days after the new releases (3.5.9.4 and 3.5.9.2) we had a fork: (L) + (G) which we successfully coordinated in the IRC channels with the people being on the fork I also noticed, though: that the "self-healing" of the client in fork situations did NOT work :-( People were for >1h and >3h on the fork still. (link to image) I'm wondering if this is just bad luck or another factor? e.g. some events on/before weekends (since it happened on a Friday +

Powered by Blogger