Author Topic: Where have all the forgers gone?  (Read 8451 times)

kani on: January 26, 2016, 04:42:02 AM

  • Senior Fimker
  • ***
  • Posts: 154
    • View Profile
I used to see many blocks by these, but they have all gone away (some recently, some long ago):
Quote
Addresses removed
Right now mostly:
Quote
Addresses removed

Oh where, oh where
have the forgers gone?
Oh where, oh where
can they be?


EDIT: Most of the forgers are back.  Removed the lists of FIMK addresses.
« Last Edit: February 20, 2016, 02:24:57 AM by kani »
BitShares - Your share in the Decentralized Exchange

eRoh #1 on: January 26, 2016, 05:47:38 AM

  • Grand Fimker
  • ****
  • Posts: 324
    • View Profile
Have you checked, if they are leasing?
FIM-34B3-PWY5-TMHC-9JYW8

kani #2 on: January 26, 2016, 05:54:59 AM

  • Senior Fimker
  • ***
  • Posts: 154
    • View Profile
None are leasing, although REDACTED had a lease recently expire to REDACTED.

These are all big boys.  IMHO they should be forging on their own anyway -- the pools look plenty big.


EDIT: Removed FIMK addresses
« Last Edit: February 20, 2016, 02:26:25 AM by kani »
BitShares - Your share in the Decentralized Exchange

Eliphaz Fimk #3 on: January 26, 2016, 07:31:46 AM

  • FIMKrypto coordinator
  • Administrator
  • *****
  • Posts: 821
    • View Profile
    • FIMKrypto
There are some forking / incompatibility issues after the last update was deployed. I've been informed further updates are released to bring things back in order.

gaianhuuto #4 on: January 26, 2016, 10:41:23 AM

  • Grand Fimker
  • ****
  • Posts: 480
    • View Profile
FIMKers' Pool is still forging. We've lately experienced some issues so our uptime hasn't been the usual 99,99%. Our pool consists of 22 leasers at the moment.
TurnTrips.poker - Ässät pöytään ja kryptovaluutat jakoon.

warmach #5 on: January 26, 2016, 01:33:12 PM

  • Senior Fimker
  • ***
  • Posts: 231
    • View Profile
Warmach's Pool is still going too.  We're at 8 lessors ourselves right now, myself included.
Warmach's Forging Pool
http://fim.warmach.info/pool/
May the forge be with you...

Dirk Diggler #6 on: January 26, 2016, 01:48:15 PM

  • FIMK Staff
  • *****
  • Posts: 486
    • View Profile
    • Krypto Fin ry
I'm still testing the version manager (and it's integration) but figured i'd share this bit since it will likely prevent these fork issues in the future.

/**
 * The version manager reads application version data from the blockchain.
 * Peers who chose to do so can have their FIMK software periodically check the
 * blockchain and be notified when their current version is out of date.
 *
 * There are three values on the blockchain that are involved in this process.
 *
 * Alias LATESTVERSION (9266582752086146948)
 *
 *    This alias holds the most recent available version and a SHA256 checksum
 *    of the downloadable package.
 *    The version notifcations use this version and checksum to generate a
 *    command you should run to update your current version to LATESTVERSION.
 *
 *    The expected format for this alias:
 *
 *        [0-9]+\.[0-9]+\.[0-9]+(-.+)?\s+[a-z0-9]{64}
 *
 * Alias MINVERSIONWARN (17359617168004080578)
 *
 *    This alias holds the version number and blockheight, only after the
 *    blockheight has passed will the version manager act upon this.
 *    The version number is the minimal version you should run before we start
 *    issuing notifications that your version can be updated.
 *
 *    You can disable this functionality in your nxt.properties config file.
 *    Set `nxt.warnNotLatestVersion=false` to disable this functionality.
 *
 *    The expected format for this alias:
 *
 *        [0-9]+\.[0-9]+\.[0-9]+(-.+)?\s+[0-9]+
 *
 * Alias MINVERSIONBLACKLIST (9364249966090852339)
 *
 *    This alias holds the version number and blockheight, only after the
 *    blockheight has passed will the version manager act upon this.
 *    The version number is the minimal version you should run before we issue
 *    a notification that your version can be updated.
 *
 *    When the version manager detects you run a version up or below this
 *    version your server WILL BE SHUTDOWN. To start the server again either
 *    update (recommended) or disable this feature in nxt.properties.
 *
 *    Peers who enable this feature will start to blacklist all nodes on the
 *    network that are running a version on or below this version.
 *
 *    You can disable this functionality in your nxt.properties config file.
 *    Set `nxt.shutdownWhenOutdated=false` to disable this functionality.
 *
 *    The expected format for this alias:
 *
 *        [0-9]+\.[0-9]+\.[0-9]+(-.+)?\s+[0-9]+
 *
 * As mentioned the default behavior for clients who do not disable this feature
 * is for their servers to SHUTDOWN when we detect the server version is up or
 * below MINVERSIONBLACKLIST.
 *
 * The rational behind this is to protect users from accidentally landing on a
 * network fork because of a required update they've missed.
 *
 * Running an unsupported version is dangerous and should be avoided for several
 * reasons:
 *
 *    1. Forgers running an unsupported version will loose their FIMK forged
 *       on that fork. Electricity is wasted running your server and damage is
 *       caused to the rest of the network when you send blocks or transactions
 *       that are incompatible.
 *    2. Exchange operators running an unsupported version run the risk of
 *       loosing money when on a fork. The exchange software will accept
 *       FIMK deposits and credit BTC or other internal tokens to the depositor
 *       if these deposits where made while on a fork the exchange will loose
 *       the deposited FIMK.
 *    3. Merchants very similar to exchange operators risk the loss of funds
 *       when they accept FIMK payments while their server is on a fork.
 *    4. Ordinary users who accept payments or asset transfers risk loosing
 *       those funds since they are on a fork.
 *
 */
FIMK Developer | GPG fingerprint: CEF2 7C39 43BE 6800 504E  71BC 7E87 A7B0 AC34 E2D5 | mofowallet.com | blog

kani #7 on: January 26, 2016, 06:19:53 PM

  • Senior Fimker
  • ***
  • Posts: 154
    • View Profile
Blockchain looks a little healthier now, but could be much better.

Too many blocks from single forger 82J2S now.

(I certainly mean no disrespect for these large single forgers I've mentioned in this thread, just that a healthy blockchain should have better distribution of block creators).  More blame rests on those who are not forging.
BitShares - Your share in the Decentralized Exchange

kani #8 on: January 26, 2016, 07:09:04 PM

  • Senior Fimker
  • ***
  • Posts: 154
    • View Profile
damage is caused to the rest of the network when you send blocks or transactions that are incompatible.

Um, please tell me this statement is a simplification

From my background it seems that relying on 'perfect' data from peers is a very dangerous assumption.
BitShares - Your share in the Decentralized Exchange

Dirk Diggler #9 on: January 26, 2016, 07:37:44 PM

  • FIMK Staff
  • *****
  • Posts: 486
    • View Profile
    • Krypto Fin ry
Um, please tell me this statement is a simplification
From my background it seems that relying on 'perfect' data from peers is a very dangerous assumption.

You are correct this is a simplification.
In no way do we rely on perfect data.

But there are cases where data that 'seems' valid is accepted by peers running older versions.
This could 'confuse' these older version peers in accepting a block or transaction that does seem valid in the older version but is not accepted on the newer versions, this leads to a fork of the network.

Eventually if the target of the 'main' fork is higher the older peers could possibly switch back to the other fork but for this to happen all bad blocks and transactions have to be deleted and re-downloaded (automatically).

Damage is probably not the right word, better way to put it is that it causes unnecessary negative side effects (like unnecessary re-downloading or unnecessarily blocking of otherwise non-evil peers).
FIMK Developer | GPG fingerprint: CEF2 7C39 43BE 6800 504E  71BC 7E87 A7B0 AC34 E2D5 | mofowallet.com | blog

kani #10 on: January 26, 2016, 07:56:04 PM

  • Senior Fimker
  • ***
  • Posts: 154
    • View Profile
Okay, that helps my understanding.  Thanks!
BitShares - Your share in the Decentralized Exchange

gaianhuuto #11 on: January 27, 2016, 07:57:53 AM

  • Grand Fimker
  • ****
  • Posts: 480
    • View Profile
FIMKers' Pool is having nasty problems at the moment. Forging works for a few hours and then I hit a fork and forge away on my own... I apologize to all lessors for mediocre uptime. Can't stay up all nite ^^
TurnTrips.poker - Ässät pöytään ja kryptovaluutat jakoon.

Dirk Diggler #12 on: January 27, 2016, 01:38:24 PM

  • FIMK Staff
  • *****
  • Posts: 486
    • View Profile
    • Krypto Fin ry
FIMK Developer | GPG fingerprint: CEF2 7C39 43BE 6800 504E  71BC 7E87 A7B0 AC34 E2D5 | mofowallet.com | blog

Eliphaz Fimk #13 on: January 27, 2016, 06:53:57 PM

  • FIMKrypto coordinator
  • Administrator
  • *****
  • Posts: 821
    • View Profile
    • FIMKrypto
Seems to be a theme around the world these days http://news.sky.com/story/1630575/apples-safari-browser-crashing-around-the-world
Hmm it's slightly challenging to see the relevance and the train of thought there. Strange problems. Thumbs up Safari will start to behave properly soon enough!

Dirk Diggler #14 on: January 29, 2016, 12:21:21 PM

  • FIMK Staff
  • *****
  • Posts: 486
    • View Profile
    • Krypto Fin ry
Hmm it's slightly challenging to see the relevance and the train of thought there. Strange problems. Thumbs up Safari will start to behave properly soon enough!

It seems we have beat them to it  ;D
Everybody update to 0.6.2 please, good chance lots of (big) forgers have been on a fork this past week.

Update to 0.6.2 and all future updates become a breeze.

https://bitcointalk.org/index.php?topic=633304.msg13707939#msg13707939
FIMK Developer | GPG fingerprint: CEF2 7C39 43BE 6800 504E  71BC 7E87 A7B0 AC34 E2D5 | mofowallet.com | blog