Bitcoin Forum

Development Roadmap

Disclaimer:
The NXT developers provide no commitment to deliver any of the features described herein, and reserve the right to change this product roadmap from time to time at their sole discretion.

NXT 1.7 (Dec 2015)
Coin shuffling
Account control for phased transactions
Immediate execution of phased transaction on approval
Stable block times, 60 s average, max 10 min
Fee spreading and throttling of unique resource allocation
Account properties
Singleton assets
Mac installer

NXT 1.8 (April 2016)
Two factor authentication
Account transfer (panic button)
Account control
Controllable assets
Exchange API

NXT 2.0 (December 2016)
White label prunable blockchains

very beautiful site...

... but seems a little slow .  bug ???

Is Smart Contracts feature not included in the tree?

That tree is lovely.  :)

version 1.4 means NXT price to da moon.

Has anyone got a link to bitcoin's technology tree? I want to know how it'll compare in 5 years....

1.4 on the other hand will include another hard fork in order to enable the Monetary System.

where can i found roadmap of features?

Visit the Nxt Technology Tree at nxttechnologytree.com (http://nxttechnologytree.com) to view the features that have been implemented in Nxt and find out more about the plans for the future.

I love this tree, but is there a way to find out which devs are working on each project.  I would love to read their updates the same way James does his updates.  

As you may have noticed I have been absent from the forum these past few weeks. As I have said in some of my last posts, this is due to "real world commitments" (job) that are taking up all my time.

Fortunately, we already have 2 new GUI developers working on core that are doing a great job. Mrv777 is working on his theme changer, a feature that I didn’t have time to develop, and is also working on the UI for a 1.4 feature, the "monetary system".

Jones as I understand it is working on wallet.dat and a few other things. And I hear crimi may also be interested in joining the GUI developers sometime soon.

Having multiple GUI developers just makes sense, it was never good to rely on a single person (me) in the past. It should also bring new ideas and innovations, such as the QR login / signing idea from HumanFractal. And of course it will speed up development, which sometimes has to wait for GUI development before being able to test things properly (this was partly why 1.3 took so long).

*snip*

For core devs Jean-Luc/Mrv777/lyaffe/ChuckOne/CfB (not so much now)/might have missed someone, it is best to follow the Nxt Commits Twitter:  https://twitter.com/nxtcommit


For James type updates, Kushti and Jones each have started their own threads-

Kushti: https://nxtforum.org/general/kushti%27s-topic/

Jones: https://nxtforum.org/general-discussion/the-official-jones-thought-thread/

I am not sure if Wesley has got his own thread, they work him hard on the GUI so I think he does that 24/7 now (had to give up working on Jinn to keep up)



Kushti is knee deep with another phd student, a maths professor on sabatical and CfB digging deep into the forging algo here...

https://nxtforum.org/general/nxt-forging-algorithm-simulating-approach/

... so you might not hear from him for a while. I think CfB is hoping Kushti gets a better knowledge of Transparent Forging than him so he can take a back seat on the technical side  :D


Failing that, you just have to ask them  :D

@Jabo38, update from Wesley on GUI progress

TL:DR
i) Wesley (GUI dev) very busy with RL work. We have two new GUI devs.
ii) Re-skin of client theme being developed by Mrv777.
iii) Monetary system confirmed by two devs now as being in version 1.4.0
iv) Due to public demand, Jones&Wesley working on a wallet.dat system for Nxt
v) A fourth GUI dev, Crimi, may be joining soon. I believe Crimi currently runs the very useful peerexplorer.com (http://peerexplorer.com) atm.
vi) Humanfractal's idea of QR login/signing seems to be in the pipeline.
vii) Having more GUI devs will speed up the releases of Nxt (and get us along the tech tree quicker  ;D)


Source: https://nxtforum.org/technical-development-committee/gui/msg122194/#msg122194

...in an effort to increase transparency, we greatly improved out presence on the BitBucket issue tracker: https://bitbucket.org/JeanLucPicard/nxt/issues?status=new&status=open ...

Kushti is also active atm...


Kushti: "Trustless escrows are coming!"

https://nxtforum.org/general/trustless-escrows-are-coming!/ (https://nxtforum.org/general/trustless-escrows-are-coming!/)

Topics covered in OP;

Trustless escrows
2-phase transactions (phasing)
Multivoting
Vote-for-hash & votable appendix

Monetary System definitely yes.
Smart Contracts definitely no.
Voting, and Phasing, not yet sure.

Smaller features that will be included: asset dividends payment transaction, alias deletion transaction.

And I forgot to mention Coin Shuffling which was initially part of the Monetary System, it will not be in 1.4, but Lior is already working on it so very likely 1.5.

Where can we get info about this Lior dev?

nxt is one of the best cryptos and gets the least respect. is there a timeline?

Hi folks,

some updates and teasers:

1.3.3 is almost finished. Its up-front improvement is the **tease**. ;)

For the 1.4 series we already decided a feature freeze:
 - Monetary System (UI in progress), mostly described here: https://bitbucket.org/JeanLucPicard/nxt/issue/136/monetary-system
 - Dividends Payment (awaiting UI, but is trivial)
 - Alias Deletion (awaiting UI, but is trivial)

We assume having a workable UI for MS in 1 or 2 weeks and we are going to put this on the testnet as 1.4.0e.

We further expect you, guys, to shit-test the MS as you did with the Asset Exchange; to test every single nasty corner and special case. The MS is a very huge feature update containing a lot of new transactions types, database upgrade and bugs (kidding but you never know, so it is your responsibility to find them). Do not forget to test dividends payments and alias deletion either.

Leave your feedback here.

Cheers,
Chuck


PS: active MS thread: https://nxtforum.org/monetary-system/monetary-system-documentation/

Generally when you see a flare up of "Nxt is a sacm", "Nxt Pirates killed Elvis" and "Nxt ate my babies" type threads on here, you know a release is just around the corner  :D :D :D There has been a persistent smearing in the week before the last two releases, always from the usual suspects. But they only delay people in discovering what is happening in Nxt, I see a troll-turned-nxter every so often :)


The 24th of November is Nxt's 1st birthday! so expect something special around then. There is a programme of a release roughly every 6 weeks, but you won't get much more precise than that.

Just published post-implementation 2-phased transactions specification: https://nxtforum.org/general/2-phased-transactions-post-implementation-specification/ . I don't know whether it will be in 1.4 or a later release as 1.4. has too many implemented features to be included probably: Monetary System, Coin Shuffling, dividends, alias deletion, Voting System, 2-phased transactions. But I would be happy see businesses around Nxt starting to think about using 2-phased transactions. For example, with Bitcoin's multisig and 2-phased transactions it's possible to provide signature escrow service without money holding on escrow's side.

A world of Nxt-based businesses could be changed a lot with Voting System(https://nxtforum.org/voting-system/voting-system-got-massive-updates/, https://nxtforum.org/general-discussion/getting-voting-system-out-the-door/) & 2-phased transactions. Distributed shareholders voting, money spendings controlled by shareholders etc

Where is CfB nowadays?

Seems Nxt and other Proof-of-Stake currencies are suffer from lack of trust to the distributed consensus algo. There are some "threats" described e.g.  Nothing-at-Stake, "weaker consensus properties"  ??? and so on. To clarify all claims around proof-of-stake currencies, investigate consensus properties and make the research widely accessible via executable parametric simulations we've started Consensus Research group with  crowdfunding via Nxt AE https://trade.secureae.com/#5841059555983208287 . First results will be published soon including the most clear and formal definition of Nothing-at-Stake to the moment!

Not planned right now as we have too many other features already started in the pipeline and need to get them out.

So, what I can project is: not this year, not in 1.4 (MS release) and not in 1.5 (VS release).

Furthermore, features in development: Coin Shuffling, 2-Phased Transactions and Account Control. So, releases 1.6, 1.7 and 1.8 are presumably occupied by those ones to go down the safest path. Their order is not necessarily presumed and they will keep us busy until March next year.

Until that, I will think about SC/AT, AE v2, RS, JS, CS and RM.

https://i.imgur.com/6wQsQWo.png
https://i.imgur.com/4748djl.png


Happy Birthday Nxt! Congrats to the devs and community on a successful year, the tech continues to roll on, transaction fees continue to rise and empty blocks continue to fall and we are due for some very nice releases in the next 3-4 months  ;D


+1 to everyone, including our lovely trolls  ;)

Visit the Nxt Technology Tree at nxttechnologytree.com (http://nxttechnologytree.com) to view the features that have been implemented in Nxt and find out more about the plans for the future.



https://i.imgur.com/jSdcGIb.jpg


Click on the icons at nxttechnologytree.com (http://nxttechnologytree.com) to find out more.

This tree was created in partnership with Come-from-Beyond and based on the notes passed to him by BCNext. The next release of Nxt, version 1.4.0, is planned to contain several of these new features after significant backend changes were completed in version 1.3.0. This thread will allow you to become acquainted with these features before they are released.

The Nxt Technology Tree is still being updated, please ask any questions you have and I will find an answer for you.


This thread is intended for factual discussion by genuinely interested parties to find out more about Nxt. Please try to respect this.

Make the code partially opensourced. You'll achieve a lots of transparency in suggesting and applying changes. Next code still has too much redundant staff.

voting system got massive update
 kushti

reviewed the VS and phasing code, added TODOs
 JeanLucPicard

Another round of shuffling code review
 lyaffe

New teasers. :)

http://s22.postimg.org/yfquib2a9/currency_founders_table.png
http://s22.postimg.org/4dm9js0up/exchange_booth.png
http://s22.postimg.org/tid9x70b5/exchange_booth_2.png

We hope next week Monday.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Release 1.4.0e

[Link removed, go to https://nxtforum.org/nrs-releases/nrs-v1-4-0e (https://nxtforum.org/nrs-releases/nrs-v1-4-0e)]

sha256:

[SHA removed, go to https://nxtforum.org/nrs-releases/nrs-v1-4-0e (https://nxtforum.org/nrs-releases/nrs-v1-4-0e)]


Change log:

This is the experimental release to test the new Monetary System major feature.
It is enabled on testnet, and those running testnet nodes should upgrade to this
release, even if they don't plan to use the MS features, otherwise will be left
on a fork. This release is also possible to run on main net, but is not to be
considered stable for production use there. The Monetary System block is not yet
defined for main net.


New features:

Monetary System.
See https://bitbucket.org/JeanLucPicard/nxt/issue/205/monetary-system-documentation
for a detailed description.
See https://bitbucket.org/JeanLucPicard/nxt/issue/207/mint-worker-utility for a
description of the MintWorker tool for currency minting.

Dividend payment transaction. Asset issuers can make a dividend payment to all
asset holders with a single transaction. Required parameters are the blockchain
height at which asset holders shares will be counted (must be less than 1440
blocks in the past), and the amount to be paid per share.

Delete alias transaction. The owner of an alias can now delete it completely,
thus making the alias available for anyone to reserve again if desired.

Message pattern in AccountInfo. An account owner can set a regular expression
pattern in the AccountInfo for his account, using the setAccountInfo API.
Once such a pattern has been set, incoming transactions to this account are only
accepted if they contain a plain text message which matches this pattern. The
syntax follows the java.util.regex.Pattern specification.


API changes:

After MS block, adding a public key announcement when sending a transaction to
an account without a public key will be optional.

Added withMessage boolean parameter to getAccountTransactions and
getAccountTransactionIds APIs, to return only transactions having a message
attachment, either non-encrypted or decryptable by the account.

Added optional includeLessors, includeAssets, and includeCurrencies boolean
parameters to getAccount API. Set to false when retrieving those data is not
needed, in order to improve the getAccount performance.

After MS block, sending messages, selling aliases, and leasing balances, to the
Genesis account, will be disallowed.

The popOff debug API now allows pop off of more than max rollback number of
blocks, triggering a full rescan in such case.


Internal changes:

After the Monetary System block, the order in which transactions in a block are
executed will be determined by the block forger, instead of by id, default being
by arrival time at the forger's node.

Improvements in blockchain download to prevent getting stuck on the wrong fork.
Nodes will download blocks in batches of not more than 719 blocks at a time
from a single peer, and after each such batch will verify  with
nxt.numberOfForkConfirmations other peers (default 5) if this is the best
fork, before continuing, unless the downloaded batch is of less than 10 blocks.

Rescan status is now saved in the database, to prevent the database from being
left in an inconsistent state when a rescan fails or is interrupted. Once a
rescan has been scheduled, it will be triggered again at restart, until it
completes successfully.

Improvements in the processing of unconfirmed transactions.

This release will perform a rescan on first start.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJUkN/4AAoJEFOhyXc7+e2ApfoQAIL+QkyZ1zvFXBy2D+u+onCS
4tzVxDmiCz0RNUvICq8XwNhLHxSt7v5FA22XRvX+tFECCiede0WOnVtK/FcSfpVI
J2mDJMLUQu13esXSUHPBu/yYbJIsD4/2eL71TNEmreXV6Hk65Eo6WErf5S6vovnK
XtAQpdpfziJ6mIeTWM7HxReJL7Ddv3w+l4b3qTESU/4aB16iE+1TFvt7z0lCF7AE
n4+0ZckzngB5SkaTPty7nguwwm9eLsPaqu5NdjEQszAclz8KxEchtRRDXEA3xSBE
FNAmS7qhcDgymR7C3sy/Rbk/dhF7m5hcDm48kyMbJOH/zeR6QoLBm8oSYA42QkaC
Ha9FitjIxUCnVWWui+mpcZEjXfpYqFGR+EoI+/AARbHdi3ezrxcfBFWLaZj96iEG
Lp8dx04kgvNxJoPd4kMHaviKSJG+uaav9/qaMRONq5nN5VcxVRmLqHFuQ1UplVvi
1UBie7hTjPMUTX7S03n+f0bZFMUdz6tSs64qcNBYv4yqMX9ycRrJ9DhvsvYHwFpt
PML1rE4bI6x8oeEOePo4TkoyjFNT1Ngz3x6etblkTrfeZk58uaUYbjzlL3J/OUuG
UIUS/uGyMaWuoaytR4aj8hPI2q2wIRXMKyD92sHDuXoa9u1MwFGoHHa4eOuLrsTt
fDATqlU/6JvTnXUnao7p
=tZtE
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Release 1.4.1e

[Link removed, see original post at https://nxtforum.org/nrs-releases/nrs-v1-4-1e (https://nxtforum.org/nrs-releases/nrs-v1-4-1e)]

sha256:

[sha256 removed, see original post at https://nxtforum.org/nrs-releases/nrs-v1-4-1e (https://nxtforum.org/nrs-releases/nrs-v1-4-1e)]


Change log:

This is a bugfix release following 1.4.0e.

Fixed Currency Exchange Booth not working. Fixed currency decimals issue.

Fixed minor bugs in MS transaction validation.

Show total alias count in aliases page. Alias deletion and dividend payment
UI fixes.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJUkfhFAAoJEFOhyXc7+e2AlyQQAOUQHpZc+03kvf0aVQIy45oU
XtHKlt98PwjSKW0MdzyKXXTohdMFTHKR3vvaSRMFqVu+Bvf8ZCL1liLD/J0kidO9
E2AxCvcvAnNKwcNlJQPZjLsboR7aACHG1qwrICOXYeYuBBLrqlUx6UuPjFZdBHXB
BszYDcxpIZ8thUwa/dPhTVdq9Q0AmKoPMME/Jq0OH2tfM3SJEMRI4NkWQbQ8YjmB
1xCt8Z2aplKIJGYmo8pvxZBXvo52N277EKXBnZfn55LoHjIQL3hX4WMBc3GwshhA
9mvJNyMsS4ZTRREH2ZjwiVsu2p+sZ53JBzwhXSpzm2R6LoUrrVA9E6h0ZzKWSj/c
yFvkZjAvGobmmZ6a1kzAiRGKLildkpS2CIDOyy32NMHL9yu538jbbmMvtVVAr1oM
uZehyJxwym+49t0F6dtjwj60nbfYgJoEjXcdidyby+0AQOBHcx+uvhz1easxtsMd
1SgkJ77EdwntK1hXM1Dkx24vA6jABkjihZyBMn3IKQvaSToZFRPe9RXMdqtu+Or6
QmAoXuvy+65I361J6m0wbB1yFvpTgPlOdBAnRr/rx85v3Z+QnNBm6ApmIirINNy7
hRtsvdv6REnI/L8MJdjyGV63nfsuOFqiP32I50cy8XhiO87Cxtpr1SZCHXyk6t5V
iO9Z9Cznf748wQC1TW3u
=TfLA
-----END PGP SIGNATURE-----

The system works, thanks to testers. Please continue trying to break MS  ;D


New testnet version below. Again, for advanced users only.

is there any method or mining software to mine the nxt coin??

The Nxt Team appears to be quite serious about the coin which is more than I can say for most so it might have some potential.

Very true. Arguably, Nxt has the biggest band of coders developing it. But Nxt is going to require patience.

If you're interested, the all-time chart shows [click the "All button on the Coinmarketcap Nxt page (http://coinmarketcap.com/currencies/nxt/) to see it] that 5000 satoshis or lower has been a good entry point. It's near there now. 

NXT needs more marketing and promotion. It should be top five easily.

The  chart shows NXT as a damp and pump coin.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Release 1.4.5

[Go to https://nxtforum.org/nrs-releases/nrs-v1-4-5]

sha256:
[deleted]

Change log:

Enable Monetary System at block 330000. This is a hard fork, therefore everybody
should upgrade to 1.4.5 or later before that.

If upgrading from 1.3.x, read the 1.4.0e and later changelogs for the important
changes and new features introduced in the 1.4 series.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJUoBwLAAoJEFOhyXc7+e2A4dMQAPNhZNnbA4UbnD0lt8tg/4Yw
mPt3qaRKYnNIregbuGWWvXVU6uEJCDXSaYMhMYV5gZBPZRn6fQWyR5BVqA0kBhBg
9PLuasfJmxCVrrDeJYkB7D2SqxjOrIEJroIYkzuqyFw6u7ZccemXcs+t392XqOS2
CMyZFFtrPSM5mPmyzPPsGj2HsDP8dUNySyUhPvcGn+QgvW3BuFsp4UdJs8GbHsBG
4qQYphH4nYSBGTAm0SoAzNsFYTP/juxFch9bCdXFABVmvYZsaCDeH9fUah6MZkD2
e+nPy102DyfjBjhx8HkwT3OBHnT2fZM0aIf5WJ06L9kL1MdPP0hLPdJz+8YGl+kI
ymdRTbRVM0MYWOoNhdhm2m31KNKVysqEO1B1YqyCEDt6P4yeQAl+x/3YjpxQ0pPw
cT9QW+X+SLhB88hyazGIlDXTapv3J5DWOTD/mWjvJ6FSm/8I/rpAwBYl6wr6jnUz
5gpT95MyHBrPAhzpvU+GL3ZCpWnOqk29t7AAWlg0E02cAobB8TeZX2R2FJchmBYI
+yL88GpC0R+RzMXm/WQchMPlRLDj9JTNTSIoiJZTs5UmdxWsDJcmo4uYfzjGvmCl
XjUoTwrT5RtE4dcQDrZi09eldD0PWdxyKwQANOYFWq/frzhnA5t9MO5xfnM9spUx
c7CIa1ZwibXB3LZAJ+wU
=Q6Qi
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Release 1.4.6
[removed, see https://nxtforum.org/nrs-releases/nrs-v1-4-6/ for Jean-Luc's message]

sha256:

[removed]


Change log:

Set MS block to 330000 in the UI too, so that the MS features menu appears
after that height.

Enforce that currency exchange offer expiration height is after the current
blockchain height.

Refactoring of the UI html, splitting index.html into multiple files.

Added offer and transfer links to currency exchange booth UI.

This release will perform a rescan on testnet only, with a rollback to block
159305.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJUpV+xAAoJEFOhyXc7+e2AMTcQAJbtNTaGqJ5tnICd43KgXhM0
FfCQ6LdByjXiZlSc7ME8orEjH9yTOGIjsXbpGD13Z43ma6rj0zYcXoJRILutaikx
CZeVQ02OUpJDqw0W01TA9OgXQ0TRqpjmv3//+R9P/wbSec2koeMDxWFq8H3ZUw1K
+ITWnH7uQFT8RfBoN2oRlhN5tGX7eOxblzS5Mfcn///farKcfcHQCruYwrHVIbeg
AvLK0/bIJaiVi5uR73/HznNkwlqipGi2NNdWL1POJ/BdwptGqVSQOadT0zzUuPqp
zYSmO3nx1sXBtgNn+ZJ4hFvR+qwz8T/o49ddRCMWzow1q7H4uzjRL4EA4m4azUVh
+Pg/s6z1EBPRRR+GnsKnX2mm1n+LVAKhT+w60a1Ma/lh6aPes0UDZd/btRRcSw4V
b/whKyaZ60uacwjcULtCRtADhj/rdeVM4eog8CR3b+aLExinEGlcynwdnUoqFjBn
W+Hzy6bhG2VTP2a79lFlb//CH7qLUpM70t4npAyNTxI3BCniHm2ynN6XY3wrBsot
bgFeoA7Sw7wk47AH3Tnp4XoTK5E4X//751H44rUYNtOj1EeTJjCVtvCqfL5Bmckl
YmELXS7rudGvUaVHeiZNCiM8Cj4RTcKbt8h0T9SM11tcvgsAYHB+auRZtorqjFkw
BoFMhcrcoI/wE6bhMcrt
=ey9U
-----END PGP SIGNATURE-----

Will we need to install a new wallet version before the Monetary System goes live?

Will we need to install a new wallet version before the Monetary System goes live?

For now, install 1.4.6: https://nxtforum.org/nrs-releases/nrs-v1-4-6/
Indeed, 1.4.6 is a hard fork.

If another version is release, I would keep it up to date if the release is another hardfork.

Is there anywhere we can download a copy of the blockchain?

Is there anywhere we can download a copy of the blockchain?

Very true. Arguably, Nxt has the biggest band of coders developing it. But Nxt is going to require patience.

If you're interested, the all-time chart shows [click the "All button on the Coinmarketcap Nxt page (http://coinmarketcap.com/currencies/nxt/) to see it] that 5000 satoshis or lower has been a good entry point. It's near there now. 

i think what NXT needs is a core marketing crew with good connections.  it's time for the platform to be marketed towards businesses. 

There is now a Nxt Wiki guide for the Monetary System (https://wiki.nxtcrypto.org/wiki/Monetary_System), based on lyaffe's documentation.

quick question, how long are the confirmation times in MS?

You could also add the wiki link in the OP.

Another good question, I assume the same as Nxt as it is part of the same system so ~1min.


I will check.

https://www.thunderclap.it/projects/20959-create-your-own-cryptocurrency

Now you can support the campaign with Twitter and Facebook accounts, also ask your friends  8)

~1 min is the average. If you check https://nxtblocks.info/#section/blockexplorer_blocks (https://nxtblocks.info/#section/blockexplorer_blocks), you can see the time between blocks.

Looking now, the shortest recent block time I see is 3 seconds, longest is over 6 minutes. There are blocks that come in in 1 seconds, occasional super long blocks will take 20 minutes.

Big movement up today for NXT.

What would be the correct price ?

I think its an error on CMC

What, I thought that price was for real! You mean it's bullshit? If that's true then coinmarketcap's getting flakey.

What, I thought that price was for real! You mean it's bullshit? If that's true then coinmarketcap's getting flakey.

https://nxtforum.org/nrs-releases/nrs-v1-4-7-1/

Update.

Yes, but there was a glitch in displaying the menu on the left to use MS :)

This update fixes it.

N.B. There are over 300 currencies and counting  :o Boom days for forgers

How come there are already so many currencies? Could you create them while the Monetary System was still in beta?

N.B. There are over 300 currencies and counting  :o Boom days for forgers

I am kind of surprised that this did nothing to improve the price ...

It will slowly because every time a coin is minted, 1 Nxt is used for tx fee.

And those fees go to the big whales who can dump the price again. :P

Which demonstrates another "Macro Implication" = Monetary System improves distribution of wealth across NXT ecosystem.

But if it costs $0.02 to mint a new coin... new coin must be worth >>> $0.02

I have earned 90 NXT by selling minted EGOLD. Neat.

What the Monetary System can do?
It's a little complicated.

MS article:
http://nxter.org/nxt-core-monetary-system/

Some MS use cases:
http://nxter.org/nxt-for-financial-experts-local-groups-and-cryptofans/

MS tutorial:
https://wiki.nxtcrypto.org/wiki/Monetary_System

And the MS help desk: https://nxtforum.org/nxt-monetary-system-helpdesk/

Ah, that felt good.  

A comparison chart between known Crypto platforms

Please let us know if you spot any mistakes, so we can correct them!

http://i.cubeupload.com/RGB3wV.jpg

I'm pretty sure Counterparty has multisig and a voting system and is at least working on smart contracts if they aren't already implemented (they ported etheruem's smart contracts over, and the main functionality itself uses a kind of smart contract), and I would think their DEX is an asset exhange isn't it?
around.

Counterparty has voting system?

Truly exciting to see the speed at which NXT continues to evolve!

Why do NXT.org use Wordpress?

What security auditing is done?

I don't know.

Ask in here UP: https://bitcointalk.org/index.php?topic=587007.0

Would you feel comfortable running a multi-million dollar business and have all your currency tied up with an organisation who use Wordpress plugins?

NXt has a lots of function, but none of is killing function.

I just deleted 2 posts by Nxts oldest friends sockpuppets  :D If you feel the need to FUD, i) preferably please do it in the main general Nxt thread and ii) reasoned arguments are preferred over one line with a ' :o '

Thanks all  ;D

I'll vote for Eamorr as not a sockpuppet.
He's pretty clueless about NXT and crypto in general, and has a very touching faith in Ripple.
Still, he does like NXT a little bit, except on the days when he's accusing us of being a bunch of barefoot hippies.

In short, he doesn't really fit the profile of any of our 'proper' trolls, unless they've decided on a much more low-key approach.

 

Already planned.

Thanks  ;D

Last news:

1. Overbusy with all the stuff I'm working on at the moment.  So sorry for long replies / low public activity.

2. Jean-Luc & me are working on 1.5.0e polishing + 2 devs(jones/holgerd77) are working on UI. So yeah it will include voting system & two-phased transactions  :)

3. After 1.5.0e I plan to switch to bugfixing / performance for a while, and also research.

4. ConsensusResearch is going to finish current simulation / theoretical work and going to practical experimental implementation with Scorex, weekends project of mine.

5. Scorex ultra-compact & intentionally not-production-ready cryptocurrency. Started from Qora source code(24K lines of Java code) it will have 6-7K lines of Scala code, no native libs, Curve25519 for signing/verification, json API, command line client. Will be opensourced in February, initial ultracompact release will be named "Lagonaki". If you want to make experiments with a cryptocurrency, start with Lagonaki :) Then we'll add multibranching forging and test it in real life.

Is there a link where I can read more about "two-phased" transactions?

edit: I found one here https://nxtforum.org/general/2-phased-transactions-post-implementation-specification/

Looks pretty good. :-)

Edit 2:  Is there a more recent update link?

Hi folks,

something for you to chew on. ;) Please notice the indicator for pending transaction.

http://fs2.directupload.net/images/150205/udmptolb.png

Why does NXT now take an unbearably long time to load? It is completely impractical to wait for hours for the client to finally open, so THEN I can finally start downloading the blockchain, which also moves at an incredibly slow pace.

Whoever JeanLuc Picard is, your newest releases have pretty much killed NXT for me. Can you please do some rollbacks and announce when the client is back to the way it used to be (which was literally 20x faster to load)?

Ultimate Guide To NXT: Monetary System (https://drive.google.com/file/d/0B8paJFYHGv0QVDN2dXFaRTBFeFE/view?usp=sharing) PDF manual. Donations greatly appreciated.

OP updated, rather than Voting System in version 1.5 and 2-Phased Transactions in v1.6..

... they will both be in the next release, v1.5  ;D



Kushti is implementing a test of changes to forging based on his POS research group's (ConsensusResearch) findings in point 5. Further details are scarce at the moment.

Account Control is not a part of Two-Phased Transaction. It will be released later(1.6-1.7).

P2SH also will be implemented later(1.6?).

1. Will have 1 hour lecture @CoinFestRussia http://en.coinfestrussia.com/ . If you around, welcome :)
2. Voting_2phased branch is merged with develop, so 1.5.0e will be deployed to the testnet soon :)

1.5 is coming soon !

Next release (1.5):
Notification system in Client (https://nxtforum.org/general-discussion/%28core%29-start-of-the-notification-system/)
Plugin system in Client (https://nxtforum.org/nrs-client-development/%28client-plugins%29-specification-developers-guide/)
Voting System (https://nxtforum.org/general-discussion/%28video%29-a-walk-through-nxts-voting-system/)
Two phased transactions (https://nxtforum.org/general-discussion/%28core%29-teaser-for-phased-transactions/)

 ;D

would be interesting if there was a way to create a dynamic password generator that is somehow linked to your mobile with with an app like google authenticator when using nxt login.

Login in Nxt 1.5 does not require a password anymore. Only sending a transaction does. In effect, 1.5 has a multi-account wallet as a client side only feature.

no what i meant was have it generate a custom QR time based code that is derived from your password. so everytime someone logins to nxt they must have the constantly changing pin # to login to their account.

Sorry, I forgot about this. I think I understand.  I'll ask the devs, Jones is always interested in stuff like this.

I knew it  :D Could it be adjusted to rely on a dynamic pin generator, a different PIN produced each use? That sounds complicated to do.

maybe make a 2fa thats somehow correlates to the block height since it changes. and with the block height u generate a 2fa code that only u remeber. say for example a math formula. ex. block height is 1000 . now u decide enter ur own 2fa formula which is: (blockheight * 2) + 5

2fa code is 2005

this is all derived from the block height and the formula u remember. this makes it a always changing pass without the need of another device.

does this make sense?

maybe make a 2fa thats somehow correlates to the block height since it changes. and with the block height u generate a 2fa code that only u remeber. say for example a math formula. ex. block height is 1000 . now u decide enter ur own 2fa formula which is: (blockheight * 2) + 5

2fa code is 2005

does this make sense?

your password is the formula. you never type the formula. you calculate it in your head and you just type it out. even if there was a key logger they wouldnt be able to steal the code since its always changing. no one will know ur formula.

This doesn't make any sense. The client (software) also have to know the same formula  -- the one that is in your head -- otherwise how does the software check if your number  is correct?

2FA  doesn't work with decentralized system. It works when there are two parties, one is a server, and the second one is your phone, both have the same secret and can verify the code generated by the same shared secret. What you are saying makes no sense, as you and the software you  are using must have the same formula on the same machine. That doesn't add any security.

What if I have a smartphone app that has a secretphrase encrypted with the data in a qr code kept somewhere else, then I need to scan that qr code to decrypt the secretphrase, the app signs the transaction bytes with it and then discards the secretphrase and qr code data.

Another dev, Petko, is working on AC. I see regular updates in a corresponding branch, so I think it will be in 1.6

This isn't true 2FA. In 2FA the code is generated dynamically, so it changes every 30  second and can't be reused.

What you describe here is static password in the phone that you are scanning instead of typing.

That isn't 2FA

Nxt client never saves the password  anyway, so if you don't like typing that password, you can write an app that scans it instead. Same thing. This isn't 2FA

2FA in Nxt will be realized with hashchains.

Hi folks,

right now, we are busy finishing the experimental version of 1.5.0e. It will contain the long-announced Voting System and phased transactions.

Voting System will give several options to create polls and several options to vote on such creates polls. Also, the set of voters can be restricted.

Phased transactions leads to a new kind of transactions: transactions included within a block but with delayed execution.

However, understand its implications require a severe amount of time and consideration (concerning the protocol, server-side, UI-side, third-party applications, etc.) which the team currently is working on. We are on a good track to pin down every corner cases, try to smooth things out and remove insensible use-cases.

That's so far for the upcoming release 1.5.0e. I cannot tell a release date for now. We first need to make sure we got it all right (at least theoretically) to reduce the amount of work later on.

Cheers,
Chuck

Yes, active contributor made some improvements to peer layer & tests and working on AC [Account Control] now.

2FA in Nxt will be realized with hashchains.

No, all is about paying to hash. In bitcoin, P2SH is paying to script hash, but there're no scripts in Nxt.

After some more brainstorming, I believe we have a working solution that I will implement for 1.5. It will be possible to use phasing to make two transactions of any type atomic (they are either both executed, or both not executed), as long as at least one of them is phasing safe (asset transfers and AE orders are safe). And the good news is that this will not require any additional transactions, just the two that need to be coupled.

If nothing serious happen, we will be able to release 1.5.0e after this weekend. Please note, this is an experimental release for testnet first.

Jean-Luc and friends have found a way to make 2 phased transactions atomic (both executed or both not executed).

Any plans to adapt that technique towards atomic Asset-to-Asset transactions?

Any plans to adapt that technique towards atomic Asset-to-Asset transactions?

I will use this for InstantDEX

There will be two ways to make two transactions execute atomically in 1.5: phasing with by-transaction voting, and phasing with by-hash voting.

By-transaction is analogous to using referenced transactions, except the attacks possible due to the fact that the referencing transaction is still in the unconfirmed pool when the other one (referenced) is broadcast are avoided, because the phased transaction is already in the blockchain (and if desired, one could wait for 720 confirmations on it) when the other one (linked) transaction is broadcast. As I said, two transactions of any type can be coupled this way, for example two asset transfers. Also a phased transaction can link to up to 10 transaction and be set to require at least n of them to be present in order to get executed.

By-hash is pay-on-reveal-secret, and takes three transactions in total. The two transactions that need to be executed atomically are created as phased, both depending on the same hash, and will be executed only when a third transaction is received that contains a secret which matches that hash. This can be extended to up to 10 transactions being released with the same secret.

Pay on reveal secret can also be used to create cross-blockchain atomic transactions with other blockchains that support the same method, as long as the same hash function (sha256 in our case) is used. If needed, we will extend this to support other hash functions.

Sorry, no additions anymore(for 1.5.x at least), we're going to release! In 1.7 / further releases some additions to VS possible(features for 1.6 already considered and mostly implemented).

*snip*

Yes, this is part of account control and is planned for 1.6, Petko is working on it.

Fix fungability and maybe i will turn my head.

Probably Coin Shuffling + Account Control(only phaseable in 1.6)

*snip*
...even with the prunable data I am implementing now...
*snip*

Prunable data being work on as we speak for a future release..  :o


Source: https://nxtforum.org/general-discussion/maximum-block-size-is-too-restrictive/msg173057/#msg173057

The implementation of prunable plain and encrypted messages is complete and will be in 1.5.1e.

Hi guys,

while checking the updates over Hyperboria I just find out that there will be an event called: "Battle of the Mesh v8" from 3rd to 9th August 2015 in Maribor, Slovenia.

Is there any Nxter who is able to attend and spread to them what can Nxt could do or how to integrate the mesh net hardware with the Nxt platform (decentralized DNS)?

That would be awesome and beneficial both for the two communities!!!

Nxt is the only coin project that constantly delivers what they've promised.

https://bitcointalk.org/index.php?topic=1022078.msg11061636#msg11061636

This got me thinking. I think its time to take another look at NXT.

For the record I joined NXT just after the release but was swayed away primarily because of the amount of coins (1 billion).

 

Total amount of coins doesn't matter.  A large float non-inflationary currency will beat a smaller float inflationary currency every time.  NXT has ZERO inflation.

wondering more about the dev though

will the technology tree ever be updated?

Devs aren't in charge of the tree website, it's a community project  ;D

QBTC runs the website, I want to update the tree. I'll try contacting her again.

there is defiently room for improvement

there is defiently room for improvement

uhhh.. not even 42 hours and you guys have another release? 1.5.5e?

does any other coin crank out this much progress?

Most businesses like Jetcoin are likely to need only a small subset of all Nxt features - I guess balance leasing, aliases, DGS, MS (or at least some MS currency versions), coin shuffling (coming in 1.6), are not needed and not relevant for Jetcoin.

It's getting really confusing what the most up-to-date version of Nxt is. There is a 1.4.xx and a 1.5.xx line at the same time.
I am in the field to understand the differences but new users must be very confused  :-\ Isn't is possible to bring both together?

any video walkthrough?

MrCluster87 has been doing videos for a long time:
https://www.youtube.com/user/MrCluster87/videos

Overview of Nxt 1.5 series:
https://www.youtube.com/watch?v=q4umpYABYt8

Walkthroughs of some of the latest features:
Plugin:
https://www.youtube.com/watch?v=I3XEehcCi4E
Voting:
https://www.youtube.com/watch?v=7YnfL5SXE8U
Phased transactions:
https://www.youtube.com/watch?v=Raq0LNN8v5k

As you know, the Tennessee Project has the full support of the core developers. The success of this fundraiser is closely linked to the future development of Nxt, and I want to post here our current roadmap, as it stands now. You can see our development plan is long term - we need a long term marketing and business plan to go with it.

Development Roadmap

Disclaimer:
The NXT developers provide no commitment to deliver any of the features described herein, and reserve the right to change this product roadmap from time to time at their sole discretion.

NXT 1.7 (Dec 2015)
Coin shuffling
Account control for phased transactions
Immediate execution of phased transaction on approval
Stable block times, 60 s average, max 10 min
Fee spreading and throttling of unique resource allocation
Account properties
Singleton assets
Mac installer

To guarantee development past release 1.7, when faced with continued price decline and almost no marketing, we need your support for the Tennessee project. Show us that you care.

NXT 1.8 (April 2016)
Two factor authentication
Account transfer (panic button)
Account control
Controllable assets
Exchange API

NXT 2.0 (December 2016)
White label prunable blockchains

Development Roadmap

NXT 1.7 (Dec 2015)
Coin shuffling
Account control for phased transactions
Immediate execution of phased transaction on approval
Stable block times, 60 s average, max 10 min
Fee spreading and throttling of unique resource allocation
Account properties
Singleton assets
Mac installer

NXT 1.8 (April 2016)
Two factor authentication
Account transfer (panic button)
Account control
Controllable assets
Exchange API

NXT 2.0 (December 2016)
White label prunable blockchains

Guys, you know we have a lot of hot discussions on AT Project then Smart Contracts proposal from cfb. I wasn't a fan of AT project(I wasn't strictly against that as well though). And I was strictly against Smart Contracts, I really don't like the idea of projecting core implementation details into the blockchain.

Having a job during last days to investigate current state of Ethereum, I would like to say it's good Nxt has delayed AT project adoption. It's not a scalable approach, it has a lot unexpected properties and so on.

Quick example, its possible to write some random crap into blockchain as contract code, e.g. https://etherscan.io/tx/0x4bb32548d3b28d8bbdbe969888dff6285a0404bb314b7a8e5d81a61a313781eb (contract https://etherscan.io/address/0x190cf16a720f69d1b1ac68e873d9c5b06c1f0f2b). It starts with invalid instruction 2f then some meaningless stuff. Fee is minimal as code execution aborts immediately. Trying to submit something about 60kb after this 1kb tx, I've got my geth stuck and broken  ;D

And please note this is not a bug, even more, this is the best behaviour probably(and with arbitraty-input JMP instruction it's not possible to analyze code execution correctness at all, probably).

And scalability would be a problem for Eth. Considering the same logic, e.g. polling to get done against Nxt & Eth, in the former case it's code running
on top of JVM while in latter it's about code running on top of EVM which is running on top of JVM/pyVM/LLVM.

Some researchers around are working on solving general problems of Ethereum-like contracts, namely scalability and privacy. I made the blogpost comparing two known proposals, Hawk and Enigma http://chepurnoy.org/blog/2015/10/towards-a-new-frontier-of-the-smart-contracts-hawk-and-enigma/ .

In both cases contract execution is happening off-chain, and blockchain is being used to store commitments / MACs or CRSes(common reference string for non-interactive Zero Knowledge Proof with size of tens kilobytes).

Surprisingly(or not), Nxt is already well ready for storing that complementary data. The only thing we need is to promote Nxt chain for being used for things like that(so to use Nxt  in both systems). Thoughts?

Very good website, it really sums up NXT's roadmap perfectly, and the design makes it user friendly.

I had to tweet it:
https://twitter.com/RealBitcoinBlog/status/660243941091078144

I think, full Account Control is most important feature in 1.7.

I've  been waiting for this feature for a long time. I thought it was originally going in 1.4 :(

1. Disable non-SmartContract transactions

Removes ability to initiate manual transactions. After they are disabled only virtual transactions initiated by smart contracts (hosted on this account) will be processed. This subfeature is necessary to unlock extra potential of Smart Contracts and should be done before I complete Smart Contracts.

Manual transactions can be enabled again only if a smart contract does it. A possible application is funding an account for a kid who will get access to this account only after some conditions r met (like becoming 18 y.o.)


2. Send money/assets only to predefined accounts

Defines a list of acconts that can be recipients of transactions initiated by the account. Besides extra protection some other schemes can use this subfeature, for example, an escrow service that can send money only to Alice or Bob, but not to himself.

 
3. Enable/Disable "Instant Transactions" mode

Enables/disables "instant" transactions mode described by BCNext here - https://bitcointa.lk/threads/nxt-instant-transactions-with-guaranteed-confirmation.179540/

Pay attention, that it doesn't automatically create IT feature. Mczarnek is working on another IT approach proposed by anon136, but I think that we need legacy IT mode just in case.


4. Allow/Disallow only some outgoing/incoming transaction types

Allows/disallows different transaction types. Besides extra security it's handy to prevent anyone from sending trash assets to ur account.


5. 2FA with hash chains

This brings 2-factor authorization into Nxt. Actually it's possible to have N-factor auth, it's similar to Multisig of Bitcoin, but requires to send two transactions instead of one. This also adds protection against quantum computers.


6. Transfer of everything to another account (at will, dead man's switch, incoming transaction)

Can be used to transfer everything from one account to another. It can also be used to "merge" multiple accounts into one.


7. Setting spending limits

As title says. Can be used for stronger security and also to limit amounts ur wife/kid spends.

The website is 99.9% by QBTC  :)

The tweet got over 70 retweets, gotta spread the word about nxt tree and upcoming features.

I advertised my tweet, lets see how efficient will be :)

...I see that people confuse Account Control and Phasing. The rule is quite simple: if it's only u who control ur account then it's AC, if other people required for control then it's Phasing [Phased Transactions].

Nice one  ;D

Over 110 retweets now. Any results so far? Let me know so that I can see if this is efficient.

In the spirit of keeping the community informed about what is coming in 1.7, here is the changelog, as it is now. All features described are already implemented, this is not a roadmap, this is completed work (for the server part at least, we are still waiting for the UI to be finished and polished).


Coin Shuffling
This feature is based on the paper by Tim Ruffing et al, http://crypsys.mmci.uni-saarland.de/projects/CoinShuffle/coinshuffle.pdf .

Coin shuffling can be used to perform mixing of NXT, MS currencies (unless created as non-shuffleable), or AE assets. Any account can create a new shuffling, specifying the holding to be shuffled, the shuffle amount, number of participants required, and registration deadline. This is done using the shufflingCreate API. The subsequent shuffling steps can be done either manually, by using the shufflingRegister (for accounts other than the creator), shufflingProcess, shufflingVerify or shufflingCancel APIs, or, much more conveniently, by starting an automated Shuffler, using the startShuffler API. Once started, the Shuffler monitors the blockchain state for transactions relevant to the specified shuffle, and automatically submits the required transactions on behalf of the user, performing shuffle processing, verification, or cancellation as needed. To do this, the Shuffler is required to keep the user secret phrase in memory, therefore it should be run on a trusted local machine only. A restart or a crash of the node requires the shuffler to be started again using the startShuffler API, as it should never save the user secret phrase on disk.

To participate in a shuffling, a deposit of 1000 NXT is needed, in addition to the amount of currency or asset being shuffled. Or if shuffling NXT, the amount of the shuffle must exceed this 1000 NXT minimum. If the shuffling completes successfully, this amount is added to the recipient account balance, to allow it to send outgoing transactions (as it is required that only new, unused accounts are specified as recipients). If the shuffle fails due to a registered participant failing to participate as required, or intentionally submitting false data, the participant responsible for the shuffle cancellation is penalized by retaining this deposit and sending it to the forger of the shuffle finish block instead. If a shuffle is cancelled because the required number of participants is not met, nobody is penalized and all deposits are refunded.

Query APIs to retrieve currently running shufflers, shufflings, and shuffling participants are: getAllShufflings, getAccountShufflings, getAssignedShufflings, getHoldingShufflings, getShufflers, getShuffling, and getShufflingParticipants.

If desired, finished shufflings can be automatically deleted from the database if the nxt.deleteFinishedShufflings property is set to true (default is false).

The fee for creating a shuffling or registering in one is 1 NXT, for the shuffling process or shuffling cancel transactions 10 NXT, and for the verify transaction 1 NXT.


Account control for phased transactions
Any account can be restricted to only be allowed to issue phased transactions subject to a specific voting model. This is achieved by the account submitting a setPhasingOnly transaction using the setPhasingOnlyControl API. The getPhasingOnlyControl API can be used to retrieve the status of an account phasing control, and getAllPhasingOnlyControls to get all accounts subject to phasing control with their respective restrictions.

Once set, the phasing only account control can only be disabled or changed with another setPhasingOnly transaction, itself subject to the currently set phasing restrictions.

Note that by-transaction and by-hash voting models are not allowed for phasing control, and setting voting model to none is used to disable the control.


Immediate release of phased transactions on approval
Phased transactions with a voting model that does not depend on account balance (such as by-transaction or by-hash), or by-account with no minimum balance and with a whitelist, will be released before their finish height as soon as approved (in the block in which the transaction causing their approval is executed), if possible. Such early finish is guaranteed for transaction types known to be phasing safe. For others, if the early finish does not succeed due to the transaction failing validation at this height or conflicting with another transaction in the same block, a second, final release attempt will be performed at finish height.


New base target adjustment algorithm
Average block times will be 60 s, with 1440 blocks per day. Block times should practically never exceed 10 min.

Limit of 1000 NXT on minimum forging balance. This applies to the total of the account own guaranteed balance plus any balances leased to it, but not to each individual balance lease. An account with balance lower than the limit can still lease its balance to another.


Account properties
Those are name / value pairs that can be set on any account (except Genesis), by either the account owner, or by another account. Names are limited to 32 characters, and values to 160 characters. Names are unique per account and per setter account, but not globally unique. Account properties cannot be transferred between accounts. The setter of an account property can edit it by replacing its value with another. Either the setter, or the recipient (if different) of an account property can delete it. There is no limit on the number of properties an account can have. Fee for setting account property is 1 NXT for value up to 32 chars, with additional 1 NXT fee for every 32 chars after that.

Account properties are managed using the setAccountProperty and deleteAccountProperty APIs. To query the properties of an account, or those set by an account, the getAccountProperties API can be used.


Singleton assets
Issuing an asset with a quantity of 1, decimals 0, and description length not exceeding 160 characters, will require a base minimum fee of 1 NXT only, instead of the regular 1000 NXT asset issuance fee. For description of more than 32 chars, an extra 1 NXT fee is added for each 32 chars. Asset name for singleton assets is limited to 10 chars, same as for regular assets.


Throttling of unique resource allocation transactions
Asset issuance (excluding singleton assets), monetary system currency issuance, and alias assignment (excluding re-assignment), will be limited to only one transaction of each type accepted per block.


Spreading back block fees for asset and currency issuance
The transaction fees for asset (excluding singleton assets) and currency issuance will be split between the forgers of the current and the previous three blocks in a 4:3:2:1 ratio.


Deletion of asset shares will be performed as a separate AssetDelete transaction type instead of as sending the shares to Genesis. Sending shares to Genesis will no longer be allowed.


Fees and size limit changes

Several transaction types or attachments will have new fees and size limits, to encourage users to utilize the prunable versions when available, and to make fees proportionate to actual blockchain space consumed.

Aliases:
Base fee 2 NXT, with 2 NXT additional fee for each 32 chars of name plus URI total length, after the first 32 chars. Name and URI size limits remain at 100 and 1000 chars respectively.

Messages and EncryptedMessages (non-prunable):
Maximum length reduced to 160 bytes. 1 NXT fee for each 32 bytes after the first 32 bytes. For encrypted messages, the length is measured excluding the nonce and the 16 byte AES initialization vector.

Fees and size limit for prunable messages remain unchanged.

AccountInfo:
Base fee 1 NXT, with 2 NXT additional fee for each 32 chars of name plus description total length, after the first 32 chars. Name and description size limits remain at 100 and 1000 chars. AccountInfo transactions throttled at one per block.

Polls:
Base fee 10 NXT for polls with up to 20 options, and total size of poll name plus poll description plus total option length not exceeding 320 chars. For each option above 20, an additional fee of 1 NXT, and for each 32 chars after 320, an additional fee of 1 NXT. Poll creation throttled to one per block. Name, description, and option length limits remain at 100, 1000, and 100 chars respectively.

DGS Listing:
Base fee 2 NXT, with 2 NXT additional fee for each 32 chars of name plus description total length, after the first 32 chars. Name and description size limits remain at 100 and 1000 max. DGS Listing throttled at one per block.

DGS Delivery:
Base fee 1 NXT, with 2 NXT additional fee for each 32 bytes of encrypted goods data after the first 32 bytes, nonce and AES initialization bytes excluded. Encrypted goods data size limit remains 1000 bytes.

Coin Shuffling
This feature is based on the paper by Tim Ruffing et al, http://crypsys.mmci.uni-saarland.de/projects/CoinShuffle/coinshuffle.pdf .

And a confirmation by Tim that all issues have been addressed:

No problem. Just to confirm: All your answers look reasonable and make sense to me

1. There will be changes in fees and permanent message size limit in 1.7. They will take effect in the 1.7 hard fork, in very early January 2016.

2. These changes will break any application that has hardcoded fees of 1 NXT, or uses permanent messages exceeding 160 bytes.

3. *snip* ALL API USERS CAN, AND ABSOLUTELY MUST START UPDATING THEIR CODE NOW. DO NOT WAIT UNTIL 1.7 STABLE IS RELEASED *snip* START UPDATING TO 1.6.2, USE SERVER-SIDE FEE CALCULATION, AND EITHER SWITCH TO PRUNABLE MESSAGES, OR MAKE SURE PERMANENT MESSAGE SIZE DOES NOT EXCEED 160 BYTES.

4. To repeat. Do not wait until 1.7.1 stable *snip* THIS IS THE ADVANCE NOTICE.

Technical questions about the transition should be discussed here: https://nxtforum.org/core-development-discussion/adapting-client-side-code-to-the-fee-changes-planned-for-1-7/