The potential for that chart to be a broad, objective comparison of some of the main 2.0 projects is there, but as it stands it is extremely biased towards NXT to the point where it's not even trying to be subtle about it (only green ticks and under construction in the NXT side...really now?), in addition a cursory glance shows glaring factually incorrect segments.
Please see the third post of this topic. I had already post the chart, but I mention the fact that it was only the Nxt collumn that was up to date. Nxt community will update the chart using the data in the current topic.
For your information, yes Nxt has every "green ticks" and "under construction ticks" for each element mention in the chart.
Nxt is NOT working on Smart Contracts, Automated Transactions, Multisig, Instant Transactions, Anonymous Transactions.
Aye...
1. smart contract is already all written from Cfb, it need to be put into the Nxt code, however there is other priority for the moment.
2. AT, well it depend on how you see this (burst and crypti are Nxt clone, afaik). But I would agree that for now it is not a priority. So that tick could be remove, I give you that one
3. multisig, yes they are working on that for whole account for next hard fork 1.7, now currently only support multisig for individual transaction with two-phase transaction.
4. anonymous transaction, yes coin suffling for NXT and MS is planned for next hard fork 1.7.
5. Instant transaction, I know a Nxt devs is working on this. but I can't remember his name. I would have to dig in the forum.
Nxt supports atomic cross-chain exchange using the pay on reveal secret method, as described here:
http://upcoder.com/11/atomic-cross-chain-exchange/#pay-on-reveal-secret
It was implemented and released in production in the 1.5 release:
https://bitbucket.org/JeanLucPicard/nxt/issues/224/proposal-new-tx-type-pay-on-reveal-secret
Automated transactions, which Nxt does not support, is one way of implementing atomic cross-chain exchange, but as you can see certainly not the only one.
Nxt does not support anonymous transactions, but it will support Coin Shuffling as described in this paper: http://crypsys.mmci.uni-saarland.de/projects/CoinShuffle/coinshuffle.pdf , here is the description of the Nxt implementation of it: https://bitbucket.org/JeanLucPicard/nxt/issues/135/coin-shuffling-monetary-system (note that it will work not only for Monetary System coins but for NXT itself too). The work as described in this issue is completed, what remains to be done is the so called "blame phase", making sure a rogue shuffle participant who tries to sabotage the shuffle is penalized for it. This will be released in 1.7.
http://upcoder.com/11/atomic-cross-chain-exchange/#pay-on-reveal-secret
It was implemented and released in production in the 1.5 release:
https://bitbucket.org/JeanLucPicard/nxt/issues/224/proposal-new-tx-type-pay-on-reveal-secret
Automated transactions, which Nxt does not support, is one way of implementing atomic cross-chain exchange, but as you can see certainly not the only one.
Nxt does not support anonymous transactions, but it will support Coin Shuffling as described in this paper: http://crypsys.mmci.uni-saarland.de/projects/CoinShuffle/coinshuffle.pdf , here is the description of the Nxt implementation of it: https://bitbucket.org/JeanLucPicard/nxt/issues/135/coin-shuffling-monetary-system (note that it will work not only for Monetary System coins but for NXT itself too). The work as described in this issue is completed, what remains to be done is the so called "blame phase", making sure a rogue shuffle participant who tries to sabotage the shuffle is penalized for it. This will be released in 1.7.
1. & 2. Smart contracts/AT: Jean-Luc I think it was you, who mentioned that it will not go into the source. With that as the current standpoint you can't say that it's being worked on.
3. Ok.
4. Coin Shuffling is not anonymous transactions. It's another feature.
5. Instant transactions were planned by Matthew C., he is now at Burst. So no, it's not being worked on.
Crypti is NOT a Nxt clone. It's written from scratch, written in Javascript/Node.js. Uses DPoS for consensus.