Topic: [ANN] FIMK: 2.5G POS, extra block rewards, messaging, asset colors, p2p shopping - page 8. (Read 184356 times)

so is there a new lompsa that embeds 0.6.4 server? I have lompsa 0.6.1 which seems to have server 0.6.2.

Your FIMK seems to still be at the address you send it to https://lompsa.com/#/accounts/FIM-UFBX-HNF7-SAKY-9C9LU/activity/latest, with matching transaction id even.
Are your sure that address belongs to CCEDK?


You could ask for a transaction id. Through the API you can inspect the details of this transaction

https://cloud.mofowallet.org:7886/nxt?requestType=getTransaction&transaction=16155014996718816215

I have an issue in that I recently sent about 8,000 Fimk to an my CCDEK address which I've used before: FIM-UFBX-HNF7-SAKY-9C9LU

The transaction has not showed up in my CCDEK account for several days, and today when I checked the address on the block chain, it said "no results" even though there have been three past successful transactions sent to that address. The transaction number is 16155014996718816215 and the Fimk are gone from my wallet, registering as having been sent. The transaction ID doesn't show up on the explorer either so it could be that I'm searching for it wrong. Can someone help me track that down? CCDEK has not responded to my support requests.

Withdrew FIMK from exchange a while back, it never showed up in my wallet even when I used the online version.

Exchange says that it has been delivered.

Also, more updates on the state of FIMK and trying to get it to be recognized as a national digital currency would be good.

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-----

Easy update to 0.6.3 ...

On linux (from the same folder that contains run.sh):

curl -L -k -o update_fimk.sh https://git.io/vzhl9
sh update_fimk.sh 0.6.3 2093ef1dbd1e112d85fd6eb96603244400658d6d7ce165184d57faf19a6436b0

Thats it.



-----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-----

DESKTOP VERSION - CONTAINS THE LATEST 0.6.2 FIMK

Edit: All this version of lompsa adds is that it embeds FIMK 0.6.2 which you need if you want to run the embedded server.
In case you have been using lompsa 0.6.0 (the previous release) but never start the embedded server (we call that running in light mode) you don't need this release.


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

███████╗██╗███╗   ███╗██╗  ██╗          Release : 0.6.1
██╔════╝██║████╗ ████║██║ ██╔╝          Date    : 2016-01-29
█████╗  ██║██╔████╔██║█████╔╝           http://fimk.fi
██╔══╝  ██║██║╚██╔╝██║██╔═██╗           https://github.com/fimkrypto/mofowallet
██║     ██║██║ ╚═╝ ██║██║  ██╗          https://lompsa.com
╚═╝     ╚═╝╚═╝     ╚═╝╚═╝  ╚═╝

                         presents:

██╗      ██████╗ ███╗   ███╗██████╗ ███████╗ █████╗
██║     ██╔═══██╗████╗ ████║██╔══██╗██╔════╝██╔══██╗
██║     ██║   ██║██╔████╔██║██████╔╝███████╗███████║
██║     ██║   ██║██║╚██╔╝██║██╔═══╝ ╚════██║██╔══██║
███████╗╚██████╔╝██║ ╚═╝ ██║██║     ███████║██║  ██║
╚══════╝ ╚═════╝ ╚═╝     ╚═╝╚═╝     ╚══════╝╚═╝  ╚═╝

Embeds FIMK 0.6.2 (based on NXT 1.5.10).

Please look here for details on  FIMK 0.6.2
https://github.com/fimkrypto/fimk/releases/tag/v0.6.2

                             ~~~ DOWNLOAD ~~~

https://github.com/fimkrypto/mofowallet/releases/download/v0.6.1/lompsa.win32-0.6.1.zip

SHA256 a3b5ae99be2defc419b8a7ad000540727c8b97e423d2d2d113d61cd28b9eae4d
MD5    ab81c3c9c58f764890c07596aded8043

https://github.com/fimkrypto/mofowallet/releases/download/v0.6.1/lompsa.win64-0.6.1.zip

SHA256 42741de735dd6fbee32984258ff609325bb7b7517895fcca3351430891d661c4
MD5    9653c2620e12cc54be98fc24e9b4cfad

https://github.com/fimkrypto/mofowallet/releases/download/v0.6.1/lompsa.osx32-0.6.1.zip

SHA256 a1b0222b89f0d2a153ece9a1ab33c750663dd4a6f5b1d91ae6bdadc2a72cd080
MD5    f721e18ee75534aa7f1b441bd6e09127

https://github.com/fimkrypto/mofowallet/releases/download/v0.6.1/lompsa.osx64-0.6.1.zip

SHA256 9d9af0071974681dec4b2dbffd869799e558d644057efb9a4977ee51c415a476
MD5    a5c5028e8f89fa9e7ea64b54a8cdcdae

https://github.com/fimkrypto/mofowallet/releases/download/v0.6.1/lompsa.linux32-0.6.1.zip

SHA256 dd8d46344b2257a580860be843c9cf56994320644cea3c57a584cb314af026b9
MD5    33d748831a4c3f818f150791d072fbdb

https://github.com/fimkrypto/mofowallet/releases/download/v0.6.1/lompsa.linux64-0.6.1.zip

SHA256 eeb5fcb9c21cff0b54447d0c06395d4b0124f4d80cd1f9b74e4bc7c3528788c0
MD5    2d1bf7526243792ebd0cb6f965bba4c8

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

iQEcBAEBAgAGBQJWq2YGAAoJEP9gzPcARnvnPxsIANMXdHW1vWwL15yxQhB0EbZ3
kewHsrheuq6HtAN5AVR5VUfVLlvuYpN4Y4BKSrhuAqv+f8ydhVazNucdrnBsClk3
LGNpHEHvVdul/DEm7h36H9f02JFhYpaFIv8F8ONQ3GP7Wi12fKFAiSP90JWtzBZ2
OJDtcYfc9sqSYl19HwzMgHnNHhdRHLC5GYAekm+vHo5XUBpsG0BvICeV3tXrAgts
TjrNC45cofRzMHtDQtPGpmyFH1l4rBpVW07R5J7yK4zsXFVXS/NJnNs862IH7bXE
du8A1n2/TeZyb1J0xq/LD/V2JmzuDjmafN9BO40iZAy5DZjVhocaPyLFYLo1KdQ=
=dtMH
-----END PGP SIGNATURE-----

I've notified funbug on forum.fimk.fi that he should upgrade since he was on 0.4.2. He most likely missed that PM.

The main SRWP (funbug) account did not forge any blocks during these past 9 days, which is to be expected when you are not on the 0.6.* fork.

For anyone who hasn't done so... Update to 0.6.2!
Updating will trim your blockchain up to the hardfork block so you are ensured you will land on the 0.6.* (main) fork.

0.6.2 has an update mechanism to help you update to newer versions.

We are working on releasing desktop versions (lompsa) that contain 0.6.2.

I dont know about that, but I have seen funbug online during that time, so at least he should be ok.

http://fimkchat.com/2016/01/fimk-0-6-2-server-released/

-----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-----

The SRWP asset hasn't paid a dividend in close to three weeks. Is everything OK in that quarter?

HELP WANTED

The new version manager in FIMK 0.6.2 comes with an update script (bash) that downloads the new version, verifies its integrity and installs it.
I've written and tested the script on my (linux) desktop but would like to hear if the script in it's current form works on the  servers or desktops of other FIMK users.

The script was uploaded to github https://gist.github.com/fimkrypto/d4da67234122889ce6ab

To (easily) test the script create a new empty directory and execute the script. It should download and install FIMK.
To see if the update part also works please try these commands and let me know it worked for you!


Thanks!

Coinmarketcap could also use an update.

http://coinmarketcap.com/currencies/fimkrypto/

Should link to the new site at http://fimk.fi.
Explorer link should point to latest client at https://lompsa.com.

Sure. The top post needs revamp anyway in the next weeks. Thumbs up we have another exchange facility online by then.

Thanks. I'll keep that in mind, especially if CCDEK drops Fimk. For now, I find it easier to work with the exchange. Can you please post updates to the top post if any new exchanges pick up Fimk?

We're adding hard fork helper functionality to the server core, the crap we are now experiencing has annoyed us long enough and has to end now.

From this coming release we will do things slightly different which will lead to faster iteration times and more streamlined hard forks over our beloved decentralized peer 2 peer network.

Hard forks are unpleasant but inevitable with a young and fast developing crypto currency like FIMK. We have tons of ideas for new features but are always severely limited by how difficult it is to get our software installed on all peers out there.

There already is a sophisticated database versioning mechanism in FIMK core which basically allows anyone running any version to simply install a newer version and have the complete blockchain/db structure dynamically updated to that newest version. With this mechanism already in place requiring peers to periodically update their software is in my view very reasonable.

We all want FIMK to develop further don't we?

---

Starting with this coming release when you start FIMK a check is made if your version is either OUTDATED is being PHASED OUT or has an UPDATE AVAILABLE. This version information is distributed over the blockchain through aliases controlled by the non profit association who makes FIMK - Krypto Fin ry - http://fimk.fi.

These three levels of software version status will allow us to quickly move through new versions (and through hard forks).

We will still announce new versions on the forum and our website but you no longer have to track that, the software will from now on warn you if you need to update. These warnings are clearly visible from either the console logs or from the desktop client, these warnings contain details on how to update.

No more forks after updates.

To prevent forking the network after updates peers will from now on actively start blacklisting nodes that run a version up or below the current OUTDATED version.

To prevent peers from not noticing that their version has expired which will undoubtedly put them on either a fork or disconnect them from the network (since no one will connect to them) we will actively shutdown the FIMK server and print a big fat notification to the logs that your version is outdated and that you need to update.

This way third party software which builds on FIMK (currency exchanges, merchants etc) will immediately be able to notify their operators through the FIMK log what has happened and that they should update their versions.

How hard is updating?

Now for the million dollar question, how difficult is it to update? How bad is it what we would be putting all you users out there through.

Luckily not difficult at all. I had something like this in mind for an update notification (you will find this in the FIMK console log).
Instructions apply to a Linux server, probably most servers running FIMK are Linux servers.


############################################################################
## WARNING!!
##
## YOU ARE RUNNING OUTDATED SOFTWARE
## FOLLOW INSTRUCTIONS BELOW TO UPDATE
##
## YOUR CURRENT VERSION IS 0.6.2
## THE LATEST VERSION IS 0.7.0
############################################################################
##
## FOR LINUX USERS RUN THE FOLLOWING COMMAND
## (requires `curl` and `zip` packages to be installed)
##
## $ FIMK_VERSION=0.7.0 sh update_fimk
##
## USERS ON OTHER PLATFORMS SHOULD DOWNLOAD THEIR UPDATE HERE..
##
## https://github.com/fimkrypto/fimk/releases/download/v0.7.0/fim-0.7.0.zip
##
############################################################################


Hopefully this way we can finally start to streamline the whole versioning and more important update process which will lead to a more stable and more frequently updated network.

Posted this same message to our blog: http://fimkchat.com/2016/01/solving-the-hard-fork-dilemma/

Dirk.

Not public exchanges that we know of. One related to Lompsa.com is in the works and it should spin off at least another one in March.

Although still low profile and being set up, you can trade FIMK on the decentralized asset exchange through the Lompsa client or on the web:

https://lompsa.com/#/assets/fim/2339799191405258101/trade

Contact me through https://forum.fimk.fi if you need to redeem the EUR tokens to real EUR BTC tokens to BTC.

I did not know Fimk ever was on Alcurex. The only exchange I know of that carries Fimk is CCDEK. Are there any other exchanges that carry it?

Hello from alcurEX.
Sadly I need to say FIMK will be soon delisted from alcurEX.
There is no almost any volume and I like to give change to some other coin.

Please withdraw all FIMK from alcurEX.
Thank you: halibit
alcurEX