elective-stereophonic
elective-stereophonic
Development roadmap
singapore
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Nxt Client: Nxt 1.11.15

Pages: [1] 2 3  All

Author Topic: Development roadmap  (Read 8659 times)

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Development roadmap
« on: April 09, 2014, 02:01:43 pm »

I am now working on integrating into the develop branch the changes from
feature/tf branch that CfB was working on. Those include Digital Goods Store,
Effective Balance Leasing, Transparent Forging changes (getNextBlockGenerators),
Phased transactions (not sure if this got completed). They will be enabled only
on test net initially, but I need to merge the code, convert all amount handling
logic to NQT, do some review and refactoring, fix obvious bugs if any.

I also need to integrate the canonical signatures and AES encrypt patches from
Dr Evil, and switch the encryption in DGS to use AES.

In the meantime, Wesley and other client devs should make the transition to NQT
so that their clients work with the 0.9 branch.

The remaining issue in AE:
https://bitbucket.org/JeanLucPicard/nxt/issue/79/buy-order-and-sell-order-matching-does-not
needs to be resolved, and this is a good warm-up task for a new developer, while
I am busy with the above work.

After bugs in fractional NXT transactions are found and fixed, we need to try on
test net the NQT_BLOCK transition without a blockchain reset. This means, first
we do another reset by setting NQT_BLOCK in the future, so that blocks with
fractional transactions on test net get deleted and again everything is only in
whole NXT. Until NQT_BLOCK, 0.9 nodes internally use NQT, but transactions are
still signed in the old format, with integer amounts. When NQT_BLOCK is reached,
transactions after that block will be signed and verified in the new format
(amounts as longs). Around the time of the transition, transactions that were
created before NQT_BLOCK but didn't get a chance to be included in the last
non-NQT block, will end up eventually being rejected. Similarly, if a fork
reached NQT_BLOCK height sooner, and its nodes started signing transactions in
the new format sooner than the real chain, those new transactions may either get
rejected, or popped off and included in new blocks after NQT, depending on their
timestamp and deadline. So overall this is a tricky transition and we need to
rehearse it first on testnet.

Only after such test is successful, and we have switched to NQT on main net, with
all clients supporting NQT and AE, we can consider launching AE.

I need to work on moving all derived objects - Accounts, Assets, etc, to the
database. I will start on that immediately after finishing the merge of the
feature/tf branch. The launch of AE does not strictly need to wait for this to
be completed, but while everything is still kept in memory we don't have a
scalable system and if AE is unexpectedly successful we will not be prepared
to handle the sudden increase in assets, orders, trades and so on. Moving those
to the database will in turn create different performance issues that need to be
found and fixed.

There are several projects that can be taken by new developers in parallel with
the above:

The Voting System needs to be tested and put in production, and will need an API
to get some statistics about voting with various restrictions - such as, only
count NXT that did not move in the last n blocks, or that did not move after the
poll was created, or do not count accounts that were created after the poll, and
so on. Having a working Voting System is important so we can agree on changes to
the minimum fee and asset issuance fee.

Alias transfer, or maybe trading, or expiration, need to be implemented. This is
again a standalone area and I don't have the time to focus on it soon.

The performance of getNextBlockGenerators, needed for TF, has to be significantly
improved. I have some ideas about it, and will see what I can do while integrating
the feature/tf branch, but finishing it may be left for a new developer. Related
to that, the implementation of UDP server and accepting transactions over UDP for
faster and DDOS-resistant processing, is again a completely standalone project
that somebody needs to take.

Features like parallel chains, blockchain shrinkage, persisting or not of some
transactions during shrinkage, will be looked at after the above work is done.

Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

Damelon

  • Administrator
  • Hero Member
  • *****
  • Karma: +792/-54
  • Offline Offline
  • Posts: 2314
    • View Profile
    • Nxt Inside
Re: Development roadmap
« Reply #1 on: April 09, 2014, 02:09:41 pm »

I love you for posting this! :)
Logged
Member of the Nxt Foundation | Donations: NXT-D6K7-MLY6-98FM-FLL5T
Join Nxt Slack! https://nxtchat.herokuapp.com/
Founder of Blockchain Workspace | Personal Site & Blog

Come-from-Beyond

  • Hero Member
  • *****
  • Karma: +794/-671
  • Offline Offline
  • Posts: 4013
    • View Profile
Re: Development roadmap
« Reply #2 on: April 09, 2014, 02:13:18 pm »

Related to that, the implementation of UDP server and accepting transactions over UDP for
faster and DDOS-resistant processing, is again a completely standalone project
that somebody needs to take.

I'm planning to implement this part by myself if others don't mind.
Logged

LiQio

  • Hero Member
  • *****
  • Karma: +50/-5
  • Offline Offline
  • Posts: 672
    • View Profile
    • NxtLoader for Windows
Re: Development roadmap
« Reply #3 on: April 09, 2014, 02:27:37 pm »

This is could easily become my most preferred thread.

Thanks developers!!!

Edit: thanks as well for the information posted below James!
« Last Edit: April 09, 2014, 02:29:41 pm by LiQio »
Logged

jl777

  • Hero Member
  • *****
  • Karma: +718/-123
  • Offline Offline
  • Posts: 6170
    • View Profile
Re: Development roadmap
« Reply #4 on: April 09, 2014, 02:28:55 pm »

For people interested in development status of NXT services, https://nxtforum.org/multigateway-(third-party)/ has info

I just made a roadmap thread too!

James
Logged
There are over 1000 people in SuperNET slack! http://slackinvite.supernet.org/ automatically sends you an invite

I am just a simple C programmer

Ludom

  • Hero Member
  • *****
  • Karma: +197/-15
  • Offline Offline
  • Posts: 1733
    • View Profile
    • Plaisir & Valeur d'histoire
Re: Development roadmap
« Reply #5 on: April 09, 2014, 02:29:26 pm »

BRAVO !

Your work is really great ! Thanks
Logged
Support us to publish "The first book about Nxt"

Daedelus

  • Hero Member
  • *****
  • Karma: +230/-12
  • Offline Offline
  • Posts: 3280
    • View Profile
Re: Development roadmap
« Reply #6 on: April 09, 2014, 08:01:07 pm »

Love It!  ;D ;D ;D ;D


 
« Last Edit: April 09, 2014, 08:59:06 pm by Daedelus »
Logged
NXT: NXT-4CS7-S4N5-PTH5-A8R2Q

kodtycoon

  • Hero Member
  • *****
  • Karma: +43/-18
  • Offline Offline
  • Posts: 916
    • View Profile
Re: Development roadmap
« Reply #7 on: April 09, 2014, 09:07:28 pm »

« Last Edit: April 09, 2014, 09:09:24 pm by ForrestGump »
Logged

antanst

  • Full Member
  • ***
  • Karma: +36/-0
  • Offline Offline
  • Posts: 216
    • View Profile
    • nxtblocks.info
Re: Development roadmap
« Reply #8 on: April 10, 2014, 08:14:06 am »

This is insightful, thank you J-L for taking the time to write it!
Logged

qbd1313

  • Sr. Member
  • ****
  • Karma: +10/-8
  • Offline Offline
  • Posts: 372
    • View Profile
Re: Development roadmap
« Reply #9 on: April 11, 2014, 08:58:28 am »

Logged

Pouncer

  • Jr. Member
  • **
  • Karma: +30/-0
  • Offline Offline
  • Posts: 65
    • View Profile
Re: Development roadmap
« Reply #10 on: April 11, 2014, 09:45:38 am »

I am now working on integrating into the develop branch the changes from
feature/tf branch that CfB was working on. Those include Digital Goods Store,
Effective Balance Leasing, Transparent Forging changes (getNextBlockGenerators),
Phased transactions (not sure if this got completed).

Thanks for the update. Does this mean that the development of TF by CfB is completed, or is this still a work in progress?
Logged

Graviton

  • Sr. Member
  • ****
  • Karma: +62/-30
  • Offline Offline
  • Posts: 297
    • View Profile
    • DGEX
Re: Development roadmap
« Reply #11 on: April 11, 2014, 10:32:48 am »

Good work. Pardon my ignorance, but what does NQT stand for and what is it?
Logged
* dgex.com operator * nextcoin.org founder * mofowallet.com multiwallet founding member

farl4bit

  • Global Moderator
  • Hero Member
  • *****
  • Karma: +210/-45
  • Offline Offline
  • Posts: 3463
    • View Profile
    • Blockchain Twitter
Re: Development roadmap
« Reply #12 on: April 11, 2014, 10:43:08 am »

No problem, here's some more info about NQT (nxtQuant).

https://wiki.nxtcrypto.org/wiki/Glossary#nxtQuant
Logged

Daedelus

  • Hero Member
  • *****
  • Karma: +230/-12
  • Offline Offline
  • Posts: 3280
    • View Profile
Re: Development roadmap
« Reply #13 on: April 11, 2014, 10:48:18 am »

+1

Whoop whoop!!!  for the use of the Glossary  ;D ;D ;D ;D ;D
Logged
NXT: NXT-4CS7-S4N5-PTH5-A8R2Q

farl4bit

  • Global Moderator
  • Hero Member
  • *****
  • Karma: +210/-45
  • Offline Offline
  • Posts: 3463
    • View Profile
    • Blockchain Twitter
Re: Development roadmap
« Reply #14 on: April 11, 2014, 12:04:45 pm »

I have it under my pillow!  - sweat Nxt-dreams -  ;D
Logged

GoldDealer

  • Jr. Member
  • **
  • Karma: +0/-0
  • Offline Offline
  • Posts: 17
    • View Profile
Re: Development roadmap
« Reply #15 on: April 11, 2014, 02:52:50 pm »

....originally posted in wrong topic sorry....

Anyway, it's very inspiring, thanks!  8)
« Last Edit: April 11, 2014, 02:55:11 pm by GoldDealer »
Logged

innovator256

  • Sr. Member
  • ****
  • Karma: +24/-2
  • Offline Offline
  • Posts: 282
    • View Profile
Re: Development roadmap
« Reply #16 on: April 11, 2014, 03:15:44 pm »

great post, al the devs here inspire me to sleep less and do more work!!! thanks for your effort guys
Logged

dmk

  • Jr. Member
  • **
  • Karma: +4/-0
  • Offline Offline
  • Posts: 56
    • View Profile
Re: Development roadmap
« Reply #17 on: April 12, 2014, 06:18:42 am »

I have a proposal for a lightweight way to implement alias transfer: how about just adding an owner_id field to alias assignment transactions?  This would essentially role alias assignment and transfer into one.  If owner_id is null, then sender_id would be considered the owner, which is the behaviour now, so nothing should break.  This would also have advantages if we ever implement alias expiration because it would assure that any alias transfers would come with a new life expectancy from the transfer operation.

Cheers,
David
Logged
dmk
I can tell you want to tip me!
NXT: NXT-ST8J-RVG5-HV8H-22JDD, BTC: 12EZmrowPGxYL7yZMTZfVKc6i5eLyCdDEs

Eadeqa

  • Hero Member
  • *****
  • Karma: +83/-68
  • Offline Offline
  • Posts: 1888
    • View Profile
Re: Development roadmap
« Reply #18 on: April 12, 2014, 06:57:52 am »

and AES encrypt patches from
Dr Evil, and switch the encryption in DGS to use AES.

Before drevil's aes code goes live,  can you add   dhSharedSecret = dhSharedSecret xor iv

and then do  byte[] key = sha256().digest(dhSharedSecret) ?

nothing else needs to be changed.  This will allow two users to share one encrypted message with a third party without sharing rest of messages between them


Logged
NXT-GZYP-FMRT-FQ9K-3YQGS

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: Development roadmap
« Reply #19 on: April 12, 2014, 11:04:12 am »

I have a proposal for a lightweight way to implement alias transfer: how about just adding an owner_id field to alias assignment transactions?  This would essentially role alias assignment and transfer into one.  If owner_id is null, then sender_id would be considered the owner, which is the behaviour now, so nothing should break.  This would also have advantages if we ever implement alias expiration because it would assure that any alias transfers would come with a new life expectancy from the transfer operation.
No. Alias transfer should be a different transaction type.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322
Pages: [1] 2 3  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly