Topic: [NXT] Development Discussion - The dev plan that keeps on delivering - page 4. (Read 22180 times)

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!!!

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

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


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

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

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

Fix fungability and maybe i will turn my head.

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

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*

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.

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

I will use this for InstantDEX

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

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

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.

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.

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

2FA in Nxt will be realized with hashchains.