This guy obviously isn't impressed with NXT.
In Depth Analysis of NXT -
http://cryptolife.net/in-depth-analysis-nxt/Regarding NXT addressing. "If you were to generate an offline address and send coins to that address, you do not have explicit ownership of that address. Someone could come along with a passphrase that has a collision with yours, announce his public key to the network, and then have explicit ownership over your coins. This means that to claim ownership over an address, you are forced to expose your public key to the network. As mentioned before, doing this decreases the overall security of that address. You just can’t win. NXT is inherently less secure that Bitcoin. It is a total step backwards in that department. Also worth mentioning is that Bitcoin addresses have a 4 byte checksum that prevents you from sending to an invalid or incorrect address. NXT addresses do not."
Does anyone have an answer for this?
The short, glib answer is that it's an open problem for the community to solve, and not in any way a showstopper.
Another easy answer is the new address format initiative, being worked on by NxtChg and others. It includes error checking, and as a side benefit it also generates very QR-code-friendly addresses. I think a link was already posted, but see:
http://wiki.nxtcrypto.org/wiki/New_Address_FormatYet another response is that a bounty has been created (100K Nxt, I believe) for the implementation of a very fast client-side Javascript library for offline signing. Once this is finished (I believe CfB is reviewing FOUR submissions, created by the community, this weekend) you will be able to generate transactions without transmission of your keys. At that point a client can very easily build in an automated one-time transaction, during account creation, that secures your account with a 256-bit key.
A final nail-in-the-coffin response is that BCNext has demonstrated through his actions, on countless occasions, that his "stub" idea for Nxt has many, many PURPOSEFUL "open ends" that the community is able to solve through its collective power. Evidence of this (and only one example of many) can be seen in the genius stroke of creating bounties for injected flaws in the source code: it has driven an excellent debugging effort, has led to the creation of a team of developers who have almost completely cleaned up and refactored the source in a matter of weeks, and has created a small community of coders whose deep understanding of the source code has
driven the creation of novel client applications on multiple platforms, TWO block explorers, FIVE online exchanges, and advanced applications like a Twitter-type public message system, games, faucets, decentralized torrent seed storage, and a PoW currency built on top of a PoS blockchain.
All this in eight weeks since the genesis block.
So: any other questions?
*EDIT* I just read the rest of that fella's post and realized I only scratched the surface of his "in-depth analysis". I welcome the debate, because criticism is healthy, but his accusations of Nxt being vulnerable to Sybil and DDOS attacks show his knowledge is quite shallow. Some of his accusations are fair (distribution will always be an issue, but it's a tired old argument in the face of
data like this, which shows Bitcoin faces the *same* issue) but on the whole, it's just ignorant. And I'm not using that word in a "mean" way -- he just isn't as "in-depth" as he claims.