You seem to be on a fork.
There is an explanation and solution on our forum http://forum.fimk.fi/index.php?topic=63.msg1668#msg1668


  You missed that we had a fork..

FIMK public wallet/node 1 (Secured HTTPS Connection) -> https://wallet.fimk.fi:7886/
FIMK public wallet/node 2 -> offline this one stays offline, the FIMKrypto Fin ry organization now runs a set of permanent FIM servers.
Blockexplorer -> Permanent address: http://explorer.fimk.fi  (forwards to http://80.240.143.139/)

We will repair the links, thanks for pointing this out.

When you started forging the total amount of stake was much lower. If you look at the current stats you'll see one account with 16K forged a block in the past 2880 blocks, all other forgers have a stake starting at 30/50K and higher.

Eventually you'll forge a block but with 25K it will take longer.

There was some confusion among forgers suddenly forging less blocks than expected.
For these people (and others) we've added a stats page to the blockexplorer that shows what account forged how many blocks in a period.

http://explorer.fimk.fi/blocks/stats/0/0

If you are suddenly forging less blocks than expected/normal it is advised to delete your blockchain and restart the FIM client.

Not to ruin your party but I don't think it's realistic to believe that FIMKrypto will have the infamous Transparent Forging feature before NXT does.
As soon as the last part of TF is available and it's desirable for FIM (since we already have 30 second blocks) we will embed that in FIM if the community decides so.

NXT is like a train that continues to push forward and has the large community behind it to develop these low level features (just like Bitcoin developed those before that).
FIMKrypto builds on that strong base and adds value and real-life applications of that technology in Finland and beyond.

We are capable developers but just a few (for now) so we will focus on creating features that offer direct value to end users. You can expect improvements to the client (support for mobile) and lighter features like adding encrypted p2p direct messaging (free/off blockchain) to the protocol.
Implementing/Completing TF is extremely resource intensive and probably not the best use of our resources.

Not yet. But this is planned.
In NXT 1.2 this seems to be implemented.
As stated in the opening post we'll be staying very close to NXT, successful features like alias transfer but also digital goods store and other improvements will find their way into FIM after we had the time to test run those in our own environments, we like to run long tests (weeks) in live environments so that part will probably take the longest before you see any new NXT feature in FIM.


Yes you can. You can do it from the client probably, but if that doesn't work please let us know.
You can do it manually (JSON API) for sure.

Just noticed the extra K at the end, that's not correct format.
It's acct:73934436533863559090@fim not acct:73934436533863559090@fimk

It doesn't matter since it's a bug in the NXT client only. Internally (in the server part) we still store your account alias by it's number.

This is the Genesis account http://80.240.143.139/accounts/FIM-MRCC-2YLS-8M54-3CMAJ
It has paid only 666 million and not 1 billion because the stakeholders and the Finnish basic income account all received 1/3 of all coins.
The last 1/3 of the coins is paid to forgers from within the protocol over a period of ~4 years.
After 4 years 1 billion FIM will be in circulation, you can follow the current amount in circulation here http://80.240.143.139/json/total_coins




Yes that is the correct format.
But we fixed that NXT bug in the FIM client https://github.com/fimkrypto/fimk/commit/1e5786abdc94583a0339557525550b9350ed9465
In the FIM client you can register an account alias with your normal RS account number.

We've updated the blockexplorer. A big part of the core is rewritten and it should no longer cause any inconsistencies.
Apart from the reworked core we've added the following.

• Full text search for accounts, blocks, transactions and aliases
• JSON API to obtain the total number of coins in circulation http://explorer.fimk.fi/json/total_coins
• Supports static links to account, block, trans, alias for easy bookmarking/sharing. Example: http://explorer.fimk.fi/accounts/FIM-MRCC-2YLS-8M54-3CMAJ

Please have a look in the Release announcement thread on http://forum.fimk.fi and you'll see that we have always signed our releases and include both SHA256 and MD5 hashes for all downloads.

There are two places where we publish these signed release announcements.

1. https://github.com/fimkrypto/fimk/releases
2. Each release gets it's own topic in the FIMK Client discussion section http://forum.fimk.fi/index.php?board=3.0

There is a dedicated FIM 0.2.2 Release thread on our forum http://forum.fimk.fi/index.php?topic=64.0.
If you run into any issues with the 0.2.2 release it is very much appreciated if people (also) used that thread to post any findings.

Thank you.

Expect the coming update to be a properly functioning blockexplorer. It sucks we know, sorry.


Good one! That's absolutely better than what we have now. I'll update it in a coming release. Thanks!


The easiest way would be to update the countdown on each block (a drawback would be that the time to forge will jump around constantly).
But since you need to send your secretPhrase along with the request for the deadline, making that automatic (without the users expressed consent) has the risk of a user on a public node sending his passphrase once. Then realizing he/she doesn't want/trust that and the client will continue doing so.

This is a first basic implementation of the forger countdown, I can imagine a next release to show the current behavior only when you are on a public node.

If in doubt you can always refresh the countdown, that's why we put it there since we expected some confusion on this subject.


  that's not supposed to happen.
What OS are you using?


If you go here http://onlinemd5.com/ you can enter the SHA256 checksum mentioned in the release announcement https://github.com/fimkrypto/fimk/releases/tag/v0.2.2 and if you check the downloaded fim-0.2.2.zip against the SHA256 in the release announcement you'll see that it does match. Sorry for the incovenience.


Did that work for you? Not sure if that has any effect.

FIM Version 0.2.2 Released

We have released FIM 0.2.2 which consists of some minor fixes related to unclear wording and some bigger improvements to client.

• Users are notified automatically when a new version is available
• Users can download the new version from within the client
• Downloaded versions can be verified to be genuine from within the client
• Account aliases can be used with both numeric and RS accounts (the ones starting with FIM)
• Forging countdown indicator and forging refresh functionality added to the client

There was some confusion if the client was forging correctly. We have added a countdown that counts down to the moment you are expected to forge the next block.
This time is an average, it is possible (and will likely happen many times) that when the countdown reaches zero you dont't actually get to forge the block. What is sure is that the chance to forge a block when the countdown has not reached zero is very small.

The so-called deadline (the time until you forge the next block) changes every block. You can refresh the deadline (ask the deadline from the FIM server) by clicking the button next to the count down indictor.

Download: https://github.com/fimkrypto/fimk/releases/download/v0.2.2/fim-0.2.2.zip

Release announcement thread on http://forum.fimk.fi
Source code for this release

Please don't mind the block explorer we're working on that (actually more trying to make time to work on it). But be assured the block explorer is nothing more than some scripts who fill a database of block data. The high number of forgers and blocks being added and removed is confusing it right now.

Edit: it's block explorer of course

Somehow your desktop has assigned gedit as the default app to execute that file. Try doing it from the command line.



We agree and are looking into that.


Trading is done at dgex last price is around 0.00000300


533 BTC was donated for 333 milion FIM which makes a stakeholder price of 0.00000150 (at least that's what was said on our other forum in the price thread http://forum.fimk.fi/index.php?topic=14.0)

We're working on the blockexplorer but decided to put this (half working) version online already since it does give a valuable insight in whats going on in the blockchain at the moment.
If in doubt please consult the FIM client which is always correct.


When you donated through blockchain.info you had to put your FIM account in the public message. If you have that account number you can look it up in the blockexplorer no need for a passphrase for that.


Please hold on I'm sure Graviton will get back to you soon.


The current height 4118. The one on the fork is on 3381. IP 84.201.3*.1** (I'd rather not post someone's IP in this forum sorry).

Fork Detected

There currently is one peer (from Germany according to whois) who is on block 3381 while all other peers on the network are on or close to block 4090.
We advise you to shutdown your FIMK server and delete the blockchain. The blockchain is the folder called "fim_db" (you can simply delete that folder and restart).

Please note that the blocks that peer is currently forging will be gone when the fork is resolved. Nothing can be done about that.

All forks are resolved.

Yes we noticed.

You should not worry, it's just the blockexplorer scraper scripts that have a small error somewhere in the transaction/balance calculations.
This is not related to the FIM blockchain in any way.

Your balance in the client is your correct balance. We'll be working on fixing the blockexplorer scripts today.

That warning is about using a FIM server that is not installed/running on your own computer.

People can run FIM on their server which you can then access, like the FIMKrypto organization does with https://wallet.fimk.fi:7886
But you should realize that you're sending your secret passphrase (the one that gives access to your account) to that other server.

The owner of that server could be collecting/intercepting your passphrases if you send it. Thats what the message is about.

Downloading FIM and running it yourself on your own computer does not expose your passphrase to anyone and is the recommended way.