e.g., if  an  account  has  more  than,  say,  300K  NXT,then it forges as if it had exactly 300K NXT

Are you planning to run the math for the optimal forging limit figure?


Edit:  Are we looking at something like...  Optimal Forging Limit == 333,333,333 / Total Number of Nxt Accounts

Or are we looking at something like...  Optimal Forging Limit == [(Total Amount of NXT Forging)/3] / Total Number of Nxt Accounts


Caught this by the way...

(corresondingly correspondingly, at least 1=2 in the case of Exp-algorithm)


Really glad Nxt has you on board!    

@anon136: "ordo ab chao" definitely not correct latin. See http://en.wikipedia.org/wiki/Ordo_Ad_Chao.

"Ordo ad chao" is incorrect Latin (correct: "ordo ad chaos")[5] for "order to chaos" – a reversal of the Latin expression "ordo ab chao" ("order from chaos")

Wikipedia.org update!

Hey guys,
after quite long time I finished creating new english version of Nxt wiki page:

https://en.wikipedia.org/wiki/Draft:NXT (it's always better to do something instead of chatting about it)

We have a very nice german version, but you cannot simply translate the text - https://de.wikipedia.org/wiki/Nxt - you need to use new citations in used language.

So it also means this article cannot be translated into languages where are missing published articles in that particular language.

I think now it needs only some grammar corrections and more wiki links and it should finally work. 22 citations could be enough

Jerical13: there is a thief who constanlty steals all money from accounts with small passwors. Last time he stole 400k. Then he decided to send 8k to his bter account.

There is no evidence Nxt is ever going to implement zerocoin. It's incompatible  with 1000 TF

Zerocoin has a number of serious limitations:
- It uses cutting-edge cryptography which may turn out to be insecure, and which is understood by relatively few people (compared to ECDSA, for example).
- It produces large (20kbyte) signatures that would bloat the blockchain (or create risk if stuffed in external storage).
- It requires a trusted party to initiate its accumulator. If that party cheats, they can steal coin. (Perhaps fixable with more cutting-edge crypto.)
- Validation is very slow (can process about 2tx per second on a fast CPU), which is a major barrier to deployment in Bitcoin as each full node must validate every transaction.
- The large transactions and slow validation also means costly transactions, which will reduce the anonymity set size and potentially make ZC usage unavailable to random members of the public who are merely casually concerned about their privacy.
- Uses an accumulator which grows forever and has no pruning. In practice this means we'd need to switch accumulators periodically to reduce the working set size, reducing the anonymity set size. And potentially creating big UTXO bloat problems if the horizon on an accumulator isn't set in advance.