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

[verymuchso]

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

[1714789005]

1714789005

[1714789005]

1714789005

[1714789005]

1714789005

[1714789005]

1714789005

[1714789005]

1714789005

[PilotofBTC]

I was wondering what all those 1million FIM transfers were.

Are there any details of this theft? What this from an exchange?

[verymuchso]

I was wondering what all those 1million FIM transfers were.
Are there any details of this theft? What this from an exchange?

No it was from a user who contacted us about it this morning.

[PilotofBTC]

I was wondering what all those 1million FIM transfers were.
Are there any details of this theft? What this from an exchange?

No it was from a user who contacted us about it this morning.

Hmm... I see. So, I assume it was his issue, and not FIMs or a FIM host wallet. Are we going to black list addresses every time someone gets hacked?

[Eliphaz Fimk]

Hmm... I see. So, I assume it was his issue, and not FIMs or a FIM host wallet.

True

Are we going to black list addresses every time someone gets hacked?

No, we're only going to do so when a significant heist like the recent 13.90% of total FIMK in circulation poses a considerable future dumping hazard if left without intervention.

In addition, the original sourcing of the FIMK in question is suspicious. Freezing the assets is more likely to benefit FIMKrypto in large. This will be discussed openly in more detail with the community as the temporary blacklisting is through technically and we can have a breather.

[PilotofBTC]

Thanks for the information. So effectively there are now 13% less FIM in the wild?

Is there a consideration of a re-org similar to what was considered with NXT after the BTER hack?

iirc it has to be done within 1440 blocks.

[Eliphaz Fimk]

Thanks for the information. So effectively there are now 13% less FIM in the wild?

Yes, during the scarce moments the blockchain makes any sense until further integration from updated peers

Is there a consideration of a re-org similar to what was considered with NXT after the BTER hack?

Not sure exactly what's meant by the reference to reorganization, but we're likely going to settle for a hard fork (handled automatically by the updated server software).

We were going to get through with the lighter means of only pushing the association's monster account in lead of the main fork and freezing his accounts, but were late for a few minutes and the thief's chain got a sizable headway. So we've been playing some catch me if you can for the best part of today to gain control of the main fork. That method seems to have some inherent problems, so Dirk is currently making another update that will blacklist all nodes using old software prior to 0.3.2 (Mofo 0.3.7), as well as all references to the thief's accounts.

[verymuchso]

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

[verymuchso]

The mofowallet version http://forum.fimk.fi/index.php?topic=494.msg3076;topicseen#msg3076

[PilotofBTC]

Updated, no my wallet just says "Downloading Blockchain.."

last block is 282569 from yesterday.

Is this because I have no connections to 1.3.3 peers?

[verymuchso]

Updated, no my wallet just says "Downloading Blockchain.."

last block is 282569 from yesterday.

Is this because I have no connections to 1.3.3 peers?

The update does some cleaning of the peer database. It deletes all stored peers and adds a set of new welknownpeers known to be running 0.3.3 after that all peers trying to connect with non 0.3.3 versions are blacklisted by default.
The 282569 block is the block of the hard fork, it could be your client was just busy scanning and verifying the blockchain which is also something done on  first start only, verifying is expected to take a while.

[PilotofBTC]

Updated, no my wallet just says "Downloading Blockchain.."

last block is 282569 from yesterday.

Is this because I have no connections to 1.3.3 peers?

The update does some cleaning of the peer database. It deletes all stored peers and adds a set of new welknownpeers known to be running 0.3.3 after that all peers trying to connect with non 0.3.3 versions are blacklisted by default.
The 282569 block is the block of the hard fork, it could be your client was just busy scanning and verifying the blockchain which is also something done on  first start only, verifying is expected to take a while.

Thanks for the info. When I woke up today and looked at it, it looks to be up to date now and forging. I hope the updates slow down a bit. 4 updates in a week or so is quite a bit. That said, it's glad to see the dev team is active.

[verymuchso]

That said, it's glad to see the dev team is active.

We have been active every day since launch, but active and doing a release is not the same.
But you're probably right that it doesn't show enough.

[funbug]

Happy Merry Christmas

All dividends for the current week are paid

Thanks

[xibeijan]

I love this project.  Nice little community building here.

nicer logo this time.

[halibit]

Updated, no my wallet just says "Downloading Blockchain.."

last block is 282569 from yesterday.

Is this because I have no connections to 1.3.3 peers?

The update does some cleaning of the peer database. It deletes all stored peers and adds a set of new welknownpeers known to be running 0.3.3 after that all peers trying to connect with non 0.3.3 versions are blacklisted by default.
The 282569 block is the block of the hard fork, it could be your client was just busy scanning and verifying the blockchain which is also something done on  first start only, verifying is expected to take a while.

We are in this situation on alcurEX.
Waiting nodes and blocks...
I download new version and start with clean database but no sync yet..

[verymuchso]

We are in this situation on alcurEX.
Waiting nodes and blocks...
I download new version and start with clean database but no sync yet..

Network seems to function normally, ran a scan which shows no forks.
Current height is 296729 blockexplorer http://explorer.fimk.fi seems to be in-sync too.
Best advice would be to:

1. Shut down fimk server
2. Delete fim_db folder - ensure it remains deleted, if FIMK server is running still in the background that folder will *re-appear*
3. Wait at least 5 minutes, more is better
4. Clean install FIMK 0.3.3 - https://github.com/fimkrypto/fimk/releases/tag/v0.3.3 - make sure to delete previous installation files
5. Start and it should work

Hope this helps.

[halibit]

We are in this situation on alcurEX.
Waiting nodes and blocks...
I download new version and start with clean database but no sync yet..

Network seems to function normally, ran a scan which shows no forks.
Current height is 296729 blockexplorer http://explorer.fimk.fi seems to be in-sync too.
Best advice would be to:

1. Shut down fimk server
2. Delete fim_db folder - ensure it remains deleted, if FIMK server is running still in the background that folder will *re-appear*
3. Wait at least 5 minutes, more is better
4. Clean install FIMK 0.3.3 - https://github.com/fimkrypto/fimk/releases/tag/v0.3.3 - make sure to delete previous installation files
5. Start and it should work

Hope this helps.

I'm working with that version and clean installation.
Few hours and no any nodes and no blocks downloaded.
I also start new installation in another server on different IP range.
So far nothing.
I'll check tomorrow.

halibit alcurEX

edit:
In another IP range, it start download blocks and service have info:

Code:

2014-12-29 04:28:30 INFO: FIM server 0.3.3 (based on NXT 1.2.6) started successf
ully.
2014-12-29 04:34:42 INFO: Block 96249 generation signature checkpoint passed

But original server have only:

Code:

2014-12-29 04:30:20 INFO: FIM server 0.3.3 (based on NXT 1.2.6) started successf
ully.

And no download blocks. Only first block is recorded.
Well, let see tomorrow..
I will chance server if original not start loading.

[funbug]

We are in this situation on alcurEX.
Waiting nodes and blocks...
I download new version and start with clean database but no sync yet..

Network seems to function normally, ran a scan which shows no forks.
Current height is 296729 blockexplorer http://explorer.fimk.fi seems to be in-sync too.
Best advice would be to:

1. Shut down fimk server
2. Delete fim_db folder - ensure it remains deleted, if FIMK server is running still in the background that folder will *re-appear*
3. Wait at least 5 minutes, more is better
4. Clean install FIMK 0.3.3 - https://github.com/fimkrypto/fimk/releases/tag/v0.3.3 - make sure to delete previous installation files
5. Start and it should work

Hope this helps.

I'm working with that version and clean installation.
Few hours and no any nodes and no blocks downloaded.
I also start new installation in another server on different IP range.
So far nothing.
I'll check tomorrow.

halibit alcurEX

edit:
In another IP range, it start download blocks and service have info:

Code:

2014-12-29 04:28:30 INFO: FIM server 0.3.3 (based on NXT 1.2.6) started successf
ully.
2014-12-29 04:34:42 INFO: Block 96249 generation signature checkpoint passed

But original server have only:

Code:

2014-12-29 04:30:20 INFO: FIM server 0.3.3 (based on NXT 1.2.6) started successf
ully.

And no download blocks. Only first block is recorded.
Well, let see tomorrow..
I will chance server if original not start loading.

1. Please install FIM server 0.3.3 in local computer and download blockchain
2. After download all block upload blockchain to server

[halibit]

It was something in our server.
Now FIMK wallet is updated and transactions works again.

Thanks for all helping.