@fimkrypto fimkrypto released this Feb 11, 2016 · 36 commits to master since this release

Assets 3

Users running 0.6.3 or later can update their FIMK installation through the update script.
To update to this latest release run this command in your installation folder.

sh update_fimk.sh 0.6.4 e02ba501fd1c321fcf4e5cda8274618beb1833366aaecc00d5bea06855a214b4

Thats it.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

███████╗██╗███╗   ███╗██╗  ██╗           Date    : 2016-02-11
██╔════╝██║████╗ ████║██║ ██╔╝           Release : 0.6.4
█████╗  ██║██╔████╔██║█████╔╝
██╔══╝  ██║██║╚██╔╝██║██╔═██╗            http://fimk.fi
██║     ██║██║ ╚═╝ ██║██║  ██╗           https://github.com/fimkrypto/fimk
╚═╝     ╚═╝╚═╝     ╚═╝╚═╝  ╚═╝           https://lompsa.com [online wallet]

Fixes a bug where fresh blockchain downloads could not verify one or more
block generation signatures.

Fixes a bug where pre-private-asset-fork asset issuance transactions where 
incorrectly read while uploading blocks to blockchain downloaders.

Introduces some new and extends some existing HTTP API's for use in new 
Lompsa client 2.0. These API's are likely to change in the future.

- - getTransactionCount
- - getAccountTransactionCount
- - getBlockchainTransactions

Introduces new websocket push event mechanism for use in Lompsa 2.0, through
this new mechanism clients can register/unregister for detailed server side
push events. Lompsa 2.0 new codebase and extension mechanism are tightly 
coupled with this event mechanism.

Adds column sort functionality to getNamespacedAlias API, this is also available 
in the bundled client.

Includes a fix for incorrect namespaced alias handling, this fix requires a 
hard fork of the network which will be enabled through the setting of another
hard fork alias (this functionality was introduced a few releases ago).

Before we enable the hard fork we would like to see a considerable amount of 
nodes to have updated.

                             ~~~ DOWNLOAD ~~~

https://github.com/fimkrypto/fimk/releases/download/v0.6.4/fim-0.6.4.zip

SHA256 e02ba501fd1c321fcf4e5cda8274618beb1833366aaecc00d5bea06855a214b4 
MD5    9ec0a3ec5b5fcf5cd2567f010adcde8c 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJWvKi1AAoJEH6Hp7CsNOLVbHcH/jl+gybWhKVzVyHBSzG9HCef
UnwroO1sajfejzsZMW3HPy9mQOBrj0f3gOwegL+c3HLfAXq9sumPnXs6yFylSqR5
BJzTaUc2cZz9ZY/d6bwkjkXFj64+x7D4p31ofnjBriH5pG007EefLz9InoOoE0Td
b62poIV12RK+aAddpUuwDl/fvBrrkHZ2e7cvUP85v5/2A16Qi/ziXTA8CJLUg3wS
r6a989MTXtq7rWsr1sowkWO0w1A6HzmVEAmleN5Wh9/EZLr6Zv6badr1SNKzruHL
wfAaZd9dQr3TmPUZZetlnDQ/X+y0ychKICu7CHKS5AgliQFjP2g+IIqH+QHg+Sk=
=MyJu
-----END PGP SIGNATURE-----

@fimkrypto fimkrypto released this Jan 30, 2016 · 65 commits to master since this release

Assets 3
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

███████╗██╗███╗   ███╗██╗  ██╗           Date    : 2016-01-30
██╔════╝██║████╗ ████║██║ ██╔╝           Release : 0.6.3
█████╗  ██║██╔████╔██║█████╔╝
██╔══╝  ██║██║╚██╔╝██║██╔═██╗            http://fimk.fi
██║     ██║██║ ╚═╝ ██║██║  ██╗           https://github.com/fimkrypto/fimk
╚═╝     ╚═╝╚═╝     ╚═╝╚═╝  ╚═╝           https://lompsa.com [online wallet]

Bug fix. Accounts that contain ask or bid orders from before the most recent
fork did not return correct results from getActivity API, this resulted in empty
activity lists in the client.

For users who do not access the getActivity API (either directly or through the
client) this update is not strictly necessary.

                          ~~~ UPDATE ~~~

The instruction displayed in the logs to update will be something like this:

    sh update_fimk.sh 0.6.3 [insert 64 character sha hash here]

To get around the missing update_fimk.sh file you instead must issue the 
following extra command to update to this version, in future versions this extra 
step is not needed since the build system now includes that script.

So to update to this release instead do this:

    curl -L -k -o update_fimk.sh https://git.io/vzhl9
    sh update_fimk.sh 0.6.3 [insert 64 character sha hash here]

If you would first like to inspect the shell script before executing it simply
open https://git.io/vzhl9 in your browser.

                             ~~~ DOWNLOAD ~~~

https://github.com/fimkrypto/fimk/releases/download/v0.6.3/fim-0.6.3.zip

SHA256 2093ef1dbd1e112d85fd6eb96603244400658d6d7ce165184d57faf19a6436b0 
MD5    7eee48f34f13614609ce60b27aa5ce45 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJWrL3qAAoJEP9gzPcARnvnkVsH/isHinJnGZw5ZQ7ZLdyP0TCK
hj9uTDDzzc9BsPMJLVXQcJlQaQAVkQtkJXRS3YQRoGaYZCRwWBa1UuX8Syv0Bubv
l7HxrXmXSLwKk+mnkEqQCtRQKWJXd/CSsihLVX4xKDJjTwTv2XkVCDr41d9DcRE2
UvHYDEKSi86MSvAyVuslAgJ9pZyGA29py4RGoMmrVyta9X7a5jjN7T5Pd6q4aooU
JpK0mdk3Rw/2cxtCCDopETd4hUCEudgxknuqkDoTVI80Uh20IRqD8x4KOOu4bK9v
xt81/oM+6tp4hvbPJOuMT6LjMADobhPl5qeE1YqYZr+OKbUbroHju/YhGXYB3io=
=Y8Tv
-----END PGP SIGNATURE-----

@fimkrypto fimkrypto released this Jan 28, 2016 · 69 commits to master since this release

Assets 3
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

███████╗██╗███╗   ███╗██╗  ██╗           Date    : 2016-01-28
██╔════╝██║████╗ ████║██║ ██╔╝           Release : 0.6.2
█████╗  ██║██╔████╔██║█████╔╝
██╔══╝  ██║██║╚██╔╝██║██╔═██╗            http://fimk.fi
██║     ██║██║ ╚═╝ ██║██║  ██╗           https://github.com/fimkrypto/fimk
╚═╝     ╚═╝╚═╝     ╚═╝╚═╝  ╚═╝           https://lompsa.com [online wallet]

Bug fix for fork issue shown in console as 'java.nio.BufferUnderflowException'.
The bug (fixed in this release) caused an error during blockchain scanning
or downloading.

To prevent peers from being on or switching to a possible fork caused by 0.6.0.
On startup we'll one time delete all blocks after PRIVATE_ASSETS_BLOCK and 
force a rescan.

This version blacklists all nodes on or below 0.6.0.

This release comes with a mechanism that allows the FIMK developers to notify
users of updates. The update notifications come with a simple instruction
to upgrade your current version.

We've also added a HardFork module which allows for saver and faster 
hardforks, fork heights are no longer hard coded in the java source but (much 
more flexibly) written on the blockchain instead. 

Special care was given to make sure these variable hard fork heights can only 
be set a single time (since you can change alias values). 

With these two mechanisms we believe we can now go and release updates at a much
faster pace and much more convenient for FIMK server operators. Without the risk
of forking the network without users noticing.

IMPORTANT INFORMATION ABOUT VERSION MANAGER ...

    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.

    LATEST VERSION (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}

    MINIMUM VERSION WARN (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]+

    MINIMUM VERSION BLACKLIST (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 must 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.

                             ~~~ DOWNLOAD ~~~

https://github.com/fimkrypto/fimk/releases/download/v0.6.2/fim-0.6.2.zip

SHA256 75fa306b987fd87f3b7900bc26df379f54e43e05e22a378b94bc83b0b7f1a6db 
MD5    3a0dd7dd1934f77fa54ece46d34db137 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJWqoVWAAoJEP9gzPcARnvnohMH/i1NnSdobvU3NmSM1zeIPDK0
ZEMKWizBWqv4gd34qgPSz+xkYQ5TNGFSseFux7MrTczbtOEQ3XECX/zCGm5paNnB
jXUd/MNqPB5txvsq0mTsxLPscpzb+bnKkfP01KZYyZQsUBRSYtm08CC165N/UFcw
DtecFZ0X7SP5hqHclUyKFwlsFZF0RIUa8nCy8XuLGjriqH+Z/20IYeIc2XLSuLdV
tXISnO+YK/n+AscMRV6HS+wg8vY2ry/LAJeurngVndRjrZTySX0/pStx9P5cHR0w
J9ZtJD0JXhIrJcPbBqCT9pSdsIR0nvOvpMBzQFZTsNcLR4GxmxIYddKeagDefR0=
=k4x8
-----END PGP SIGNATURE-----

@fimkrypto fimkrypto released this Jan 20, 2016 · 116 commits to master since this release

Assets 3
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

 /$$$$$$$$ /$$$$$$ /$$      /$$          Release : 0.6.1          
| $$_____/|_  $$_/| $$$    /$$$          Date    : 2016-01-20          
| $$        | $$  | $$$$  /$$$$                  
| $$$$$     | $$  | $$ $$/$$ $$          http://fimk.fi
| $$__/     | $$  | $$  $$$| $$          http://mofowallet.com
| $$        | $$  | $$\  $ | $$          http://forum.fimk.fi
| $$       /$$$$$$| $$ \/  | $$          https://github.com/fimkrypto/fimk
|__/      |______/|__/     |__/                 
                     /$$                                       /$$              
                    | $$                                      | $$              
                    | $$   /$$  /$$$$$$  /$$   /$$  /$$$$$$  /$$$$$$    /$$$$$$ 
                    | $$  /$$/ /$$__  $$| $$  | $$ /$$__  $$|_  $$_/   /$$__  $$
                    | $$$$$$/ | $$  \__/| $$  | $$| $$  \ $$  | $$    | $$  \ $$
                    | $$_  $$ | $$      | $$  | $$| $$  | $$  | $$ /$$| $$  | $$
                    | $$ \  $$| $$      |  $$$$$$$| $$$$$$$/  |  $$$$/|  $$$$$$/
                    |__/  \__/|__/       \____  $$| $$____/    \___/   \______/ 
                                         /$$  | $$| $$                          
                                        |  $$$$$$/| $$                          
                                         \______/ |__/  

This release blacklists all nodes that have not updated to 0.6.0, it seems 
not all nodes have updated to 0.6.* which will cause a fork of the network.

By running this version you can be sure not to end up on that fork that will
eventually die when everyone else updates to 0.6.*.

                             ~~~ DOWNLOAD ~~~

https://github.com/fimkrypto/fimk/releases/download/v0.6.1/fim-0.6.1.zip

SHA256 66a68b9591b79655568b485dd048d501e2761da310d43ce40b6c8ec828be1847 
MD5    aa6f644858a41d317b665d46f5bf1ed5 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJWn2tYAAoJEP9gzPcARnvnvB0H/1rlmXZN4X0vjEUvFnhGoX+T
8Rk9ROyxxnSnG5IX25ixbgt0yXQ9ro/xTe0huWWWxihQJiMknM8kRCq5Wfi8Hs57
DtmaKyBCW4mZAEaAjrMgGc42wLqoXeNZbb7pV+wQcisr7FyXFERbRn5dxS0OvB/B
nzQIY3zyIvbpxIfLKF0XJanhH04eF6kF5CtBnRHR+7LIAU0zAMuHBQJBdVcYrRD7
BpEZZSB/8eCkyM+DnhM71nBgah3sresHj7DTPLm1AHMU4XjArUhvB0YNJHPWOqNI
DZOwZaqPe5OzhHl9z4ZOLz8rOdKf6frzJ2GZ+ZPfHZRg8q0UKnZvcmwaYzImAsU=
=hdUn
-----END PGP SIGNATURE-----

@fimkrypto fimkrypto released this Jan 5, 2016 · 140 commits to master since this release

Assets 3
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

 /$$$$$$$$ /$$$$$$ /$$      /$$          Release : 0.6.0          
| $$_____/|_  $$_/| $$$    /$$$          Date    : 2016-01-05          
| $$        | $$  | $$$$  /$$$$                  
| $$$$$     | $$  | $$ $$/$$ $$          http://fimk.fi
| $$__/     | $$  | $$  $$$| $$          http://mofowallet.com
| $$        | $$  | $$\  $ | $$          http://forum.fimk.fi
| $$       /$$$$$$| $$ \/  | $$          https://github.com/fimkrypto/fimk
|__/      |______/|__/     |__/                 
                     /$$                                       /$$              
                    | $$                                      | $$              
                    | $$   /$$  /$$$$$$  /$$   /$$  /$$$$$$  /$$$$$$    /$$$$$$ 
                    | $$  /$$/ /$$__  $$| $$  | $$ /$$__  $$|_  $$_/   /$$__  $$
                    | $$$$$$/ | $$  \__/| $$  | $$| $$  \ $$  | $$    | $$  \ $$
                    | $$_  $$ | $$      | $$  | $$| $$  | $$  | $$ /$$| $$  | $$
                    | $$ \  $$| $$      |  $$$$$$$| $$$$$$$/  |  $$$$/|  $$$$$$/
                    |__/  \__/|__/       \____  $$| $$____/    \___/   \______/ 
                                         /$$  | $$| $$                          
                                        |  $$$$$$/| $$                          
                                         \______/ |__/  

FIMK 0.6.0 is a mandatory update, you must update to this version before:

                    Jan 18th 2016 - 21.00 GMT

This is a critical update and will cause you to be on a fork if you don't
update. The hard fork will happen by setting a set of pre-determined aliases
on the FIMK blockchain.  

FIMK 0.6.0 is based on NXT 1.5.10

  NXT 1.5.10 is the last NXT release before enabling the following 
  functionalities:

  - Monetary System
  - Voting
  - Phasing
  - Prunable Message Data

  At this stage while this code is ready and available on the FIMK testnet we
  did not yet decide to enable these functionalities on the main FIMK net.
  Instead this release enables only new FIMK functionalities.

FIMK 0.6.0 changes:

This release embeds Lompsa client 0.5.0.

Private Assets 

  When issueing an asset users can choose to issue a 'private' asset instead
  of a 'standard' asset. This functionality is implemented through a change 
  to the internal asset exchange mechanism where we've introduced the 'type'
  property for each asset. Currently there are the types 'standard' and 
  'private', in the future more asset types can be added through this 
  mechanism.

  A private asset is meant for use in financial institutions, it is an asset
  class which gives the asset issuer more control over the asset on the
  decentralized FIMK network.

  Issueing a private asset costs 10,000 FIM.

  A private asset issuer can do the following:

  1. Issue a new asset and mark it private

     To create a private asset either use the Lompsa client and tick the 
     'private' checkbox when issueing a new asset.
     Or use the HTTP API "issueAsset" and provide a "type" parameter which 
     is set to "1" for private assets. ("0" is the default but can be 
     omitted for standard assets). 

  2. Determine (to) who the asset can be traded or transfered.

     Accounts are either allowed or not allowed to trade and transfer, the
     asset issuer can add and remove these accounts.
     Buy or sell orders from accounts that are removed from the list of 
     accounts allowed to trade or transfer are automatically cancelled.

     Adding an account to the list of allowed accounts costs 10 FIM,
     removing an account from the list of allowed accounts costs 0.1 FIM.

     To add (or remove) allowed accounts either use the Lompsa client (see
     Lompsa Advanced section).
     Or use the HTTP API "addPrivateAssetAccount" or 
     "removePrivateAssetAccount", provide the asset identifier as the 'asset'
     parameter and set the account to add/remove as the transaction 
     recipient. 

  3. Set and collect trade fee

     Asset issuer can (optionally) set a trade fee for the private asset. 
     Upon each automated trade which occurs in the decentralized order 
     matching engine a percentage is taken from the receiving account, this
     is either FIM (or colored FIM) or the private asset being traded.

     Changing the trade fee costs 0.1 FIM, default trade fee is set to 0%.

  4. Set and collect order fee

     Asset issuer can (optionally) set a order fee for private assets. When
     selling an asset the order fee is paid as a percentage of the amount of
     assets offered, when buying an asset the order fee fee is paid as a 
     percentage of the total amount of FIMK (or colored FIMK) offered.

     Changing the order fee costs 0.1 FIM, default order fee is set to 0%.

     To change the order or trade fee percentage either use the Lompsa 
     client (see Lompsa Advanced section).
     Or use the HTTP API "setPrivateAssetFee" this API call allows to set  
     both order and trade fee with a single call. The call expects the 
     "asset" parameter to identify the asset and a percentage value for 
     either (or both) "orderFeePercentage" and "tradeFeePercentage".

     See the following table for what values relate to which percentages.

     -----------------------------------------------------------------------
     | Parameter (**FeePercentage)              | Actual percentage        | 
     -----------------------------------------------------------------------
     | 1                                        | 0.000001%                | 
     | 10                                       | 0.00001%                 | 
     | 100,000                                  | 0.1%                     | 
     | 1,000,000                                | 1%                       | 
     | 10,000,000                               | 10%                      |
     ----------------------------------------------------------------------- 

     When using the Lompsa client UI these values are calculated and 
     formatted automatically for you.         

Colored Accounts

  Colored accounts is a new FIMK feature which borrows it's name from the 
  concept of colored-coins.
  With colored accounts any user can create their own account color and create
  one or more initial colored accounts.

  This is similar in many ways to the Monetary System but with some key 
  differences:

  1. You must send FIM to a colored account to turn it into colored FIM (no need
     for large amounts - works just as well with NQT (0.00000001 FIM)).

  2. Colored accounts are not limited in functionality as Monetary System units
     are; colored accounts can be used in the Asset Exchange as well as in the
     Marketplace and all other current and future FIMK functionalities.

  3. Colored accounts are supported in the Lompsa client as regular accounts.

  4. FIM can be transfered to colored FIM and back to FIM again by sending it 
     to the color creator.

  Once the color creator has created the account color and the initial colored
  account is assigned you can create any new number of colored accounts simply 
  by sending them a payment, asset transfer or message. Only new accounts can 
  become colored accounts.

  Creating a new account color costs 10,000 FIM.

  To create a new account color either use the Lompsa client (see advanced 
  section).
  Or use the HTTP API "accountColorCreate" which expects a 'name' and 
  'description' parameter.

  To assign the initial colored account either use the Lompsa client (see
  advanced section).
  Or use the HTTP API "accountColorAssign" which expects an "accountColorId" and
  the "recipient".

Email Account Identifiers

  The preparation for this feature is still under way, this release enables the
  core requirements to move to this new method of identifying accounts.

                             ~~~ DOWNLOAD ~~~

https://github.com/fimkrypto/fimk/releases/download/v0.6.0/fim-0.6.0.zip

SHA256 0be939172917f1bc14cf1b09903b47045124f0fab12b5dfae1fb8f5f405c8470 
MD5    dee88e8164b84fd291a796c737414991 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJWi4Z4AAoJEP9gzPcARnvnloYH/1BIm6OUCy7SsPmnWMaXhD3Q
/bmPDgOgkRYLIVKgiT4KyW97XqG5jK3Jlw3irEygOsP3bEqpchea073dh2R+G1a/
gtUdVI7Bi13p9y9ys2vLKWR+mztv8mks/d4Vtk5IV28qLaclj1t8KzlsmAVkOefg
mR8fGUn6azK0SBlWWrwJP7zLsb0cNV5HXMDLOT8xreHes1RsD3CyULRyUsNpPHpY
1wCwivdMQKHfMnZsj7Vu04XP1325wLQEin/uOYgEiAr9uQOUGcqXmbBmLIG+BZpQ
G7TTCAHfXWHXlVCkv3ugPh11/W+Ll9rsBZoZqvax5Vh0XikVMhEb32tHETyad1E=
=ausr
-----END PGP SIGNATURE-----

@fimkrypto fimkrypto released this Apr 28, 2015 · 1986 commits to master since this release

Assets 3
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

 /$$$$$$$$ /$$$$$$ /$$      /$$          Release : 0.4.2          
| $$_____/|_  $$_/| $$$    /$$$          Date    : 2015-04-28          
| $$        | $$  | $$$$  /$$$$                  
| $$$$$     | $$  | $$ $$/$$ $$          http://fimk.fi
| $$__/     | $$  | $$  $$$| $$          http://mofowallet.com
| $$        | $$  | $$\  $ | $$          http://forum.fimk.fi
| $$       /$$$$$$| $$ \/  | $$          https://github.com/fimkrypto/fimk
|__/      |______/|__/     |__/                 
                     /$$                                       /$$              
                    | $$                                      | $$              
                    | $$   /$$  /$$$$$$  /$$   /$$  /$$$$$$  /$$$$$$    /$$$$$$ 
                    | $$  /$$/ /$$__  $$| $$  | $$ /$$__  $$|_  $$_/   /$$__  $$
                    | $$$$$$/ | $$  \__/| $$  | $$| $$  \ $$  | $$    | $$  \ $$
                    | $$_  $$ | $$      | $$  | $$| $$  | $$  | $$ /$$| $$  | $$
                    | $$ \  $$| $$      |  $$$$$$$| $$$$$$$/  |  $$$$/|  $$$$$$/
                    |__/  \__/|__/       \____  $$| $$____/    \___/   \______/ 
                                         /$$  | $$| $$                          
                                        |  $$$$$$/| $$                          
                                         \______/ |__/  

NXT 1.4.17 upstream changes:
  This is a critical bugfix release. Everyone is required to update.
  Fixed validation of asset exchange order cancellations.
  Fixed excessive memory usage in unconfirmed transaction processing.

FIMK 0.4.2 changes:

  - Removed the lucene index on the account name and account description 
    tables. this temporarily removes the search by account name functionality
    but i expect to re-introduce that in a future release.
    This change will dramatically increase the speed with wihch blocks can 
    be processed while downloading.

  - Removed the alias dependency for the public key hard fork change.
    From now on not requiring the public key is hardcoded in the source code.

  - Redone the build system that integrates and tunes mofowallet for use in
    FIMK server. This is not immediately visible to end users.

                             ~~~ DOWNLOAD ~~~

https://github.com/fimkrypto/fimk/releases/download/v0.4.2/fim-0.4.2.zip

SHA256 727d7e45d35f5f5501ad8dc3c111a67316e7051a60e31208e3e53ad3b6e4c56a 
MD5    96c021b942be7de3a5da8251b022de56 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJVP2UWAAoJEP9gzPcARnvnJ84H/1bOjcbEGlC2e562YqX957kV
N+xgXh28TFIn3a9lxynWy/YlVkecvNyNJ/tR+eFRhrBdtn+XIV5VozTu8Hx2QOZt
Cas6amVfccdjH56ZyyUNKs+IrPK2A+FYlW5GK0k4Uc6kqUSI5ZeKy9ytkm2hzv30
qh1VtZ8WQc3WlCw9fwMqH3MTNBBdCmC7Nwo/G5tWkyUUZWj4PW2qJkmucBs7gBj9
k7FJzjiE4Xqn/PiIYCuK2zkDPGu8qkRT8XAGqsuhMjFlsL8htExRf+QTSaUScnRS
SahQ8nzXhRd7MyNFs8hNRxE4JaYfGNEUlpopfXW1pN5UrPkw81z7UEGtbBYTE9Q=
=LNE6
-----END PGP SIGNATURE-----

@fimkrypto fimkrypto released this Apr 12, 2015 · 2008 commits to master since this release

Assets 3
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

 /$$$$$$$$ /$$$$$$ /$$      /$$          Release : 0.4.1          
| $$_____/|_  $$_/| $$$    /$$$          Date    : 2015-04-12          
| $$        | $$  | $$$$  /$$$$                  
| $$$$$     | $$  | $$ $$/$$ $$          http://fimk.fi       
| $$__/     | $$  | $$  $$$| $$          http://mofowallet.com
| $$        | $$  | $$\  $ | $$          http://forum.fimk.fi          
| $$       /$$$$$$| $$ \/  | $$          https://github.com/fimkrypto/mofowallet
|__/      |______/|__/     |__/                 
                     /$$                                       /$$              
                    | $$                                      | $$              
                    | $$   /$$  /$$$$$$  /$$   /$$  /$$$$$$  /$$$$$$    /$$$$$$ 
                    | $$  /$$/ /$$__  $$| $$  | $$ /$$__  $$|_  $$_/   /$$__  $$
                    | $$$$$$/ | $$  \__/| $$  | $$| $$  \ $$  | $$    | $$  \ $$
                    | $$_  $$ | $$      | $$  | $$| $$  | $$  | $$ /$$| $$  | $$
                    | $$ \  $$| $$      |  $$$$$$$| $$$$$$$/  |  $$$$/|  $$$$$$/
                    |__/  \__/|__/       \____  $$| $$____/    \___/   \______/ 
                                         /$$  | $$| $$                          
                                        |  $$$$$$/| $$                          
                                         \______/ |__/  

This is the FIMK server package, while you can run this on your computer it's
not intended as such. Users of the FIMK server package generally install it 
on a server.

For people looking for the installable FIMK client please check out our 
desktop client dubbed MofoWallet which can be found at our github repo which 
is here https://github.com/fimkrypto/mofowallet/releases.

http://fimkchat.com/2015/04/fimk-server-0-4-1-available-in-64-languages-baby/


FIMK 0.4.1 is based on NXT 1.4.13 (plus the critical parts of 1.4.16)

This release contains many bug fixes in both client and server. 

1. Many bugs fixed
2. Free text (instant) blockchain search
3. Client translated in 64 languages
4. Built into the client crowd-translator tool
5. New Payments module that allows for sending many payments at once 
  (basic income, dividends etc..)

                             ~~~ DOWNLOAD ~~~

https://github.com/fimkrypto/fimk/releases/download/v0.4.1/fim-0.4.1.zip

SHA256 8ff9982bd28d516e6454f260e3503314032ee3d57366c2580687671093b39624 
MD5    09917bc677449ee2b3ae31bad6bc5bf9 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJVKpWCAAoJEP9gzPcARnvnTMIIALzs27v1y9oTM9po30+K4TXK
cwvpBTC421Xi4LOflYh8cH4FECNKLfJmmSp4hkv6/Pu8JUNWVOUvCV/JAW3dAs9q
HcHBGSACMGLrVlScHu1DqAlY4ujdcV+AyMK4HOtly7X8oJlHBe9fKdqnpIwxo7AG
fY2+jy+U1bmRfB76DaQgER9RNkkVxEYuwDmvRo86Bj1J7D9Ab4CR/RdLIdHoNisK
X3pDHQkN+mEkZwj1NLR/8OglnZ1raTXGf3u4Exc58r5msrMNK19DqSDJWF444zvU
DTdHCRT7MxfWHeisgNikXCczfIdsJ7wP/UakPW44qygeOwFTtmjlvL1FZe1HrKM=
=A/N8
-----END PGP SIGNATURE-----

@fimkrypto fimkrypto released this Mar 20, 2015 · 2025 commits to master since this release

Assets 3
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

 /$$$$$$$$ /$$$$$$ /$$      /$$          Release : 0.4.0          
| $$_____/|_  $$_/| $$$    /$$$          Date    : 2015-03-20          
| $$        | $$  | $$$$  /$$$$                  
| $$$$$     | $$  | $$ $$/$$ $$          http://fimk.fi       
| $$__/     | $$  | $$  $$$| $$          http://mofowallet.com
| $$        | $$  | $$\  $ | $$          http://forum.fimk.fi          
| $$       /$$$$$$| $$ \/  | $$          https://github.com/fimkrypto/mofowallet
|__/      |______/|__/     |__/                 
                     /$$                                       /$$              
                    | $$                                      | $$              
                    | $$   /$$  /$$$$$$  /$$   /$$  /$$$$$$  /$$$$$$    /$$$$$$ 
                    | $$  /$$/ /$$__  $$| $$  | $$ /$$__  $$|_  $$_/   /$$__  $$
                    | $$$$$$/ | $$  \__/| $$  | $$| $$  \ $$  | $$    | $$  \ $$
                    | $$_  $$ | $$      | $$  | $$| $$  | $$  | $$ /$$| $$  | $$
                    | $$ \  $$| $$      |  $$$$$$$| $$$$$$$/  |  $$$$/|  $$$$$$/
                    |__/  \__/|__/       \____  $$| $$____/    \___/   \______/ 
                                         /$$  | $$| $$                          
                                        |  $$$$$$/| $$                          
                                         \______/ |__/  

This is the FIMK server package, while you can run this on your computer it's
not intended as such. Users of the FIMK server package generally install it 
on a server.

For people looking for the installable FIMK client please check out our 
desktop client dubbed MofoWallet which can be found at our github repo which 
is here https://github.com/fimkrypto/mofowallet/releases.




FIMK 0.4.0 is based on NXT 1.4.13 (plus the critical parts of 1.4.16)

This is a hard fork everyone MUST update to this release. The hard fork will go 
into effect the moment we set an alias that enables new accounts without public
key to receive FIMK.

On first startup a series of changes will be performed on the database, these 
changes are quite extensive and might take a while to complete. Just let it run
and FIMK will start when it's ready.

* Fixed the recent forking issues

* Upgraded to NXT 1.4.13/16 (most recent NXT release)

  Tons of upstream (NXT) security updates and general improvements.

  - Improvements in exception handling, transaction validation, error logging.
  - Prevent server from starting if any of the startup tasks failed.
  - Avoid unnecessary DNS queries.
  - No longer process or return "comment" parameters in Asset Transfer.
  - Stores all derived objects in the database, instead of keeping all of them 
    in memory only.
  - Startup time is now reduced to a few seconds only.
  - Everywhere, object ids that used to be Longs are now primitive longs.
  - Preserve and re-process unconfirmed transactions after fork resolution 
    pop-off.
  - Improved propagation of unconfirmed transactions.
  - Multiple minor improvements and optimizations based on profiling results.
  - Updated to latest Jetty version
  - Allow re-broadcasting of transactions already in the unconfirmed pool.
  - Show correct timestamps in asset transfer history.
  - Only try to set account public key when inside a database transaction,
    fixes a bug in setting public keys for accounts that never had an
    outgoing transaction.
  - Improved default H2 cache size allocation.
  - Disabled the SSLv3 protocol when using SSL for the API.
  - Fixed incorrect guaranteed balance bug in getAccountLessors API.
  - Cache hallmarked peer account balances to reduce number of database calls.
  - Other minor performance improvements and bugfixes.
  - Fixed decryption of purchased DGS goods.
  - Fixed missing DGS purchase feedbacks.
  - Implemented full text search using the Lucene library, as supported by H2.
  - Show purchase counts and public feedback counts in all API responses 
    returning Goods JSON, unless includeCounts parameter is false.
  - Increased default purchase delivery deadline to 168 hours (1 week).
  - Include full peer info in getPeers API if includePeerInfo=true, to avoid 
    having to do a separate getPeer request for each peer.
  - Allow transaction signing in signTransaction to skip the validation of the
    transaction bytes being signed, if an optional validate=false parameter is 
    added.
  - Allow sending messages with no recipient.
  - Automatically blacklist peers with version older than 0.3.3
  - After the Monetary System block, the order in which transactions in a block 
    are executed will be determined by the block forger, instead of by id, 
    default being by arrival time at the forger's node.
  - Improvements in blockchain download to prevent getting stuck on the wrong 
    fork.
  - Nodes will download blocks in batches of not more than 719 blocks at a time
    from a single peer, and after each such batch will verify  with
    nxt.numberOfForkConfirmations other peers (default 5) if this is the best
    fork, before continuing, unless the downloaded batch is of less than 10 
    blocks.
  - Rescan status is now saved in the database, to prevent the database from 
    being left in an inconsistent state when a rescan fails or is interrupted. 
    Once a rescan has been scheduled, it will be triggered again at restart, 
    until it completes successfully.
  - Improvements in the processing of unconfirmed transactions.
  - Fixed currency decimals issue.
  - Fixed minor bugs in MS transaction validation.
  - Additional validations of Monetary System transactions, and bugfixes
    in existing validations.
  - Bugfixes in currency minting and in MintWorker.
  - Improved peer networking to run the sending of blocks and transactions
    to peers in a background thread.
  - Do not log currency exchanges of zero amount.
  - Fixed setting of peer state. Improvements in connecting to peers.
  - Enforce that currency exchange offer expiration height is after the current
    blockchain height.
  - The Message Pattern in AccountInfo feature, introduced in 1.4.0e, has been
    disabled, and will not be activated. This is to prevent
    possible denial of service attacks by malicious regular expression patterns
    which can cause excessive CPU load with certain inputs.
  - Enhanced nxt.allowedBotHosts property to also accepts a range of addresses
    using CIDR notation.
  - Allow no more than one unconfirmed minting transaction per account and minted
    currency to be accepted in the unconfirmed pool.
  - Better validation of hallmarks for peers with multiple addresses. Do not
    blacklist peers with invalid hallmarks but just treat them as not hallmarked.
  - Minor peer networking improvement, addPeers and processBlock requests are now
    executed in the background.
  - Improvements in fork resolution. The peer networking getNextBlocks API no 
    longer limits the number of blocks returned to 1 MB total payload size, 
    but always returns 720 blocks, if available.
  - Fixed a bug in transaction bytes parsing which could cause signature
    verification failed errors and break forging.
  - When downloading the blockchain, require at most one fork confirmation when
    still below the last hardcoded checkpoint.
  - Peer port handling has been improved to allow different peers to share the 
    same IP address provided they use different ports.
  - To prevent overloading a node with invalid peer addresses, the maximum total
    number of known peers is limited to nxt.maxNumberOfKnownPeers (default 2000).
    Once this number has been reached, new peer addresses are not added, and peers
    that have been last connected to more than a week ago are removed from the known
    peer list, provided the node has enough connected public peers, until the number
    of known peers is again reduced to below nxt.minNumberOfKnownPeers (default
    1000).
  - Improved database performance by storing currency supply and reserve per unit
    data in a separate table.
  - Fixed a bug in transaction validation that could break blockchain downloading.
  - The default (and minimum allowed) value for nxt.maxRollback is now 1441.
  - Restrict maximum HTTP request and response size in peer networking to prevent
    potential out of memory attacks.
  - Improved fork resolution by allowing a better difficulty block pushed from a
    peer to replace the current last block.
  - When forging, do not accept a peer block with hit time after the next hit time
    of a currently forging account (i.e. prevent front-running in forging).
  - Removed the possibility of a forger to miss his turn. Even if late, the block
    will still be generated and submitted.
  - Delay forging and submission of blocks by 20 s, configurable via the
    nxt.forgingDelay property, in order to be able to accumulate more transactions
    in the forged block. The arrival of a front-running block from a peer however
    cancels that delay and the next block is generated up to 3 s earlier instead,
    which can be controlled via the nxt.forgingSpeedup property.
  - Better logging of peer networking errors. Log, but do not blacklist missing or
    malformed JSON responses.
  - Database optimization. Moved the public key of accounts, transaction senders,
    and block forgers to a separate table, resulting in 15% reduction of total
    database size.
  - Enforce that the nxt-default.properties file used matches the version of the
    current release.
  - Peer networking improvements, better logging, bugfixes.

* The NXT client (known as wesley client) has been removed from the FIMK server 
  package. A slimmed down single currency (without NXT support) version of
  the FIMK client (aka MofoWallet) has replaced it.

  If people want the old client back they can copy it back from the FIMK 0.3.3 
  release. You should copy the entire 'html' folder from 0.3.3 and move it to 
  FIMK 0.4.0. Then in nxt.properties set 'nxt.apiResourceBase=html/ui'.

  We will no longer do work on the old client.

* FIMK now has an embedded WebSocket server, it's separate from the existing
  API server. 

  The WebSocket protocol is an improvement of the more than 25 year
  old HTTP protocol. WebSockets are faster, more efficient and allow for 
  two-way communication.

  See these posts for background information:

  http://fimkchat.com/2015/03/connecting-to-fimk-websockets/
  http://fimkchat.com/2015/03/fimk-adds-websocket-support-to-its-core/

* New functionality for FIMK is now exposed as asynchronous RPC calls accessed 
  over the WebSocket server.

  Because of the two-way communication abilities of WebSockets now RPC calls 
  can be created that do work in a background thread on the server and will 
  notify the client when they are ready. Meanwhile the server and client can 
  be used as normal.

* The old API server is turned off by default. If you need to access it you can
  enable it in nxt.properties through 'nxt.enableAPIServer=true'

* A bridge exists in the callFunction RPC to call any old API method by name,
  the old API calls are accessed from memory so no need to actually run/start
  the API server (saves memory/cpu).

* Tons of new RPC calls, each one tailored to support a different aspect of the
  FIMK client (aka MofoWallet).

  List of new RPC calls (WebSocket API).

  - CallAPIFunction  
    Call any old API calls in the old HTTP API server. We support each call 
    listed here http://wiki.nxtcrypto.org/wiki/Nxt_API. It is not necessary
    for the API server to be running.    

  - GetAccount  
    Returns the account balance, name and some other account related things. 

  - GetAccountAssets  
    Allows to paginate through list of account owned assets. Asset data always 
    includes the asset name, decimal places etc for easy access on the client.
    Pagination is index based. 

  - GetAccountCurrencies  
    Allows pagination through all currencies owned by an account, currency 
    details are always included.
    Pagination is index based.

  - GetAccountPosts  
    Allows to paginate through all POSTS written by an account. 
    POSTS are stored in the mofo_post database table.
    Pagination is index based.

  - GetAssetPosts  
    Same as account posts but works for asset posts

  - GetComments  
    Allows to paginate over comments for account and asset posts.
    Pagination is index based.

  - GetCommentCount  
    Returns the number of comments for a post.

  - GetAccounts  
    Returns balances for multiple accounts

  - GetActivity  
    Returns blocks, transactions and trades. This extensive RPC call can be used
    to return all trades + transactions spanning a selection of blocks. Supports
    a filter mechanism to query for transactions based on time and on a range
    of transaction types.

  - GetActivityStatistics  
    Returns network statistics, average block time, block rewards per day, week 
    month.

  - GetAskOrder, GetBidOrder  
    Returns an ask/bid order.

  - GetAsset  
    Does what it says

  - GetAssetChartData  
    There is a listener that listens trades in blocks. The asset prices are 
    bundled per hour, 3 hour, day and week to get a moving average and open, 
    close, high, low and average prices. 
    These moving averages (and open/close etc) are stored in a new table in the
    database and this RPC accesses that data.

  - GetAssetOrders, GetAssetTrades  
    Does what it says. Pagination is index based.

  - GetBlockchainState  
    Minimalist blockchain state includes only height and timestamp.

  - GetForgingStats
    Allows paginating over the list of top forgers for the past 24 hours.
    Pagination is timestamp based.

  - GetMyOpenOrders
    Allows paginating over all open orders but for a list of accounts.
    Pagination is index based.

  - GetRecentTransactions
    Returns recent transactions (includes unconfirmed) for a list of accounts.
    Supports the same filter mechanism as GetActivity RPC.
    Pagination is index based.

* New feature.. Write POSTS/BLOGS linked to an Account or Asset. The POSTS are
  stored on the blockchain (for now) and are entered through AM (arbitrary 
  messages). The AM format was chosen instead of a new transaction type in 
  order to stay compatible with NXT and allow the functionality to be used in 
  multi-currency MofoWallet client.

  The POSTS are stored in the database and are fully aware of blockchain reorgs.

  Note: POSTS are limited to accounts and assets but will be extended to 
  currencies and goods on the goods store.  

* New feature.. Write COMMENTS to POSTS/BLOGS every account can leave a comment
  on each Asset or Account POST.

* Added tests for most new functionality

* Upcoming big feature PRIVATE ASSETS.

                             ~~~ DOWNLOAD ~~~

https://github.com/fimkrypto/fimk/releases/download/v0.4.0/fim-0.4.0.zip

SHA256 de58bc4a8b256e71bb3e9a37a066422e777d649c32d0f5838f5d5def6eb1d7a5 
MD5    76a905741dd7954f80f485a11aa68459 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJVDFTLAAoJEP9gzPcARnvnzwoH/i9TqpsXfM6WmYM8nHH2kpmP
p7MGFa26frJ7gSxxgrSsRE1gvexNmus1eibtZ+1LT/uIkch3Lm/Xph7QAnRH9h5s
cZ266Kz88pA4B3CadsOG5cbacLofQue2wyU+J4gwLrGqOF+owfob9w0rox+N03PM
qFNIoYn/mM/bTiKCXuBvktcph0Hu1ecTWSSojfNCfVq1H7O4ZLdQs1iWzKHMhUI3
PF+XunNyfwnzwD0lKIOH1LUk1PGzwmfpNPBcidQsS4/a3Jsk/2qv6krk6Gex40+v
ZndWR8cV6ZX0Xwnak30VCo7FW5yDo8y/W53dT5xizviahc1a4KROhUL8qxVTX0o=
=1uAF
-----END PGP SIGNATURE-----
Assets 3
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

 /$$$$$$$$ /$$$$$$ /$$      /$$                Release : 0.3.3          
| $$_____/|_  $$_/| $$$    /$$$                Date    : 2014-12-20          
| $$        | $$  | $$$$  /$$$$                  
| $$$$$     | $$  | $$ $$/$$ $$                http://fimk.fi       
| $$__/     | $$  | $$  $$$| $$                http://forum.fimk.fi
| $$        | $$  | $$\  $ | $$                http://mofowallet.com
| $$       /$$$$$$| $$ \/  | $$                https://github.com/fimkrypto/fimk                 
|__/      |______/|__/     |__/                 
                     /$$                                       /$$              
                    | $$                                      | $$              
                    | $$   /$$  /$$$$$$  /$$   /$$  /$$$$$$  /$$$$$$    /$$$$$$ 
                    | $$  /$$/ /$$__  $$| $$  | $$ /$$__  $$|_  $$_/   /$$__  $$
                    | $$$$$$/ | $$  \__/| $$  | $$| $$  \ $$  | $$    | $$  \ $$
                    | $$_  $$ | $$      | $$  | $$| $$  | $$  | $$ /$$| $$  | $$
                    | $$ \  $$| $$      |  $$$$$$$| $$$$$$$/  |  $$$$/|  $$$$$$/
                    |__/  \__/|__/       \____  $$| $$____/    \___/   \______/ 
                                         /$$  | $$| $$                          
                                        |  $$$$$$/| $$                          
                                         \______/ |__/            

FIMK 0.3.3 is based on NXT 1.2.6.

This is a hard fork everyone MUST update to this release. 

This release and all future releases blacklist any peer that is on or below 
version 0.3.2. 

On startup a one time scan and verification of the blockchain will be performed. 
Deleting your folder blockchain is not required for this update.

About the hard fork:

  On Friday December 19th 2014 we were informed of a theft of 57 Million FIMK 
  from a user's account by a hacker, who gained gained access to the accounts 
  through the user carelessly sending his account passphrases to a rigged public 
  node. The hacker transferred a total of approx. 57 Million FIMK from several 
  accounts to 59 other accounts, each account receiving roughly 1M FIMK. 
  In total this amounts to 13.9 % of all FIMK in existence at this time.

  As the portion of stolen funds is a significant portion of the total FIMK in 
  circulation, the association is obliged to intervene. To avoid a situation 
  where FIMK would at the mercy of a thief in possession of a large portion of 
  total funds, strengthening her stake by forging constantly and thus gaining 
  undue control of the network, AND likely dumping some of the large stash 
  constantly rendering the remaining FIMK worthless (as has happened before with 
  other coins in similar large scale incidents) the association decided to freeze 
  the hacker assets by releasing customized emergency version of the FIMKrypto 
  server which does just that. 

  This release temporarily seals the stolen FIMK in the protocol making them 
  untouchable by no one, not even by the association. This is done to prevent 
  mixing of the stolen funds through further transfers to obfuscate the origin, 
  which we were able to prevent just in time. The following steps and measures 
  to be taken for the frozen stash are discussed with the community and decided 
  on the basis of those discussions.

Mandatory update

  Earlier server releases (before 0.3.3) are blacklisted by default to prevent 
  the chance of future forks and keep the network coherent.

Hacker accounts locked

  There are 59 accounts identified that hold the stolen FIMK, the public keys to
  these accounts are locked from making outgoing transactions and are not allowed
  to forge blocks.



                             ~~~ DOWNLOAD ~~~

https://github.com/fimkrypto/fimk/releases/download/v0.3.3/fim-0.3.3.zip

SHA256 6d4a17cd24f74031b2fe4ea4fb62b8f62b49987f49f1986c234433aa27c56daf 
MD5    cc5e8c8aa32f6ee0dcc0e7a1ed696a0f 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJUldAtAAoJEP9gzPcARnvnipwH/ixagY+l9jaCEMRywyUrbvFk
JXDKckz34VVC7uHY59razENP4sdlLD8t8FXicy/YHYAjIDFChr9woSg+lPJSDAJP
YOy8zKjiLi+aj4KG3Bl2G/2Lxfl383Zs039cNCoDcOyLMFS/eeLi+aUuSifnuANl
f4f+8uz8rcjq0KYS8Xk1fHEiS/W9+NxDDXRrzRB0v4NlFvWkx0apU9sdfZz1nwmH
DbK6NFjDinecvjN5PgRzjLp/iLcRe7j8RStKl/3LYYTMgKEl7a1LhIg3Uc1MlUj7
WjqVoNsbXLro0fKQMuCpgY4vdn6OUikqm4+Oh0fiwmliSYgFASbj+7K43jU3Wjc=
=nWvD
-----END PGP SIGNATURE-----

@fimkrypto fimkrypto released this Dec 19, 2014 · 3782 commits to master since this release

Assets 3
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

 /$$$$$$$$ /$$$$$$ /$$      /$$                Release : 0.3.2          
| $$_____/|_  $$_/| $$$    /$$$                Date    : 2014-12-19          
| $$        | $$  | $$$$  /$$$$                  
| $$$$$     | $$  | $$ $$/$$ $$                http://fimk.fi       
| $$__/     | $$  | $$  $$$| $$                http://forum.fimk.fi
| $$        | $$  | $$\  $ | $$                http://mofowallet.com
| $$       /$$$$$$| $$ \/  | $$                https://github.com/fimkrypto/fimk                 
|__/      |______/|__/     |__/                 
                     /$$                                       /$$              
                    | $$                                      | $$              
                    | $$   /$$  /$$$$$$  /$$   /$$  /$$$$$$  /$$$$$$    /$$$$$$ 
                    | $$  /$$/ /$$__  $$| $$  | $$ /$$__  $$|_  $$_/   /$$__  $$
                    | $$$$$$/ | $$  \__/| $$  | $$| $$  \ $$  | $$    | $$  \ $$
                    | $$_  $$ | $$      | $$  | $$| $$  | $$  | $$ /$$| $$  | $$
                    | $$ \  $$| $$      |  $$$$$$$| $$$$$$$/  |  $$$$/|  $$$$$$/
                    |__/  \__/|__/       \____  $$| $$____/    \___/   \______/ 
                                         /$$  | $$| $$                          
                                        |  $$$$$$/| $$                          
                                         \______/ |__/            

FIMK 0.3.2 is based on NXT 1.2.6.

Temporarily blocked all transactions from acccounts with confirmed stolen funds 
after a major theft of 57M FIMK



                             ~~~ DOWNLOAD ~~~

https://github.com/fimkrypto/fimk/releases/download/v0.3.2/fim-0.3.2.zip

SHA256 7df3f9ffd5926d024202b820417eb9f48c04681b4a0c11c3b9d5604cfb255e32 
MD5    b128d3cec7df25320c113791594794fc 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJUlDmiAAoJEP9gzPcARnvnqsYH/RSYDZ/HVNoRckgmiIsVU+Pf
YbbUOPOAply2dcoopVsoqy4EnpFq2wRXedPt9wl5aYwQ8I3eLjShZRAWO7iPVKF3
bs8gKWcllOfNoEeuF9PjDokTnFAAO0z0ddlZKHgLCYhlZqWo+iiE3bbKDCWm8UOZ
S3c0a6CgJifc9wfX1f/bVFGlZ4jhUNruIGZkK8jKKIzTGJUpmnVC7MZqfqbWAe0B
YuR8jmUXKfarEr00aDIF6v/ZehrCE0lQisRvprFf9WB0kIaBBiF0lGepBsBxQg/X
gEzr0MgtNyAm+wmzbVtkNlYRwrB2jNbxiBnHwK0v0cxFAZumpm8m7weLxejUD1k=
=nWEc
-----END PGP SIGNATURE-----