Seems too complicated as we are far from even knowing if we need a robot gateway for this and how will that even be implemented, details, details...

Separately, would it be possible to get an API call that somehow implements:

The client (spender) generates a CoinSpend signature on the transaction that includes the hash of the transaction as well as the Accumulator and PrivateCoin object. The resulting CoinSpend embeds both a coin serial number and a set of zero-knowledge proofs that prove (A) that the spender knows a coin in the transaction set, (B) that the serial number is consistent with the coin, and (C) the spender knows the secret values for the coin. These are all tied to the transaction hash. The client (spender) serializes the CoinSpend object and transmits the completed ZEROCOIN_SPEND transaction to the network.
[from https://github.com/Zerocoin/libzerocoin/wiki/Integrating-with-bitcoin-clients]

The above needs to trigger a NXT payment from some magic acct that previously received NXT. I just can't figure out the logistics of all that.

James

Looks good!

The Transactions Per Second section says Nxt will be able to handle 1000 TPS with Transparent Forging. My understanding is that it won't be limited to this, but may actually support much larger numbers. What is a better way to phrase this? "thousands of transactions per second"?

The section on mixing services could be expanded to include examples that the average citizen would find useful. e.g. "you can prevent your insurance company or employer from snooping on your medical expenses and terminating your contract if they suspect you of being ill, and prevent advertizing companies or neighbors from spying on your spending habits".

Typo in Transparent Forging section: desifgned => designed.

Depends on AE client devs, community that will test them and Jean-Luc who will decide what height to add the feature at.

where it says "nxt uses a simple script for transactions, so they can be secured only by a mobile phone or raspberry pi" It's a bit confusing. Maybe consider changing it to something like "nxt uses a simple script for transactions, so they can even be secured by a mobile phone or raspberry pi"

Why "script"? Nxt uses data-driven approach, not predicate-driven.

Complete iteration thru all account lets to calculate the time when a particular account could forge a block. Coins r not unique. The public key does.



Part of Nxt Messaging is already implemented (Arbitrary Messages, Alias System), part is being implemented (Account Control).



No. Maybe it won't be implemented at all if someone does it by using Arbitrary Messages and Account Control.

There is a problem, it's incorrect to say "script". But salsacz couldn't know that, coz it requires deep knowledge of Nxt internals.

That's right. Ur English is quite illogical from point of view of the Slavs.

Number of blocks includes orphaned blocks.