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.

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.

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.

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.

The blockchain pruning planned for 2.0 is a prerequisite before increase of transaction throughput can be considered. Before thinking of how to process thousands of transactions per second, we must solve the problem of where those transactions would be stored and how the resulting increase in database size will affect performance, and without pruning it won't scale.

This is a great project for both NXT and NXT investors. Might I add, for the building of "real world" applications, NXT might want to host NXT hackathons. This may draw more people to be interested from outside the crypto-community, while building some great applications for all alike.

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.

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.

Maybe really stupid question: Jean-Luc posted roadmap for NXT and one of the planned features will be blockchain "pruning" (next year). Could Iota help using checkpoints not only for security, but also for "pruning" blockchain resulting data size decrease of it? In other words, how close NXT and Iota can cooperate?

They can cooperate on that. Every iota transaction has "attachment" field that can store up to 385.14 bits of data which can be used for checkpointing and other things. One of such thing is the root of a Merkle tree storing a complete snapshot of Nxt ledger at some block height.

They can cooperate on that. Every iota transaction has "attachment" field that can store up to 385.14 bits of data which can be used for checkpointing and other things. One of such thing is the root of a Merkle tree storing a complete snapshot of Nxt ledger at some block height.

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.

They can cooperate on that. Every iota transaction has "attachment" field that can store up to 385.14 bits of data which can be used for checkpointing and other things. One of such thing is the root of a Merkle tree storing a complete snapshot of Nxt ledger at some block height.

They can cooperate on that. Every iota transaction has "attachment" field that can store up to 385.14 bits of data which can be used for checkpointing and other things. One of such thing is the root of a Merkle tree storing a complete snapshot of Nxt ledger at some block height.

I've been toying around with a 384 bit quadratic extension field curve that supports a four dimensional endomorphism (GLV-GLS). The use of the quadratic extension avoids much of the bad scaling, but I'm not to a point where I can benchmark anything yet.

They can cooperate on that. Every iota transaction has "attachment" field that can store up to 385.14 bits of data which can be used for checkpointing and other things. One of such thing is the root of a Merkle tree storing a complete snapshot of Nxt ledger at some block height.

Full transparent forging, meaning getting rid of base target adjustment, exact 60 s or shorter block intervals, predicting the queue of next forgers and penalizing a forger that misses his turn, sending transactions directly to the processing hub announced by the next forger, will only be needed in order to increase a lot the transaction throughput and shorten block times. This is going back to the issue of having to have pruning in place first, in 2.0.

With the improved base target adjustment in 1.7, we will have much less variation in blocktimes, so this advantage of TF will no longer be that important, it is only for further reducing the blocktimes and increasing transactions per second that we will need TF.