Hi,
Short status update, been a while I know..
When is MoFo going to update for NXT 1.5.x? Running anything before that at this point might put you on a fork, and probably eventually be locked out.
Our
NXT+ product (the made ready for mofowallet version of NXT) has been on 1.5 since before the hard fork. Otherwise no-one could have used NXT since then. So unless you want to run the NXT server yourself locally from within the client, all should work.
The one-click exe version does not allow copy and paste, which makes working with large secure password a pain.
Saving password in the wallet also is not a very secure option for me.
I've had some reports of the copying issue. Thats OSX right?
For the upcoming release I've changed the way keys are stored.
Instead of in the encrypted wallet file they will live (encrypted) in your browser localStorage (your client side db, all browsers have that and it is very secure).
But the main method of login will consist of secret URL's that embed the encrypted passphrase in the url, so you'll need to place that url on your toolbar or something or save it somewhere. You basically only need to visit that url once since visiting it will store the wallet in the browser db, you then need to provide the wallet password each time you do a transaction.
Until we get the proper tools in place for 2FA this will remain a weak spot but it's the same with all other brainwallet coins.
--------
We have completed the
Private Assets feature which has been running on testnet for a while now. It has been used for demoing purposes by Eliphaz his banking contacts.
For the purpose of these demos we also
reskinned the AE UI.
To get rid of the slowness of the AE (the need to wait for blocks) we developed the
Virtual Exchange layer.
This turned out to be a pretty difficult task but as always all turned out well in the end (thanks to our new testing tools).
What the virtual exchange does is exactly as it says provide an exchange but a virtual one.
While in the normal AE orders are matched (and balances are updated etc ..) when a new block comes in, in the virtual exchange orders are matched the millisecond an unconfirmed transaction hits the network. So basically instant. The fun thing now is when you place an order you'll see in realtime (all over the world basically) what the consequences of that action are (your balance will change immediately as will you see all trades that happen from that order as well see all partially matched orders have their remaining amounts updated).
This layer of course had to made fully aware of when new blocks come or blocks are popped. Since you cannot know for sure the order in which transactions are finally placed in the block by the forger the layer (which works like a event system over websockets) had to also be made aware of this and be able to correct it on the clients.
Currently we are finalizing the
new identifier mechanism, the goal is to do away with all FIM-XXX addresses, while they are miles better than the old numeric addresses they still don't allow for easy adoption. The system being tested now will offer two types of ID's. There are your free
name@fimk.fi names available to anyone (for free through our faucet) and then there are the verified addresses
name@gmail.com for instance. If you want one of those you'll have to go through our verification process where you verify (all done using cryptographic methods) that you own that address. Then in a later stadium those verified addresses will become part of the platform in even more integrated ways.
The FIM-XXX address will probably remain working forever but all new things we do will focus on the new identifiers. In the current implementation you can have multiple identifiers point to a single account.
To make all these big and complex changes to the core possible and stay compatible with the upstream NXT critical security releases we now also developed our very own
blockchain testing tool suite. While I don't mind writing Java, I like writing Javascript a lot more, mostly since you can so much more with much less code. After writing some tests in Java I figured since FIMK is on Java 8 now, why not make use of the new built-in Nashorn js engine to write tests in javascript instead ?
The result has given me joy and speed ever since, writing tests has become a breeze now, the suite (at least the parts released) can be seen here
https://github.com/fimkrypto/fimk/tree/master/src/test/resources.
Dirk
