[ANN] FIMK: 2.5G POS, extra block rewards, messaging, asset colors, p2p shopping

[verymuchso]

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

[1714949963]

1714949963

[LemonAndFriesOne]

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.

[wiser]

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.

[verymuchso]

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

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?

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.

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

[PilotofBTC]

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.

[wiser]

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

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?

yes

[BlackFor3st]

I sent FIMK to CCEDK (FIM-6LV5-GQDK-S4LE-F4E4D) but the coins doesn't arrive.
The CCEDK-support told me that the problem is on side of FIMK.
Can you please check this. I send a lot of coins 
Thak you.

[Eliphaz Fimk]

CCEDK hasn't been in touch with FIMK for a long time. They probably had the blockchain / forking problems with 0.6.3 like many did. Those have been fixed in the recently released 0.6.4 https://github.com/fimkrypto/fimk/releases/download/v0.6.4/fim-0.6.4.zip . Someone should let them know to update

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.

Unfortunately not yet. You can just replace the Lompsa server directory with the files in the package https://github.com/fimkrypto/fimk/releases/download/v0.6.4/fim-0.6.4.zip

and it should work fine.

[quasimodo]

CCEDK hasn't been in touch with FIMK for a long time. They probably had the blockchain / forking problems with 0.6.3 like many did. Those have been fixed in the recently released 0.6.4 https://github.com/fimkrypto/fimk/releases/download/v0.6.4/fim-0.6.4.zip . Someone should let them know to update

I think it is your responsibility to inform the exchange about mandatory updates.  

[Eliphaz Fimk]

I think it is your responsibility to inform the exchange about mandatory updates.  

0.6.4 is not mandatory as such, meaning if a node has up to date blockchain then existing 0.6.3 and 0.6.2 should still work fine. I don't have direct channel to Ronny,  someone already in contact for support case could mention the available update for faster resolution of CCEDK's trouble.

[BlackFor3st]

And now, my 1,970,039 FIM are lost???

[wiser]

I think it is your responsibility to inform the exchange about mandatory updates.  

0.6.4 is not mandatory as such, meaning if a node has up to date blockchain then existing 0.6.3 and 0.6.2 should still work fine. I don't have direct channel to Ronny,  someone already in contact for support case could mention the available update for faster resolution of CCEDK's trouble.

I agree with quasimodo. It is the responsibility of the developers to keep exchanges informed about updates!

[verymuchso]

And now, my 1,970,039 FIM are lost???

If you have send your FIM to an account which belongs to CCEDK then they can access it which I don't believe counts as lost.

I agree with quasimodo. It is the responsibility of the developers to keep exchanges informed about updates!

AFAIK FIMK is the only crypto currency that actively prevents exchanges and merchants from ever landing on a fork because of a missed update.

See

https://bitcointalk.org/index.php?topic=633304.msg13640010#msg13640010

and

https://bitcointalk.org/index.php?topic=633304.msg13707939#msg13707939

[wiser]

And now, my 1,970,039 FIM are lost???

If you have send your FIM to an account which belongs to CCEDK then they can access it which I don't believe counts as lost.

I agree with quasimodo. It is the responsibility of the developers to keep exchanges informed about updates!

AFAIK FIMK is the only crypto currency that actively prevents exchanges and merchants from ever landing on a fork because of a missed update.

See

https://bitcointalk.org/index.php?topic=633304.msg13640010#msg13640010

and

https://bitcointalk.org/index.php?topic=633304.msg13707939#msg13707939

That's great, but I still can't see my recent deposit in my CCEDK account. I did send them a message referring them to Eliphaz Fimk's message about the recent update, but I honestly believe they will pay more attention if an actual developer contacts them. Can someone from the development team please do so? I'd sure appreciate it.

[wiser]

Just an update on my situation: I did get a couple emails from Ronny Boesing, CEO of CCEDK. He said that he will work on trouble shooting the issue with Fimk transactions on Monday. I'm guessing based on what's said here that it's a matter of updating the CCEDK wallets, and that once that happens all deposits made to CCEDK wallets should show up. I'm not sure about withdrawals, though, if they were done on a fork, what happens to those. Hopefully by Tuesday everything there will be running smoothly.

[Primitive]

its about time this coin gets listed on bittrex or poloniex

[wiser]

its about time this coin gets listed on bittrex or poloniex

I would LOVE that

Poloniex has a new coin request form, which the developers should definitely fill out. Anyone can, actually, but Polo should get at least one request from development team.

Not sure on BitTrex' process but they probably have one.

[Eliphaz Fimk]

Poloniex has a new coin request form, which the developers should definitely fill out. Anyone can, actually, but Polo should get at least one request from development team.

I've filled out the request form once more than a year ago. Any FIMK community member is welcome to work towards listing FIMK on their favorite exchange

[SyRenity]

Link for the form?

[PilotofBTC]

Just an update on my situation: I did get a couple emails from Ronny Boesing, CEO of CCEDK. He said that he will work on trouble shooting the issue with Fimk transactions on Monday. I'm guessing based on what's said here that it's a matter of updating the CCEDK wallets, and that once that happens all deposits made to CCEDK wallets should show up. I'm not sure about withdrawals, though, if they were done on a fork, what happens to those. Hopefully by Tuesday everything there will be running smoothly.

If withdrawals were sent on a fork, then the person waiting for them, never got them, or were also on the fork. Once they are on the correct chain they will have the coins back and can re-send them correctly.