FIMK CLIENT 0.4.1 – FORGING & LEASING IMPROVEMENTS

FIMK Client 0.4.1 (still named mofowallet) has been updated to give better forging and leasing feedback. After feedback from the community we decided to fix the forging and leasing issues people where experiencing. This release has better “Am I forging or not?” and better “Who am I leasing to and who is leasing to me?” feedback.

Downloads

Download Windows 32bit
Download Window 64bit

Download OSX 32bit
Download OSX 64bit

Download Linux 32bit
Download Linux 64bit

Better leasing insight

An indicator was added to all accounts which shows if, to who and for how long their balance is leased. To find out if a FIMK or NXT account has currently leased his/her balance and to who … go to that accounts Activity or Pulse page and look at the top if it says Lease in the balance section. If the balance for that account is currently leased out you’ll see to who and for how long.

Balance lease feedback

Balance lease feedback

Clicking the link that leads to the account to which the balance was leased will put you straight into the new Balance Leasing page. The Balance Leasing page will list all account who have leased their balance to that account.

A new RPC GetAccountLessors call was added to the websocket server to include the Account name and the data for “from” and “to” columns. People re-using the WebSocket server for their own purposes now have access to this new RPC call.

Balance leasing accounts

Balance leasing accounts

Better forging insight

In 0.4.0 it was unclear when your account was successfully forging. For 0.4.1 we make use of a new server API in combination with a client side WebSocket event listener (listens for new blocks).

You now no longer need to send your passphrase to the server to obtain your account forging status. To start forging it is still required that you send your passphrase to your (local) server.

Lets have a look at an account while it’s not forging and then when it is forging.

Sample of account which is not forging

Sample of account which is not forging

Now lets turn on forging and see what it gives.

Account that is forging

Account that is forging

As you see we have three new parts here.

  1. Spinning indicator (spins when you are forging)
  2. Next block forging expectancy (counts down the seconds until you forge your next block, this is updated on each block)
  3. History link to see what blocks you forged in the past

To have quick access to the blocks you forged click the history link which leads you to the blocks forged by your account.

Blocks forged by account

Blocks forged by account

Improved (local) server

As you may (or may not) know FIMK Client/MofoWallet has excellent support for running your FIMK or NXT server on your desktop. Having to open a command line and running a start-up script has been a thing of the past for some time now.

For 0.4.1 we fixed a bug that prevented the WebSocket listeners from correctly reconnecting with the locally running FIMK or NXT server. This bug also prevented some users from starting to forge on their local server.

To start your local FIMK or NXT server is easy, either click the monitor symbol in the bottom right network height indicators.

Click monitors to go to the console

Click monitors to go to the console

 

Or if you prefer click Settings/FIM Server or Settings/NXT Server in the top right drop down menu.

Once you are on the console page either select the FIMK or NXT console and start one or both servers.

Running both NXT and FIMK at the same time

Running both NXT and FIMK at the same time

As you see in the sample above you could even run NXT and FIMK at the same time, if you look close you’l see that the NXT blockchain on the local server is actually further than the one on the remote server. The reason for this is that we hava a brand new server and it is still downloading the blockchain, normally you would not see this.

Only when the local server is running can you start forging. It is also at this time that forging can only start on the localhost address, this is and has been hardcoded in the client.

It is planned to make the connection parameters in the client configurable so you can point the client at any of your own (hosted) servers.

Share Your Thoughts

Leave a Reply