https://bitcointalk.org/index.php?topic=407115.0

It seems like a very bad idea to suggest people use this form of online wallet!

I am kind of feel bored these days because I cannot really read codes. So there aren't much to do except contacting some prospective investors and leisurely browsing this thread and some forums  

the link http://download.nxtcrypto.org/nxt-client-0.5.3.zip does appear to be valid though

Generated code approx 2x faster than my implementation, but not readable. And still no enough fast as required.

I didn't check it yet. It's not fast enough AFAIK.

If I hardcode 136941 first blocks and run it at single node will my chain win? Why not?

What would you want to see in a coin?
What would you not want to see?

I want proof of work not from calculating useless numbers.

Currently i can't see solution for speed up my code to achieve goal, so i decided release it in current state. Other conditions are met.

https://github.com/moadib/nxt_crypto_js

On my PC(core i5 2.6ghz) Java implementation from Nxt sources took approx 20ms for one signature.
My JS code on Google V8(chrome, nodejs) took approx 200ms.

The main problem is that JS doesn't support 64bit math, so script spend most time on emulating this.

Dependencies, included in script:

    Long class from Google Closure Library (Apache license)
    jssha256 by B. Poettering (GNU GPL)

Bounty announcement

100'000 NXT will be paid for working JavaScript code that signs and verifies signatures using NRS algo.

- The licence must allow to use the code in any application
- Sign/verify speed must be not lower than 100 signatures per second on a 1 GHz CPU (1 core)
- All the code must be in a single non-obfuscated well-formatted .js file
- Input/output values must be strings like "8302504e4e57c6c65335289879c6915a273d3aae7bd086058e403fcd2bc18341"

The bounty is valid till the 20th of January, 2014 12:00:00 UTC. The complete code must be published in this thread.

Any ways to speed up block generating? Maybe target manipulating?

I finally read that paper

http://www.links.org/files/decentralised-currencies.pdf

Beyonce posted this a while back... Are there any discussions on bitcointalk about it?

An easy fix would be to extend 15 sec gap for transaction timestamp... If a timestamp is more than 15 sec in the future, the transation is ignored.

U just have to convince the community that it's a useful feature and find someone who will write the code.

I would wait for at least ten blocks to see if a transaction appears in that account.

Edit: This just happened to me too... I got a transaction number for the alias assignment... but nothing has appeared in the Block Explorer yet.

Most mainstream users just like what are friendly and easy to use.

Useful for stop-on-fork-chain monitoring

Or, for non-Ubuntu OS, "ec2-user".

If there are some accounts with substancial amounts of NXT which are nobody's property and have weaker passwords than maybe we could create special thread to organise group cracking.

I'm sure a lot of people would like to use script/program to make such group brute force treasure hunting
It could be constructed in similar way as altcoins pool mining with system of distribution f.e. lucky one would get half of found NXTs and the rest of could get proportional part of other half. Also it could be a simple solo treasure hunting.

This would be great for increasing NXT community and would be simply fun. In future because of growing amounts of NXT's lost in void it would become even more successful. What do you think about it?

amazons instructions were to use it like I have always used it "ssh -i PATHTOPEMFILE root@IPADDRES" yet it doesnt work.  Surely there is someone there that can reset it?

See those *.asc files in the http://download.nxtcrypto.org/ directory? Those are GPG signatures of the corresponding zip files. If you download both nxt-client-0.5.3.zip and nxt-client-0.5.3.zip.asc in the same directory, you can run "gpg --verify nxt-client-0.5.3.zip.asc" to verify my signature of the zip package. This gives you one independent way of checking, and a hacker cannot provide a signature for a modified zip package without somehow stealing my private GPG key.

The nxt-client-0.5.3.zip.sha256.txt.asc is again a GPG signed file containing the sha256 sum. You can run "gpg --verify nxt-client-0.5.3.zip.sha256.txt.asc" to verify its content, then run "sha256sum -c nxt-client-0.5.3.zip.sha256.txt.asc" which will say "nxt-client-0.5.3.zip: OK" if the sha256 sum matches (ignore the warning about the extra lines, those are the gpg signature).

Finally, the value of the NRSversion alias on the blockchian contains the sha256 sum of the last stable release.

That gives you quite a few independent ways of verifying the package.

Max 10 hours. Never generated a block, allways error.