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

Your concern my be more relevant at their forum
https://forum.fimk.fi/index.php?board=1.0

Hi FIM and dev.

Im an investor of this coin, and until now Im not happy about this investment.

Are we going to see changes soon? Are you planning to do some more marketing and bring some major releases?

What is the roadmap?

As I can remember you collected many BTC for the IPO. It would be nice if the investors start seeing something after 2 years now.

Thank you.

Yes I have some thoughts about 2.0.

https://nxtforum.org/core-development-discussion/nxt-2-0-design/msg210552/#msg210552
https://nxtforum.org/core-development-discussion/nxt-2-0-design/msg210562/#msg210562
https://nxtforum.org/core-development-discussion/nxt-2-0-design/msg210588/#msg210588

TL;DR

It's very unlikely we will go the same route as NXT has gone with the 2.0 design.

We believe to tackle the scalability issue you first have to move the so called "derived data" away from the core FIMK database (the same one holding the blocks and transactions) and into a database optimized for serving big numbers of users.

Right now we do that with MySQL but our replicator setup could just as easily work with larger databases since it's much like a plugin.

Then for anyone hosting a site that uses FIMK in whatever way the setup is to install the FIMK background process (which talks to the p2p network) and tell the FIMK background process to what external database it has to replicate the data now stored in the FIMK database.

This way we can remove the biggest part of all the various tables and indexes in the FIMK database and even stop creating new Attachment types (which require hardforks to implement) since they will exist outside the blockchain and only have meaning in the replicated database.

All of this fits nicely with our recently shifted focus towards a bigger end to end setup which consists of:

- a client framework (we have rewritten lompsa in Typescript and Angular 2 for this - this is mostly done)
- a server framework (this part is under heavy development and uses Scala and Play framework, this is both enterprise friendly and can run under heavy server load)
- a replicator framework (there is a functioning prototype on github right now which creates a one to one replication of various blockchain data to an external MySQL database)

Any thoughts on nxt 2.0? Aka. Will fimk take a similar scalability approach?

This is correct. Coins would not be lost.

If CCEDK sends FIMK to wiser while on the fork, then only according to that fork did wiser receive that FIMK.
As soon as CCEDK switches to the master fork they will see the FIMK they send on the bad fork to wiser actually never got send on the master fork and they will appear again in the CCEDK account.

The only real real risk of forks is when you sell something for FIMK, you then see the FIMK appear in your account, then you hand over whatever you wanted to sell and when the buyer has disappeared you'll notice his payment was never actually performed on the master fork.

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.

Link for the form?

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

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.

its about time this coin gets listed on bittrex or poloniex

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.

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.

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.


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://bitcointalksearch.org/topic/m.13640010

and

https://bitcointalksearch.org/topic/m.13707939

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

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

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 think it is your responsibility to inform the exchange about mandatory updates.  

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

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.

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.

yes