Nxt Forum

Nxt Discussion => Nxt Core Development => Core Development Discussion => Topic started by: Sebastien256 on June 05, 2015, 04:34:04 pm

Title: List of feature request for Ardor, Ignis, and Nxt (with the full list in OP)
Post by: Sebastien256 on June 05, 2015, 04:34:04 pm
I would like to compile a list of feature request concerning NRS server, client, plugin, etc.. Anything related to Nxt, from tiny detailed to larger features. Post below what you would like and I will update the the OP. Make sure you can define the request with a title, at least one description sentence and in which category[core/gui/plugin/hardware/installer/others] the request is (this is now mandatory for a feature to be showed in OP because I do not always understand the feature request and this greatly simplify the management of this topic). You can describe in your post why you think it is a good feature, if you wish. From this list, people working on Nxt could get new ideas. I will try to maintain the list up to date as long as I'm not overwhelm. If you find something in the list that is already in NRS, please post it below and I will remove the item from the list. Also, do not hesitate to point out any significative errors or misunderstanding.

Note that this is not a list endorsed by the Nxt devs team. It is only a casual list maintain from my own initiative. Later on, maybe most wanted feature poll could be organized from such a list. Let see where this will lead us.


ARDOR feature request:
F001. 2016-05-24. Let people create either global or local assets, currencies, aliases... (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg217840/#msg217840)

NRS core feature request:
A001. 2015-06-14. Nxt Auction House. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg184004/#msg184004)
A002. 2015-06-14. Confidential transaction. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg184064/#msg184064)
A004. 2015-06-15. Set-heir(s)-transaction. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg184169/#msg184169)
A007. 2015-06-16. Add the time limit of sell asset options when issuing asset on AE. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg184358/#msg184358)
A008. 2015-06-16. Digital Rights Management. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg184362/#msg184362)
A009. 2015-06-16. Account Control. (https://nxtforum.org/general-discussion/examples-of-how-to-use-phased-transactions-(multi-sig-on-steroids)-in-nxt/msg190841/?topicseen#msg190841)
A011. 2015-06-19. Creation of additional key pairs under the same account. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg185012/#msg185012)
A013. 2015-07-09. Swarm like messaging protocol. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg187528/#msg187528)
A014. 2015-07-14. "Block Account" transaction. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg188212/#msg188212)
A015. 2015-07-18. An Improved NXT Market Function. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg188624/#msg188624)
A018. 2015-07-28. Micropayment channel. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg189895/#msg189895) 
A019. 2015-07-28. Allow AE issuer to use Asset to send Nxt message to all shareholder at once. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg189903/#msg189903)
A020. 2015-08-02. Private/encrypted marketplace listings. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg190359/#msg190359)
A021. 2015-08-03. Tx type / Long term "bonded leases". (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg190447/#msg190447)
A022. 2015-08-06. Lending System. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg190707/#msg190707)
A025. 2015-08-11. Extended HD wallet. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg191081/#msg191081)
A027. 2015-10-02. More types of Monetary System coins. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg196930/#msg196930)
A028. 2015-11-12. Blank transactions proposal. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg200375/#msg200375)
A029. 2015-11-12. Advanced Reporting System for external use. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg200408/#msg200408)
A030. 2015-11-24. Two "simple" ideas for Nxt Marketplace. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg201461/#msg201461)
A031. 2015-12-01. Add an option to exclude Account Leasing when setting up mandatory approval account. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg202530/#msg202530)
A032. 2015-12-12. DNS System in NXT - Improvements or Redesigned. (https://nxtforum.org/core-development-discussion/feature-request-dns-system-in-nxt-improvements-or-redesigned/msg203414/#msg203414)
A033. 2015-01-17. RSS feeder api with fully customizable filter. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg206965/#msg206965)
A034. 2015-01-19. Allow node to announce web serve. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg206564/#msg206564)
A035. 2016-02-05. Incentivize nodes participating in shuffle via 1000 NXT blame redistribution. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg208392/#msg208392)
A036. 2016-03-16. "Buy Offer Confirmed Order Book" for shops ? (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg212793/#msg212793)
A037. 2016-03-30. Optimized config files. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg213964/#msg213964)
A038. 2016-03-30. Automatically send the forging revenue to other accounts. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg214671/#msg214671)
A039. 2016-04-29. Free transactions for forgers. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg216723/#msg216723)
A040. 2016-05-22. A crash reporter analyzer. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg217648/#msg217648)
A041. 2016-07-14. Auto-forging. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg221780/#msg221780)

NRS client GUI feature request:
B004. 2015-06-15. Special message to add latest news about the asset. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg184164/#msg184164)
B007. 2015-06-15. List the accounts by account name in the login window. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg184242/#msg184242)
B009. 2015-06-19. Comments to specified voting. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg185008/#msg185008)
B011. 2015-07-14. Customizable dashboard tiles. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg188260/#msg188260)
B012. 2015-07-17. Add a way to link to an account with an URL. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg188610/#msg188610)
B013. 2015-07-19. Message hover-over. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg188758/#msg188758)
B014. 2015-07-23. Make it easy for websites to post links directly to "your Asset", "your marketplace Item" etc. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg189424/#msg189424)
B015. 2015-07-28. Better means of handling multiple accounts. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg204562/#msg204562)
A023. 2015-08-10. Hierarchical Deterministic (HD) wallet. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg191149/#msg191149)
B016. 2015-08-14. Ability to initiate forging even though blockchain is not downloaded. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg191341/#msg191341)
B017. 2015-08-17. One click NRS update from the client. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg191665/#msg191665)
B018. 2015-09-08. Simplified NRS Wallet option. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg193372/#msg193372)
B019. 2015-09-11. Asset turnover ratio. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg193676/#msg193676)
B021. 2015-10-16. History of dividends paid. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg196854/#msg196854)
B022. 2015-10-17. Need Weighted Average Cost when selling assets. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg196936/#msg196936)
B022. 2015-10-17. Colorize contacts to differ them at AE and Dashboard by color label. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg196937/#msg196937)
B023. 2015-11-01. Button to download the trade history as a .csv file. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg198422/#msg198422)
B024. 2015-12-19. Notary and property register. (https://nxtforum.org/core-development-discussion/feature-request-notary-and-property-register/msg204018/#msg204018)
B027. 2015-12-28. On the login page, keep separate account lists for MainNet and TestNet. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg204564/#msg204564)
B028. 2016-01-10. Nxt Arbitrary Messages use case: Certified e-mails. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg205554/#msg205554)
B029. 2016-01-17. Turn off plugin warning. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg206402/#msg206402)
B031. 2016-01-20. Block time counter. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg206719/#msg206719)
B032. 2016-01-20. Login with Alias button like http://jnxt.org/nxt/. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg206702/#msg206702)
B033. 2016-01-20. Supernet-like login screen. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg206750/#msg206750)
B034. 2016-04-04. Multiple destinations for AM in the UI. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg214730/#msg214730)
B035. 2017-10-02. Suggestion of relooking of the lockscreen interface. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg236696/#msg236696)

Feature request for Nxt plugin or by a third party:
A010. 2015-06-17. Need to be done outside the core. (https://nxtforum.org/general-discussion/price-speculation/msg190050/#msg190050)   Add vpn function. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg184618/#msg184618)
C002. 2015-06-30. A blockchain statistic plugin. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg186374/#msg186374)
A024. 2015-08-10. Need to be done outside the core. (https://nxtforum.org/general-discussion/price-speculation/msg196327/#msg196327) Direct trade/exchange between MSCoin_1 and MSCoin_2, or between Asset_1 and Asset_2. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg191048/#msg191048)
C003. 2015-11-01. Telegram. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg198434/#msg198434)

Hardware related feature request:
D001. 2015-06-19. All in one NXT-SuperNet-FreeMarket-MeshNet Raspberry Pi Device. (https://nxtforum.org/index.php?topic=9491.0)

NRS installer feature request:
E001. 2015-09-08. Different shortcut icon for the Nxt wallet and Nxt Server. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg193357/#msg193357)
E002. 2015-11-17. Archive Nxt node check box in the Nxt installer setup. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg200854/#msg200854)


To be released feature request (in Ardor):
To be released in Ardor. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg229174/#msg229174) A006. 2015-06-16. Allow AE issuer use MS to devidents payment. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg184353/#msg184353)
To be released in Ardor. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg229174/#msg229174) A017. 2015-07-28. Allow AE issuer use Asset to make dividends payment in another Asset. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg189891/#msg189891)

Released feature request:
Thanks to MrV777. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg212144/#msg212144)         C001. 2015-06-13. Candle sticks graphs for the price of the assets in the AE. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg183748/#msg183748)
Released in NRS 1.7.4.   B025. 2015-12-21. Add "Data Cloud"->"Upload Data" submenu. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg204117/#msg204117)
Released in NRS 1.7.0e. (https://nxtforum.org/nrs-releases/nrs-v1-7-0e/) B024. 2015-11-21. To the list of peers, add columns to say whether the peer offers archival and open API services. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg201494/#msg201494)
Released in NRS 1.7.0e. (https://nxtforum.org/nrs-releases/nrs-v1-7-0e/) A016. 2015-07-18. Shuffling for NXT. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg184084/#msg184084)
Released in NRS 1.7.0e. (https://nxtforum.org/nrs-releases/nrs-v1-7-0e/) A012. 2015-07-07. Blocktimes never exceed 3 minutes. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg187189/#msg187189)
Released in NRS 1.7.0e. (https://nxtforum.org/nrs-releases/nrs-v1-7-0e/) A005. 2015-06-15. Tradable token that represent a non divisible virtual unique object (special lower fee in AE for that special used case). (https://nxtforum.org/nrs-releases/nrs-v1-6-1e/msg196921/#msg196921)
Released in NRS 1.7.0e. (https://nxtforum.org/nrs-releases/nrs-v1-7-0e/) A003. 2015-06-14. Shuffling for assets. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg184084/#msg184084)
Released in NRS 1.6.2. (https://nxtforum.org/nrs-releases/nrs-v1-6-2/)   B020. 2015-10-05. Have the categories sorted alphabetically on the http://localhost:7876/test - page. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg195677/#msg195677)
Released in NRS 1.6.2.    (https://nxtforum.org/nrs-releases/nrs-v1-6-2/)A028. 2015-10-16. An easier way to manage hallmarks. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg196914/#msg196914)
Released in NRS 1.6.0e. (https://nxtforum.org/nrs-releases/nrs-v1-6-0e/msg193687/#msg193687) B001. 2015-06-07. Add forging block fee reward in the transaction dashboard. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg182424/#msg182424)
Released in NRS 1.6.0e. (https://nxtforum.org/nrs-releases/nrs-v1-6-0e/msg193687/#msg193687) B003. 2015-06-13. Core dividend feature notification. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg183746/#msg183746)
Released in NRS 1.5.15. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg196929/#msg196929) B008. 2015-06-16. Unsigned Transaction Bytes + QRCode if Secret Phrase not specified. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg185110/#msg185110)
Released in NRS 1.5.15. (https://nxtforum.org/nrs-releases/nrs-v1-5-15/msg191323/#msg191323) B010. 2015-06-19. Display total MS currency value in NXT. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg185110/#msg185110)
Released in NRS 1.5.15. (https://nxtforum.org/nrs-releases/nrs-v1-5-15/msg191323/#msg191323) B005. 2015-06-15. Enable "anonymous" offline transactions. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg184167/#msg184167)
Released in NRS 1.5.15. (https://nxtforum.org/nrs-releases/nrs-v1-5-15/msg191323/#msg191323) B006. 2015-06-15. Make issuing an asset or MS coin with less than 2 or more than 6 decimals hard to do. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg184244/#msg184244)
Released in NRS 1.5.15. (https://nxtforum.org/nrs-releases/nrs-v1-5-15/msg191323/#msg191323) B002. 2015-06-13. A button/something to set leasing duration to the max possible value in the leasing dialog. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg190358/#msg190358)

Feature requests that were deemed impossible:
Reference. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg196929/#msg196929) A026. 2015-08-29. Unique serial numbers attached to each cryptocurrency unit (option for MS). (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg192740/#msg192740)
Title: Re: List of feature request for NRS
Post by: Sebastien256 on June 05, 2015, 04:34:47 pm
Reserved
Title: Re: List of feature request for NRS
Post by: Sebastien256 on June 06, 2015, 10:05:16 pm
Ok, I'll start with something quite simple that I used to love in the Nxt client, but gone since a while now.
Client feature request:
Add forging block fee reward in the transaction dashboard.

Older Nxter know what I mean. This was available prior to version NRS 1.0. Presently, you can't see the block reward unless you go to the block section.
It is fine, but I think that a special transaction for this could also be add in the dashboard for more instant view. Obviously, only put the reward in the dashboard if it is not zero.

Are they any particular reasons why this has been removed?

As you can see, this is obviously not a priority. But that is one of the kind of thing I would make a list if you have some requests. Don't be shy. I don't want this list to be a Sebastien256 whishlist haha :D
Title: Re: List of feature request for NRS
Post by: stdset on June 12, 2015, 10:22:39 pm
A button/something to set leasing duration to the max possible value in the leasing dialog.
Title: Re: List of feature request for NRS
Post by: Sebastien256 on June 12, 2015, 10:28:38 pm
A button/something to set leasing duration to the max possible value in the leasing dialog.

Finally, thanks for the input...
Title: Re: List of feature request for NRS
Post by: TwinWinNerD on June 12, 2015, 10:31:10 pm
Core dividend feature notification (Currently there is no dividend notification in the NRS client if you receive a dividend via the core dividend feature)
Title: Re: List of feature request for NRS
Post by: Nxter on June 12, 2015, 10:35:49 pm
Candle sticks graphs for the price of the assets in the AE
Title: Re: List of feature request for NRS
Post by: Sebastien256 on June 14, 2015, 04:50:55 pm
I'll add something that could be interesting. Now this is more or less a bigger feature than given up to now in this topic.

Nxt Auction House.

In fact, an auction house would be a mix between the Nxt marketplace and AE. Indeed, AE fee to create an asset are too high to do such kind of thing and marketplace do not allows bidding on item. Overall, I think Nxt has most necessary code to do such a thing.

As a use case, this AH could be used to trade virtual in-game items in gaming platform. I'm sure a cryptocurrency auction house could attract some niche people also in other markets (for example, you know what Mt gox was before being a cryptoexchange haha  :D).

The way I see it, is that someone would be able to create a prunable asset where anyone or a whitelist could bid on it. Once time-out is achieved, the largest bidder would be contact by the issuer to do an exchange in a similiar fashion as in the Nxt marketplace. Probably people would like to used escrow, but eventually that would result in the creation of a market or trustable escrow around the Nxt ecosystem, which certainly be a good thing.

Also, check out this older topic on this subject:
https://nxtforum.org/general-discussion/nxt-auction-system/

Don't be shy to post your idea.  :)
Title: Re: List of feature request for NRS
Post by: Nxter on June 14, 2015, 05:26:20 pm
I'll add something that could be interesting. Now this is more or less a bigger feature than given up to now in this topic.

Nxt Auction House.

In fact, an auction house would be a mix between the Nxt marketplace and AE. Indeed, AE fee to create an asset are too high to do such kind of thing and marketplace do not allows bidding on item. Overall, I think Nxt has most necessary code to do such a thing.

As a use case, this AH could be used to trade virtual in-game items in gaming platform. I'm sure a cryptocurrency auction house could attract some niche people also in other markets (for example, you know what Mt gox was before being a cryptoexchange haha  :D).

The way I see it, is that someone would be able to create a prunable asset where anyone or a whitelist could bid on it. Once time-out is achieved, the largest bidder would be contact by the issuer to do an exchange in a similiar fashion as in the Nxt marketplace. Probably people would like to used escrow, but eventually that would result in the creation of a market or trustable escrow around the Nxt ecosystem, which certainly be a good thing.

Don't be shy to post your idea.  :)

This would be a nice one for Freemarket
Title: Re: List of feature request for NRS
Post by: ChuckOne on June 14, 2015, 06:38:57 pm
@Sebastien256
Please take into account that we already have issue for some of these features on BitBucket. Some of them are closed and marked as "to-be-done as a plugin"; such as the candle sticks.
Title: Re: List of feature request for NRS
Post by: TwinWinNerD on June 14, 2015, 07:22:21 pm
https://bitbucket.org/JeanLucPicard/nxt/issues?status=new&status=open
Title: Re: List of feature request for NRS
Post by: ThomasVeil on June 14, 2015, 08:26:46 pm
It's a big ask, but I would like to see privacy. Trying to stay anonymous is very hard with the current setup, but necessary.

Maybe (just a noob idea) the recent Bitcoin concept of keeping values private could be applied to NXT (https://people.xiph.org/~greg/confidential_values.txt).
Title: Re: List of feature request for NRS
Post by: Sebastien256 on June 14, 2015, 08:48:36 pm
It's a big ask, but I would like to see privacy. Trying to stay anonymous is very hard with the current setup, but necessary.

Maybe (just a noob idea) the recent Bitcoin concept of keeping values private could be applied to NXT (https://people.xiph.org/~greg/confidential_values.txt).

I will label this as "Confidential transaction" as NRS core request feature in OP.
Title: Re: List of feature request for NRS
Post by: Sebastien256 on June 14, 2015, 08:58:50 pm
https://bitbucket.org/JeanLucPicard/nxt/issues?status=new&status=open
@Sebastien256
Please take into account that we already have issue for some of these features on BitBucket. Some of them are closed and marked as "to-be-done as a plugin"; such as the candle sticks.

Whoa, that list is pretty large and difficult to navigate as the title of the issue are not necessary informative. I note that candle stick should be done as plugin tho.
Title: Re: List of feature request for NRS
Post by: valarmg on June 14, 2015, 09:23:48 pm
Shuffling for assets and NXT.

I believe shuffling is planned for Monetary System, but that's not all that useful compared to being able to shuffle NXT itself and Nxt assets.
Title: Re: List of feature request for NRS
Post by: jl777 on June 14, 2015, 09:33:09 pm
Shuffling for assets and NXT.

I believe shuffling is planned for Monetary System, but that's not all that useful compared to being able to shuffle NXT itself and Nxt assets.
with a layer that shuffles the MS coin and an automated way to use the shuffled coins to convert to NXT or assets, then isnt the net effect the same?
Title: Re: List of feature request for NRS
Post by: Sebastien256 on June 14, 2015, 09:35:21 pm
Shuffling for assets and NXT.

I believe shuffling is planned for Monetary System, but that's not all that useful compared to being able to shuffle NXT itself and Nxt assets.
with a layer that shuffles the MS coin and an automated way to use the shuffled coins to convert to NXT or assets, then isnt the net effect the same?

There is the slippage, if any.
Title: Re: List of feature request for NRS
Post by: jl777 on June 14, 2015, 09:36:28 pm
Shuffling for assets and NXT.

I believe shuffling is planned for Monetary System, but that's not all that useful compared to being able to shuffle NXT itself and Nxt assets.
with a layer that shuffles the MS coin and an automated way to use the shuffled coins to convert to NXT or assets, then isnt the net effect the same?

There is the slippage, if any.
yes, need a low spread environment
Title: Re: List of feature request for NRS
Post by: TheCoinWizard on June 15, 2015, 12:27:30 am
I have a heritage proposal which might be just an Automated Transaction... :)

With introducing a new kind of private transaction setHeirs, where one can specify both
your idle nxt account will either

https://nxtforum.org/nxt-improvement-proposals/set-heir-transaction/ (https://nxtforum.org/nxt-improvement-proposals/set-heir-transaction/)
Title: Re: List of feature request for NRS
Post by: jones on June 15, 2015, 02:17:40 am
Candle sticks graphs for the price of the assets in the AE

http://jnxt.org/jayex

I could do a plugin of this if it's wanted.
Title: Re: List of feature request for NRS
Post by: ThomasVeil on June 15, 2015, 08:57:50 am
I have a heritage proposal which might be just an Automated Transaction... :)

With introducing a new kind of private transaction setHeirs, where one can specify both
  • one or plural heir accounts
  • after how many blocks since last transaction
your idle nxt account will either
  • send your encrypted passphrase to these accounts
  • or just send/divide all the nxt and assets to

https://nxtforum.org/nxt-improvement-proposals/set-heir-transaction/ (https://nxtforum.org/nxt-improvement-proposals/set-heir-transaction/)

+1 Love this idea. Would really solve a problem.
Curious if it would stay anonymous before the transfer - maybe you wouldn't want your relatives to know how many billion NXT you have :D
Title: Re: List of feature request for NRS
Post by: Sebastien256 on June 15, 2015, 10:58:01 am
I have a heritage proposal which might be just an Automated Transaction... :)

With introducing a new kind of private transaction setHeirs, where one can specify both
  • one or plural heir accounts
  • after how many blocks since last transaction
your idle nxt account will either
  • send your encrypted passphrase to these accounts
  • or just send/divide all the nxt and assets to

https://nxtforum.org/nxt-improvement-proposals/set-heir-transaction/ (https://nxtforum.org/nxt-improvement-proposals/set-heir-transaction/)

Hi,

So the title of the request is "Automated Transaction" or "set-heir-transaction"? It look like to me that there is more than one feature request there (I barely understand the feature request). If that is the case, please make it so in as many posts as feature requests with titles and descriptions. I am not able to decode exactly what you want here, so I can't update OP. If not, you can just update your original post with a title and I'll delete my current post.

Thank you for your input.
Title: Re: List of feature request for NRS
Post by: capodieci on June 15, 2015, 11:02:38 am
News ticker in Asset Page

My dream: accounts that is asset issuer can send a special message to add latest news about the asset. In the UI they appear like this:

(http://i.imgur.com/7VJgKSQ.png)
Title: Re: List of feature request for NRS
Post by: Sebastien256 on June 15, 2015, 11:10:50 am
My dream: accounts that is asset issuer can send a special message to add latest news about the asset. In the UI they appear like this:

Interesting! I like this one.
Title: Re: List of feature request for NRS
Post by: verymuchso on June 15, 2015, 11:18:20 am
My dream: accounts that is asset issuer can send a special message to add latest news about the asset. In the UI they appear like this:

This has been available in mofowallet/NXT+ for some time now. I've named it Pulse.
It even comes with a commenting/feedback functionality, all data is stored on the blockchain in it's own (indexed) db tables.

Try it!

Debune: https://www.mofowallet.com/launch.html#/assets/nxt/6926770479287491943/pulse

MofoAsset (test asset with populated data): https://www.mofowallet.com/launch.html#/assets/fim/13664938383416975974/pulse

Edit: seems the comment button doesn't work in the hosted edition, the desktop version seems to work. but you'll get the idea
Edit2: the AE stuff was updated recently (private assets) but has not been released yet, old version looked kinda bad..

(http://i.imgur.com/Zh9ZiY6.png)

Edit3: same Pulse functionality is available for accounts (so your account becomes a blog sort of) Goods and MS Currencies will follow, will use the same the mechanism
https://www.mofowallet.com/launch.html#/accounts/NXT-GQ27-DD53-YM6K-ER6HK/pulse/latest
Title: Re: List of feature request for NRS
Post by: TheCoinWizard on June 15, 2015, 11:21:27 am
Enable "anonymous" offline transactions.

When, in properties, nxt.isOffline=true
no more "waiting for the blockchain to download" in the client gui

Instead set current last online block height (aka set ec_block_height) in the options off fortransactions, defaulted with current last block height.

This would enable all offline transactions, without anonymity being hurt by using the same ec_block_height for multiple accounts...

Currently it is impossible generate offline transactions (not broadcasted) with the standard client once the blockchain hasn't been updated for about 24 hours.
Title: Re: List of feature request for NRS
Post by: TheCoinWizard on June 15, 2015, 11:39:51 am
I have a heritage proposal which might be just an Automated Transaction... :)

With introducing a new kind of private transaction setHeirs, where one can specify both
  • one or plural heir accounts
  • after how many blocks since last transaction
your idle nxt account will either
  • send your encrypted passphrase to these accounts
  • or just send/divide all the nxt and assets to
https://nxtforum.org/nxt-improvement-proposals/set-heir-transaction/ (https://nxtforum.org/nxt-improvement-proposals/set-heir-transaction/)

Hi,

So the title of the request is "Automated Transaction" or "set-heir-transaction"? It look like to me that there is more than one feature request there (I barely understand the feature request). If that is the case, please make it so in as many posts as feature requests with titles and descriptions. I am not able to decode exactly what you want here, so I can't update OP. If not, you can just update your original post with a title and I'll delete my current post.

Thank you for your input.
Sorry for my programming style of typing...  ;)
I write it that way because there are many ways to implement it.

Set-heir-transaction

set inactive blocks = 300000
heir account = NXT-K5KL-23DJ-3XLK-22222

this would send the passphrase of my account to NXT-K5KL-23DJ-3XLK-22222, after I stopped doing outgoing transactions from my account for 300.000 blocks.

Set-heirs-transaction

set inactive blocks = 300000
heir account 1= NXT-K5KL-23DJ-3XLK-22222
heir account 2= NXT-NLFZ-23B5-F98Y-22222
heir account 3= NXT-RRVG-2HWZ-TZEM-22222

this would somehow make sure the account gets split over these three accounts.
 :)
Title: Re: List of feature request for NRS
Post by: Sebastien256 on June 15, 2015, 03:54:58 pm
Tradable token that represent a non divisible virtual unique object (special lower fee in AE for that special used case).

I think that AE exchange can right now be used to make this, such as in-game item property or such. However, AE creation fee are way to high for this to be done in practice. I think that a special reduced fee for a non divisible asset of size 1 should be allowed in the AE. It is special case where MMO such as voxelnault may be happy to have.

I think that this can be done by changing very few lines of code in Nxt.


I was thinking also of the use case of spell of genesis (https://nxtforum.org/nxt-projects/possibility-of-integration-of-alternate-cryptocurrencies-into-spells-of-genesis/msg182880/#msg182880) where they will do ingame virtual card (similar to the game magic), then property can be easily exchange between player and real perveived value is achievable with bidding on AE.

Imo, it is pretty easy to offer such a solution to apps and games devellopers, it is kind of only a "if" statement to be add in the Nxt code!

Imagine a game where every unique item in a game like Diablo 3 suddently appears on Nxt blockchain when they drop and the item can readily be trade on Nxt AE. Nxt cannot do that right now as fee for asset creation are way to high. But they could be reduced for that special limit case.
Title: Re: List of feature request for NRS
Post by: jl777 on June 15, 2015, 03:59:24 pm
Tradable token that represent a non divisible virtual unique object (special lower fee in AE for that special used case).

I think that AE exchange can right now be used to make this, such as in-game item property or such. However, AE creation fee are way to high for this to be done in practice. I think that a special reduced fee for a non divisible asset of size 1 should be allowed in the AE. It a special case where MMO such as voxelnault may be happy to have.

I think that this can be done by changing very few lines of code in Nxt.
why not markeplace listing that has automated digital codes it issues on purchase?
Title: Re: List of feature request for NRS
Post by: Sebastien256 on June 15, 2015, 04:42:16 pm
Tradable token that represent a non divisible virtual unique object (special lower fee in AE for that special used case).

I think that AE exchange can right now be used to make this, such as in-game item property or such. However, AE creation fee are way to high for this to be done in practice. I think that a special reduced fee for a non divisible asset of size 1 should be allowed in the AE. It a special case where MMO such as voxelnault may be happy to have.

I think that this can be done by changing very few lines of code in Nxt.
why not markeplace listing that has automated digital codes it issues on purchase?

Marketplace items... can't be trade easilly between trader. I was thinking also of the use case of spell of genesis (https://nxtforum.org/nxt-projects/possibility-of-integration-of-alternate-cryptocurrencies-into-spells-of-genesis/msg182880/#msg182880) where they will do ingame virtual card (similar to the game magic), then property can be easily exchange between player and real perveived value is achievable with bidding on AE.

Imo, it is pretty easy to offer such a solution to apps and games devellopers, it is kind of only a "if" statement to be add in the Nxt code!

Imagine a game where every unique item in a game like Diablo 3 suddently appears on Nxt blockchain when they drop and the item can readily be trade on Nxt AE. Nxt cannot do that right now as fee for asset creation are way to high. But they could be reduced for that special limit case.
Title: Re: List of feature request for NRS
Post by: jl777 on June 15, 2015, 04:44:48 pm
Tradable token that represent a non divisible virtual unique object (special lower fee in AE for that special used case).

I think that AE exchange can right now be used to make this, such as in-game item property or such. However, AE creation fee are way to high for this to be done in practice. I think that a special reduced fee for a non divisible asset of size 1 should be allowed in the AE. It a special case where MMO such as voxelnault may be happy to have.

I think that this can be done by changing very few lines of code in Nxt.
why not markeplace listing that has automated digital codes it issues on purchase?

Marketplace items... can't be trade easilly between trader. I was thinking also of the use case of spell of genesis where they will do ingame virtual card (similar to the game magic), then property can be easily exchange between player and real perveived value is achievable with bidding on AE.

Imo, it is pretty easy to offer such a solution to apps and games devellopers, it is kind of only a "if" statement to be add in the Nxt code!

Imagine a game where every unique item in a game like Diablo 3 suddently appears on Nxt blockchain when they drop and the item can readily be trade on Nxt AE. Nxt cannot do that right now as fee for asset creation are way to high. But they could be reduced for that special limit case.
MSCOIN 40 nxt is too much?
Title: Re: List of feature request for NRS
Post by: Sebastien256 on June 15, 2015, 04:47:54 pm
Tradable token that represent a non divisible virtual unique object (special lower fee in AE for that special used case).

I think that AE exchange can right now be used to make this, such as in-game item property or such. However, AE creation fee are way to high for this to be done in practice. I think that a special reduced fee for a non divisible asset of size 1 should be allowed in the AE. It a special case where MMO such as voxelnault may be happy to have.

I think that this can be done by changing very few lines of code in Nxt.
why not markeplace listing that has automated digital codes it issues on purchase?

Marketplace items... can't be trade easilly between trader. I was thinking also of the use case of spell of genesis where they will do ingame virtual card (similar to the game magic), then property can be easily exchange between player and real perveived value is achievable with bidding on AE.

Imo, it is pretty easy to offer such a solution to apps and games devellopers, it is kind of only a "if" statement to be add in the Nxt code!

Imagine a game where every unique item in a game like Diablo 3 suddently appears on Nxt blockchain when they drop and the item can readily be trade on Nxt AE. Nxt cannot do that right now as fee for asset creation are way to high. But they could be reduced for that special limit case.
MSCOIN 40 nxt is too much?

What? you know what look the MS booth..., it is not designed for that purpose at all.
But 40 Nxt would be more reasonable than 1000Nxt to create a tradable virtual non-divisible unique item in AE, imho.
Title: Re: List of feature request for NRS
Post by: Nxter on June 15, 2015, 06:05:19 pm
In the logging window now we have a drop down list of our accounts, but we only see them by address. Would be nice to see them by name as well.
Title: Re: List of feature request for NRS
Post by: jl777 on June 15, 2015, 06:08:37 pm
Please make it so that issuing an asset or MS coin with less than 2 or more than 6 decimals is hard to do, or just not allowed from the GUI

and default to 4 decimals as that gives the best balance between volume and price granularity.

assets with 0 or 8 decimals are severely problematic and if the GUI prevented their issuance without three confirmation dialogs about how useless it could be, then we would avoid issues like happened with XORA

James
Title: Re: List of feature request for NRS
Post by: jl777 on June 15, 2015, 06:10:08 pm
Tradable token that represent a non divisible virtual unique object (special lower fee in AE for that special used case).

I think that AE exchange can right now be used to make this, such as in-game item property or such. However, AE creation fee are way to high for this to be done in practice. I think that a special reduced fee for a non divisible asset of size 1 should be allowed in the AE. It a special case where MMO such as voxelnault may be happy to have.

I think that this can be done by changing very few lines of code in Nxt.
why not markeplace listing that has automated digital codes it issues on purchase?

Marketplace items... can't be trade easilly between trader. I was thinking also of the use case of spell of genesis where they will do ingame virtual card (similar to the game magic), then property can be easily exchange between player and real perveived value is achievable with bidding on AE.

Imo, it is pretty easy to offer such a solution to apps and games devellopers, it is kind of only a "if" statement to be add in the Nxt code!

Imagine a game where every unique item in a game like Diablo 3 suddently appears on Nxt blockchain when they drop and the item can readily be trade on Nxt AE. Nxt cannot do that right now as fee for asset creation are way to high. But they could be reduced for that special limit case.
MSCOIN 40 nxt is too much?

What? you know what look the MS booth..., it is not designed for that purpose at all.
But 40 Nxt would be more reasonable than 1000Nxt to create a tradable virtual non-divisible unique item in AE, imho.
I look at MS API, not the GUI

MS coin can be issued for 40 NXT
it is tradeable
it can be made into a non-divisible unique item

so what is the problem?
Title: Re: List of feature request for NRS
Post by: Nxter on June 15, 2015, 06:25:00 pm
Tradable token that represent a non divisible virtual unique object (special lower fee in AE for that special used case).

I think that AE exchange can right now be used to make this, such as in-game item property or such. However, AE creation fee are way to high for this to be done in practice. I think that a special reduced fee for a non divisible asset of size 1 should be allowed in the AE. It a special case where MMO such as voxelnault may be happy to have.

I think that this can be done by changing very few lines of code in Nxt.
why not markeplace listing that has automated digital codes it issues on purchase?

Marketplace items... can't be trade easilly between trader. I was thinking also of the use case of spell of genesis where they will do ingame virtual card (similar to the game magic), then property can be easily exchange between player and real perveived value is achievable with bidding on AE.

Imo, it is pretty easy to offer such a solution to apps and games devellopers, it is kind of only a "if" statement to be add in the Nxt code!

Imagine a game where every unique item in a game like Diablo 3 suddently appears on Nxt blockchain when they drop and the item can readily be trade on Nxt AE. Nxt cannot do that right now as fee for asset creation are way to high. But they could be reduced for that special limit case.
MSCOIN 40 nxt is too much?

What? you know what look the MS booth..., it is not designed for that purpose at all.
But 40 Nxt would be more reasonable than 1000Nxt to create a tradable virtual non-divisible unique item in AE, imho.
I look at MS API, not the GUI

MS coin can be issued for 40 NXT
it is tradeable
it can be made into a non-divisible unique item

so what is the problem?

There is a limitation with this use of the MS...
The tickers of the MS coins are unique and limited.
Title: Re: List of feature request for NRS
Post by: Nxter on June 15, 2015, 08:20:08 pm
In the logging window now we have a drop down list of our accounts, but we only see them by address. Would be nice to see them by name as well.

Please entitled the feature request.

List the accounts by account name in the login window
Title: Re: List of feature request for NRS
Post by: Sebastien256 on June 15, 2015, 08:54:37 pm
Tradable token that represent a non divisible virtual unique object (special lower fee in AE for that special used case).

I think that AE exchange can right now be used to make this, such as in-game item property or such. However, AE creation fee are way to high for this to be done in practice. I think that a special reduced fee for a non divisible asset of size 1 should be allowed in the AE. It a special case where MMO such as voxelnault may be happy to have.

I think that this can be done by changing very few lines of code in Nxt.
why not markeplace listing that has automated digital codes it issues on purchase?

Marketplace items... can't be trade easilly between trader. I was thinking also of the use case of spell of genesis where they will do ingame virtual card (similar to the game magic), then property can be easily exchange between player and real perveived value is achievable with bidding on AE.

Imo, it is pretty easy to offer such a solution to apps and games devellopers, it is kind of only a "if" statement to be add in the Nxt code!

Imagine a game where every unique item in a game like Diablo 3 suddently appears on Nxt blockchain when they drop and the item can readily be trade on Nxt AE. Nxt cannot do that right now as fee for asset creation are way to high. But they could be reduced for that special limit case.
MSCOIN 40 nxt is too much?

What? you know what look the MS booth..., it is not designed for that purpose at all.
But 40 Nxt would be more reasonable than 1000Nxt to create a tradable virtual non-divisible unique item in AE, imho.
I look at MS API, not the GUI

MS coin can be issued for 40 NXT
it is tradeable
it can be made into a non-divisible unique item

so what is the problem?

There is a limitation with this use of the MS...
The tickers of the MS coins are unique and limited.

Using MS would also required to build a decent gui for trading the items. Im not saying MS is not good, just saying the type of booth is not adequate for this type of usage. GUI for AE is ready and perfectly adequate for this purpose and it allows non-unique name and infinite tickers.

Not 100% sure, but we are talking about a few lines of code change here to make this a possibility in Nxt, probably easier this than making a whole new GUI using a core MS coin for trading items.
Title: Re: List of feature request for NRS
Post by: TheCoinWizard on June 15, 2015, 11:20:31 pm
Enable "anonymous" offline transactions.

When, in properties, nxt.isOffline=true
no more "waiting for the blockchain to download" in the client gui

Instead set current last online block height (aka set ec_block_height) in the options off fortransactions, defaulted with current last block height.

This would enable all offline transactions, without anonymity being hurt by using the same ec_block_height for multiple accounts...

Currently it is impossible generate offline transactions (not broadcasted) with the standard client once the blockchain hasn't been updated for about 24 hours.
This is not a core feature, just a NRS client GUI feature request.

Thanks for adding it  :)
Title: Re: List of feature request for NRS
Post by: qq2536007339 on June 16, 2015, 02:10:06 am
Allow AE issuer use MS to devidents payment.
Title: Re: List of feature request for NRS
Post by: allwelder on June 16, 2015, 05:09:15 am
Add the time limit of sell asset options when issuing asset on AE,so this will froze part of the asset to prevent the issuer to dump all asset.

And it's better to have more time limit options.

This will let investors know that when these frozen asset will be sold,much like limit sell shares in traditional market,and can give nxt AE more transparecy

I have heard more ppl worried about the asset issuer to dump one time and run away,so they selected not to join the AE.

Look at the not active volume of AE,we need more ppl join this fantastic feature,but we first need to provide necessary protection and transparency to our investors as much as possible.

Title: Re: List of feature request for NRS
Post by: Roiman on June 16, 2015, 05:19:35 am
I'll add something that could be interesting. Now this is more or less a bigger feature than given up to now in this topic.

Nxt Auction House.

In fact, an auction house would be a mix between the Nxt marketplace and AE. Indeed, AE fee to create an asset are too high to do such kind of thing and marketplace do not allows bidding on item. Overall, I think Nxt has most necessary code to do such a thing.

As a use case, this AH could be used to trade virtual in-game items in gaming platform. I'm sure a cryptocurrency auction house could attract some niche people also in other markets (for example, you know what Mt gox was before being a cryptoexchange haha  :D).

The way I see it, is that someone would be able to create a prunable asset where anyone or a whitelist could bid on it. Once time-out is achieved, the largest bidder would be contact by the issuer to do an exchange in a similiar fashion as in the Nxt marketplace. Probably people would like to used escrow, but eventually that would result in the creation of a market or trustable escrow around the Nxt ecosystem, which certainly be a good thing.

Also, check out this older topic on this subject:
https://nxtforum.org/general-discussion/nxt-auction-system/

Don't be shy to post your idea.  :)

This is a great idea.
Dont forget the Digital Rights Management (DRM) as brought up in the linked topic.
I think DRM is very important not just for auctions but for many market place transactions
Title: Re: List of feature request for NRS
Post by: capodieci on June 16, 2015, 01:32:16 pm
Unsigned Transaction Bytes + QRCode if Secret Phrase not specified

I was playing around with the last NRS and I saw a few new things... In a transaction, when clicking on the "do not broadcast" it returns also the unsigned transaction bytes:

(http://i.imgur.com/BoUCtrO.png)

Still, when creating the transaction, the passphrase is required, else it does not show the transaction data. Is it because the passphrase is necessary to generate the unsigned bytes? I would love that if the passphrase is not entered there was only the unsigned transaction data.

(http://i.imgur.com/aDrM7h6.png)

I have to try with the API, not sure if it is a limit of the UI, but it would be AMAZING if the API given the data of a transaction was returning unsigned data that can then be signed with whatever secret key one pleases, also somewhere else (maybe if passphrase is not entered, in place of signed transaction bytes there could be a QRCode of the unsigned transaction bytes?

I don't know the specs of transaction bytes (signed or unsigned) so I am not sure I am saying something that makes sense or not...

R
Title: Re: List of feature request for NRS
Post by: Sebastien256 on June 16, 2015, 01:38:51 pm
@capodieci

^^ please entitled the feature request and all future one  :). That count for everyone else also. I'm not english native and some time, technical stuff is not easy for me to find fast a title for the OP.
Title: Re: List of feature request for NRS
Post by: capodieci on June 16, 2015, 01:49:50 pm
@capodieci

^^ please entitled the feature request and all future one  :). That count for everyone else also. I'm not english native and some time, technical stuff is not easy for me to find fast a title for the OP.

I am not sure what you are asking me to do :'(
Title: Re: List of feature request for NRS
Post by: Sebastien256 on June 16, 2015, 01:54:26 pm
@capodieci

^^ please entitled the feature request and all future one  :). That count for everyone else also. I'm not english native and some time, technical stuff is not easy for me to find fast a title for the OP.

I am not sure what you are asking me to do :'(

If you want the your request to be add in the original post, please find a short title for the request. Otherwise I need to find one and this is pretty time consuming for every request.   :D

Take a look at the original post so you might more understand what I mean  :)
Title: Re: List of feature request for NRS
Post by: capodieci on June 16, 2015, 02:03:01 pm
@capodieci

^^ please entitled the feature request and all future one  :). That count for everyone else also. I'm not english native and some time, technical stuff is not easy for me to find fast a title for the OP.

I am not sure what you are asking me to do :'(

If you want the your request to be add in the original post, please find a short title for the request. Otherwise I need to find one and this is pretty time consuming for every request.   :D

Take a look at the original post so you might more understand what I mean  :)

Oh, ok. editing it now :)
Title: Re: List of feature request for NRS
Post by: verymuchso on June 16, 2015, 03:05:04 pm
I have to try with the API, not sure if it is a limit of the UI, but it would be AMAZING if the API given the data of a transaction was returning unsigned data that can then be signed with whatever secret key one pleases, also somewhere else (maybe if passphrase is not entered, in place of signed transaction bytes there could be a QRCode of the unsigned transaction bytes?

I don't think that is possible since the unsigned transaction bytes include the sender account id, so this requires the sender to be known upfront.

Not sure if it's the case but i don't see a reason why the sender address could not be taken out of the unsigned bytes part or be pre/a-ppended some other way in the transaction bytes.

But since the signing process in itself is already a complex task why not make it so that it can generate raw transaction bytes from the passphrase alone, kinda chicken and egg problem so it seems.
Title: Re: List of feature request for NRS
Post by: blackyblack1 on June 16, 2015, 04:23:41 pm
I have to try with the API, not sure if it is a limit of the UI, but it would be AMAZING if the API given the data of a transaction was returning unsigned data that can then be signed with whatever secret key one pleases, also somewhere else (maybe if passphrase is not entered, in place of signed transaction bytes there could be a QRCode of the unsigned transaction bytes?

I don't think that is possible since the unsigned transaction bytes include the sender account id, so this requires the sender to be known upfront.

Not sure if it's the case but i don't see a reason why the sender address could not be taken out of the unsigned bytes part or be pre/a-ppended some other way in the transaction bytes.

But since the signing process in itself is already a complex task why not make it so that it can generate raw transaction bytes from the passphrase alone, kinda chicken and egg problem so it seems.
You are wrong. Passphrase is not necessary to create unsigned transaction. Sender is perfectly known from given sender address.
Title: Re: List of feature request for NRS
Post by: verymuchso on June 16, 2015, 05:13:46 pm
I have to try with the API, not sure if it is a limit of the UI, but it would be AMAZING if the API given the data of a transaction was returning unsigned data that can then be signed with whatever secret key one pleases, also somewhere else (maybe if passphrase is not entered, in place of signed transaction bytes there could be a QRCode of the unsigned transaction bytes?

I don't think that is possible since the unsigned transaction bytes include the sender account id, so this requires the sender to be known upfront.

Not sure if it's the case but i don't see a reason why the sender address could not be taken out of the unsigned bytes part or be pre/a-ppended some other way in the transaction bytes.

But since the signing process in itself is already a complex task why not make it so that it can generate raw transaction bytes from the passphrase alone, kinda chicken and egg problem so it seems.
You are wrong. Passphrase is not necessary to create unsigned transaction. Sender is perfectly known from given sender address.

Carefully read back my reply and then your reply and you'll spot the error  ;)
Title: Re: List of feature request for NRS
Post by: xivba on June 16, 2015, 09:01:19 pm
Just want to mention: Account Control.
NXT needs multisig accounts badly, which allows additional layer of security via nxtvault.
Title: Re: List of feature request for NRS
Post by: Tosch110 on June 16, 2015, 11:00:28 pm
Just want to mention: Account Control.
NXT needs multisig accounts badly, which allows additional layer of security via nxtvault.

Is this not exactly what phasing does?
Title: Re: List of feature request for NRS
Post by: xivba on June 16, 2015, 11:31:06 pm
Just want to mention: Account Control.
NXT needs multisig accounts badly, which allows additional layer of security via nxtvault.

Is this not exactly what phasing does?
No. Phasing can control outgoing transactions only via different conditions. It is like voting. Can be used as escrow service.

It doesn't secure accounts or funds already stored in. Account control will do that. I hope soon.
Title: Re: List of feature request for NRS
Post by: qq2536007339 on June 17, 2015, 08:21:00 am
Add vpn function,just like vpncoin did.It's very usefully in China since many popular website is banned by goverment.
Title: Re: List of feature request for NRS
Post by: verymuchso on June 17, 2015, 08:43:56 am
Add vpn function,just like vpncoin did.It's very usefully in China since many popular website is banned by goverment.

Haven't seen that one before. Looking at their btt page https://bitcointalk.org/index.php?topic=705446.0 it seems every node in the network becomes an end point for others who connect to the internet through their internet connection.
One thing that immediately springs to mind is what will happen if I run the vpn wallet and the person who accesses the internet through my connection is surfing for illegal content? My ISP will likely contribute that serving behavior to me I'd think.
Title: Re: List of feature request for NRS
Post by: verymuchso on June 17, 2015, 08:59:58 am
I have to try with the API, not sure if it is a limit of the UI, but it would be AMAZING if the API given the data of a transaction was returning unsigned data that can then be signed with whatever secret key one pleases, also somewhere else (maybe if passphrase is not entered, in place of signed transaction bytes there could be a QRCode of the unsigned transaction bytes?

I don't think that is possible since the unsigned transaction bytes include the sender account id, so this requires the sender to be known upfront.

Not sure if it's the case but i don't see a reason why the sender address could not be taken out of the unsigned bytes part or be pre/a-ppended some other way in the transaction bytes.

But since the signing process in itself is already a complex task why not make it so that it can generate raw transaction bytes from the passphrase alone, kinda chicken and egg problem so it seems.
You are wrong. Passphrase is not necessary to create unsigned transaction. Sender is perfectly known from given sender address.

Carefully read back my reply and then your reply and you'll spot the error  ;)

And? Did you spot it? I'll explain if you wish.
Title: Re: List of feature request for NRS
Post by: blackyblack1 on June 17, 2015, 09:56:49 am
And? Did you spot it? I'll explain if you wish.
Ok explain it.
Title: Re: List of feature request for NRS
Post by: verymuchso on June 17, 2015, 10:08:58 am
And? Did you spot it? I'll explain if you wish.
Ok explain it.

Happy to  ;D

Copdieci wanted to use the API to generate unsigned transaction bytes that can later be signed by whatever secretkey.

But the problem here is that the unsigned transaction bytes (as returned from the API) embed the sender address in the form of the sender public key (see here for example https://github.com/fimkrypto/nxt-plus/blob/master/src/java/nxt/TransactionImpl.java#L590)
So now the problem becomes generating the transaction bytes (which you later sign) which needs the sender address (at least the API does), since that is part of the transaction bytes. Thats what i mean with the chicken and egg problem.

But there is a solution. You could generate the transaction bytes yourself (in javascript for instance), leaving out the senderPublicKey (just put 64 0's in there) and then when it comes to signing them with whatever secretkey (as was requested) first calculate the public key from the secret key you are using, replace the 64 0's with that public key and then sign the transaction bytes with the secret key.

So what i'm saying is since it's such a complex task already, perhaps bypassing the API completely is the better option here.
Title: Re: List of feature request for NRS
Post by: blackyblack1 on June 17, 2015, 11:18:42 am
And? Did you spot it? I'll explain if you wish.
Ok explain it.

Happy to  ;D

Copdieci wanted to use the API to generate unsigned transaction bytes that can later be signed by whatever secretkey.

But the problem here is that the unsigned transaction bytes (as returned from the API) embed the sender address in the form of the sender public key (see here for example https://github.com/fimkrypto/nxt-plus/blob/master/src/java/nxt/TransactionImpl.java#L590)
So now the problem becomes generating the transaction bytes (which you later sign) which needs the sender address (at least the API does), since that is part of the transaction bytes. Thats what i mean with the chicken and egg problem.

But there is a solution. You could generate the transaction bytes yourself (in javascript for instance), leaving out the senderPublicKey (just put 64 0's in there) and then when it comes to signing them with whatever secretkey (as was requested) first calculate the public key from the secret key you are using, replace the 64 0's with that public key and then sign the transaction bytes with the secret key.

So what i'm saying is since it's such a complex task already, perhaps bypassing the API completely is the better option here.
Thanks. I missed the part capodieci wished to use whatever secret.
Title: Re: List of feature request for NRS
Post by: verymuchso on June 17, 2015, 11:27:31 am
Thanks. I missed the part capodieci wished to use whatever secret.

Thats what I thought. Since your argument was valid.
Title: Re: List of feature request for NRS
Post by: jl777 on June 17, 2015, 11:31:07 am
And? Did you spot it? I'll explain if you wish.
Ok explain it.

Happy to  ;D

Copdieci wanted to use the API to generate unsigned transaction bytes that can later be signed by whatever secretkey.

But the problem here is that the unsigned transaction bytes (as returned from the API) embed the sender address in the form of the sender public key (see here for example https://github.com/fimkrypto/nxt-plus/blob/master/src/java/nxt/TransactionImpl.java#L590)
So now the problem becomes generating the transaction bytes (which you later sign) which needs the sender address (at least the API does), since that is part of the transaction bytes. Thats what i mean with the chicken and egg problem.

But there is a solution. You could generate the transaction bytes yourself (in javascript for instance), leaving out the senderPublicKey (just put 64 0's in there) and then when it comes to signing them with whatever secretkey (as was requested) first calculate the public key from the secret key you are using, replace the 64 0's with that public key and then sign the transaction bytes with the secret key.

So what i'm saying is since it's such a complex task already, perhaps bypassing the API completely is the better option here.
Thanks. I missed the part capodieci wished to use whatever secret.
I think it can be sent to any address and as long as whitelist isnt used, then anybody can approve the phased tx by publishing the secret
Title: Re: List of feature request for NRS
Post by: verymuchso on June 17, 2015, 04:10:36 pm
And? Did you spot it? I'll explain if you wish.
Ok explain it.

Happy to  ;D

Copdieci wanted to use the API to generate unsigned transaction bytes that can later be signed by whatever secretkey.

But the problem here is that the unsigned transaction bytes (as returned from the API) embed the sender address in the form of the sender public key (see here for example https://github.com/fimkrypto/nxt-plus/blob/master/src/java/nxt/TransactionImpl.java#L590)
So now the problem becomes generating the transaction bytes (which you later sign) which needs the sender address (at least the API does), since that is part of the transaction bytes. Thats what i mean with the chicken and egg problem.

But there is a solution. You could generate the transaction bytes yourself (in javascript for instance), leaving out the senderPublicKey (just put 64 0's in there) and then when it comes to signing them with whatever secretkey (as was requested) first calculate the public key from the secret key you are using, replace the 64 0's with that public key and then sign the transaction bytes with the secret key.

So what i'm saying is since it's such a complex task already, perhaps bypassing the API completely is the better option here.
Thanks. I missed the part capodieci wished to use whatever secret.
I think it can be sent to any address and as long as whitelist isnt used, then anybody can approve the phased tx by publishing the secret

Not following you there.

Sure I understand that anybody can publish the secret if whitelist is not used (i'm guessing this is how phased txns work - thanks for that).
Not sure how it relates to the discussion.
Title: Re: List of feature request for NRS
Post by: qq2536007339 on June 18, 2015, 01:04:36 am
Haven't seen that one before. Looking at their btt page https://bitcointalk.org/index.php?topic=705446.0 it seems every node in the network becomes an end point for others who connect to the internet through their internet connection.
One thing that immediately springs to mind is what will happen if I run the vpn wallet and the person who accesses the internet through my connection is surfing for illegal content? My ISP will likely contribute that serving behavior to me I'd think.

First of all,I think vpn function is not mandatory,and default set to disable.You will not have trouble if you don't want to.

Second,this function is like commerce VPN service,they don't get punishment for user accesses the illegal content,so do you.
Title: Re: List of feature request for NRS
Post by: verymuchso on June 18, 2015, 07:38:52 am
First of all,I think vpn function is not mandatory,and default set to disable.You will not have trouble if you don't want to.
Second,this function is like commerce VPN service,they don't get punishment for user accesses the illegal content,so do you.

First argument I fully accept.

But how can you be sure the second argument is valid, that would mean that any and all serving for illegal content could potentially be waived away by saying you ran a proxy of some sort. I don't think that would hold, at least not in all places in the world.

Don't get me wrong I like the idea and see the potential, just sounds like the risks are somewhat overlooked.
Title: Re: List of feature request for NRS
Post by: jl777 on June 18, 2015, 07:42:07 am
First of all,I think vpn function is not mandatory,and default set to disable.You will not have trouble if you don't want to.
Second,this function is like commerce VPN service,they don't get punishment for user accesses the illegal content,so do you.

First argument I fully accept.

But how can you be sure the second argument is valid, that would mean that any and all serving for illegal content could potentially be waived away by saying you ran a proxy of some sort. I don't think that would hold, at least not in all places in the world.

Don't get me wrong I like the idea and see the potential, just sounds like the risks are somewhat overlooked.
just require all packets to be high entropy
Title: Re: List of feature request for NRS
Post by: verymuchso on June 18, 2015, 11:02:05 am
First of all,I think vpn function is not mandatory,and default set to disable.You will not have trouble if you don't want to.
Second,this function is like commerce VPN service,they don't get punishment for user accesses the illegal content,so do you.

First argument I fully accept.

But how can you be sure the second argument is valid, that would mean that any and all serving for illegal content could potentially be waived away by saying you ran a proxy of some sort. I don't think that would hold, at least not in all places in the world.

Don't get me wrong I like the idea and see the potential, just sounds like the risks are somewhat overlooked.
just require all packets to be high entropy

How does that work in practice?
Why does that matter when you are still sending/receiving the packets from/to a suspicious domain.
Title: Re: List of feature request for NRS
Post by: jl777 on June 18, 2015, 11:25:46 am
First of all,I think vpn function is not mandatory,and default set to disable.You will not have trouble if you don't want to.
Second,this function is like commerce VPN service,they don't get punishment for user accesses the illegal content,so do you.

First argument I fully accept.

But how can you be sure the second argument is valid, that would mean that any and all serving for illegal content could potentially be waived away by saying you ran a proxy of some sort. I don't think that would hold, at least not in all places in the world.

Don't get me wrong I like the idea and see the potential, just sounds like the risks are somewhat overlooked.
just require all packets to be high entropy

How does that work in practice?
Why does that matter when you are still sending/receiving the packets from/to a suspicious domain.
plausible deniability
also last I checked the possibility that something bad is happening is not enough, but maybe things have gotten worse in USSA where just the possibility is enough to send in the SWAT team.

However, if only high entropy encrypted packets are passively being routed and there is also some doubt as to the origin/destination of the packets, then it is two levels removed and I cant see how on a practical basis this is becoming any problem.

James
Title: Re: List of feature request for NRS
Post by: grewalsatinder on June 19, 2015, 01:43:19 am
All in one NXT-SuperNet-FreeMarket-MeshNet Raspberry Pi Device

https://nxtforum.org/general-discussion/all-in-one-nxt-supernet-freemarket-meshnet-raspberry-pi-device/

Please advise and share your views.

Cheers,
Satinder
Title: Re: List of feature request for NRS
Post by: qq2536007339 on June 19, 2015, 06:53:24 am
But how can you be sure the second argument is valid, that would mean that any and all serving for illegal content could potentially be waived away by saying you ran a proxy of some sort. I don't think that would hold, at least not in all places in the world.

Don't get me wrong I like the idea and see the potential, just sounds like the risks are somewhat overlooked.

I'm not sure,I think VPN will like DGS market,some people will like,and some people will hate it.Just give user a choice,and let each individual decide.
Title: Re: List of feature request for NRS
Post by: qq2536007339 on June 19, 2015, 07:00:11 am
Allow user to post comments to specified voting,and show those comments in the back of voting result.So people can debate directly,should be interesting.

Title: Re: List of feature request for NRS
Post by: sadface on June 19, 2015, 07:34:56 am
this belongs here i think:

quoted from here by kwilliams: https://nxtforum.org/account-control/derived-keys/

NRS should be modified to allow creation of additional key pairs under the same account. They will derive trust from the main account (similar to SSL certificates chains) but have additional restrictions applied to them at creation. For example I should be able to create a "non-spending" keypair that is good for everything else except direct balance transfers. I would use it in my daily activities (sending messages, forging, transferring assets, etc) and even if private key becomes known, people wont be able to steal my balance directly.

Conceptually such keypairs would not be much different from aliases - they will all resolve to the same main identity but be used for different means. Each will have one or more standard policies associated to it ("Can transfer balance", "Can transfer asset", "Can forge", "Can pay network fee", etc). In addition they can have activity quotas ("max_per_block=3","max_per_day=50" which means the key can be used maximum 3 times per block and maximum 50 times per day (1440 blocks)). This is in case they get hacked, the owner will not be bled dry before he has time to revoke the keys.

The usefulness of such keys gets beyond simple security. For example I can create a "messaging only" key and give it to my marketing person to manage the communications of my account without having to worry about them getting hacker, etc. I can also have "asset trading key" which I give to a trading desk which is only interested in managing my asset portfolio (so they can sell my assets or transfer them out, yet have no direct access to my NRS balance)
Title: Re: List of feature request for Nxt and NRS
Post by: Sebastien256 on June 19, 2015, 08:03:27 am
I just change the title of the topic instead to:
List of feature request for Nxt and NRS

Requests are sometime so general, that adding Nxt seems appropriate for the topic title.
Title: Re: List of feature request for Nxt and NRS
Post by: futurist on June 19, 2015, 07:56:44 pm
NRS client GUI feature request:

Somewhere in the dashboard it would be nice to see "Currency Value" that shows the total value of the MS currency you possess.
Title: Re: List of feature request for NRS
Post by: jones on June 29, 2015, 07:44:44 am

http://jnxt.org/jayex

I could do a plugin of this if it's wanted.

I regularly open the jayex page when I'm waiting for a Tx, just to see the little counter in the bottom right.

I think it's a neat little countdown when you're waiting for a confirmation. Could we have a plugin of just the counter?

How does it know (to within a few seconds) when forging is going to occur?

This is doable, I could either make one that fits on a plugin page as its supposed to, or I could probably break the sandboxing and make a static countdown appear all the time at the bottom right corner of the screen on your nxt client, I can make a setting to toggle this.

It is able to calculate when forging occurs because of Nxt's transparent forging ability. With every new block each forger has a wait time until they can create the next block, once a nodes wait time is up, they have 15 seconds to create and distribute the block to everyone.
To calculate the next block, I get a list of the top 80% or so of forgers, then do the calculation on all of them each block to find the one that will win, then I have the next nxt block prediction time with 80% certainty.
For extra credit you are also able to calculate what forger will make the block after the next one and so on, this is shown at http://jnxt.org/blocks, after each block prediction the certainty is diminished slightly.

I will play around with the plugin system tomorrow or the next day, see what I can come up with.
Title: Re: List of feature request for Nxt and NRS
Post by: Sebastien256 on June 30, 2015, 06:59:50 pm
A blockchain statistic plugin would be nice. I will add this one on the list.
https://nxtforum.org/general-discussion/blockchain-statistic/msg185789/#msg185789

Please feel free to contribute about other ideas.
Title: Re: List of feature request for Nxt and NRS
Post by: Nxter on July 04, 2015, 12:22:37 am
Tradable token that represent a non divisible virtual unique object (special lower fee in AE for that special used case).

I think that AE exchange can right now be used to make this, such as in-game item property or such. However, AE creation fee are way to high for this to be done in practice. I think that a special reduced fee for a non divisible asset of size 1 should be allowed in the AE. It a special case where MMO such as voxelnault may be happy to have.

I think that this can be done by changing very few lines of code in Nxt.
why not markeplace listing that has automated digital codes it issues on purchase?

Marketplace items... can't be trade easilly between trader. I was thinking also of the use case of spell of genesis where they will do ingame virtual card (similar to the game magic), then property can be easily exchange between player and real perveived value is achievable with bidding on AE.

Imo, it is pretty easy to offer such a solution to apps and games devellopers, it is kind of only a "if" statement to be add in the Nxt code!

Imagine a game where every unique item in a game like Diablo 3 suddently appears on Nxt blockchain when they drop and the item can readily be trade on Nxt AE. Nxt cannot do that right now as fee for asset creation are way to high. But they could be reduced for that special limit case.
MSCOIN 40 nxt is too much?



Why don't use the alias system for this?
You just create an alias with a code that represents de virtual asset.

Aliases are unique, tradeable and transferable.

Aliases cost 1nxt..
Title: Re: List of feature request for Nxt and NRS
Post by: Sebastien256 on July 04, 2015, 04:56:07 am
Tradable token that represent a non divisible virtual unique object (special lower fee in AE for that special used case).

I think that AE exchange can right now be used to make this, such as in-game item property or such. However, AE creation fee are way to high for this to be done in practice. I think that a special reduced fee for a non divisible asset of size 1 should be allowed in the AE. It a special case where MMO such as voxelnault may be happy to have.

I think that this can be done by changing very few lines of code in Nxt.
why not markeplace listing that has automated digital codes it issues on purchase?

Marketplace items... can't be trade easilly between trader. I was thinking also of the use case of spell of genesis where they will do ingame virtual card (similar to the game magic), then property can be easily exchange between player and real perveived value is achievable with bidding on AE.

Imo, it is pretty easy to offer such a solution to apps and games devellopers, it is kind of only a "if" statement to be add in the Nxt code!

Imagine a game where every unique item in a game like Diablo 3 suddently appears on Nxt blockchain when they drop and the item can readily be trade on Nxt AE. Nxt cannot do that right now as fee for asset creation are way to high. But they could be reduced for that special limit case.
MSCOIN 40 nxt is too much?



Why don't use the alias system for this?
You just create an alias with a code that represents de virtual asset.

Aliases are unique, tradeable and transferable.

Aliases cost 1nxt..

Alias transfer is not phase safe I think, so they can't be trade as the asset in AE. Nothing garanty will get your Nxt once you tranfer the alias and vice versa.
Title: Re: List of feature request for Nxt and NRS
Post by: NxtSwe on July 04, 2015, 08:43:51 am
Tradable token that represent a non divisible virtual unique object (special lower fee in AE for that special used case).

I think that AE exchange can right now be used to make this, such as in-game item property or such. However, AE creation fee are way to high for this to be done in practice. I think that a special reduced fee for a non divisible asset of size 1 should be allowed in the AE. It a special case where MMO such as voxelnault may be happy to have.

I think that this can be done by changing very few lines of code in Nxt.
why not markeplace listing that has automated digital codes it issues on purchase?

Marketplace items... can't be trade easilly between trader. I was thinking also of the use case of spell of genesis where they will do ingame virtual card (similar to the game magic), then property can be easily exchange between player and real perveived value is achievable with bidding on AE.

Imo, it is pretty easy to offer such a solution to apps and games devellopers, it is kind of only a "if" statement to be add in the Nxt code!

Imagine a game where every unique item in a game like Diablo 3 suddently appears on Nxt blockchain when they drop and the item can readily be trade on Nxt AE. Nxt cannot do that right now as fee for asset creation are way to high. But they could be reduced for that special limit case.
MSCOIN 40 nxt is too much?



Why don't use the alias system for this?
You just create an alias with a code that represents de virtual asset.

Aliases are unique, tradeable and transferable.

Aliases cost 1nxt..

Alias transfer is not phase safe I think, so they can't be trade as the asset in AE. Nothing garanty will get your Nxt once you tranfer the alias and vice versa.
I think you can use referenced transaction for this type of transfer. You can look at it as a trustless escrow.
http://wiki.nxtcrypto.org/wiki/Nxt_API#Escrow_Operations
Title: Re: List of feature request for Nxt and NRS
Post by: Jean-Luc on July 06, 2015, 08:28:36 pm
I think we can consider that for 1.6, a singleton asset issued with a quantity of 1 to have a fee of 10 instead of 1000, and then it can be used to represent a single tradeable object.
Title: Re: List of feature request for Nxt and NRS
Post by: Nxter on July 06, 2015, 09:57:23 pm
I think we can consider that for 1.6, a singleton asset issued with a quantity of 1 to have a fee of 10 instead of 1000, and then it can be used to represent a single tradeable object.

There it goes nxtebay. :)
Title: Re: List of feature request for Nxt and NRS
Post by: Tosch110 on July 06, 2015, 10:12:19 pm
I think we can consider that for 1.6, a singleton asset issued with a quantity of 1 to have a fee of 10 instead of 1000, and then it can be used to represent a single tradeable object.

There it goes nxtebay. :)

ehm. great idea btw.
Title: Re: List of feature request for Nxt and NRS
Post by: jl777 on July 06, 2015, 10:26:33 pm
I think we can consider that for 1.6, a singleton asset issued with a quantity of 1 to have a fee of 10 instead of 1000, and then it can be used to represent a single tradeable object.
this is wonderful!!

can you also make the blocktimes never exceed 3 minutes (at current forging levels) by capping the range of the target? I think instead of dividing by 2 without limit, just make it so it can never get to a basetarget below whatever value ends up at ~3 minutes

or instead of divide by 2, do a 7/8 cap on the range of basetarget

these occasional 15+ minute blocks just make things much more difficult as what should be extraordinary edge cases happen every day

James
Title: Re: List of feature request for Nxt and NRS
Post by: landomata on July 06, 2015, 11:03:33 pm
I think we can consider that for 1.6, a singleton asset issued with a quantity of 1 to have a fee of 10 instead of 1000, and then it can be used to represent a single tradeable object.

Will the 1 asset be divisible?
Title: Re: List of feature request for Nxt and NRS
Post by: jl777 on July 06, 2015, 11:10:10 pm
I think we can consider that for 1.6, a singleton asset issued with a quantity of 1 to have a fee of 10 instead of 1000, and then it can be used to represent a single tradeable object.

Will the 1 asset be divisible?
depends on decimals
I think the GUI should default to 4 decimals, which is the most likely to work decently in either direction (price or volume)

and some warning if less than 2 decimals or more than 6

so many assets with hard to deal with 0 decimals or 8 decimals
Title: Re: List of feature request for Nxt and NRS
Post by: verymuchso on July 09, 2015, 08:17:30 am
Got these ideas from a discussion we had on slack yesterday.

Swarm like messaging protocol.

Allows to send a transaction with zero fee that is not stored in the blockchain, instead it is kept in a FIFO queue whose length is adjustable.
Bigger nodes can set the FIFO queue of fee-less transactions to several gigabytes while the smaller ones will only have one of a few MB.

The idea is to be able to send a message to the network that is propagated to all other nodes just as if it was a transaction, it's just not stored in the blockchain.

Use cases:

- free encrypted chat
- other uses like sending NXT off-blockchain (teleport style)

Q: Why use transactions instead of some other data format?
A: Because all the wiring is there already and it could utilize the existing peer protocol + this opens up use cases where the initially (freely) send transactions can later be included in the blockchain, after for instance some co-signature.

Q: What about spam?
A: Well what about it really? Users would only listen to certain messages just as if they only listen for certain transactions.

Q: Anonymity?
A: If everyone sends to everyone else then you would never know who the real recipient was.

Q: Encryption?
A: Messages could use the existing public/private key encryption available already.
Title: Re: List of feature request for Nxt and NRS
Post by: Sebastien256 on July 11, 2015, 01:56:05 pm
I think we can consider that for 1.6, a singleton asset issued with a quantity of 1 to have a fee of 10 instead of 1000, and then it can be used to represent a single tradeable object.

Great!

I think we can consider that for 1.6, a singleton asset issued with a quantity of 1 to have a fee of 10 instead of 1000, and then it can be used to represent a single tradeable object.

Will the 1 asset be divisible?

I think that if it is a single tradable object. This mean that this special case is for 0 decimal. Maybe not...
Title: Re: List of feature request for Nxt and NRS
Post by: Sebastien256 on July 11, 2015, 06:39:12 pm
I think we can consider that for 1.6, a singleton asset issued with a quantity of 1 to have a fee of 10 instead of 1000, and then it can be used to represent a single tradeable object.

Great!

I think we can consider that for 1.6, a singleton asset issued with a quantity of 1 to have a fee of 10 instead of 1000, and then it can be used to represent a single tradeable object.

Will the 1 asset be divisible?

I think that if it is a single tradeable object. This mean that this special case is for 0 decimal. Maybe not...

If it was divisible, wouldn't that be a loophole for releasing a regular asset while avoiding the higher asset issuance fee? Instead of each unit being represented as a whole they would be represented as a decimal.

I agree.
Title: Re: List of feature request for Nxt and NRS
Post by: verymuchso on July 13, 2015, 08:02:38 am
Got these ideas from a discussion we had on slack yesterday.

Swarm like messaging protocol.

Allows to send a transaction with zero fee that is not stored in the blockchain ....

Transient

lasting only for a short time; impermanent.



Thought a bit more about this.
The swarm like protocol remains but it gets a little better integrated with existing NXT infra while making use of verified user balances to prevent network spam.

I propose a new property which applies to all transactions, after we've added the phased property now lets introduce the transient property.

Transactions send to the network with the transient flag will work in the exact same manner as normal transactions (except that they are not applied and are not included in the blockchain), all 'normal' verifications of the transaction validity will apply to transient transactions. This way a user cannot send a million transient messages to the network without having at least 1 million of his NXT locked during the time the transient transactions are available.

This locking of user funds is an extremely effective way of preventing misuse of an open swarm like messaging network and something only available on a p2p network with a blockchain (hello NXT).

Short term use-cases I see immediate need for are:


Jean-Luc, Lior, others what do you think?
Where should the transient transactions be stored and how to go about expiration time, should it be height based or should there be a max size of the table they are stored in?

All feedback is appreciated.
Title: Re: List of feature request for Nxt and NRS
Post by: tribbles on July 14, 2015, 09:05:30 am
*
Title: Re: List of feature request for Nxt and NRS
Post by: Sebastien256 on July 14, 2015, 04:20:39 pm
NRS GUI feature:
Customizable dashboard tiles.

It would be nice if the dashboard tiles and their order (Account balance, Asset value, Currencies, Purchased Products, etc...) could be customizable (by account) from a list of possible tiles instead of being fix and choose by the Nxt devellopement team.

For example, I have currently no use of the "pending sale" tile and it would be nice to be able to choose what I want in this part of my screen. Indeed, the dashboard is the most use page of the Nxt wallet and some part of it are useless to me and others.

As Nxt is growing in functionnality (new voting system tiles would be nice...), different account may have different use and someone may want to customize their different account. So overall, it would be nice to put the effort of making the main page of the Nxt wallet as customizable as possible with modular tiles functionnality.
Title: Re: List of feature request for Nxt and NRS
Post by: futurist on July 14, 2015, 08:11:47 pm
NRS GUI feature:
Customizable dashboard tiles.

It would be nice if the dashboard tiles and their order (Account balance, Asset value, Currencies, Purchased Products, etc...) could be customizable (by account) from a list of possible tiles instead of being fix and choose by the Nxt devellopement team.

For example, I have currently no use of the "pending sale" tile and it would be nice to be able to choose what I want in this part of my screen. Indeed, the dashboard is the most use page of the Nxt wallet and some part of it are useless to me and others.

As Nxt is growing in functionnality (new voting system tiles would be nice...), different account may have different use and someone may want to customize their different account. So overall, it would be nice to put the effort of making the main page of the Nxt wallet as customizable as possible with modular tiles functionnality.
Good idea
Title: Re: List of feature request for Nxt and NRS
Post by: qq2536007339 on July 17, 2015, 01:54:57 pm
I have 2 ideas about AM system.

1) Allow user to send completely prunch message.Like Bitmessage,all message will complete delete after a while.But unlike bitmessage,user can choice how long the message can exist in network,cost can set to 0.02nxt/day/kb.

2) If a message bigger than 64 byte,user can choice if this message can prunch later,only left hash value on blockchain.If choice prunch,lower cost to 0.1nxt.

AM is a great function,allow user to have more choice is a win for everybody.
Title: Re: List of feature request for Nxt and NRS
Post by: Sebastien256 on July 17, 2015, 05:52:03 pm
Post below what you would like and I will update the the OP. Make sure you can define the request with a title and at least one description sentence (this is now mandatory for a feature to be showed in OP because I do not always understand the feature request and this greatly simplify the management of this topic). You can describe in your post why you think it is a good feature, if you wish.

This is just a reminder, and
Please post ideas. I really like to compile them  ;D
Title: Re: List of feature request for Nxt and NRS
Post by: Brangdon on July 17, 2015, 08:16:41 pm
It would be nice if the dashboard tiles and their order (Account balance, Asset value, Currencies, Purchased Products, etc...) could be customizable (by account) from a list of possible tiles instead of being fix and choose by the Nxt devellopement team.
It would also be nice if zero tiles could be hidden automatically. For example, my forging account has no currencies, no sales, no purchased products, no pending or completed sales, no messages and no aliases.

A newly created account could have a much simpler initial dashboard. There's an argument that having these empty tiles serve to advertise the services Nxt offers, but I think the tabs down the left-hand side are sufficient for that purpose, and I'd rather the UI was less complex and did not dazzle new users with pointless information. This will become increasingly important as Nxt gains more features.
Title: Re: List of feature request for Nxt and NRS
Post by: Brangdon on July 17, 2015, 08:36:16 pm
Client GUI: Add a way to link to an account with an URL. For example, clicking on:

http://localhost:7876/index.html?NXT-MRCC-2YLS-8M54-3CMAJ

could open the client with the Genesis account loaded. I would like this to use with bookmarks in my browser, to save a few clicks.


We could go further and have, for example:

http://localhost:7876/index.html?acc=NXT-MRCC-2YLS-8M54-3CMAJ+sendNxt=100+to=NXT-RTYD-LJXQ-EPNJ-H7AQ5+msg=Services+rendered

open the Send NXT page, but this is getting into deeper territory. It'd probably be better to use a more explicit protocol like nxt://... than http. That has been talked about before, although nothing seems to have come of it. I guess reviving that project counts as a separate suggestion.
Title: Re: List of feature request for Nxt and NRS
Post by: agree on July 18, 2015, 06:42:18 am
I suggest improvements to the market rules, introduce intelligent function of contract, the new rules are as follows:

1. When the seller release information about the goods to sell, then frozen and commodity prices the same amount of NXT.

2. The buyer saw sales information, click to purchase goods, and immediately freeze NXT as 2 times commodity prices.

3. The seller see buying information and payment information, send the goods.

4. Assuming that the price is P, when the buyer has received the goods, he click on the "confirm receipt" button, the activation transfer deals, the system automatically will amount to (2 * P – fee) NXT sent to the seller, at the same time, the number of P NXT sent to the buyer.

5. After the seller release information to sell goods, before people buy, the seller may modify or cancel; After the buyer to purchase goods, the seller will not be able to modify or cancel, if he don't send the goods, then the NXT which he froze  don't come back.

6. When the seller after delivery, if the buyer does not confirm the goods, then the NXT which the buyer frozen could not take back.

7. After the buyer to purchase goods, if the time past 30000 blocks, the buyer has not yet been "confirmed receiving", considered the deal default, frozen funds into assets income system. During this period, the buyer and the seller must complete communication, shipment and negotiation.

or we can take a compromise, let the seller to chose , if the seller chose to freeze the NXT, then the buyer must also freeze NXT; If  the seller don't choose to freeze NXT,  the buyer also do not need, like  now.

Title: Re: List of feature request for Nxt and NRS
Post by: Sebastien256 on July 18, 2015, 06:55:06 am
I suggest improvements to the market rules, introduce intelligent function of contract, the new rules are as follows:

1. When the seller release information about the goods to sell, then frozen and commodity prices the same amount of NXT.

2. The buyer saw sales information, click to purchase goods, and immediately freeze NXT as 2 times commodity prices.

3. The seller see buying information and payment information, send the goods.

4. Assuming that the price is P, when the buyer has received the goods, he click on the "confirm receipt" button, the activation transfer deals, the system automatically will amount to (2 * P – fee) NXT sent to the seller, at the same time, the number of P NXT sent to the buyer.

5. After the seller release information to sell goods, before people buy, the seller may modify or cancel; After the buyer to purchase goods, the seller will not be able to modify or cancel, if he don't send the goods, then the NXT which he froze  don't come back.

6. When the seller after delivery, if the buyer does not confirm the goods, then the NXT which the buyer frozen could not take back.

7. After the buyer to purchase goods, if the time past 30000 blocks, the buyer has not yet been "confirmed receiving", considered the deal default, frozen funds into assets income system. During this period, the buyer and the seller must complete communication, shipment and negotiation.

or we can take a compromise, let the seller to chose , if the seller chose to freeze the NXT, then the buyer must also freeze NXT; If  the seller don't choose to freeze NXT,  the buyer also do not need, like  now.

For additional discussion please go to the main topic.
https://nxtforum.org/general-discussion/nxt-(an-improved-nxt-market-function)/
Title: Re: List of feature request for Nxt and NRS
Post by: Sebastien256 on July 18, 2015, 07:49:18 am
I would like to organize some polls on the Nxt blockchain in order to see what are the most wanted features for Nxt and/or NRS. In order to do that, I have created a Nxt account to gather fund from the community to finance the cost of the polls:
Nxt address: NXT-5WQF-E38F-ZBQT-BEHTW
public key: d6ee2946ca3dd864a8ae4ad312dcc41484021ba7aabc89ea527ad8ce78173b11
Once I get enough fund for a couple of polls, I will start some interesting poll on the subject!
Please follow this topic with the notify forum option if you do not want to miss the polls.
Title: Re: List of feature request for Nxt and NRS
Post by: TwinWinNerD on July 19, 2015, 10:03:44 am
Feature Request: "Message hover-over"

On the overview and my transaction section, there is a small "message" icon. I would like to read the message by hovering my mouse over this ico, instead of needing to open the transaction for it. If its encrypted, just write: "Encrypted"
Title: Re: List of feature request for Nxt and NRS
Post by: Sebastien256 on July 23, 2015, 06:23:15 pm
I update in the OP list what I think is being considered for Nxt 1.6 release.
Please don't hesitate to post what you would like  ;D, but follow the OP guideline if you want the suggestion in the OP.
https://nxtforum.org/index.php?topic=9305.msg182234#msg182234

Title: Re: List of feature request for Nxt and NRS
Post by: Tosch110 on July 23, 2015, 09:14:56 pm
I got another request for the GUI.

Make it easy for websites to post links directly to "your Asset", "your marketplace Item" etc.

We could add it to the GUI, in a special folder of the html or use a liteclient within the Nxt folders to archieve this. I have once coded this but it kept breaking with every new release. Still, the idea is there. Nxt would not be more difficult to use than paypal (this could be done with any POST request, so the user would not have to search for an account and look again how much to transfer. Everything could be filled in for him/her in the page to just verify the purchase)

http://www.youtube.com/watch?v=a6lcrNh9AuI&t=2m0s
Title: Re: List of feature request for Nxt and NRS
Post by: Sebastien256 on July 23, 2015, 09:26:28 pm
I got another request for the GUI.

You can have as many as you want.  :D
Title: Re: List of feature request for Nxt and NRS
Post by: capodieci on July 24, 2015, 03:47:37 pm
Show a transaction when dividend payment has been received from an asset.

R
Title: Re: List of feature request for Nxt and NRS
Post by: Sebastien256 on July 24, 2015, 04:31:38 pm
Show a transaction when dividend payment has been received from an asset.

R

Yes, this is being considered for NRS 1.6.  :)
Title: Re: List of feature request for Nxt and NRS
Post by: Sebastien256 on July 28, 2015, 12:55:58 pm
I know we already have this request for MS coin,

but "Allow AE issuer use Asset to make dividends payment in another Asset".

That would be useful for certain use case, as well as permitting Nxt to do easy new asset "swap" in case a change to the asset need to be made (number of unit, decimal, description, etc...).

Please post your ideas!
Title: Re: List of feature request for Nxt and NRS
Post by: grewalsatinder on July 28, 2015, 12:57:54 pm
Is there any micropayment channel like feature in NXT already? If there is, may I get some more info or link to learn more about it?

If not, then I think there must be something like that in NXT.

Reference Link: https://bitcoinj.github.io/working-with-micropayments

Cheers,
Satinder
Title: Re: List of feature request for Nxt and NRS
Post by: grewalsatinder on July 28, 2015, 01:01:34 pm
Is there any micropayment channel like feature in NXT already? If there is, may I get some more info or link to learn more about it?

If not, then I think there must be something like that in NXT.

Reference Link: https://bitcoinj.github.io/working-with-micropayments

Cheers,
Satinder

What category this feature is, Gui or core?

That seems to be core feature.
Title: Re: List of feature request for Nxt and NRS
Post by: Sebastien256 on July 28, 2015, 01:58:28 pm
Just got another one in mind and want to put it out my mind.

"Allow AE issuer use Asset to send Nxt message to all shareholder at once".

This would allowed to store the message only 1 time on the blockchain instead of sending it to every shareholder. It would also make a preferential channel between the issuer and the holder. Every holder would be garanty to get the message.
Title: Re: List of feature request for Nxt and NRS
Post by: TheCoinWizard on July 28, 2015, 01:58:56 pm
but "Allow AE issuer use Asset to make dividends payment".
"Allow AE issuer use Asset to send Nxt message to all shareholder at once".

This would allowed to store the message only 1 time on the blockchain instead of sending it to every shareholder. It would also make a preferential channel between the issuer and the holder. Every holder would be garanty to get the message.
Something like this?

Code: [Select]

TRANSACTION : 7653714893178470041
» Transaction Type : Undefined
» TX Timestamp : 24.07.2015 10:42:25
» Block Timestamp : 24.07.2015 10:51:46
» Block : 10845528220079182759
» Amount : 0
» Fee : 1
» Confirmations : +100
» Deadline : 1440
» Sender : 14464602519333459973
» Recipient : 1739068987193023818
» Sender RS : NXT-GQ27-DD53-YM6K-ER6HK
» Recipient RS : NXT-MRCC-2YLS-8M54-3CMAJ
» ecBlockId : 10102742510963857981
» ecBlockHeight : 480952
» Type : 2
» Subtype : 6
» Attachment :
message :
Hello DeBuNe Asset Holders. DeBuNe had its first income of USD1'500 :)
This means that each asset has an income of USD0.0015 (USD1'500 divided by 1'000'000 DeBuNe Assets available).
Not much, but it is a start! Using nxt2btx.com I have the exchange rate where USD0.0015=NXT0.1166.
I am thus paying dividend of NXT0.1166 per DeBuNe share. It is not much, I know. More will come soon! Enjoy :)
messageHash : b6b93305f5f0c9ebf5b4c31aa09f2531063135ba8b2f149f2a5d67a0b15161f5
version.DividendPayment : 1
version.PrunablePlainMessage : 1
height : 480780
amountNQTPerQNT : 1166
asset : 6926770479287491943
messageIsText : true
» Signature : ba8d0984c67020378a14cfc03973d287370c04324e3ce8f0277514ff9177480b20b5ed1096a67dcfb754471de14a6579b789bc135519c989a9e81e83c0bad9cd
» Signature Hash : a31489bc2ed5c6ef46efd149a1a7a11ac627c8b918148d3cfe0dcb94e2a55f32
» Full Hash : 99fe04ec2475376add3d3ae6461c83726ef741484113f7671162a12405c76f40
» Sender Public Key : 46749b71a632268145a4f415dc95843ec875e27f66fea8aba4018153bb1b007b


I don't recall this being implemented neither though...
Which version implemented this first?
Title: Re: List of feature request for Nxt and NRS
Post by: TheCoinWizard on July 28, 2015, 02:04:16 pm
^^ not sure what all the code mean.
go to http://nxtexplorer.com/ (http://nxtexplorer.com/) and type in 7653714893178470041

That is the type of transaction you are proposing, it is already implemented...
Title: Re: List of feature request for Nxt and NRS
Post by: Sebastien256 on July 28, 2015, 02:07:43 pm
^^ not sure what all the code mean.
go to http://nxtexplorer.com/ (http://nxtexplorer.com/) and type in 7653714893178470041

That is the type of transaction you are proposing, it is already implemented...

Not sure about this. You can send a message to all shareholder without sending dividends? And you can distribute any asset you hold to all other asset shareholder in equal proportion?
Title: Re: List of feature request for Nxt and NRS
Post by: Brangdon on July 28, 2015, 08:56:26 pm
Client UI: better means of handling multiple accounts.

Historically Nxt has strongly encouraged account re-use. However, as I understand it, account re-use is more or less incompatible with privacy (because it makes block-chain analysis too easy). In particular, the forthcoming shuffle feature will require all the output accounts to be brand new. If I get paid weekly, and I shuffle a portion of what I earn, then I could be creating around 50 new accounts a year, each year. Managing this in the current UI would be impractical. Even if that example is too extreme, I think if Nxt wants to position itself as supporting privacy, it should look to managing scores of accounts.
Title: Re: List of feature request for Nxt and NRS
Post by: NxtSwe on August 02, 2015, 07:09:35 am
Hi,

I have a feature request for a reeeaaaalllly small feature.
In the "Lease your balance" - dialog, how about having a "maximum period" button next to the Period textbox to automatically have it set to 32767, which is the maximum allowed period. I always forget what number it is when I want to lease, and I end up typing 33000 to have an error message saying it cannot be more than 32767, so I enter that instead.
I just figured it would be a nice thing from a usability perspective.
Title: Re: List of feature request for Nxt and NRS
Post by: Sabertooth on August 02, 2015, 07:18:55 am
This is something that is not important currently but maybe in the future private/encrypted marketplace listings.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on August 02, 2015, 09:01:39 am
Hi,

I have a feature request for a reeeaaaalllly small feature.
In the "Lease your balance" - dialog, how about having a "maximum period" button next to the Period textbox to automatically have it set to 32767, which is the maximum allowed period. I always forget what number it is when I want to lease, and I end up typing 33000 to have an error message saying it cannot be more than 32767, so I enter that instead.
I just figured it would be a nice thing from a usability perspective.

Thanks, this is second time that such feature is requested. I have updated OP with your link instead as you also give a description why the feature is needed.
-------------

On another subject, I have update the topic title to be more descriptive.

And thank to whose participating on giving away their good ideas!
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: coretechs on August 03, 2015, 12:29:28 pm
Tx type / Long term "bonded leases"

A long term account lease transaction where the tx fee includes a bond proportional to the length of the lease.  If the effective balance of the account goes below a threshold the lease is broken and the bond is paid out to forgers as additional fees over a number of blocks.  This may be useful for TF, e.g. if a forger skips their turn they lose their bond, similar to Tendermint/Ethereum PoS proposals.  I believe it should be possible using phased transactions but I don't know what kind of risks it would introduce.




Title: Re: List of feature request for Nxt and NRS
Post by: NxtSwe on August 03, 2015, 01:24:39 pm
Hi,

I have a feature request for a reeeaaaalllly small feature.
In the "Lease your balance" - dialog, how about having a "maximum period" button next to the Period textbox to automatically have it set to 32767, which is the maximum allowed period. I always forget what number it is when I want to lease, and I end up typing 33000 to have an error message saying it cannot be more than 32767, so I enter that instead.
I just figured it would be a nice thing from a usability perspective.
The devs are working fast, https://twitter.com/nxtcommit/status/627919359688736768 :)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: kwilliams on August 06, 2015, 04:55:10 pm
Feature Request: Lending System

The main goal is to facilitate origination and payment of NXT loans. As a borrower I should be able to go to the “Lending System” tab and issue a “Loan” with following parameters:

Notes:

Such system (if properly implemented) could:
a)   Facilitate NXT corporations (aka asset issuers)  in issuing and managing their loans
b)   Create a secondary market for loan instruments (bonds)
c)   Improve the visibility of good and bad borrowers and become a basis for building trust (ala credit rating) for NXT bond issuers.

In addition there could be the ability to assign collateral to bonds (at time of issuance) for example an X amount of asset or currency per bond. The collateral would be automatically transferred to bond holders in case of bond defaults. This way a corporation could raise capital posting it’s shares (or other instruments like aliases, etc) as collateral thus limiting the risk for bond holders.

Due to its similarity with assets, bonds could be implemented as another asset type
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: dude on August 10, 2015, 01:30:26 pm
NRS core feature request: Hierarchical Deterministic (HD) wallet

One password, multiple addresses.

Improves privacy and usability.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Jimmy2011 on August 10, 2015, 03:06:32 pm

I request for a feature: direct trade/exchange between MSCoin_1 and MSCoin_2, or between Asset_1 and Asset_2.


Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on August 10, 2015, 07:18:35 pm
Thanks you for the feature request submissions. The big list is growing.  ;D
https://nxtforum.org/general/list-of-feature-request-for-nrs/
Keep the ideas comming!  :D
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: grewalsatinder on August 10, 2015, 09:19:05 pm
Hi Sebastien,

Can you please update the thread link for Hardware related features?
Quote
Hardware related feature request:
D001. 2015-06-19. All in one NXT-SuperNet-FreeMarket-MeshNet Raspberry Pi Device.

I started with 'All in one' thread. Then it evolved to 'SuperMesh / SpaceMesh' being partner of SuprNET. Here's the official thread:
https://nxtforum.org/index.php?topic=9491.0

Cheers,
Satinder
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: jones on August 11, 2015, 03:09:07 am
I would like to extend the HD wallet idea with disposable addresses for one time payments and shuffled coins

https://nxtforum.org/general-discussion/price-speculation/msg191075/#msg191075
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Brangdon on August 11, 2015, 07:30:30 pm
NRS core feature request: Hierarchical Deterministic (HD) wallet

One password, multiple addresses.

Improves privacy and usability.
This shouldn't need to be a core feature; it could be client-only.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: NxtSwe on August 14, 2015, 02:30:02 pm
The ability to initiate forging even though blockchain is not downloaded would be nice.
I understand that NRS cannot forge until it has the full blockchain, but it could accept the password and display a message like: "forging will start once the blockchain is downloaded".
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on August 15, 2015, 12:48:20 pm
Release 1.5.15

...

Full offline transaction signing support.

...
Display warning when trying to issue an asset or currency with less than 2
or more than 6 decimals.

Display total value of currencies owned on dashboard. Set default leasing
period to the maximum allowed (32767) in the UI. Other UI improvements.


Good, these gui requests has been taken into account in the lastest 1.5.15 release. Thanks you!

Released in NRS 1.5.15. (https://nxtforum.org/nrs-releases/nrs-v1-5-15/msg191323/#msg191323) B010. 2015-06-19. Display total MS currency value in NXT. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg185110/#msg185110)
Released in NRS 1.5.15. (https://nxtforum.org/nrs-releases/nrs-v1-5-15/msg191323/#msg191323) B005. 2015-06-15. Enable "anonymous" offline transactions. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg184167/#msg184167)
Released in NRS 1.5.15. (https://nxtforum.org/nrs-releases/nrs-v1-5-15/msg191323/#msg191323) B006. 2015-06-15. Make issuing an asset or MS coin with less than 2 or more than 6 decimals hard to do. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg184244/#msg184244)
Released in NRS 1.5.15. (https://nxtforum.org/nrs-releases/nrs-v1-5-15/msg191323/#msg191323) B002. 2015-06-13. A button/something to set leasing duration to the max possible value in the leasing dialog. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg190358/#msg190358)

Please do not hesitate to post more feature requests. I'm sure the devs are reading this topic from time to time and it may happen that they take your request into account.

PS. If you note anything incorrect, please let me know.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on August 17, 2015, 02:44:46 pm
GUI request,

One click NRS update from the client.

I would love that  :D

https://nxtforum.org/nxt-helpdesk/nxt-update-procedure-very-confusing/
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: futurist on August 18, 2015, 12:22:13 am
https://nxtforum.org/general/list-of-feature-request-for-nrs/msg185110/#msg185110

Thanks to whoever implemented this.  :)
This thread was a great idea.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: KarlKarlsson on August 18, 2015, 10:15:46 am
Nice thread, will hopefully help to improve client quality a lot  :)

Has anyone already mentioned graphs for the asset exchange? Like the graph showing the orderbooks on both sides (see bter for example - https://bter.com/trade/btc_cny (https://bter.com/trade/btc_cny), below orderbook) or the latest X trades. Or is this unnecessary due to the launch of InstantDEX?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on August 20, 2015, 03:49:33 am
Nice thread, will hopefully help to improve client quality a lot  :)

Has anyone already mentioned graphs for the asset exchange? Like the graph showing the orderbooks on both sides (see bter for example - https://bter.com/trade/btc_cny (https://bter.com/trade/btc_cny), below orderbook) or the latest X trades. Or is this unnecessary due to the launch of InstantDEX?

Yes, these thing should be made as plugin.
However, Jones made something very nice, take a look at:
http://jnxt.org/jayex/?17554243582654188572
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: jl777 on August 26, 2015, 01:11:48 am

I request for a feature: direct trade/exchange between MSCoin_1 and MSCoin_2, or between Asset_1 and Asset_2.
I still need to test mscoin support, but InstantDEX will allow this. also it will be possible to get pricing of more decimals than the asset/mscoin has

James

####
just pushed a version that enables MScoin transfers
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: PICISI.com on August 29, 2015, 09:29:37 pm
For the NXT Monetary System when creating a currency, provide an option to have publicly identified unique serial numbers attached to each CC unit that remains with that CC from birth to death.  In this way if it is identified as stolen potential buyers can decide make a purchase decision with that in mind.

At PICISI we believe a unique serial number would enable us to instantly and discriminately target specific units as unacceptable, there would be no collateral damage, or widespread harm to other currency units.  In fact, an argument could be made that as currencies are identified as stolen the value of the remaining units should rise at least in proportion to the reduction of value for the compromised units.

That feature would allow us to at least avoid buying merchandise we believe is stolen, especially if it was stolen from us.




 
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on September 02, 2015, 02:48:54 am
For the NXT Monetary System when creating a currency, provide an option to have publicly identified unique serial numbers attached to each CC unit that remains with that CC from birth to death.  In this way if it is identified as stolen potential buyers can decide make a purchase decision with that in mind.

At PICISI we believe a unique serial number would enable us to instantly and discriminately target specific units as unacceptable, there would be no collateral damage, or widespread harm to other currency units.  In fact, an argument could be made that as currencies are identified as stolen the value of the remaining units should rise at least in proportion to the reduction of value for the compromised units.

That feature would allow us to at least avoid buying merchandise we believe is stolen, especially if it was stolen from us.

Thanks for the input. I think it is a good idea that this could be possible when issuing a MS currency.

Keep up new inputs to this topic nxter.  :)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: PICISI.com on September 03, 2015, 02:42:17 am
When placing my NXT MS currency sell order I used an expiration of 600000, which likely will be too long, is there any way to stop, change, or cancel an order?  If so how; if not, I would like to make a suggestion to enable buyer/seller to cancel a posted buy/sell listing at anytime.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on September 03, 2015, 03:49:11 am
When placing my NXT MS currency sell order I used an expiration of 600000, which likely will be too long, is there any way to stop, change, or cancel an order?  If so how; if not, I would like to make a suggestion to enable buyer/seller to cancel a posted buy/sell listing at anytime.

Yes you can cancel, you need to publish a new exchange offer of amount 0, if i'm not mistaken.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: PICISI.com on September 03, 2015, 06:46:36 am
When placing my NXT MS currency sell order I used an expiration of 600000, which likely will be too long, is there any way to stop, change, or cancel an order?  If so how; if not, I would like to make a suggestion to enable buyer/seller to cancel a posted buy/sell listing at anytime.

Yes you can cancel, you need to publish a new exchange offer of amount 0, if i'm not mistaken.

thanks, I'll give that a try on Sept 15, my target end date.

thanks again
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on September 08, 2015, 07:40:00 pm
Installer feature request:
Different shortcut icon for the Nxt wallet and Nxt Server.

When the shortcut are put on the taskbar (on windows) they cannot be differentiate visually from one another (unless we check the properties).
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Riker on September 08, 2015, 07:59:11 pm
Installer feature request:
Different shortcort icon for the Nxt wallet and Nxt Server.

When the shortcut are put on the taskbar (on windows) they cannot be differentiate visually from one another (unless we check the properties).

Currently we are using ./html/ui/favicon.ico for both shortcuts. If someone prepares better icons we can easily incorporate them into the next release.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: grewalsatinder on September 08, 2015, 09:17:06 pm
Installer feature request:
Different shortcort icon for the Nxt wallet and Nxt Server.

When the shortcut are put on the taskbar (on windows) they cannot be differentiate visually from one another (unless we check the properties).

Currently we are using ./html/ui/favicon.ico for both shortcuts. If someone prepares better icons we can easily incorporate them into the next release.

Point me to NXT's Presskit with logos. I'll try to make some decent windows/mac icons with hi res PNG files.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: grewalsatinder on September 08, 2015, 09:56:13 pm
Installer feature request:
Different shortcort icon for the Nxt wallet and Nxt Server.

When the shortcut are put on the taskbar (on windows) they cannot be differentiate visually from one another (unless we check the properties).

Currently we are using ./html/ui/favicon.ico for both shortcuts. If someone prepares better icons we can easily incorporate them into the next release.

Point me to NXT's Presskit with logos. I'll try to make some decent windows/mac icons with hi res PNG files.

Here are some windows icons with PNG files: https://drive.google.com/folderview?id=0B37pxDeQ4x1lRkZvRjVFTzJONXc
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: apenzl on September 08, 2015, 09:58:33 pm
Nxt Styleguide + files
https://copy.com/DFNKnLBgkiFPgqxX
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on September 08, 2015, 10:09:45 pm
Thanks for the mobilization on that simple feature request, nxters ;D

Anyone feel free to post what you would like. Nxt community is listening  :).

Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: EvilDave on September 08, 2015, 10:26:04 pm
Let's see how you get on with this one:

GUI request: Simplified NRS Wallet option.

I've been talking to a few potential projects that want to use an Nxt Asset or MS Currency as their 'main' currency.
Think of an AirMiles type token system, or local currencies like the Drachmae project.
One problem with using Nxt (from these projects point of view) is that the users do not need (or want to have) full Nxt functionality in their wallets.
All that they will need are enough tools to handle one asset or currency, with those tools immediately available for use.

Would it be possible to produce a simplified NRS client with this sort of restricted focus, only showing by default Nxt and one other Asset/currency ?
Obviously, outside projects could create their own methods of handling their Assets/currencies, but it would be good to have this functionality built in, allowing projects to distribute an NRS client that is tailored specifically to that project.

Preferably, I'd like to be able to set this behaviour from the config file, so that the NRS can be set to focus on any Asset/currency, and we won't have to worry about distributing different NRS versions for each seperate project..
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on September 08, 2015, 10:28:40 pm
@EvilDave

That one is a good one. I like it very much. +1
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: CryptKeeper on September 09, 2015, 06:39:35 am
Let's see how you get on with this one:

GUI request: Simplified NRS Wallet option.

I've been talking to a few potential projects that want to use an Nxt Asset or MS Currency as their 'main' currency.
Think of an AirMiles type token system, or local currencies like the Drachmae project.
One problem with using Nxt (from these projects point of view) is that the users do not need (or want to have) full Nxt functionality in their wallets.
All that they will need are enough tools to handle one asset or currency, with those tools immediately available for use.

Would it be possible to produce a simplified NRS client with this sort of restricted focus, only showing by default Nxt and one other Asset/currency ?
Obviously, outside projects could create their own methods of handling their Assets/currencies, but it would be good to have this functionality built in, allowing projects to distribute an NRS client that is tailored specifically to that project.

Preferably, I'd like to be able to set this behaviour from the config file, so that the NRS can be set to focus on any Asset/currency, and we won't have to worry about distributing different NRS versions for each seperate project..

IMHO putting this functionality into the NRS is not the right approach for this. For a consumer-friendly wallet we have to analyse the whole process downloading/installing/using of the wallet. It would be better to implement such functions in a light wallet without java installation and without downloading the blockchain.
I'm not sure if we have to implement something like SPV (https://en.bitcoin.it/wiki/Thin_Client_Security (https://en.bitcoin.it/wiki/Thin_Client_Security)) for that.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: EvilDave on September 09, 2015, 01:20:58 pm
Either approach would work for me, the important point is to be able to offer a radically simplified client (either standalone or web-based) for use by other projects.
I know it's been said before, but it bears repeating: complexity is not going to get us mainstream adoption, we need to be able to offer a simplified user experience.

Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: oldnbold on September 11, 2015, 10:11:09 am
Either for GUI or plug-in (not sure which):

Asset turnover ratio (not to be confused with http://www.investopedia.com/terms/a/assetturnover.asp)

As applied in respect of the AE, this would show the extent of trading in the market for each asset relative to the total NXT value of the asset issued, so assets' market liquidity could be more easily compared amongst themselves and over successive periods.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: KarlKarlsson on September 11, 2015, 10:48:20 am

Either for GUI or plug-in (not sure which):

Asset turnover ratio (not to be confused with http://www.investopedia.com/terms/a/assetturnover.asp)

As applied in respect of the AE, this would show the extent of trading in the market for each asset relative to the total NXT value of the asset issued, so assets' market liquidity could be more easily compared amongst themselves and over successive periods.
Hi Robert

Will write this down for implementation in NXTinfo.

Thanks,
Karl
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on September 11, 2015, 06:33:20 pm
Released feature request:
Released in NRS 1.6.0e. (https://nxtforum.org/nrs-releases/nrs-v1-6-0e/msg193687/#msg193687) B001. 2015-06-07. Add forging block fee reward in the transaction dashboard. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg182424/#msg182424)
Released in NRS 1.6.0e. (https://nxtforum.org/nrs-releases/nrs-v1-6-0e/msg193687/#msg193687) B003. 2015-06-13. Core dividend feature notification. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg183746/#msg183746)

Ok, I updated the released features which are made available with the new account ledger. Please, post what you would like too, but follow the rules.

I thank everyone for their participation.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: oldnbold on September 12, 2015, 08:37:02 am
Hi Robert

Will write this down for implementation in NXTinfo.

Thanks,
Karl

Thanks Karl - look forward to seeing it in operation  :)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on October 01, 2015, 09:42:16 pm
It been almost three weeks without any new suggestions.
Is there a good nxter with a good feature request in mind?

Please check for duplicate there before submitting:
https://nxtforum.org/general/list-of-feature-request-for-nrs/

Thank you for your participation.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: artik123 on October 01, 2015, 10:02:20 pm
How about two more types of Monetary System coins:

1. Forgeable - Proof of Stake coins.

2. Hybrid - Proof of Work that later switches to Proof of Stake.

Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: NxtSwe on October 05, 2015, 06:02:48 pm
Here's a really minor request that only a few will even notice:
Have the categories sorted alphabetically on the http://localhost:7876/test - page.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on October 16, 2015, 10:06:50 am
I'd like to be able to colorize contacts to differ them at AE and Dashboard by color label.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on October 16, 2015, 10:13:59 am
I'd like to be able to colorize contacts to differ them at AE and Dashboard by color label.

Thanks for the suggestion, but I know well the gui, but cannot understand or figure out what you want exactly. Could you elaborate a bit more before I add the request in the list?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: shmoula on October 16, 2015, 10:56:06 am
History of dividends paid (paid with core dividend feature) for every asset would be nice.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: shmoula on October 16, 2015, 10:57:55 am
delete this pls
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: artik123 on October 16, 2015, 11:47:29 am
How about two more types of Monetary System coins:

1. Forgeable - Proof of Stake coins.

2. Hybrid - Proof of Work that later switches to Proof of Stake.

Bump.

Can't we develop proof of stake coins on top of Nxt proof of stake?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Brangdon on October 16, 2015, 07:56:51 pm
An easier way to manage hallmarks.

Currently we have around public 260 nodes, but only 70 or so are hallmarked. I think this may be because setting up hallmarks is quite hard. It involves editing configuration files and generating hashes via the admin interface. If it was easier, more of the people who run public nodes might hallmark them. More hallmarked nodes would make it more expensive to conduct Sybil attacks.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Jean-Luc on October 17, 2015, 01:03:29 am
Have the categories sorted alphabetically on the http://localhost:7876/test - page.
OK, done in 1.7.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Jean-Luc on October 17, 2015, 01:11:22 am
A026. 2015-08-29. Unique serial numbers attached to each cryptocurrency unit (option for MS). (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg192740/#msg192740)
This one is not possible.

Quote
B008. 2015-06-16. Unsigned Transaction Bytes + QRCode if Secret Phrase not specified. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg184432/#msg184432)
Offline transaction signing is fully supported in most recent 1.5 versions, including offline encryption of messages, I see nothing more to be done about that.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: futurist on October 17, 2015, 01:16:38 am
How about two more types of Monetary System coins:

1. Forgeable - Proof of Stake coins.

2. Hybrid - Proof of Work that later switches to Proof of Stake.

3. MS algorithm that contributes to projects like seti@home, boinc, etc
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: futurist on October 17, 2015, 03:21:38 am
Would be nice to be able to send encrypted message to all asset holders. I know this was brought up before, but i don't think being encrypted was mentioned.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: danisapfirov on October 17, 2015, 06:00:05 am
Need Weighted Average Cost when selling assets.

First Let me give you the formula:

Weighted Average Cost = Sum(AssetQuantityPurchased(I)*AssetPricePurchased(I)/Sum(AssetQuantityPurchased(I)
I=1 to number of purchases

When you click on Asset Trading History and button You, there is a list of all purchases and and sales for given asset.

WAC gives the price based of all purchases and gives information if you sell the asset will you have profit or loss based on this.
This info is not available at present and there is a need to calculate WAC every time when I sell an asset, so I can see profit/loss data based on this.

Would like to see WAC on trading history when "You" filter is active. It would be nice also when someone sells to see exactly how much profit/loss will have after the transaction takes place.

http://1drv.ms/1jKSwPr

Also, please update Bulgarian language as I made few fixes.

Thanks.

Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on October 17, 2015, 06:08:18 am
I'd like to be able to colorize contacts to differ them at AE and Dashboard by color label.

Thanks for the suggestion, but I know well the gui, but cannot understand or figure out what you want exactly. Could you elaborate a bit more before I add the request in the list?

Gmail-like lables:

Contacts: (http://i.imgur.com/ysnq900.png)

e.g. transactions list: (http://i.imgur.com/nLt17eA.png)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on October 17, 2015, 06:20:06 am
A026. 2015-08-29. Unique serial numbers attached to each cryptocurrency unit (option for MS). (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg192740/#msg192740)
This one is not possible.

Quote
B008. 2015-06-16. Unsigned Transaction Bytes + QRCode if Secret Phrase not specified. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg184432/#msg184432)
Offline transaction signing is fully supported in most recent 1.5 versions, including offline encryption of messages, I see nothing more to be done about that.


I suppose it's Jay-like behaviour to pair with NXTVault
+1
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: shmoula on October 17, 2015, 08:44:05 am
...

History of dividends paid (paid with core dividend feature) for every asset would be nice.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on October 17, 2015, 08:55:24 am
...

History of dividends paid (paid with core dividend feature) for every asset would be nice.

Yes, I add it label B021. TY
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: shmoula on October 17, 2015, 12:11:47 pm
Awesome, thanks!

Yes, I add it label B021. TY
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Riker on October 17, 2015, 02:05:56 pm
How about two more types of Monetary System coins:

1. Forgeable - Proof of Stake coins.

2. Hybrid - Proof of Work that later switches to Proof of Stake.

3. MS algorithm that contributes to projects like seti@home, boinc, etc

Regarding (1) and (2), MS currencies are not used to secure the network, this is done by the NXT Proof Of Stake system itself, therefore Proof Of Stake is irrelevant for MS and POW is only used for generating new currency units not for forging new blocks which is done by NXT nodes.

(3) If there is a concrete use case for a POW algorithm which benefits humanity (i.e. seti@home, boinc or a similar project), written in Java or better yet written in native code in a way which allows invocation from Java code and has permissive open source license then we can certainly consider supporting it as a new MS algorithm.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: artik123 on October 17, 2015, 02:14:11 pm
How about two more types of Monetary System coins:

1. Forgeable - Proof of Stake coins.

2. Hybrid - Proof of Work that later switches to Proof of Stake.

3. MS algorithm that contributes to projects like seti@home, boinc, etc

Regarding (1) and (2), MS currencies are not used to secure the network, this is done by the NXT Proof Of Stake system itself, therefore Proof Of Stake is irrelevant for MS and POW is only used for generating new currency units not for forging new blocks which is done by NXT nodes.

(3) If there is a concrete use case for a POW algorithm which benefits humanity (i.e. seti@home, boinc or a similar project), written in Java or better yet written in native code in a way which allows invocation from Java code and has permissive open source license then we can certainly consider supporting it as a new MS algorithm.

Hi lyaffe,

I'm not talking about securing the network, I'm talking about efficiency.

Take a look at Alt Announcements on bitcointalk. Most new Alts are PoS or Hybrid.

If MS would have 100 successful coins, we would be one of the most unefficient cryptos out-there, which would defeat the whole idea of PoS.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Riker on October 17, 2015, 02:20:31 pm
If MS would have 100 successful coins, we would be one of the most unefficient cryptos out-there, which would defeat the whole idea of PoS.

I'm not following you, in what sense would it be inefficient to run 100 successful coins on top of NXT ?
Do you mean NXT would be inefficient since it will be flooded by transactions ?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: artik123 on October 17, 2015, 02:26:44 pm
If MS would have 100 successful coins, we would be one of the most unefficient cryptos out-there, which would defeat the whole idea of PoS.

I'm not following you, in what sense would it be inefficient to run 100 successful coins on top of NXT ?
Do you mean NXT would be inefficient since it will be flooded by transactions ?

Correct me if I'm wrong, but wouldn't MS miners need to utilize their CPU/GPU to generate hashes in order to solve blocks?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Riker on October 17, 2015, 08:25:16 pm
If MS would have 100 successful coins, we would be one of the most unefficient cryptos out-there, which would defeat the whole idea of PoS.

I'm not following you, in what sense would it be inefficient to run 100 successful coins on top of NXT ?
Do you mean NXT would be inefficient since it will be flooded by transactions ?

Correct me if I'm wrong, but wouldn't MS miners need to utilize their CPU/GPU to generate hashes in order to solve blocks?

In case the currency is mintable which is optional, solving a hash will mint additional currency units according to the currency specifications. Nothing to do with solving a block.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: artik123 on October 17, 2015, 08:46:08 pm
If MS would have 100 successful coins, we would be one of the most unefficient cryptos out-there, which would defeat the whole idea of PoS.

I'm not following you, in what sense would it be inefficient to run 100 successful coins on top of NXT ?
Do you mean NXT would be inefficient since it will be flooded by transactions ?

Correct me if I'm wrong, but wouldn't MS miners need to utilize their CPU/GPU to generate hashes in order to solve blocks?

In case the currency is mintable which is optional, solving a hash will mint additional currency units according to the currency specifications. Nothing to do with solving a block.

That's a better description...

My point was, that mintable coins are inefficient.

100 successful mintable coins and you would have a huge waste of electricity, just like any other proof of work coins.

Nxt could not be proud anymore as being a green cryptocurrency.


Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: NxtSwe on October 17, 2015, 08:53:29 pm
Would be nice to be able to send encrypted message to all asset holders. I know this was brought up before, but i don't think being encrypted was mentioned.

Interesting suggestion, however it would require one encrypted message for each asset holder.
If there's 500 asset owner, 500 encrypted messages are required.

I guess a plugin could be created to handle this as well, creating 500 transactions in my sample above, it should be fairly easy to create.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sabertooth on October 17, 2015, 09:09:25 pm
Would be nice to be able to send encrypted message to all asset holders. I know this was brought up before, but i don't think being encrypted was mentioned.

Interesting suggestion, however it would require one encrypted message for each asset holder.
If there's 500 asset owner, 500 encrypted messages are required.

I guess a plugin could be created to handle this as well, creating 500 transactions in my sample above, it should be fairly easy to create.

Then why couldn't prunable messages be used where they are encrypted and concatenated from multiple messages if needed. It would be cheaper and take up less space on the blockchain. The client I am assuming would have to be changed to process such messages.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: martismartis on October 23, 2015, 08:55:36 am
Seems not requested, sorry if it was.

Is it possible to make voting due date and time, not due some block? I mean end of voting is XX:XX:XX hour XXXX.XX.XX date. Valid votes counting by vote transaction time, they must be before voting end time and date.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: yassin54 on October 23, 2015, 09:02:47 am
Seems not requested, sorry if it was.

Is it possible to make voting due date and time, not due some block? I mean end of voting is XX:XX:XX hour XXXX.XX.XX date. Valid votes counting by vote transaction time, they must be before voting end time and date.
even thought
It is possible? date and time is better than block  :)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: martismartis on October 23, 2015, 09:22:51 am
Seems not requested, sorry if it was.

Is it possible to make voting due date and time, not due some block? I mean end of voting is XX:XX:XX hour XXXX.XX.XX date. Valid votes counting by vote transaction time, they must be before voting end time and date.
even thought
It is possible? date and time is better than block  :)

I think it is possible, every transaction have their time and date. Let's wait for devs :)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: NxtSwe on October 23, 2015, 09:52:09 am
Seems not requested, sorry if it was.

Is it possible to make voting due date and time, not due some block? I mean end of voting is XX:XX:XX hour XXXX.XX.XX date. Valid votes counting by vote transaction time, they must be before voting end time and date.
even thought
It is possible? date and time is better than block  :)

I think it is possible, every transaction have their time and date. Let's wait for devs :)

Good idea!

I don't think you can use the transaction timestamp for such a feature.
In theory, I believe you could wait 10 hours after the voting deadline (must be less than 1440 blocks), create a transaction with timestamp set to 15 hours earlier, so it seems it was created before the deadline. Broadcast it, and have count as a valid vote.
It would be much harder to do such a thing if both block timestamp and transaction timestamp must be earlier than the set date.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: martismartis on October 23, 2015, 10:01:30 am
Seems not requested, sorry if it was.

Is it possible to make voting due date and time, not due some block? I mean end of voting is XX:XX:XX hour XXXX.XX.XX date. Valid votes counting by vote transaction time, they must be before voting end time and date.
even thought
It is possible? date and time is better than block  :)

I think it is possible, every transaction have their time and date. Let's wait for devs :)

Good idea!

I don't think you can use the transaction timestamp for such a feature.
In theory, I believe you could wait 10 hours after the voting deadline (must be less than 1440 blocks), create a transaction with timestamp set to 15 hours earlier, so it seems it was created before the deadline. Broadcast it, and have count as a valid vote.
It would be much harder to do such a thing if both block timestamp and transaction timestamp must be earlier than the set date.

Or next block after deadline fixes votes with correct timestamp :) I mean vote ends with next block after deadline, it could be flag, that vote already ended and no new votes are accepted. Just brainstorming :)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: NxtSwe on October 23, 2015, 10:21:33 am
Seems not requested, sorry if it was.

Is it possible to make voting due date and time, not due some block? I mean end of voting is XX:XX:XX hour XXXX.XX.XX date. Valid votes counting by vote transaction time, they must be before voting end time and date.
even thought
It is possible? date and time is better than block  :)

I think it is possible, every transaction have their time and date. Let's wait for devs :)

Good idea!

I don't think you can use the transaction timestamp for such a feature.
In theory, I believe you could wait 10 hours after the voting deadline (must be less than 1440 blocks), create a transaction with timestamp set to 15 hours earlier, so it seems it was created before the deadline. Broadcast it, and have count as a valid vote.
It would be much harder to do such a thing if both block timestamp and transaction timestamp must be earlier than the set date.

Or next block after deadline fixes votes with correct timestamp :) I mean vote ends with next block after deadline, it could be flag, that vote already ended and no new votes are accepted. Just brainstorming :)

This would be a problem if you happen to get a 30 minute block, but since there's a plan to fix that, your idea could work.
And it could not only work for voting, but for phasing transactions and why not MS currency foundraising as well? :)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: SonsofCrypto on October 23, 2015, 04:47:30 pm
Feature Request: Lending System

The main goal is to facilitate origination and payment of NXT loans. As a borrower I should be able to go to the “Lending System” tab and issue a “Loan” with following parameters:
  • Total loan size. For example 100000 NXT
  • Loan repayment (aka maturity) date. For example 30000 blocks from now
  • Individual bond size. For example 200 NXT. The number of bonds is [loan size] / [bond size], in this case it would be 100000/200 = 500
  • Interest payment schedule (aka “coupons”). For example 1 NXT per bond, payable every 10000 blocks (until maturity)

Notes:
  • Once the loan is created, the bonds become tradeable much like other assets. They can be bought sold, transferred, etc.
  • Bond issuer receives a notification message when interest (or principal) payments are due and can make payments to bondholders much like one would do with dividends for an asset.
  • When the final (principal) payment is made, the bond becomes “redeemed” and can be removed from the block chain history much like transient messages.
  • If one (or more) payments are missed, the bond becomes “in arears” and is displayed with different color in the UI. When enough payments are missed (say for 20K blocks), the bond becomes “in default”

Such system (if properly implemented) could:
a)   Facilitate NXT corporations (aka asset issuers)  in issuing and managing their loans
b)   Create a secondary market for loan instruments (bonds)
c)   Improve the visibility of good and bad borrowers and become a basis for building trust (ala credit rating) for NXT bond issuers.

In addition there could be the ability to assign collateral to bonds (at time of issuance) for example an X amount of asset or currency per bond. The collateral would be automatically transferred to bond holders in case of bond defaults. This way a corporation could raise capital posting it’s shares (or other instruments like aliases, etc) as collateral thus limiting the risk for bond holders.

Due to its similarity with assets, bonds could be implemented as another asset type

^this

I like the idea of being able to put up collateral albeit, NXT, NXT Assets, or other coins...all via the NXT infrastructure.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Seccour on October 28, 2015, 10:45:44 am
Small idea ( i don't know if it has already been said here ) :

Allow AE issuer to create new pairs for their assets. Now, all the asset are paired with NXT like that : NXT / assets. But it would be cool if an asset issuer could create new pair like xxx / assets where xxx can be an another asset or a MS currency ( this should be a pay feature to avoid spam, like you need to pay the price of an asset to get a new trading pair of your choice ).

This would be cool so we can get USD / BTC pair inside the AE with CoinoUSD and superBTC and other things.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on October 28, 2015, 12:15:58 pm
Small idea ( i don't know if it has already been said here ) :

Allow AE issuer to create new pairs for their assets. Now, all the asset are paired with NXT like that : NXT / assets. But it would be cool if an asset issuer could create new pair like xxx / assets where xxx can be an another asset or a MS currency ( this should be a pay feature to avoid spam, like you need to pay the price of an asset to get a new trading pair of your choice ).

This would be cool so we can get USD / BTC pair inside the AE with CoinoUSD and superBTC and other things.

Feature request to be done as a Nxt plugin or by a third party:
A024. 2015-08-10. Need to be done outside the core. (https://nxtforum.org/general-discussion/price-speculation/msg196327/#msg196327) Direct trade/exchange between MSCoin_1 and MSCoin_2, or between Asset_1 and Asset_2. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg191048/#msg191048)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Seccour on October 28, 2015, 02:26:14 pm
Small idea ( i don't know if it has already been said here ) :

Allow AE issuer to create new pairs for their assets. Now, all the asset are paired with NXT like that : NXT / assets. But it would be cool if an asset issuer could create new pair like xxx / assets where xxx can be an another asset or a MS currency ( this should be a pay feature to avoid spam, like you need to pay the price of an asset to get a new trading pair of your choice ).

This would be cool so we can get USD / BTC pair inside the AE with CoinoUSD and superBTC and other things.

Feature request to be done as a Nxt plugin or by a third party:
A024. 2015-08-10. Need to be done outside the core. (https://nxtforum.org/general-discussion/price-speculation/msg196327/#msg196327) Direct trade/exchange between MSCoin_1 and MSCoin_2, or between Asset_1 and Asset_2. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg191048/#msg191048)

Do you know why it will not be done in the core ? I don't see any explanation...
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on October 28, 2015, 03:58:44 pm
Small idea ( i don't know if it has already been said here ) :

Allow AE issuer to create new pairs for their assets. Now, all the asset are paired with NXT like that : NXT / assets. But it would be cool if an asset issuer could create new pair like xxx / assets where xxx can be an another asset or a MS currency ( this should be a pay feature to avoid spam, like you need to pay the price of an asset to get a new trading pair of your choice ).

This would be cool so we can get USD / BTC pair inside the AE with CoinoUSD and superBTC and other things.

Feature request to be done as a Nxt plugin or by a third party:
A024. 2015-08-10. Need to be done outside the core. (https://nxtforum.org/general-discussion/price-speculation/msg196327/#msg196327) Direct trade/exchange between MSCoin_1 and MSCoin_2, or between Asset_1 and Asset_2. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg191048/#msg191048)

Do you know why it will not be done in the core ? I don't see any explanation...

I don't.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: blackyblack1 on October 28, 2015, 07:40:33 pm
Small idea ( i don't know if it has already been said here ) :

Allow AE issuer to create new pairs for their assets. Now, all the asset are paired with NXT like that : NXT / assets. But it would be cool if an asset issuer could create new pair like xxx / assets where xxx can be an another asset or a MS currency ( this should be a pay feature to avoid spam, like you need to pay the price of an asset to get a new trading pair of your choice ).

This would be cool so we can get USD / BTC pair inside the AE with CoinoUSD and superBTC and other things.

Feature request to be done as a Nxt plugin or by a third party:
A024. 2015-08-10. Need to be done outside the core. (https://nxtforum.org/general-discussion/price-speculation/msg196327/#msg196327) Direct trade/exchange between MSCoin_1 and MSCoin_2, or between Asset_1 and Asset_2. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg191048/#msg191048)
Direct trading of assets and MS coins is already supported with 3rd party app. However direct trading is not so convinient as Asset Exchange.
I want to notice that asset-asset volumes on NXT AE would be very thin. This option is only valuable for crowdfunding projects.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: barbierir on November 01, 2015, 08:12:41 am
GUI feature: button to download the trade history as a .csv file
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: MrCluster87 on November 01, 2015, 08:48:26 am
A plug-in: https://nxtforum.org/nxt-plugins/telegram/

Telegram API: https://core.telegram.org/api

Protocol: https://core.telegram.org/mtproto
Title: Re: List of feature request for Nxt and NRS
Post by: doppelganger on November 08, 2015, 11:50:21 am
This feature would help us tremendously. Any chances it will be included?..

Got these ideas from a discussion we had on slack yesterday.

Swarm like messaging protocol.

Allows to send a transaction with zero fee that is not stored in the blockchain, instead it is kept in a FIFO queue whose length is adjustable.
Bigger nodes can set the FIFO queue of fee-less transactions to several gigabytes while the smaller ones will only have one of a few MB.

The idea is to be able to send a message to the network that is propagated to all other nodes just as if it was a transaction, it's just not stored in the blockchain.

Use cases:

- free encrypted chat
- other uses like sending NXT off-blockchain (teleport style)

Q: Why use transactions instead of some other data format?
A: Because all the wiring is there already and it could utilize the existing peer protocol + this opens up use cases where the initially (freely) send transactions can later be included in the blockchain, after for instance some co-signature.

Q: What about spam?
A: Well what about it really? Users would only listen to certain messages just as if they only listen for certain transactions.

Q: Anonymity?
A: If everyone sends to everyone else then you would never know who the real recipient was.

Q: Encryption?
A: Messages could use the existing public/private key encryption available already.
Title: Re: List of feature request for Nxt and NRS
Post by: remix on November 10, 2015, 02:31:00 pm
Got these ideas from a discussion we had on slack yesterday.

Swarm like messaging protocol.
Allows to send a transaction with zero fee that is not stored in the blockchain, instead it is kept in a FIFO queue whose length is adjustable.
Bigger nodes can set the FIFO queue of fee-less transactions to several gigabytes while the smaller ones will only have one of a few MB.

The idea is to be able to send a message to the network that is propagated to all other nodes just as if it was a transaction, it's just not stored in the blockchain.

I noticed it is possible to send messages for free. If referencedTransactionHash is set to a non-existent transaction, the transaction will never confirm, but it will be propagated to all nodes. The recipient will see it in unconfirmed transactions. About 100 NXT is reserved from the sending account, but will again be available after the transaction has expired. Maybe this could be considered spamming.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: blackyblack1 on November 12, 2015, 11:09:09 am
Blank transactions proposal.

I think the idea of blank transactions could be useful for NXT. The blank transaction is the transaction where only part of the fields is filled. For example Alice creates a transaction to send 10 NXT but recipient field is marked as blank. Alice signs such transaction and gives it to Bob. Now Bob can fill blank field at any time, sign with own secret phrase and broadcast to the network.

This feature can be even more useful if network fees are payed by Bob. In this case Alice could transfer assets without holding any NXT on the account.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on November 12, 2015, 11:49:11 am
Blank transactions proposal.

I think the idea of blank transactions could be useful for NXT. The blank transaction is the transaction where only part of the fields is filled. For example Alice creates a transaction to send 10 NXT but recipient field is marked as blank. Alice signs such transaction and gives it to Bob. Now Bob can fill blank field at any time, sign with own secret phrase and broadcast to the network.

This feature can be even more useful if network fees are payed by Bob. In this case Alice could transfer assets without holding any NXT on the account.

This is core or gui feature?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: blackyblack1 on November 12, 2015, 12:06:13 pm
Blank transactions proposal.

I think the idea of blank transactions could be useful for NXT. The blank transaction is the transaction where only part of the fields is filled. For example Alice creates a transaction to send 10 NXT but recipient field is marked as blank. Alice signs such transaction and gives it to Bob. Now Bob can fill blank field at any time, sign with own secret phrase and broadcast to the network.

This feature can be even more useful if network fees are payed by Bob. In this case Alice could transfer assets without holding any NXT on the account.

This is core or gui feature?
Core.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: allwelder on November 12, 2015, 02:23:38 pm
Can we delist some un-used features to make NXT much more lite?
So this will let users remember good/clear vision or features of NXT and make a good broadcast effect.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Ludom on November 12, 2015, 03:03:29 pm
Can we use MScoins or Assets to buy things on the Digital Good store?
I think to list a good with a price in defined number of assets or MScoin. It will be a huge feature for the use of MScoins/assets and Market Place.

Can we delist some un-used features to make NXT much more lite?
So this will let users remember good/clear vision or features of NXT and make a good broadcast effect.

We don't need to delist features, we need to propose a lite GUI or a GUI that can be simplify (you choose what you want to see). Some feature are not a lot used yet, but we never know if they will be use full later.
I think that the big thing of Nxt is the combination of the features. Not features alone.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: OutSL on November 12, 2015, 04:55:34 pm
Thank you for your great work, I do not dare ask for more but my suggestion seems useful because it will reduce the workload either at the clients or the API.

Title : Advanced Reporting System for external use.
Category : Core / GUI for settings (optional).

Description :
Currently, all clients (websites or wallets) must operate a lot of API calls to get the data they need to work ... without that the clients does not know what is going on the server and need to repeat the calls again and again into cron jobs or other ...

I think it will be easier if the server can send a rich data notifications to an URL allowing by that the clients to synchronize their databases with the blockchain just by listening ...

over 50% of this feature already exists in the core and the GUI (the notifications in the top bar) you have just to add what is requiered to operate the POSTs in conjunction with the parameters registered by the server user in nxt.properties

for example (nxt.properties):
# Add a notification URL (where my script peeled and work data)
someDomaine.web / myPHP.php

# Add accounts to monitor
accountRS, accountRS1, accountRS2 ... n

# Add assets to be monitored
assetId, assetID1, assetID2 n ...

if (an event occurs in the monitored accounts or assets ){ a notification with event details is sent to the URL ... (transaction, message, buying / selling ...)};

Practical case :
Imagine i have a website with many members and I want to make deposits with NXT available but I do not want to create one wallet account/user account and store their data (passphrases) in my database ...
for this, creates three wallet  accounts; 1 (accountRS) for the verification, one for the deposits (accountRS1) and 1 for withdrawals (main ... withdrawal under supervision)

on my website, my member will be invited to register his NXT address and prove that he is the owner of that wallet account ... with a single-use code will be generated and displayed to him ... he must use his wallet and send the code as verification message to my verification address.

When done, the server will send a notification to my site (someDomaine.web / myPHP.php) informing him that a new message has arrived to the verification address sent from the member's wallet account, after what my site send a call to the API to decrypt it, see if it that matches the data (verification code) in my database and changes the status of the member according to ...

if my member deposits an amount later in the deposit account (accountRS1), the server sends a notification to my script that automatically updates the member's amount according to the number of confirmations and this without any API call...

I hope you understand the idea and are going to implement it ... this will greatly facilitate things in the clients development like mobile apps... and it's more economic in terms of resources usages and may improve performance on all that is communicating with the API ...
(listening or bombarding the API with requests? what is the best?)

thank you again ang good continuation :) (sorry for my poor english)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: NxtSwe on November 12, 2015, 06:02:34 pm
OutSL, I think what you are describing already exist in eventRegister / eventWait API's.

First, call eventRegister with Transaction.ADDED_CONFIRMED_TRANSACTIONS as argument, and then call eventWait and it will return any new confirmed transactions.
However you'll have to filter out the transactions that you actually need in your own code.

More info here: https://wiki.nxtcrypto.org/wiki/The_Nxt_API#Event_Register
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: OutSL on November 12, 2015, 07:02:20 pm
OutSL, I think what you are describing already exist in eventRegister / eventWait API's.

First, call eventRegister with Transaction.ADDED_CONFIRMED_TRANSACTIONS as argument, and then call eventWait and it will return any new confirmed transactions.
However you'll have to filter out the transactions that you actually need in your own code.

More info here: https://wiki.nxtcrypto.org/wiki/The_Nxt_API#Event_Register

Thanks for this info :) but this need to call the API the thing that i try to avoid... the notifications system in my vision have to do that without any call from the client or with the minimal requiered 1st time for the new registrations or the new linked website account to the wallet accounts... next time , any event that happend in the monitored account do that the server send a new notification to the registred URL... the member's accountRS is stored in my database... when a notification is recived the 1st thing that my script will do is searching this accountRS in my database and in function of the event it's update the website database... no calls after the 1st registration or will be just for more verifications but always the minimal...

NxtSwe: your help will be the welcome if you want to work in an implementation of NXT in opensimulator (c#)! your NxtLib is perfect for that and for a skilled person like you :) you can do that in 3 days clock in hand... ;D
your work will bring ~100k new users to the NXT network :) opensim users...

in the virtual worlds we use an unknown scripting language called "Linden Script Language" aka LSL... with this language we can animate the 3D items or building a client for the NRS :) but they are a lot of limitations that we have to deal with for a correct use that include the number of the requests that a script can send and more... i will write a dedicated post around opensimulator and what we can do with it... a 3D wall street like for the monetary system and the asset exchange displaying real-time data for eg; or better! a virtual world dedicated to the NXT and it's community :)

[White Rabbit]
https://www.youtube.com/watch?v=49vj9HEI2OY
https://www.youtube.com/watch?v=_CqbqY2p6gQ
http://wiki.secondlife.com/wiki/Category:LSL_HTTP

thank you and @+
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: blackyblack1 on November 14, 2015, 11:48:25 am
I propose to have a set of hashes for phased transactions approved by hash. So N transactions should be exisiting on the blockchain to approve phased transaction.

Oops. It is already implemented this way.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: NxtSwe on November 16, 2015, 08:14:05 am
OutSL, I think what you are describing already exist in eventRegister / eventWait API's.

First, call eventRegister with Transaction.ADDED_CONFIRMED_TRANSACTIONS as argument, and then call eventWait and it will return any new confirmed transactions.
However you'll have to filter out the transactions that you actually need in your own code.

More info here: https://wiki.nxtcrypto.org/wiki/The_Nxt_API#Event_Register

Thanks for this info :) but this need to call the API the thing that i try to avoid... the notifications system in my vision have to do that without any call from the client or with the minimal requiered 1st time for the new registrations or the new linked website account to the wallet accounts... next time , any event that happend in the monitored account do that the server send a new notification to the registred URL... the member's accountRS is stored in my database... when a notification is recived the 1st thing that my script will do is searching this accountRS in my database and in function of the event it's update the website database... no calls after the 1st registration or will be just for more verifications but always the minimal...

NxtSwe: your help will be the welcome if you want to work in an implementation of NXT in opensimulator (c#)! your NxtLib is perfect for that and for a skilled person like you :) you can do that in 3 days clock in hand... ;D
your work will bring ~100k new users to the NXT network :) opensim users...

in the virtual worlds we use an unknown scripting language called "Linden Script Language" aka LSL... with this language we can animate the 3D items or building a client for the NRS :) but they are a lot of limitations that we have to deal with for a correct use that include the number of the requests that a script can send and more... i will write a dedicated post around opensimulator and what we can do with it... a 3D wall street like for the monetary system and the asset exchange displaying real-time data for eg; or better! a virtual world dedicated to the NXT and it's community :)

[White Rabbit]
https://www.youtube.com/watch?v=49vj9HEI2OY
https://www.youtube.com/watch?v=_CqbqY2p6gQ
http://wiki.secondlife.com/wiki/Category:LSL_HTTP

thank you and @+

You should start a new thread, telling us more about opensimulatur and the ideas you have about this.
So we can keep this thread on topic.
*cheers*
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on November 17, 2015, 08:05:30 pm
Installer request:

Archive Nxt node check box in the Nxt installer setup.

When installing Nxt, make it possible to setup Nxt as a achival node. That should be simple as possible to install archive node, i.e. just check a box in the installation process. That will certainly promote archive node and this request is very easy to be done, i think. Overall, this feature request, once implement, will promote decentralization of Nxt archive data.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Jean-Luc on November 17, 2015, 09:00:37 pm
Well, the installer is mostly used by people setting up the client on their desktops. Those running archival nodes will be using linux VPS's, just unzipping the zip package and editing nxt.properties manually.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on November 17, 2015, 09:47:26 pm
Well, the installer is mostly used by people setting up the client on their desktops. Those running archival nodes will be using linux VPS's, just unzipping the zip package and editing nxt.properties manually.

Still, more windows user would run archival nodes. I know it simple to change it manually. But overall, i think you can't deny that if this option would be available in the installer that would be good for Nxt  :). Imo, you should think of this feature request as a future possible improvement of the installer. This is not a hurry features and should only be see as a way to support and improve the network.

I for one, would run a archival node on my windows desktop with such option. My desktop has 12TB of storage and high performance internet connection. I think this will be sufficent for a while.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Brangdon on November 21, 2015, 03:51:19 pm
Client GUI: to the list of peers, add columns to say whether the peer offers archival and open API services. (Also would be nice if online peer explorers did this.)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: crimi on November 21, 2015, 04:51:40 pm
Client GUI: to the list of peers, add columns to say whether the peer offers archival and open API services. (Also would be nice if online peer explorers did this.)

I know only of a way to check open API nodes via getState - includeExpiredPrunable":true,".There is nothing in the API to check for closed API nodes via getPeer?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Jean-Luc on November 21, 2015, 06:01:59 pm
I know only of a way to check open API nodes via getState - includeExpiredPrunable":true,".There is nothing in the API to check for closed API nodes via getPeer?
getState, in 1.6 at least, also returns the services the peer provides - in 1.6 the possible services are PRUNABLE and HALLMARK, in 1.7 there will be two more services, API and API_SSL, i.e. if the peer has an open API.
getPeers supports a service parameter, to find only peers providing some service. In 1.6 you can search for one service at a time only, but in 1.7 this parameter is multivalued, allowing searching for peers that for example provide both PRUNABLE and API_SSL service.

A peer does not need to have open API in order to provide the PRUNABLE service, the requests for retrieving pruned data are handled on the peer networking port, 7874.

Also note that includeExpiredPrunable:true is not sufficient to provide PRUNABLE, it means the node will return prunable data it has even if older than the default expiration of two weeks, but does not necessarily mean the node keeps prunable data indefinitely. To be considered archival node, prunable lifetime must be set to the maximum, nxt.maxPrunableLifetime=-1 in nxt.properties which will result in maxPrunableLifetime:2147483647 in getState. Or just check that the services json array includes PRUNABLE.


From the 1.7 changelog:

Peers that provide http or https API access open to anyone, configured with
nxt.apiServerHost=0.0.0.0 and nxt.allowedBotHosts=* , are now labelled as
providing a service, API or API_SSL, and can be found using the getPeers API
with the corresponding "service" parameter. This API has been modified to
accept multivalued "service" parameter, returning peers that match all
requested services. The ports on which the open API access is running are
included in the peer info of peers providing those services as apiPort and
apiSSLPort fields.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: crimi on November 21, 2015, 06:54:49 pm
I know only of a way to check open API nodes via getState - includeExpiredPrunable":true,".There is nothing in the API to check for closed API nodes via getPeer?
getState, in 1.6 at least, also returns the services the peer provides - in 1.6 the possible services are PRUNABLE and HALLMARK, in 1.7 there will be two more services, API and API_SSL, i.e. if the peer has an open API.
getPeers supports a service parameter, to find only peers providing some service. In 1.6 you can search for one service at a time only, but in 1.7 this parameter is multivalued, allowing searching for peers that for example provide both PRUNABLE and API_SSL service.

A peer does not need to have open API in order to provide the PRUNABLE service, the requests for retrieving pruned data are handled on the peer networking port, 7874.

Also note that includeExpiredPrunable:true is not sufficient to provide PRUNABLE, it means the node will return prunable data it has even if older than the default expiration of two weeks, but does not necessarily mean the node keeps prunable data indefinitely. To be considered archival node, prunable lifetime must be set to the maximum, nxt.maxPrunableLifetime=-1 in nxt.properties which will result in maxPrunableLifetime:2147483647 in getState. Or just check that the services json array includes PRUNABLE.


From the 1.7 changelog:

Peers that provide http or https API access open to anyone, configured with
nxt.apiServerHost=0.0.0.0 and nxt.allowedBotHosts=* , are now labelled as
providing a service, API or API_SSL, and can be found using the getPeers API
with the corresponding "service" parameter. This API has been modified to
accept multivalued "service" parameter, returning peers that match all
requested services. The ports on which the open API access is running are
included in the peer info of peers providing those services as apiPort and
apiSSLPort fields.

Ty, you could not give me a more accurate response.

Quote
Version 1.6.0e Changelog

To configure a peer to provide the Prunable service, nxt.maxPrunableLifetime must be set to -1 and nxt.includeExpiredPrunable must be true (default). Such a peer will then provide expired prunable data to other peers when requested.
If nxt.includeExpiredPrunable is false, the node will still keep prunable data indefinitely (if nxt.maxPrunableLifetime is -1), but will not provide them to others.

For example i found a node in the mesh with open API, includeExpiredPrunable = false and maxPrunableLifetime = 2147483647, this would mean in that case this node does not provide data to others? How is this node configuration useful to anyone? Can you call the API for the prunable data? The node is just not sharing the data on port 7874?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Jean-Luc on November 21, 2015, 07:50:20 pm
The result of setting nxt.includeExpiredPrunable=false is that such node will not return expired prunable data on port 7874, when requested by other peers using getNextBlocks peer API, and will also reject the getTransactions API on that port (used to retrieve prunable data from archive nodes).

On the 7876 API port, such node will also not include expired prunable data in the response of getTransaction or getBlockchainTransactions API. However, if queried with APIs that return specifically prunable data, such as getPrunableMessages or getTaggedData, it will return those as long as it has them.

It is not a very logical setting to have includeExpiredPrunable=false, yet provide open API access. The default for includeExpiredPrunable is true, and a node should set it to false only in order to save on bandwith and load from peers requesting old data, yet keep all prunable data for its own use permanently. But why would then such a node opt to have its API access open?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: crimi on November 21, 2015, 09:40:51 pm
The result of setting nxt.includeExpiredPrunable=false is that such node will not return expired prunable data on port 7874, when requested by other peers using getNextBlocks peer API, and will also reject the getTransactions API on that port (used to retrieve prunable data from archive nodes).

On the 7876 API port, such node will also not include expired prunable data in the response of getTransaction or getBlockchainTransactions API. However, if queried with APIs that return specifically prunable data, such as getPrunableMessages or getTaggedData, it will return those as long as it has them.

It is not a very logical setting to have includeExpiredPrunable=false, yet provide open API access. The default for includeExpiredPrunable is true, and a node should set it to false only in order to save on bandwith and load from peers requesting old data, yet keep all prunable data for its own use permanently. But why would then such a node opt to have its API access open?

The term includeExpiredPrunable can give you a little headaches. Its on of those properties you are guessing to set to true or false either way it sounds ok. Might be the reason half of the archival nodes go with the illogical settings. :D
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: qq2536007339 on November 24, 2015, 07:52:19 am
1) Node number seems keep falling,maybe some forging reward goes to full nodes? And those hallmark nodes get higher percent.

2) When click a asset Transaction,we can see the asset name,I hope can add a hyperlink redirect to this asset exchange.

3) Allow user to bookmark a currency without own any of this currency.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: ifinta on November 24, 2015, 02:04:19 pm
Two "simple" ideas for Nxt Marketplace:

1.) Price also could be defined as a MS Currency.
2.) It would be greet to have not only "Products for Sale" but also - symmetrically - "Products for Buy".
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on November 24, 2015, 05:51:54 pm
Client GUI: to the list of peers, add columns to say whether the peer offers archival and open API services. (Also would be nice if online peer explorers did this.)

@Brangdon
With anwser from  crimi and JL do this feature request still to be add?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Brangdon on November 24, 2015, 08:40:21 pm
With anwser from  crimi and JL do this feature request still to be add?
Well, yes. Those answers are saying how it could be implemented; I don't think they invalidate the idea of the feature. It's not particularly high priority, but if the GUI is to have a peers list at all, I think it makes sense for this services info to be included. I suggested it because currently there is a dearth of information about archival nodes.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: crimi on November 25, 2015, 02:31:27 pm
With anwser from  crimi and JL do this feature request still to be add?
Well, yes. Those answers are saying how it could be implemented; I don't think they invalidate the idea of the feature. It's not particularly high priority, but if the GUI is to have a peers list at all, I think it makes sense for this services info to be included. I suggested it because currently there is a dearth of information about archival nodes.

peerexplorer.com shows so far open api archival nodes via peerexplorer api(http://www.peerexplorer.com/api) and you can also find it in the node information for example: (http://www.peerexplorer.com/info?node=62.75.156.175). still need to include archival nodes without open api in the specific node information.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on November 30, 2015, 09:35:19 pm
Updated feature request from the recent 1.7.0e release.

Released feature request:
Released in NRS 1.7.0e. (https://nxtforum.org/nrs-releases/nrs-v1-7-0e/) A016. 2015-07-18. Shuffling for NXT. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg184084/#msg184084)
Released in NRS 1.7.0e. (https://nxtforum.org/nrs-releases/nrs-v1-7-0e/) A012. 2015-07-07. Blocktimes never exceed 3 minutes. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg187189/#msg187189)
Released in NRS 1.7.0e. (https://nxtforum.org/nrs-releases/nrs-v1-7-0e/) A005. 2015-06-15. Tradable token that represent a non divisible virtual unique object (special lower fee in AE for that special used case). (https://nxtforum.org/nrs-releases/nrs-v1-6-1e/msg196921/#msg196921)
Released in NRS 1.7.0e. (https://nxtforum.org/nrs-releases/nrs-v1-7-0e/) A003. 2015-06-14. Shuffling for assets. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg184084/#msg184084)

Please don't hesitate to post your request. I will add it to the list, but please follow the rules in OP:
https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: TwinWinNerD on November 30, 2015, 09:58:50 pm
Title: Asset/Asset trading in NXT AE

CORE!  Adding the option to trade assets directly in thw style of the current asset exhange. So with public orders and orderbook. Fees are paid in NXT. All possible Asset to asset combinations must be possible. GUI should make it easy to choose the trading pairs. Possibly through 2 dropdown where all bookmarked normal assets are available. Then you choose two and can add them to your bookmarks
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on November 30, 2015, 10:11:11 pm
Title: Asset/Asset trading in NXT AE

CORE!  Adding the option to trade assets directly in thw style of the current asset exhange. So with public orders and orderbook. Fees are paid in NXT. All possible Asset to asset combinations must be possible. GUI should make it easy to choose the trading pairs. Possibly through 2 dropdown where all bookmarked normal assets are available. Then you choose two and can add them to your bookmarks

Hmm Twin, JL already said this would not be in the core.

A024. 2015-08-10. Need to be done outside the core. (https://nxtforum.org/general-discussion/price-speculation/msg196327/#msg196327) Direct trade/exchange between MSCoin_1 and MSCoin_2, or between Asset_1 and Asset_2. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg191048/#msg191048)

You need to convince him, I would say.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Brangdon on December 01, 2015, 07:06:18 pm
"To the list of peers, add columns to say whether the peer offers archival and open API services" is in 1.7e too. Thanks!
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on December 01, 2015, 07:43:24 pm
"To the list of peers, add columns to say whether the peer offers archival and open API services" is in 1.7e too. Thanks!

Thanks for the input.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Eveready on December 01, 2015, 09:56:23 pm
Just tried the awesome account control in 1.7.0e  ;D
but have 1 request - "Add an option to exclude Account Leasing when setting up mandatory approval account"

With this feature it is safer every time passphrase is used to renew lease. Maybe this will encourage more whales to forge.
Or is there another way to do it without this feature ??? i mean convenient (yet safe) way to do account leasing without using other complicated methods?

Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: TwinWinNerD on December 01, 2015, 10:35:15 pm
Title: Asset/Asset trading in NXT AE

CORE!  Adding the option to trade assets directly in thw style of the current asset exhange. So with public orders and orderbook. Fees are paid in NXT. All possible Asset to asset combinations must be possible. GUI should make it easy to choose the trading pairs. Possibly through 2 dropdown where all bookmarked normal assets are available. Then you choose two and can add them to your bookmarks

Hmm Twin, JL already said this would not be in the core.

A024. 2015-08-10. Need to be done outside the core. (https://nxtforum.org/general-discussion/price-speculation/msg196327/#msg196327) Direct trade/exchange between MSCoin_1 and MSCoin_2, or between Asset_1 and Asset_2. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg191048/#msg191048)

You need to convince him, I would say.

really awesome explanation from our "benevolent dictator"... not.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: _mr_e on December 01, 2015, 10:36:43 pm
Title: Asset/Asset trading in NXT AE

CORE!  Adding the option to trade assets directly in thw style of the current asset exhange. So with public orders and orderbook. Fees are paid in NXT. All possible Asset to asset combinations must be possible. GUI should make it easy to choose the trading pairs. Possibly through 2 dropdown where all bookmarked normal assets are available. Then you choose two and can add them to your bookmarks

Hmm Twin, JL already said this would not be in the core.

A024. 2015-08-10. Need to be done outside the core. (https://nxtforum.org/general-discussion/price-speculation/msg196327/#msg196327) Direct trade/exchange between MSCoin_1 and MSCoin_2, or between Asset_1 and Asset_2. (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg191048/#msg191048)

You need to convince him, I would say.

really awesome explanation from our "benevolent dictator"... not.

Nxt is getting a little too centrally controlled for my liking...
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on December 01, 2015, 10:53:40 pm
But as far as I know, instandex will resolve that. No need to do twice the work. Unless instantdex feature would not be enought.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: TwinWinNerD on December 01, 2015, 10:59:07 pm
But as far as I know, instandex will resolve that. No need to do twice the work. Unless instantdex feature would not be enought.

Instantdex does no provide the features our NXT AE does. In reality Instantdex is very much inferior actually. You need to be online 24/7 (or atleast your passphrase does), you pay fee to a 3rd party, you have to use extra software, you can't really place and order and just wait for it to be taken like on AE, you have to replace it constantly (thats how I understood it). Also it doesn't exist yet in a public release....

Its a poor excuse to say: "Ohh someone esle will probably do it". Not to mention that superNET is currently divorcing from NXT and removed all dependecies from NXT. Great 3rd party provider you rely on.

But "Need to be done outside the core" ---> yeah I am will do my next crowdsale externally for BTC on another provider as it looks like.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on December 01, 2015, 11:03:27 pm
But "Need to be done outside the core" ---> yeah I am will do my next crowdsale externally for BTC on another provider as it looks like.

Please read the warning in the first post of this topic. These are my wording (the best i can come up with my limited english) not the one from any Nxt devs or JLP.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: TwinWinNerD on December 01, 2015, 11:04:36 pm
But "Need to be done outside the core" ---> yeah I am will do my next crowdsale externally for BTC on another provider as it looks like.

Please read the warning in the first post. Thse are my wording not the one from any devs or JLP.

You literally linked to him saying No without an explanation.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on December 01, 2015, 11:05:51 pm
But "Need to be done outside the core" ---> yeah I am will do my next crowdsale externally for BTC on another provider as it looks like.

Please read the warning in the first post. Thse are my wording not the one from any devs or JLP.

You literally linked to him saying No without an explanation.

Well I can't force him to elaborate, He is a free man.

However, it obvious like anyone else that I would have prefer a more detailed answer.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on December 01, 2015, 11:16:08 pm
Just tried the awesome account control in 1.7.0e  ;D
but have 1 request - "Add an option to exclude Account Leasing when setting up mandatory approval account"

With this feature it is safer every time passphrase is used to renew lease. Maybe this will encourage more whales to forge.
Or is there another way to do it without this feature ??? i mean convenient (yet safe) way to do account leasing without using other complicated methods?

That would be GUI or core feature?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Eveready on December 01, 2015, 11:46:31 pm
Just tried the awesome account control in 1.7.0e  ;D
but have 1 request - "Add an option to exclude Account Leasing when setting up mandatory approval account"

With this feature it is safer every time passphrase is used to renew lease. Maybe this will encourage more whales to forge.
Or is there another way to do it without this feature ??? i mean convenient (yet safe) way to do account leasing without using other complicated methods?

That would be GUI or core feature?

idk but think it has to be core plus gui bcos currently there is no such option in the setPhasingOnlyControl API
Title: Add prove of services function
Post by: qq2536007339 on December 09, 2015, 08:17:15 am
Core feature:prove of services.

According to http://www.peerexplorer.com/ statistics,NXT peers number seems keep reduce.To solve this problem,I suggest we give some forging income to full node,and full node with hallmark should get more income.

Dash already implement this function,according to https://bitinfocharts.com/ ,their full node is 14 times of ours.
Title: Re: Add prove of services function
Post by: abctc on December 09, 2015, 09:26:31 am
I suggest we give some forging income to full node, and full node with hallmark should get more income.
- I'm afraid it is not possible. Someone can set up 1000 "nodes" (even with, say, 10 Nxt hallmark) that fake a full node (just relay transactions, but even do not have blockchain). Like this:

Quote from: Come-from-Beyond link=https://bitcointalk.org/index.php?topic=345619.msg3856526#msg3856526
... our peer network has a lot of zombie nodes with modified soft (I bet it's just a dumb script). So, next few hours I spent playing with the zombies trying to find a way to counteract a hypothetical cancer nodes attack. ...
Title: Re: Add prove of services function
Post by: Brangdon on December 09, 2015, 10:06:35 am
Core feature:prove of services.

According to http://www.peerexplorer.com/ statistics,NXT peers number seems keep reduce.To solve this problem,I suggest we give some forging income to full node,and full node with hallmark should get more income.

Dash already implement this function,according to https://bitinfocharts.com/ ,their full node is 14 times of ours.
That's the goal of NSC (https://nxtforum.org/assets-board/%28ann%29-nxt-security-coin-%28nsc%29-get-paid-for-supporting-the-nxt-network!/). It's done off-chain, though. It has to be, because the block-chain doesn't know about nodes unless they forge.

Also, getting a fraction of transaction fees would not be a strong motivator today because the fees are so low. Few people want to increase the fees because it would discourage use.

Title: Re: Add prove of services function
Post by: qq2536007339 on December 10, 2015, 07:58:03 am
I suggest we give some forging income to full node, and full node with hallmark should get more income.
- I'm afraid it is not possible. Someone can set up 1000 "nodes" (even with, say, 10 Nxt hallmark) that fake a full node (just relay transactions, but even do not have blockchain). Like this:

Quote from: Come-from-Beyond link=https://bitcointalk.org/index.php?topic=345619.msg3856526#msg3856526
... our peer network has a lot of zombie nodes with modified soft (I bet it's just a dumb script). So, next few hours I spent playing with the zombies trying to find a way to counteract a hypothetical cancer nodes attack. ...

Thanks for the reply,but that's early situation.Maybe we can find a way to avoid that now,I mean DASH can do it,why can't we.I know the coding is complete diffierent,but we can borrow the idea.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: grewalsatinder on December 12, 2015, 07:31:41 am
Feature Request: DNS System in NXT - Improvements or Redesigned

https://nxtforum.org/core-development-discussion/feature-request-dns-system-in-nxt-improvements-or-redesigned/
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: blackyblack1 on December 21, 2015, 09:02:52 am
UI feature request:
Add "Data Cloud"->"Upload Data" submenu on the sidebar so new data could be uploaded in one click.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: cc001 on December 21, 2015, 09:29:47 am
UI feature request:
Add "Data Cloud"->"Upload Data" submenu on the sidebar so new data could be uploaded in one click.
... and add help texts (?-icon) to the fields "Mime Type" and "Channel" describing what is it for and what exactly has to be entered
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on December 25, 2015, 12:00:29 am
UI feature request: supernet-like PINcode login screen.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: asfd on December 25, 2015, 10:21:12 am
UI feature request: supernet-like PINcode login screen.
That would be fantastic for smartphone use. Something like NxtVault, integrated in the core.
Title: Re: List of feature request for Nxt and NRS
Post by: Sebastien256 on December 28, 2015, 12:45:49 pm
Client UI: better means of handling multiple accounts.

Historically Nxt has strongly encouraged account re-use. However, as I understand it, account re-use is more or less incompatible with privacy (because it makes block-chain analysis too easy). In particular, the forthcoming shuffle feature will require all the output accounts to be brand new. If I get paid weekly, and I shuffle a portion of what I earn, then I could be creating around 50 new accounts a year, each year. Managing this in the current UI would be impractical. Even if that example is too extreme, I think if Nxt wants to position itself as supporting privacy, it should look to managing scores of accounts.

@Brangdon, is the new way of switching account in 1.7 is good enough such that this feature request could be considered done?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on December 28, 2015, 12:47:05 pm
UI feature request:
Add "Data Cloud"->"Upload Data" submenu on the sidebar so new data could be uploaded in one click.

100% agree, it should definitively be a submenu.
Title: Re: List of feature request for Nxt and NRS
Post by: Brangdon on December 28, 2015, 03:05:16 pm
Client UI: better means of handling multiple accounts.

Historically Nxt has strongly encouraged account re-use. However, as I understand it, account re-use is more or less incompatible with privacy (because it makes block-chain analysis too easy). In particular, the forthcoming shuffle feature will require all the output accounts to be brand new. If I get paid weekly, and I shuffle a portion of what I earn, then I could be creating around 50 new accounts a year, each year. Managing this in the current UI would be impractical. Even if that example is too extreme, I think if Nxt wants to position itself as supporting privacy, it should look to managing scores of accounts.

@Brangdon, is the new way of switching account in 1.7 is good enough such that this feature request could be considered done?
It's a big improvement for my three MainNet accounts, but I don't think it scales adequately to scores of accounts. I currently have about 10 accounts on TestNet that came from testing shuffling, and I don't let the UI remember the account numbers because it would be too cluttered and disorganised. I keep my TestNet accounts in a list in another app, and I put notes next to each to remind me what the account is for, whether it's shuffled, even what its current balance is.

I have to say, I've no idea how shuffling is going to be used on MainNet.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Brangdon on December 28, 2015, 03:09:27 pm
Client GUI Request: on the login page, keep separate account lists for MainNet and TestNet. Only list MainNet accounts when on MainNet and only list TestNet accounts when on TestNet. This will reduce clutter for those of us who use TestNet, and make it harder to accidentally use a MainNet account on TestNet.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: qq2536007339 on December 29, 2015, 01:27:38 am
Client GUI Request: on the login page, keep separate account lists for MainNet and TestNet. Only list MainNet accounts when on MainNet and only list TestNet accounts when on TestNet. This will reduce clutter for those of us who use TestNet, and make it harder to accidentally use a MainNet account on TestNet.

That's the request I'm also hoping for.
Title: Re: List of feature request for Nxt and NRS
Post by: blackyblack1 on December 29, 2015, 05:46:15 am
I have to say, I've no idea how shuffling is going to be used on MainNet.
Well it's simple. It won't be used on mainnet.
Title: Re: List of feature request for Nxt and NRS
Post by: Tosch110 on December 29, 2015, 10:29:11 am
I have to say, I've no idea how shuffling is going to be used on MainNet.
Well it's simple. It won't be used on mainnet.

Why not?...
Title: Re: List of feature request for Nxt and NRS
Post by: blackyblack1 on December 29, 2015, 10:34:05 am
I have to say, I've no idea how shuffling is going to be used on MainNet.
Well it's simple. It won't be used on mainnet.

Why not?...
You can read my opinion in this discussion: https://nxtforum.org/index.php?topic=10420.msg202498#msg202498
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: TheCoinWizard on December 29, 2015, 12:18:04 pm
I have to say, I've no idea how shuffling is going to be used on MainNet.
Well it's simple. It won't be used on mainnet.

Why not?...
You can read my opinion in this discussion: https://nxtforum.org/index.php?topic=10420.msg202498#msg202498
You are not alone, same opinion here...  :(
Though it might be used more than minting  :D


Why can I not close my account after creating/joinging a shuffle?

Why is there a prefixed number of participants in a created shuffle?

Why can I not shut down my node after creating/joining a shuffle?

Why can I not shuffle to other peoples account? In other words:
Why do I need the private key of the receivers account?

Seems to me shuffling would be much better without these limitations.
It might actually even be used after removing all these limitations....
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: MrCluster87 on January 10, 2016, 12:03:46 pm
GUI improvement of an existing Core function: Nxt Arbitrary Messages use case: Certified e-mails: https://www.youtube.com/watch?v=ycPv0eFJw-k
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Brangdon on January 11, 2016, 11:26:46 am
It might actually even be used after removing all these limitations....
Did you see my post #16 (https://nxtforum.org/nrs-releases/nrs-v1-7-3e/msg204178/#msg204178) answering those questions? There are good reasons for limitations. In general, doing things trust-free is simply harder than having a central authority you have to trust.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on January 15, 2016, 05:02:44 pm
GUI improvement of an existing Core function: Nxt Arbitrary Messages use case: Certified e-mails: https://www.youtube.com/watch?v=ycPv0eFJw-k

Great idea! +1
It would be relatively easy for devs to do such a thing, I believe. I mean compare to what they have done up to now...

I Would really like to see such a feature in Nxt! Thanks for sharing.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on January 15, 2016, 05:06:40 pm
What about NXT Lite, able to connect to different peers? Just frontend w local signing? Like SN Lite ;)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: yassin54 on January 15, 2016, 05:23:21 pm
What about NXT Lite, able to connect to different peers? Just frontend w local signing? Like SN Lite ;)
Same here!! would like to see this feature  ::)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on January 15, 2016, 05:41:04 pm
What about NXT Lite, able to connect to different peers? Just frontend w local signing? Like SN Lite ;)
Same here!! would like to see this feature  ::)

With this feature a bunch of new !simple userfriendly GUIs may flourish.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Riker on January 16, 2016, 04:29:40 pm
GUI improvement of an existing Core function: Nxt Arbitrary Messages use case: Certified e-mails: https://www.youtube.com/watch?v=ycPv0eFJw-k

I can see the advantage of using NXT for the purpose of message signing and delivery guarantee to remove the need for maintaining a network of PEC servers like in the case of the Italian Posta Elettronica Certificata (https://tools.ietf.org/html/rfc6109)
However, NXT relies on proprietary signing method (not X509 certificates) and I can't think of a simple way to integrate NXT into existing email clients in a general way without coding some client specific plugin for each email client, and there are so many email clients many of them does not support plugins.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Riker on January 16, 2016, 04:33:36 pm
What about NXT Lite, able to connect to different peers? Just frontend w local signing? Like SN Lite ;)

What prevents you from currently downloading the client from a remote peer ? No need for any local installation and the standard client already supports local signing.
Or are you looking for a standalone application installed locally that will be able to find peers on it's own using a 3rd party service like peer explorer ?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on January 16, 2016, 04:41:22 pm
GUI improvement of an existing Core function: Nxt Arbitrary Messages use case: Certified e-mails: https://www.youtube.com/watch?v=ycPv0eFJw-k

I can see the advantage of using NXT for the purpose of message signing and delivery guarantee to remove the need for maintaining a network of PEC servers like in the case of the Italian Posta Elettronica Certificata (https://tools.ietf.org/html/rfc6109)
However, NXT relies on proprietary signing method (not X509 certificates) and I can't think of a simple way to integrate NXT into existing email clients in a general way without coding some client specific plugin for each email client, and there are so many email clients many of them does not support plugins.

I think it should be the other way around, i.e. Nxt to offer a certified email client of it own. If that is possible.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Riker on January 16, 2016, 04:46:12 pm
GUI improvement of an existing Core function: Nxt Arbitrary Messages use case: Certified e-mails: https://www.youtube.com/watch?v=ycPv0eFJw-k

I can see the advantage of using NXT for the purpose of message signing and delivery guarantee to remove the need for maintaining a network of PEC servers like in the case of the Italian Posta Elettronica Certificata (https://tools.ietf.org/html/rfc6109)
However, NXT relies on proprietary signing method (not X509 certificates) and I can't think of a simple way to integrate NXT into existing email clients in a general way without coding some client specific plugin for each email client, and there are so many email clients many of them does not support plugins.

I think it should be the other way around, i.e. Nxt to offer an certified email client of it own.

Develop an email client from scratch ? Surely we don't have the resources for this and even assuming that we find an open source email client and somehow integrate it, only messages between two such clients would be certified and if the users use NXT anyway they might as well just send message transactions.
What is the benefit of using email in this case ?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on January 16, 2016, 04:50:27 pm
GUI improvement of an existing Core function: Nxt Arbitrary Messages use case: Certified e-mails: https://www.youtube.com/watch?v=ycPv0eFJw-k

I can see the advantage of using NXT for the purpose of message signing and delivery guarantee to remove the need for maintaining a network of PEC servers like in the case of the Italian Posta Elettronica Certificata (https://tools.ietf.org/html/rfc6109)
However, NXT relies on proprietary signing method (not X509 certificates) and I can't think of a simple way to integrate NXT into existing email clients in a general way without coding some client specific plugin for each email client, and there are so many email clients many of them does not support plugins.

I think it should be the other way around, i.e. Nxt to offer an certified email client of it own.

Develop an email client from scratch ? Surely we don't have the resources for this and even assuming that we find an open source email client and somehow integrate it, only messages between two such clients would be certified and if the users use NXT anyway they might as well just send message transactions.
What is the benefit of using email in this case ?

Not from scracht, maybe using open source software like thunderbird.

Well, even if the message are only between Nxt user, a better gui and advertisement that secure and non tampered communication can occur on Nxt would be a good start.

I mean Nxt AM can already do that, but can't offer file attachment and font, subject field, multiple output adress, etc... AM at this point is more for machine messaging, not human messaging as is it way too primitive.

These are improvement that do not seems to require a fork.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Riker on January 16, 2016, 05:07:42 pm
Well, even if the message are only between Nxt user, a better gui and advertisement that secure and non tampered communication can occur on Nxt would be a good start.
I mean Nxt AM can already do that, but can't offer file attachment and font, subject field, multiple output adress, etc... AM at this point is more for machine messaging, not human messaging as is it way too primitive.

Email uses SMTP (https://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol) for communication, trying to somehow tunnel SMTP messages using the existing NXT transaction types ... not sure ... for example the NXT cloud data is visible to anyone so not suitable for traditional email attachments which are visible just to the sender, recipient and the servers storing the messages so need to store encrypted cloud data and decrypt it on the client.
Or we can just make something that looks like email but does not rely on SMTP for communication, instead uses the NXT APIs directly but then we cannot use existing email clients, need to develop from scratch.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on January 16, 2016, 05:13:00 pm
I see, personally, I was not thinking about regular email communication, but messaging between Nxt user in a much more "email" type of gui. As long as the communication are secure, can't be tampered and be human friendly , that would be useful.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on January 16, 2016, 07:15:12 pm
What about NXT Lite, able to connect to different peers? Just frontend w local signing? Like SN Lite ;)

What prevents you from currently downloading the client from a remote peer ? No need for any local installation and the standard client already supports local signing.
Or are you looking for a standalone application installed locally that will be able to find peers on it's own using a 3rd party service like peer explorer ?

Did you use SN Lite? Second one, but without installation, and with ability to connect to localhost or remote peer.

I don't quite understand the first question. Now i download official client posted by JL in a zip package. It requires full blockchain download, not so convenient.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Riker on January 16, 2016, 09:04:55 pm
Did you use SN Lite? Second one, but without installation, and with ability to connect to localhost or remote peer.

Not recently, can you point me to the instructions ?

Quote
I don't quite understand the first question. Now i download official client posted by JL in a zip package. It requires full blockchain download, not so convenient.

My testnet node is listening at http://107.170.3.62:6876/index.html connect to it and use it. No download no installation and your passphrase is never sent to the server unless you are forging or participate in shuffling.
What is preventing you from using one of the public nodes this way ?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: blackyblack1 on January 16, 2016, 10:38:49 pm
Did you use SN Lite? Second one, but without installation, and with ability to connect to localhost or remote peer.

Not recently, can you point me to the instructions ?

Quote
I don't quite understand the first question. Now i download official client posted by JL in a zip package. It requires full blockchain download, not so convenient.

My testnet node is listening at http://107.170.3.62:6876/index.html connect to it and use it. No download no installation and your passphrase is never sent to the server unless you are forging or participate in shuffling.
What is preventing you from using one of the public nodes this way ?
How could I know that the passphrase is not sent to your node? Maybe you have changed the script to send it to the server.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on January 17, 2016, 12:13:42 am
Did you use SN Lite? Second one, but without installation, and with ability to connect to localhost or remote peer.

Not recently, can you point me to the instructions ?

Quote
I don't quite understand the first question. Now i download official client posted by JL in a zip package. It requires full blockchain download, not so convenient.

My testnet node is listening at http://107.170.3.62:6876/index.html connect to it and use it. No download no installation and your passphrase is never sent to the server unless you are forging or participate in shuffling.
What is preventing you from using one of the public nodes this way ?
How could I know that the passphrase is not sent to your node? Maybe you have changed the script to send it to the server.

"testnet"?

https://github.com/Tosch110/SuperNet-Lite
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: MrCluster87 on January 17, 2016, 12:27:06 am
I see, personally, I was not thinking about regular email communication, but messaging between Nxt user in a much more "email" type of gui. As long as the communication are secure, can't be tampered and be human friendly , that would be useful.

Me too.   ;)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Riker on January 17, 2016, 06:13:30 am
I see, personally, I was not thinking about regular email communication, but messaging between Nxt user in a much more "email" type of gui. As long as the communication are secure, can't be tampered and be human friendly , that would be useful.

Me too.   ;)
Why not write a plugin why does it have to be in the core?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Gurd on January 17, 2016, 06:49:57 am
Need instructions for starting up the clone
Payment - 50 USD
In the Russian branch - made
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on January 17, 2016, 07:18:36 am
I see, personally, I was not thinking about regular email communication, but messaging between Nxt user in a much more "email" type of gui. As long as the communication are secure, can't be tampered and be human friendly , that would be useful.

Me too.   ;)
Why not write a plugin why does it have to be in the core?

There is already a 35k nxt bounty for such plugin (if i understand mrcluster et al. bounty):
https://nxtforum.org/nxt-plugins/telegram/msg206157/#msg206157

But I have to say that if it require no fork and only Gui improvement, such improvement could be directly into NRS. Directly in NRS is always better than a plugin and more user friendly, imho, because it get the approval of the Nxt devs, and seriously you guys are genius ;D

Riker, if you think this has to be done as plugin, please say it so as an affirmation and I will move the request to the plugin section.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on January 17, 2016, 05:31:35 pm
Feature request, probably core, but would not require a fork, I believe.

RSS feeder api with fully customizable filter (by Nxt account, tags, file type, free string, etc...). This would be very usefull with the new Data cloud feature (i.e. for seedbox RSS reader), or even for receving AM message from Nxt but to receive the message in another software than NRS (i.e. receive NXT AM message in any RSS reader).

https://en.wikipedia.org/wiki/RSS

Is that a possible feature to implement? I think Nxt only need new read only blockchain api to make this possible. Nxt probably already have  much of the require api code to do this, but the current api output might not be RSS compatible.

I would like to put something like this in any RSS reader:
http://107.170.3.62:6876/rss.xml?type=torrent&NxtID=NXT-Y8FL-UJCB-R25H-23BT2&tags=linux&string=ubuntu
and receive all the recent rss feeds which concerns torrent with tags linux, contain string ubuntu and that is from that particular Nxt account...

It could be something like this:
http://107.170.3.62:6876/rss.xml?type=AM&NxtID=NXT-Y8FL-UJCB-R25H-23BT2
And I would receive all the recent unencrypted AM of that particular account in a RSS format...

Some public node could have public web adresss where rss aggregator may be able to ask for new feeds, as I describe up there. But, I could also ask my own computer instead of Riker computer if I run the Nxt server on my computer. This feature do not necessary require public node to be useful as the blockchain carry all the data I need to generate the rss feeds, it only need to be presented in the correct format by the Nxt api.

So I could use my personal local host to receive the RSS feeds instead.
http://localhost:7876/rss.xml?type=torrent&NxtID=NXT-Y8FL-UJCB-R25H-23BT2&tags=linux&string=ubuntu

And voila, Nxt becomes (the first, afaik) decentralized RSS feeder.

Once something like this is made avaliable by Nxt, Nxt could take off as a nice easy to use decentralized torrent offering platform, I believe. Indeed, the data cloud feature could offer a customizable RSS link generator and it then become super easy to download torrent from the data cloud, as all the necessary info to download the torrent is automatically transmit by RSS to any torrent client, like utorrent for example. So a user do not even need to know Nxt to use Nxt, because RSS link generator could also be web-based!


Personnaly, I use RSS feeds everyday, so I would embraced such an addition to Nxt.
Here all potential new Nxt users:
https://en.wikipedia.org/wiki/Comparison_of_feed_aggregators
Indeed, the list of feed aggregators and potential user that may use this decentralized RSS feeds is huge...

Any thoughts on the subject?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: blackyblack1 on January 18, 2016, 11:30:40 am
Feature request: i need to sign transaction unsigned bytes but cannot do it when "Remember password" option is activated. Please add such a call in the JS API.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on January 18, 2016, 04:35:23 pm
Feature request: i need to sign transaction unsigned bytes but cannot do it when "Remember password" option is activated. Please add such a call in the JS API.

Can you give a title to your request so I can put it in the list. Ty
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on January 18, 2016, 06:17:19 pm
Feature request: i need to sign transaction unsigned bytes but cannot do it when "Remember password" option is activated. Please add such a call in the JS API.

Can you give a title to your request so I can put it in the list. Ty

So... what about this one?
https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg206360/#msg206360
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: blackyblack1 on January 18, 2016, 06:35:45 pm
Feature request: i need to sign transaction unsigned bytes but cannot do it when "Remember password" option is activated. Please add such a call in the JS API.

Can you give a title to your request so I can put it in the list. Ty

So... what about this one?
https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg206360/#msg206360
I am writing a plugin. Secret phrase is not accessible when "Remember password" option is on and I need to sign unsigned bytes with it.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: blackyblack1 on January 18, 2016, 06:36:19 pm
Feature request: i need to sign transaction unsigned bytes but cannot do it when "Remember password" option is activated. Please add such a call in the JS API.

Can you give a title to your request so I can put it in the list. Ty
I don't know. I guess it will be faster to ask for this feature in the release section.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Riker on January 18, 2016, 08:07:19 pm
RSS feeder api with fully customizable filter (by Nxt account, tags, file type, free string, etc...). This would be very usefull with the new Data cloud feature (i.e. for seedbox RSS reader), or even for receving AM message from Nxt but to receive the message in another software than NRS (i.e. receive NXT AM message in any RSS reader).

https://en.wikipedia.org/wiki/RSS

Is that a possible feature to implement? I think Nxt only need new read only blockchain api to make this possible. Nxt probably already have  much of the require api code to do this, but the current api output might not be RSS compatible.

RSS usage peaked in 2006 (that's 10 years ago) the relevancy of this technology is slowly declining https://www.google.com/trends/explore#q=rss
Does it really worth the effort ?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on January 18, 2016, 09:27:24 pm
RSS feeder api with fully customizable filter (by Nxt account, tags, file type, free string, etc...). This would be very usefull with the new Data cloud feature (i.e. for seedbox RSS reader), or even for receving AM message from Nxt but to receive the message in another software than NRS (i.e. receive NXT AM message in any RSS reader).

https://en.wikipedia.org/wiki/RSS

Is that a possible feature to implement? I think Nxt only need new read only blockchain api to make this possible. Nxt probably already have  much of the require api code to do this, but the current api output might not be RSS compatible.

RSS usage peaked in 2006 (that's 10 years ago) the relevancy of this technology is slowly declining https://www.google.com/trends/explore#q=rss
Does it really worth the effort ?

Really? I'm using the technology everyday to read news.  :D

For torrent, in particular, RSS is very usefull. Is it possibke to see the trend of RSS usage in torrent client. I think this trend is not going down, maybe for other usage RSS is going down, but I doubt it the case for torrent client, unless the bittorrent network trend usage is also going down. Open any torrent client, like utorrent, and you will find the RSS section not far (RSS=feed section). I think you should investigate RSS for torrent, it definitely worth the effort imo. It would make Nxt more usable as a torrent offering platform.

I think it worth implementing this RSS output for the torrent particular application. There is still probably millions of RSS users in torrent client, or potential hundred toushand client at the very least...
Title: Allow node to announce web serve
Post by: qq2536007339 on January 19, 2016, 05:59:23 am
GUI and CORE feature request

Title:Allow node to announce web serve

I use Raspberry to run NRS,and I also installed lamp,so I came up with this idea.

Why not allow a NRS node announce it's web serve(http or ftp) to other nodes.My suggest is add a new property in nxt-default.properties file,if a node do run web serve,the owner can set in nxt.properties.And the new serve will show in the Peers page Services column,maybe better to add a hyperlink,and when mouse move on it,show little intro if there is one.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on January 19, 2016, 11:00:00 am
What about NXT Lite, able to connect to different peers? Just frontend w local signing? Like SN Lite ;)

?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Hachoir on January 19, 2016, 11:04:18 am
Doesn't that already exist ?

https://nxtforum.org/general-discussion/(ann)-nxtlite/ (https://nxtforum.org/general-discussion/(ann)-nxtlite/)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on January 20, 2016, 11:20:29 am
Doesn't that already exist ?

https://nxtforum.org/general-discussion/(ann)-nxtlite/ (https://nxtforum.org/general-discussion/(ann)-nxtlite/)


No, thats not it (is it being updated?).

I want an exactly same as supernet lite login page to be implemented in NXT client, without this supernet thing, and maintained by NXT UI devs.
Its not an app.

Try it yourself (SN lite), works great.
https://github.com/Tosch110/SuperNet-Lite


(http://i.imgur.com/aSStpoq.png)


Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on January 20, 2016, 07:19:41 pm
Doesn't that already exist ?

https://nxtforum.org/general-discussion/(ann)-nxtlite/ (https://nxtforum.org/general-discussion/(ann)-nxtlite/)


No, thats not it (is it being updated?).

I want an exactly same as supernet lite login page to be implemented in NXT client, without this supernet thing, and maintained by NXT UI devs.
Its not an app.

Try it yourself (SN lite), works great.
https://github.com/Tosch110/SuperNet-Lite


(http://i.imgur.com/aSStpoq.png)

Thanks, will add to the list.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: allwelder on January 21, 2016, 06:02:24 am
Plze consider to add login with Alias button like http://jnxt.org/nxt/ did. :)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on January 21, 2016, 11:58:16 am
Thank you!

Could you elaborate please, why this shouldn't be in NRS without messing with plugins, that are totally dead as a concept (for now)?

1. C001. 2015-06-13. Need to be done as a Nxt plugin. Candle sticks graphs for the price of the assets in the AE.

IMHO THIS IS A MUST HAVE OPTION!
A lot of people are waiting for simple AE candle charts for so long already. Things getting worse with SAE and NXTBlocks closed!
Others are not informative(nxtreporting). There is no trust in plugins nor in 3rdparty services, today they are alive, tomorrow they're not.

Please reconsider!
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on January 21, 2016, 12:03:26 pm
And block time counter maybe too. Could be very handy. Tired of opening nxtportal just to look at next block arrival time.
There's a lot of place at the top of the left column to display two numbers without plugins:   like 27/60  or 57/130   
elapsed/estimated
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on January 21, 2016, 06:22:16 pm
UI feature request: supernet-like PINcode login screen.

Doesn't that already exist ?

https://nxtforum.org/general-discussion/(ann)-nxtlite/ (https://nxtforum.org/general-discussion/(ann)-nxtlite/)



No, thats not it (is it being updated?).

I want an exactly same as supernet lite login page to be implemented in NXT client, without this supernet thing, and maintained by NXT UI devs.
Its not an app.

Try it yourself (SN lite), works great.
https://github.com/Tosch110/SuperNet-Lite


(http://i.imgur.com/aSStpoq.png)




What is the difference between the two requests?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on January 21, 2016, 06:28:40 pm
Yes, i noticed, the first was about pincode, second is about  connection to local/remote
Could you please merge them?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on January 21, 2016, 06:41:14 pm
Yes, i noticed, the first was about pincode, second is about  connection to local/remote
Could you please merge them?

Please make a new post with all the required information and feature that you want and I will update the OP with that feature request instead of the two others. And please, always put a title to the request, otherwise I have to decifer. In the future I may not put the request in OP if the feature request is not entitle.

Anoter possibility is to simply update your own post which I already link to.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on January 21, 2016, 06:46:57 pm
GUI feature request
Title: Supernet-like login screen.

(http://i.imgur.com/aSStpoq.png)

It should have multiple accounts selector secured by pincode and local/remote peer connection options, as long as new account button and language selector.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on January 21, 2016, 09:15:52 pm
Thank you!

C001. 2015-06-13. Need to be done as a Nxt plugin. Candle sticks graphs for the price of the assets in the AE.

Could you elaborate please, why this shouldn't be in NRS without messing with plugins, that are totally dead as a concept (for now)?

IMHO THIS IS A MUST HAVE OPTION!
A lot of people are waiting for simple AE candle charts for so long already. Things getting worse with SAE and NXTBlocks closed!
Others are not informative(nxtreporting). There is no trust in plugins nor in 3rdparty services, today they are alive, tomorrow they're not.

Please reconsider!

?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on January 21, 2016, 10:02:32 pm
Thank you!

C001. 2015-06-13. Need to be done as a Nxt plugin. Candle sticks graphs for the price of the assets in the AE.

Could you elaborate please, why this shouldn't be in NRS without messing with plugins, that are totally dead as a concept (for now)?

IMHO THIS IS A MUST HAVE OPTION!
A lot of people are waiting for simple AE candle charts for so long already. Things getting worse with SAE and NXTBlocks closed!
Others are not informative(nxtreporting). There is no trust in plugins nor in 3rdparty services, today they are alive, tomorrow they're not.

Please reconsider!

?

To whom you are asking? Because from what concern me, I'm just maintaning the list for my personal pleasure and because I like Nxt.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on January 21, 2016, 10:29:56 pm
Released in NRS 1.7.4. B025. 2015-12-21. Add "Data Cloud"->"Upload Data" submenu. (https://nxtforum.org/core-development-discussion/list-of-feature-request-for-nrs/msg204117/#msg204117)

Thanks to whoever did this!
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on January 22, 2016, 09:03:23 am
Thank you!

C001. 2015-06-13. Need to be done as a Nxt plugin. Candle sticks graphs for the price of the assets in the AE.

Could you elaborate please, why this shouldn't be in NRS without messing with plugins, that are totally dead as a concept (for now)?

IMHO THIS IS A MUST HAVE OPTION!
A lot of people are waiting for simple AE candle charts for so long already. Things getting worse with SAE and NXTBlocks closed!
Others are not informative(nxtreporting). There is no trust in plugins nor in 3rdparty services, today they are alive, tomorrow they're not.

Please reconsider!

?

To whom you are asking? Because from what concern me, I'm just maintaning the list for my personal pleasure and because I like Nxt.

I saw Riker around couple of times.
You do a very good thing with this list. I'm posting here because I like Nxt too. :)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Jose on January 23, 2016, 02:18:32 pm
It would be nice to have the posibility to vote/give score/rate the files uploaded using the "data cloud" feature :)
Or even add comments.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Jose on January 23, 2016, 02:25:47 pm
Feature request, probably core, but would not require a fork, I believe.

RSS feeder api with fully customizable filter (by Nxt account, tags, file type, free string, etc...). This would be very usefull with the new Data cloud feature (i.e. for seedbox RSS reader), or even for receving AM message from Nxt but to receive the message in another software than NRS (i.e. receive NXT AM message in any RSS reader).

https://en.wikipedia.org/wiki/RSS

Is that a possible feature to implement? I think Nxt only need new read only blockchain api to make this possible. Nxt probably already have  much of the require api code to do this, but the current api output might not be RSS compatible.

I would like to put something like this in any RSS reader:
http://107.170.3.62:6876/rss.xml?type=torrent&NxtID=NXT-Y8FL-UJCB-R25H-23BT2&tags=linux&string=ubuntu
and receive all the recent rss feeds which concerns torrent with tags linux, contain string ubuntu and that is from that particular Nxt account...

It could be something like this:
http://107.170.3.62:6876/rss.xml?type=AM&NxtID=NXT-Y8FL-UJCB-R25H-23BT2
And I would receive all the recent unencrypted AM of that particular account in a RSS format...

Some public node could have public web adresss where rss aggregator may be able to ask for new feeds, as I describe up there. But, I could also ask my own computer instead of Riker computer if I run the Nxt server on my computer. This feature do not necessary require public node to be useful as the blockchain carry all the data I need to generate the rss feeds, it only need to be presented in the correct format by the Nxt api.

So I could use my personal local host to receive the RSS feeds instead.
http://localhost:7876/rss.xml?type=torrent&NxtID=NXT-Y8FL-UJCB-R25H-23BT2&tags=linux&string=ubuntu

And voila, Nxt becomes (the first, afaik) decentralized RSS feeder.

Once something like this is made avaliable by Nxt, Nxt could take off as a nice easy to use decentralized torrent offering platform, I believe. Indeed, the data cloud feature could offer a customizable RSS link generator and it then become super easy to download torrent from the data cloud, as all the necessary info to download the torrent is automatically transmit by RSS to any torrent client, like utorrent for example. So a user do not even need to know Nxt to use Nxt, because RSS link generator could also be web-based!


Personnaly, I use RSS feeds everyday, so I would embraced such an addition to Nxt.
Here all potential new Nxt users:
https://en.wikipedia.org/wiki/Comparison_of_feed_aggregators
Indeed, the list of feed aggregators and potential user that may use this decentralized RSS feeds is huge...

Any thoughts on the subject?

I really love this idea.

Some kind of aggregation feature (RSS?) that would let you see all the files (torrents, txt or whatever) uploaded using the "data cloud" feature from a specific user/tag/channel/sender/receiver... (or even just plain text messages, no need for content from the "data cloud")

That way, Nxt could somehow become a resilient platform to news and freespeech, wherever freedom isn't available.

The final reader would be able to see all this content with no censorship possible, just all together in the screen according to the filter the user set.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on January 23, 2016, 05:12:57 pm
Feature request, probably core, but would not require a fork, I believe.

RSS feeder api with fully customizable filter (by Nxt account, tags, file type, free string, etc...). This would be very usefull with the new Data cloud feature (i.e. for seedbox RSS reader), or even for receving AM message from Nxt but to receive the message in another software than NRS (i.e. receive NXT AM message in any RSS reader).

https://en.wikipedia.org/wiki/RSS

Is that a possible feature to implement? I think Nxt only need new read only blockchain api to make this possible. Nxt probably already have  much of the require api code to do this, but the current api output might not be RSS compatible.

I would like to put something like this in any RSS reader:
http://107.170.3.62:6876/rss.xml?type=torrent&NxtID=NXT-Y8FL-UJCB-R25H-23BT2&tags=linux&string=ubuntu
and receive all the recent rss feeds which concerns torrent with tags linux, contain string ubuntu and that is from that particular Nxt account...

It could be something like this:
http://107.170.3.62:6876/rss.xml?type=AM&NxtID=NXT-Y8FL-UJCB-R25H-23BT2
And I would receive all the recent unencrypted AM of that particular account in a RSS format...

Some public node could have public web adresss where rss aggregator may be able to ask for new feeds, as I describe up there. But, I could also ask my own computer instead of Riker computer if I run the Nxt server on my computer. This feature do not necessary require public node to be useful as the blockchain carry all the data I need to generate the rss feeds, it only need to be presented in the correct format by the Nxt api.

So I could use my personal local host to receive the RSS feeds instead.
http://localhost:7876/rss.xml?type=torrent&NxtID=NXT-Y8FL-UJCB-R25H-23BT2&tags=linux&string=ubuntu

And voila, Nxt becomes (the first, afaik) decentralized RSS feeder.

Once something like this is made avaliable by Nxt, Nxt could take off as a nice easy to use decentralized torrent offering platform, I believe. Indeed, the data cloud feature could offer a customizable RSS link generator and it then become super easy to download torrent from the data cloud, as all the necessary info to download the torrent is automatically transmit by RSS to any torrent client, like utorrent for example. So a user do not even need to know Nxt to use Nxt, because RSS link generator could also be web-based!


Personnaly, I use RSS feeds everyday, so I would embraced such an addition to Nxt.
Here all potential new Nxt users:
https://en.wikipedia.org/wiki/Comparison_of_feed_aggregators
Indeed, the list of feed aggregators and potential user that may use this decentralized RSS feeds is huge...

Any thoughts on the subject?

I really love this idea.

Some kind of aggregation feature (RSS?) that would let you see all the files (torrents, txt or whatever) uploaded using the "data cloud" feature from a specific user/tag/channel/sender/receiver... (or even just plain text messages, no need for content from the "data cloud")

That way, Nxt could somehow become a resilient platform to news and freespeech, wherever freedom isn't available.

The final reader would be able to see all this content with no censorship possible, just all together in the screen according to the filter the user set.

@Riker,

Maybe it would be less effort to convert Nxt json output into an RSS feed using the x-stream java library (as RSS is XML formatted plain text afaik)
http://x-stream.github.io/

Quote
Due to XStream's flexible architecture, handling of JSON mappings is as easy as handling of XML documents. All you have to do is to initialize XStream object with an appropriate driver and you are ready to serialize your objects to (and from) JSON.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: martismartis on January 26, 2016, 02:44:09 pm
Hello people

I had a dream tonight about some real world use cases where it is possible to use NXT technology (Monetary system). Was thinking all the day about it, but one thing stopped me to go further. For my plan (I don't want to reaveal some details, yet) is needed transaction fees paid by receiver (to pay fees in MS currency would be the best). What I mean, is like you pay with credit card, if something cost 10 EUR, you pay exactly 10 EUR (withdraw from your bank account) and all required fees are paid by seller (receiver). Is there any possibility to put in NXT core and some optional in transaction dialog, that fees is paid by receiver?

I understand it could be achieved by the third party, but my plan works without third party, it needs direct transaction between both parties (sender and receiver only) and fee paid by receiver.

IMO, this could boost real use cases, especially in MS, but with MS I think I ask too much :) What do I miss?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Riker on January 26, 2016, 08:25:47 pm
Is there any possibility to put in NXT core and some optional in transaction dialog, that fees is paid by receiver?

No, since this will allow a malicious sender to exploit the receiver.
In the past we discussed implementing an MS currency wallet which automatically funds user accounts with NXT to pay the transaction fees by exchanging their MS currency to NXT when required. It's not too complex to implement but no one has implemented this yet TTBOMK.
In the future once we have child chains, you'll be able to use the child chain token both as a transaction token and for paying fees to the child chain (still being discussed)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: blackyblack1 on January 27, 2016, 10:31:02 am
Is there any possibility to put in NXT core and some optional in transaction dialog, that fees is paid by receiver?

No, since this will allow a malicious sender to exploit the receiver.
In the past we discussed implementing an MS currency wallet which automatically funds user accounts with NXT to pay the transaction fees by exchanging their MS currency to NXT when required. It's not too complex to implement but no one has implemented this yet TTBOMK.
In the future once we have child chains, you'll be able to use the child chain token both as a transaction token and for paying fees to the child chain (still being discussed)
This could be solved with this proposal: https://nxtforum.org/index.php?topic=9305.msg200375#msg200375
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: martismartis on January 27, 2016, 10:45:30 am
Is there any possibility to put in NXT core and some optional in transaction dialog, that fees is paid by receiver?

No, since this will allow a malicious sender to exploit the receiver.
In the past we discussed implementing an MS currency wallet which automatically funds user accounts with NXT to pay the transaction fees by exchanging their MS currency to NXT when required. It's not too complex to implement but no one has implemented this yet TTBOMK.
In the future once we have child chains, you'll be able to use the child chain token both as a transaction token and for paying fees to the child chain (still being discussed)

From where and by whom these funds could come?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: MrV777 on February 04, 2016, 03:47:46 pm
Not sure if there was a bounty on this, but I attempted to try and tackle this one today:
C001. 2015-06-13. Need to be done as a Nxt plugin. Candle sticks graphs for the price of the assets in the AE.

and I got decently far.  Here is a screenshot of it with the asset ID hardcoded into the plugin:
(http://i67.tinypic.com/2iaeno4.jpg)

Edit:  Finished now with only two known bug: If there has been no trades it doesn't display correctly and you need to own at least one asset.  Anyone want to try it?  :)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: blackyblack1 on February 05, 2016, 09:41:21 am
Core feature proposal: incentivize nodes participating in shuffle via 1000 NXT blame redistribution.

I found a way to incentivize people to participate in shufflings (found this idea in russian thread actually). We should redistribute blamed node fee not between forgers but between shuffling participants (except blamed node). It will attract additional nodes to participate in all shuffles because of a chance to win a part of 1000 NXT reward.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on March 09, 2016, 06:21:42 pm
Hey Nxter, last post in here is more than one month old.

You still can proposed feature request even tho Nxt 2.0 is about one year ahead. The 1.x branch will still be improved by the core devs. I'm sure they like to read your great ideas.

Keep them comming :)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on March 09, 2016, 06:23:19 pm
Not sure if there was a bounty on this, but I attempted to try and tackle this one today:
C001. 2015-06-13. Need to be done as a Nxt plugin. Candle sticks graphs for the price of the assets in the AE.

and I got decently far.  Here is a screenshot of it with the asset ID hardcoded into the plugin:
(http://i67.tinypic.com/2iaeno4.jpg)

Edit:  Finished now with only two known bug: If there has been no trades it doesn't display correctly and you need to own at least one asset.  Anyone want to try it?  :)

A link to the plugin would be usefull I think. Seems to me like a nice work. Unfortunally, no bounty on this afaik.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: MrV777 on March 09, 2016, 06:32:49 pm
A link to the plugin would be usefull I think. Seems to me like a nice work. Unfortunally, no bounty on this afaik.

Since the NXT 2.0 conversation started, I haven't worked much on the plugin, but it should be working and can be found here:
https://github.com/mrv777/NXT_asset_analysis
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on March 09, 2016, 06:35:45 pm
A link to the plugin would be usefull I think. Seems to me like a nice work. Unfortunally, no bounty on this afaik.

Since the NXT 2.0 conversation started, I haven't worked much on the plugin, but it should be working and can be found here:
https://github.com/mrv777/NXT_asset_analysis

Since the code is opensource I will mark this feature request as completed and link to your post.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: websioux on March 16, 2016, 03:34:58 pm
Here is mine here : https://nxtforum.org/general/a-'buy-offer-confirmed-order-book'-for-shops/

Its about an option for asset issuance that reserve the right to make sell offers to the asset issuer only.

This could bring back balance to the world with a fair price discovery technology.
It will add up the power of deflationary forces (consumers) that are born in a global inflationary economical set up  ;)
To understand, follow the link.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Dr.Beer on March 21, 2016, 09:55:00 am
Hi!
I have a question: I need to implement on the basis of NXT, such task:
1. There is a transaction (A) containing some information
2. At transaction an execution established period, i.e. on an example - transaction will shall be executed in 10 days
3. I need to implement: that when sending additional transaction (B) to cancel execution of the current transaction (A). I.e. analog the phased transaction which will be cancelled if in the blokcheena the given transaction appears (B).
Whether creation of such functionality in NXT is possible?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: CryptKeeper on March 21, 2016, 02:43:51 pm
I have a use case for the feature on top of the OP list:

Nxt Auction House (https://nxtforum.org/general/list-of-feature-request-for-nrs/msg184004/#msg184004)

I've started to sell Nxt Vanity Account Names on the Marketplace and it would be a cool feature if I could set up auctions for some premium accounts! When a given block height is reached, the highest bidder could automatically receive the pass phrase for the vanity account as a marketplace delivery.

I this a feature we can expect soon? Like in 1.9?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Riker on March 21, 2016, 05:43:17 pm
Hi!
I have a question: I need to implement on the basis of NXT, such task:
1. There is a transaction (A) containing some information
2. At transaction an execution established period, i.e. on an example - transaction will shall be executed in 10 days
3. I need to implement: that when sending additional transaction (B) to cancel execution of the current transaction (A). I.e. analog the phased transaction which will be cancelled if in the blokcheena the given transaction appears (B).
Whether creation of such functionality in NXT is possible?

There is no strait forward way to do this.
To delay a transaction by 10 days is simple. However the only way to cancel it is to indirectly cause it to fail validation at it's finish height.
For example, if you submit a transaction A to transfer an asset 10 days from now. To cancel it, issue transaction B to transfer the asset to another account so that transfer A is no longer legal. So depending on your usage scenario this may or may not be possible.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: websioux on March 21, 2016, 08:29:40 pm
@cryptKeeper singleton?

Envoyé de mon GT-I9195 en utilisant Tapatalk

Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: CryptKeeper on March 21, 2016, 08:51:30 pm
@cryptKeeper singleton?

How can I auction singletons? Put it on the AE and let users bid for it? But no automatic end on certain block height and no automatic delivery!
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: websioux on March 21, 2016, 09:07:46 pm
AFAIK there is no automatic delivery either in DGS. You could program something for end of auction. They have to trust you anyway.

But like with my idea you wouldn't like someone to resell under your "asset".

Envoyé de mon GT-I9195 en utilisant Tapatalk

Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Dr.Beer on March 21, 2016, 09:12:15 pm
Hi!
I have a question: I need to implement on the basis of NXT, such task:
1. There is a transaction (A) containing some information
2. At transaction an execution established period, i.e. on an example - transaction will shall be executed in 10 days
3. I need to implement: that when sending additional transaction (B) to cancel execution of the current transaction (A). I.e. analog the phased transaction which will be cancelled if in the blokcheena the given transaction appears (B).
Whether creation of such functionality in NXT is possible?

There is no strait forward way to do this.
To delay a transaction by 10 days is simple. However the only way to cancel it is to indirectly cause it to fail validation at it's finish height.
For example, if you submit a transaction A to transfer an asset 10 days from now. To cancel it, issue transaction B to transfer the asset to another account so that transfer A is no longer legal. So depending on your usage scenario this may or may not be possible.

Hi ! Thanks for you answer!

I considered similar decisions too, but all of them "not simple", and require more "strange" actions :) And it is so difficult to realize function transaction "canceling"?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Jean-Luc on March 21, 2016, 09:30:05 pm
I have an idea that may work, but you should test it. Create a singleton asset that the controlling account owns. Make a phased transaction by asset balance, based on that asset, with a quorum of 1, and the controlling account on the whitelist. Then approve it. Since it is balance dependent, it will not finish early but wait until finish height. If you do nothing, it will get executed. If you transfer that asset to another account of yours, the quorum will no longer be met and the transaction should be cancelled. So this transfer of the asset away is in effect a cancellation transaction.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Dr.Beer on March 22, 2016, 07:36:54 am
I have an idea that may work, but you should test it. Create a singleton asset that the controlling account owns. Make a phased transaction by asset balance, based on that asset, with a quorum of 1, and the controlling account on the whitelist. Then approve it. Since it is balance dependent, it will not finish early but wait until finish height. If you do nothing, it will get executed. If you transfer that asset to another account of yours, the quorum will no longer be met and the transaction should be cancelled. So this transfer of the asset away is in effect a cancellation transaction.

Jean-Luc, Thanks for your response ! I will try the offered option though it and not a direct way, but perhaps it will allow to solve the problem
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: CryptKeeper on March 22, 2016, 10:49:43 am
AFAIK there is no automatic delivery either in DGS. You could program something for end of auction. They have to trust you anyway.

But like with my idea you wouldn't like someone to resell under your "asset".

Yes, I think singletons might be usable for auctions, but in no way perfect.
The "resell problem" can be avoided if the seller buyer must transfer the asset back to the issuer to receive the good.
The issuer can then delete the singleton, to prevent further trading on the AE.

Lots of manual steps involved, I don't like it.  :-\

But thanks for the idea!  :)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: websioux on March 22, 2016, 08:33:21 pm
I think you should have wrote : the buyer sends back...

But yes, it is too much steps. They must bid something and no more.

Did you read my whole suggestion?  Your situation is the same.

You are not obliged to set timing for the end of auction because people can cancel their bid at anytime.

Then for marketing reason you can announce that you will take the highest bid in X days. hours.. You can then program it or do it by hand.


Envoyé de mon GT-I9195 en utilisant Tapatalk

Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: lopalcar on March 22, 2016, 11:46:44 pm
Since next releases till 2.0 are focused in interface improvements... will be possible to add something like the Qora web in nxt?
Maybe concatenating some transactions or referenced transactions or such things is viable to upload even larger images to the blockchain?

I think some decentralized webpages would be nice, even if only small pages are allowed for the moment "till 40kb"
And also make the pages posible to update by the creator "maybe just attach a bunch of transaction with the web code to an alias and build some viewer for bundle all of them and show the page? and every time you want to update some part of the page, the alias is updated with the necessary changes?"

I suppose this can be done via plugin also, right? But would be cool to have something like that in-wallet in my opinion
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Tosch110 on March 30, 2016, 10:49:59 am
I have a feature request.

Currently Nxt comes with one "optimal" config file, which is conf/nxt-default.properties.

Could we add some optimized config files to the distribution where

1) Optimal user config file (nxt-default.properties)
2) Optimal node config file (nxt-node.properties)
3) Optimal archival node config file (nxt-archival-node.properties)
...

So the user would not have to fiddle all the options out for himself when he wants to setup a full node, a full archival node or whatever.
Currently this takes a lot of effort because you have to find all the necessary values in the config file and have to test it before you can host a public node. When we could just switch those files it might be a lot easier to create nodes for Nxt.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Tosch110 on March 30, 2016, 05:39:07 pm
I have a feature request.

Currently Nxt comes with one "optimal" config file, which is conf/nxt-default.properties.

Could we add some optimized config files to the distribution where

1) Optimal user config file (nxt-default.properties)
2) Optimal node config file (nxt-node.properties)
3) Optimal archival node config file (nxt-archival-node.properties)
...

So the user would not have to fiddle all the options out for himself when he wants to setup a full node, a full archival node or whatever.
Currently this takes a lot of effort because you have to find all the necessary values in the config file and have to test it before you can host a public node. When we could just switch those files it might be a lot easier to create nodes for Nxt.

Now after reading the Nxt 1.8e description I think this could also be done as "AddOn" where the user can choose between server types. Just an idea.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Jose on April 03, 2016, 12:01:59 pm
Feature request:

An option that allows you to automatically send the fees you receive from forging (or a % of them) to a choosen NXT addres (the Nxt devs address, the Nxt foundation address, a NGO address... or simply a third party address) without the need to lease your stake to a forging pool.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on April 03, 2016, 12:08:54 pm
Feature request:

An option that allows you to automatically send the fees you receive from forging (or a % of them) to a choosen NXT addres (the Nxt devs address, the Nxt foundation address, a NGO address... or simply a third party address) without the need to lease your stake to a forging pool.

Simple and nice feature request, I would add an option where we can set the pourcentage would like to send and also allows multiple possible output adress for sending the forging revenue.

That may promote more people to forge and adding active node in the Nxt network.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: websioux on April 03, 2016, 08:06:09 pm
This is the kind of thing that can be done with the new java plugin feature. And once some libs will become available, I guess non java progs like me can achieve what you are talking about.

This is the kind of things that do not fully require to be decentralized.

When it becomes used a lot then its good to implement in core.

I'm not saying this for not including your suggestions but to underline the possibilities that are coming.

Envoyé de mon GT-I9195 en utilisant Tapatalk

Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on April 03, 2016, 09:10:35 pm

If the feature is done as a a plugin I will mark it as done, either way it would be a nice feature. But I think witha core functionn it could be less cheap to execute all transaction as 1 transaction instead of many.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: websioux on April 03, 2016, 09:57:36 pm
in general, multiple destinations for AM in the UI would certainly be useful.

Envoyé de mon GT-I9195 en utilisant Tapatalk

Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: testdruif on April 03, 2016, 10:25:56 pm

If the feature is done as a a plugin I will mark it as done, either way it would be a nice feature. But I think witha core functionn it could be less cheap to execute all transaction as 1 transaction instead of many.

It won't be a hard thing to write an addon for this.
It would require you to put your passphrase in a config file tho...
A big security issue :(

Also can't forget to check that the amount to be sent isn't below 1 nxt (or the forged amount isn't below X) or it would cost you money to send a %
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: websioux on April 04, 2016, 02:30:27 pm
A big security issue :(
Only proportional to the forged amount. Regarding security isn't it similar to having a hot wallet that process automations with API ?

Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on April 04, 2016, 09:27:47 pm

If the feature is done as a a plugin I will mark it as done, either way it would be a nice feature. But I think witha core functionn it could be less cheap to execute all transaction as 1 transaction instead of many.

It won't be a hard thing to write an addon for this.
It would require you to put your passphrase in a config file tho...
A big security issue :(

Also can't forget to check that the amount to be sent isn't below 1 nxt (or the forged amount isn't below X) or it would cost you money to send a %

Aye, that change the scope of the feature and make it not that usefull if this is in plugin in the end. Maybe for a very big forger it could be usefull.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: NxtSwe on April 04, 2016, 09:55:06 pm
One of the big problems with MS currencies is that you still need NXT in order to transact, this has been discussed many times before.

What about if you were able to set the currency itself as fee, and as long as it has a value, ie. there's a buyer for that specific currency a portion will be sold to cover the fees?

Example:
I have 100 EGOLD and 0 NXT in my wallet.
There is a buyer for EGOLD in the MS Exchange Booth, buying 20 EGOLD for 1 NXT.
So I can have the option of sending 80 EGOLD to a friend and paying 20 EGOLD as fee, which will be sold and 1 NXT will be used to pay the tx fee.

I can't remember if this has been mentioned before.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Riker on April 05, 2016, 07:23:53 am
One of the big problems with MS currencies is that you still need NXT in order to transact, this has been discussed many times before.

What about if you were able to set the currency itself as fee, and as long as it has a value, ie. there's a buyer for that specific currency a portion will be sold to cover the fees?

Example:
I have 100 EGOLD and 0 NXT in my wallet.
There is a buyer for EGOLD in the MS Exchange Booth, buying 20 EGOLD for 1 NXT.
So I can have the option of sending 80 EGOLD to a friend and paying 20 EGOLD as fee, which will be sold and 1 NXT will be used to pay the tx fee.

I can't remember if this has been mentioned before.

It was discussed before, these automatic conversions are difficult to implement and simple to manipulate.

There are currently two directions how to address this:
1. The "Funding Monitor" feature we introduced in 1.8.0e - it allows the main stake holder of EGOLD to automatically make sure EGOLD holders will always have some NXT in their account in order to transact. Assuming that the issuer of EGOLD has strong motivation for EGOLD to succeed the assumption is that they would be able to absorb these transaction fees or somehow raise them from their users.

2. NXT 2.0 child chain - in a child chain the fees are paid using the child chain token. The transactions "bundler" which is possibly the FXT forger will take care of converting the child token fee to FXT fee.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: LocoMB on April 05, 2016, 09:28:37 am
maybe this is the right place to bounce this around. as this was raised in the other thread.

This conceptual difference between API and Protocol keeps bugging me.
I am wondering what there is in terms of documentation- I know there was some wiki stuff documentig the API, but I don't know the status.

Would there be any beneifit in having a bunch of UML diagrams as a first step towards enabling access by a broader dev base and language agnostic protocol specs?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Brangdon on April 28, 2016, 09:08:15 pm
NRS Core/GUI: Free transactions for forgers.

Instead of broadcasting a transaction, add an option to store it until it can be included in a block forged by the node (so the user is paying fees to themselves). This option would be in the Advanced section, and only enabled if the node was forging with at least one account.

By default any account unlocked on the node should be allowed to include the transaction, not just the account that creates the transaction. The transaction would not be broadcast, but stored locally by the node until it forges a block, and then included before other transactions. Ideally the storage would be persistent over stopping and restarting the node. There should be a limit to how long the transaction may be delayed, in case someone uses it when their balance is low. I'd suggest a default of 1440 blocks. This limit would also ensure that the transaction got broadcast even if the node stopped forging (or got stopped and restarted and the user forgot to log in).

Ideally the option would be available when using public nodes and/or offline signing. Perhaps public nodes should be able to force the option on, so they always get the fees for transactions submitted through them. There would need to be some defence against abuse. Limiting the number of stored transactions (eg, to 256) would be a start. It might be nice to have way to nominate a preferred public node, and submit transactions to it even if a local node is running - but that is getting complicated.

The intended benefits are:
People like free stuff.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Riker on April 29, 2016, 08:19:12 am
Thoughts: overall I like the idea, power users can already implement this so why not allow everyone.
You'll have to specify in the transaction that only a specific account can forge it and thereby allow a fee market to form or with less flexibility that just the submitting account can forge it. I don't think allowing any forging account on the node to forge it is a good idea, since any account can start forging on a public node.

If this "pending transaction" is stored in the node's database there should be no problem with node restarts.
In the past this would have enabled whales to squat all the 3 letters currency codes for example but now that we split forging rewards 40:30:20:10 ratio this is not a major concern since they'll still pay 60% of the fee to other forgers.

As to implementation, need to discuss with jean-luc of course, doesn't look too complex to implement. May not even require a hard fork, perhaps even can be implemented as an add-on.
Perhaps there could be security issues with these transaction only revealed at the last moment before forging and not broadcasted to the network as unconfirmed but again there is nothing which prevents someone from implementing this mechanism on a specific forging node now.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: blackyblack1 on April 29, 2016, 08:20:08 am
How should it work? The fee is taken from the sender's account so such transactions won't be free for senders. Does it require the core modification?

Oh they are free only for forgers... Forgers are wealthy guys. Why should they bother for pennies waiting all day to forge own transaction?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Riker on April 29, 2016, 08:21:45 am
How should it work? The fee is taken from the sender's account so such transactions won't be free for senders. Does it require the core modification?

If the sender of the transaction is later also the forger then this transaction is practically free.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: websioux on April 29, 2016, 09:22:50 am
The intended benefits are:
  • Free transactions! Should encourage Nxt use.
  • More incentive to run a forging node.
  • More incentive to run a public node (that also forges).
  • A way for users to reward those who run public nodes, that doesn't cost the user anything they wouldn't have paid anyway.
People like free stuff.

I do not know where you guys see any incentive.

If you'd have a free transaction when you forge, you either already have a lot of Nxt or you "never" have free transactions !
"Hey Bob, Nxt is cool, get 50 000 tokens + a node and then once a week you will have a free transaction ! Cool hey ! 0.007 $ free, take a node !
"People like free stuff." => but they are no stupid. You are just adding +0.1 % to the forging reward (I did not calculate this number but that's how I perceive it).
So yes it is cool from a theoretical perspective (it is natural/logical) but from a practical one, I'm afraid it is completely useless (at least to my point of view it is).

Do what you want, but it is not because you see a benefit that it means it is worth it. With limited ressources, it is even more important to try to focus on the higher return tasks.
However fun things are also good for global devs productivity so...
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Riker on April 29, 2016, 12:33:16 pm
So yes it is cool from a theoretical perspective (it is natural/logical) but from a practical one, I'm afraid it is completely useless (at least to my point of view it is).

One use case can be for a funding monitor which needs to submit a lot of low priority transactions to fund many accounts. Trading bot is another use case or applications which need reduced transaction fees. I also like that this idea can develop into a fee market.
Anyway, I agree it's not high priority at the current market price and activity rate.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: coretechs on April 29, 2016, 01:15:39 pm
Another use is for exchanges with large cold-wallets.  If they forge they can process withdrawals many times a day for free.

It's also very cost-effective for making dividend payouts to multiple accounts.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: websioux on April 29, 2016, 01:41:14 pm
I just realized that there can be MANY free transactions per block forged, not just one, so it's just a LOT more interesting than I initially thought.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on April 29, 2016, 02:04:50 pm
If the free-transaction feature is really easy to add to the Nxt platform I think it would be a nice feature to have, especially for marketing. It nice to promote that you can have free transaction on the network if you hold enough NXT.

@brangdon thanks for the feature request.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: CryptKeeper on May 03, 2016, 09:09:06 am
I think you should have wrote : the buyer sends back...

But yes, it is too much steps. They must bid something and no more.

Did you read my whole suggestion?  Your situation is the same.

You are not obliged to set timing for the end of auction because people can cancel their bid at anytime.

Then for marketing reason you can announce that you will take the highest bid in X days. hours.. You can then program it or do it by hand.


Envoyé de mon GT-I9195 en utilisant Tapatalk

My idea was to make it as "ebay-like" as possible, so sure there must be an auction deadline.

I've tinkered with a program to automatically create a corresponding ask for the highest bid on the deadline, but I'm not sure if this is a safe procedure. Couldn't someone watch auction ask transactions coming up in the mempool and simply inject one bid 0.1 NXT higher than the current highest bid? So he could win every auction!  ???

I think at ebay they call those "snipers".
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: remix on May 07, 2016, 06:32:46 pm
Thoughts: overall I like the idea, power users can already implement this so why not allow everyone.
You'll have to specify in the transaction that only a specific account can forge it and thereby allow a fee market to form or with less flexibility that just the submitting account can forge it.

How about a lower fee for these types of transactions?

An optional parameter in a transaction specifies which account can forge it. Also nodes would refuse to relay transactions which have this parameter set.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Brangdon on May 08, 2016, 12:08:34 pm
You'll have to specify in the transaction that only a specific account can forge it and thereby allow a fee market to form or with less flexibility that just the submitting account can forge it. I don't think allowing any forging account on the node to forge it is a good idea, since any account can start forging on a public node.
Is forging on public nodes an important use case? I hadn't realised people did that.

I was hoping to keep this feature simple to use, and avoiding the need to set the forging account is one way of simplifying it. However, if the forging account defaulted to the account the user has leased their own account to, then much of the time that would do.

Ideally, if you lease your balance to a forging pool, it should be easy to have your transactions forged by that pool. Is there a way to discover which accounts are forging on a node? GetState() returns numberOfUnlockedAccounts, but doesn't seem to list them. We also have hallmarks as a way of mapping nodes to accounts, but that doesn't quite fit here (eg, an account can hallmark many nodes, in which case we don't know which node it is forging on). Maybe this should be presented as a new service, along with HALLMARK and PRUNABLE. Then the user's node could search its peers for the node the forging pool is forging on.

Quote
May not even require a hard fork, perhaps even can be implemented as an add-on.
It was my intention that it be a core change, but not one needing a hard fork.

"People like free stuff." => but they are no stupid. You are just adding +0.1 % to the forging reward (I did not calculate this number but that's how I perceive it).
When the forging account is your own, I'd see it in terms of free transactions rather than increased forging reward. How much it is worth to you depends on how many transactions you make.

If the forging account is a pool, then what it's worth depends on whether people bother to, in effect, donate their fees to it. I will say that at the moment we still have a lot of empty blocks, so if you are forging, say, once a day, then you'll often get zero fees for that day. If you can hold onto transactions and keep them for your own block, you won't be forging empty blocks so long as people are actually sending you their transactions. Even if its only a couple of transactions a day, your forging reward could be doubled or tripled.

I agree that the amounts of money are small. However, I think this could be at least as effective as the NSC currency as a way of rewarding people.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: websioux on May 08, 2016, 01:14:10 pm
I think at ebay they call those "snipers".

Yes, to buy in demand stuff on eBay, you have to use a sniper because somebody else do. And it helps to no succumb the emotional fire that sellers benefit from in the last minutes and even seconds of the auction. This reveals that the auction model used by eBay does not suit a blockchain : the last block will receive all the sniper bids.. so which one win ?

However, this model could work : you set a high price, the first that buy gets it (classical shop sell). But they also set lower prices, that they can cancel when they want, and when you decide, you pick up one. This would bring back balance to the price discovery mechanisms for good & services which I think is necessary in a deflationary monetary system. 

With a price discovery mechanism where only sellers have a voice (they try to sell at the price they choose), economists rapidly discover the benefit of an inflationary monetary system. For a deflationary system to not break the economy, business facilitators need price discovery mechanisms that goes reverse = give voice to buyers.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on May 08, 2016, 01:27:25 pm
I think at ebay they call those "snipers".

Yes, to buy in demand stuff on eBay, you have to use a sniper because somebody else do. And it helps to no succumb the emotional fire that sellers benefit from in the last minutes and even seconds of the auction. This reveals that the auction model used by eBay does not suit a blockchain : the last block will receive all the sniper bids.. so which one win ?

However, this model could work : you set a high price, the first that buy gets it (classical shop sell). But they also set lower prices, that they can cancel when they want, and when you decide, you pick up one. This would bring back balance to the price discovery mechanisms for good & services which I think is necessary in a deflationary monetary system. 

With a price discovery mechanism where only sellers have a voice (they try to sell at the price they choose), economists rapidly discover the benefit of an inflationary monetary system. For a deflationary system to not break the economy, business facilitators need price discovery mechanisms that goes reverse = give voice to buyers.


I guess that if there is sniper on the blockchain, the forger would accept the sniper transaction that set the highest fee. I'm not against that, would that be wrong?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: NxtSwe on May 10, 2016, 07:24:54 am
Ideally, if you lease your balance to a forging pool, it should be easy to have your transactions forged by that pool. Is there a way to discover which accounts are forging on a node? GetState() returns numberOfUnlockedAccounts, but doesn't seem to list them.
getForging with adminPassword will give you what you are looking for.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: NxtSwe on May 19, 2016, 08:29:10 am
NRS Core/GUI: Free transactions for forgers.

Instead of broadcasting a transaction, add an option to store it until it can be included in a block forged by the notde (so the user is paying fees to themselves). This option would be in the Advanced section, and only enabled if the node was forging with at least one account.
...
I came up with a practical example, freemarket could use this feature to make listing/buying items completely free, given they have a forging node with enough stake. The user would have to wait for the node to forge next block, but that's the price you pay instead of using your NXT.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: MrCluster87 on May 22, 2016, 07:31:31 am
Hey, my request should be added to the main software.

I would like to see integrated a crash reporter analyzer that allows me to send the errors directly to developers in a standardized way. In order to don't come to the forum or slack to report them.

To give you an idea this is present in firefox when it closes unexpectedly.

https://support.mozilla.org/en-US/kb/mozillacrashreporter
Title: Re: List of feature request for Nxt and NRS
Post by: Sebastien256 on May 22, 2016, 08:46:35 am
Client GUI: Add a way to link to an account with an URL. For example, clicking on:

http://localhost:7876/index.html?NXT-MRCC-2YLS-8M54-3CMAJ

could open the client with the Genesis account loaded. I would like this to use with bookmarks in my browser, to save a few clicks.


We could go further and have, for example:

http://localhost:7876/index.html?acc=NXT-MRCC-2YLS-8M54-3CMAJ+sendNxt=100+to=NXT-RTYD-LJXQ-EPNJ-H7AQ5+msg=Services+rendered

open the Send NXT page, but this is getting into deeper territory. It'd probably be better to use a more explicit protocol like nxt://... than http. That has been talked about before, although nothing seems to have come of it. I guess reviving that project counts as a separate suggestion.

Looking to update OP, do this feature reqyest were filled, I mean is it now possible to do with Nxt client? Im on the intuition that yes, but im not sure. Thanks.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: blackyblack1 on May 24, 2016, 04:18:35 pm
NXT 2.0 feature request.

Let people create either global or local assets, currencies, aliases. Make global asset issuance 10x-100x more expensive than local assets.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: shmoula on June 13, 2016, 08:15:48 pm
Feature request for asset listing

Nowadays it's impossible to get news for asset except to watch it on third party sites (nxtforum, website etc). It would be nice to have some "news stream" right in the asset listing. I mean either editable asset description, or something like messaging - where asset issuer sends message to some special account and this message gets displayed somewhere in asset description.
Title: Re: List of feature request for NRS
Post by: Sebastien256 on June 24, 2016, 07:34:26 pm
Feature request for asset listing

Nowadays it's impossible to get news for asset except to watch it on third party sites (nxtforum, website etc). It would be nice to have some "news stream" right in the asset listing. I mean either editable asset description, or something like messaging - where asset issuer sends message to some special account and this message gets displayed somewhere in asset description.

News ticker in Asset Page

My dream: accounts that is asset issuer can send a special message to add latest news about the asset. In the UI they appear like this:

(http://i.imgur.com/7VJgKSQ.png)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: neofelis on June 24, 2016, 08:45:31 pm
I think you should have wrote : the buyer sends back...

But yes, it is too much steps. They must bid something and no more.

Did you read my whole suggestion?  Your situation is the same.

You are not obliged to set timing for the end of auction because people can cancel their bid at anytime.

Then for marketing reason you can announce that you will take the highest bid in X days. hours.. You can then program it or do it by hand.


Envoyé de mon GT-I9195 en utilisant Tapatalk

My idea was to make it as "ebay-like" as possible, so sure there must be an auction deadline.

I've tinkered with a program to automatically create a corresponding ask for the highest bid on the deadline, but I'm not sure if this is a safe procedure. Couldn't someone watch auction ask transactions coming up in the mempool and simply inject one bid 0.1 NXT higher than the current highest bid? So he could win every auction!  ???

I think at ebay they call those "snipers".

This is true and I've done it.  The solution is to have the auction end on a certain day but the exact time would be random. I could be 2AM or 9:32PM.  No way to snipe.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: websioux on June 24, 2016, 09:04:58 pm
Feature request for asset listing

Nowadays it's impossible to get news for asset except to watch it on third party sites (nxtforum, website etc). It would be nice to have some "news stream" right in the asset listing. I mean either editable asset description, or something like messaging - where asset issuer sends message to some special account and this message gets displayed somewhere in asset description.

News ticker in Asset Page

My dream: accounts that is asset issuer can send a special message to add latest news about the asset. In the UI they appear like this:

(http://i.imgur.com/7VJgKSQ.png)
Sounds like a good plugin. Issuer publish a public message. Plugin scan for these messages and publish div content accordingly. Main work is to define the message format such that it is convenient to use for other stuff as well.

Once plugin gets concensus it goes default within client.

We must build more plugins guys. Client plugins are to Nxt client what apps are to iPhone!  This is really where the value  of the disrupting tech gets revealed.

This one is a good project, I suggest to call it : Feed Profile
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: NxtSwe on June 26, 2016, 12:10:09 pm
Sounds like a good plugin. Issuer publish a public message. Plugin scan for these messages and publish div content accordingly. Main work is to define the message format such that it is convenient to use for other stuff as well.

Once plugin gets concensus it goes default within client.

We must build more plugins guys. Client plugins are to Nxt client what apps are to iPhone!  This is really where the value  of the disrupting tech gets revealed.

This one is a good project, I suggest to call it : Feed Profile
A bit offtopic but posting here for visibility.
https://nxtforum.org/nxt-plugins/asset-feeds/
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Brangdon on July 14, 2016, 07:10:22 pm
The ability to initiate forging even though blockchain is not downloaded would be nice.
I understand that NRS cannot forge until it has the full blockchain, but it could accept the password and display a message like: "forging will start once the blockchain is downloaded".
Auto-forging: it would be nice if we could initiate forging from an entry in the nxt.properties file, so it always happens when the node starts.

(Obviously using leased balances so that the pass phrase in the file is from a low balance account.)
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: MrCluster87 on July 18, 2016, 09:42:13 am
Hi!!

If this is true: https://bitcointalk.org/index.php?topic=1518497.msg15597185#msg15597185

can you please change the name "EffectiveBalance" in forging power in the NRS wallet. It would more intuitive this way.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: OutSL on July 31, 2016, 12:05:01 pm
Hello World  :D

Title : Add new API Function - CreateAccount
Category : Core.

Description:
this API function is for the account creation by some external applications allowing the injection of costom data (applications data) in the operation.
this function is similar to the getAccountId but in addition, there will be some additional values in the request, eg;
http://localhost:7876/nxt?requestType=CreateAccount&secretPhrase=IWontTellYou&optional=some_data&optional1=some_other_data&optional2=more_data...
can up to 5 or more optional fields... the first optional field/data have to act like a primary key and have/need the same level as the account RS eg;
to get some data from the blockchain relative to an account created with this function you can use the first optional as marker...
http://localhost:7876/nxt?requestType=getAccount&optional=some_data
will return the same as
http://localhost:7876/nxt?requestType=getAccount&account=NXT-4VNQ-RWZC-4WWQ-GVM8S
if the optional some_data was linked to the NXT-4VNQ-RWZC-4WWQ-GVM8S account...

in my specific case i need a way to link an NXT account to an opensim account by storing some data in the blockchain see here what kind of data (Universal User Identifier (UUI)):
https://www.ics.uci.edu/~lopes/opensim/HypergridReferenceGuide.html#MainTypes

storing the avatar's Universal User Identifier (UUI) in the blockchain will allow the cross grids and an avatar will have/use a single hot wallet everywhere in the metaverse (where my module is working)

Thank you and @++
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Riker on July 31, 2016, 12:48:22 pm
Hello World  :D

Title : Add new API Function - CreateAccount
Category : Core.

Description:
this API function is for the account creation by some external applications allowing the injection of costom data (applications data) in the operation.
this function is similar to the getAccountId but in addition, there will be some additional values in the request, eg;
http://localhost:7876/nxt?requestType=CreateAccount&secretPhrase=IWontTellYou&optional=some_data&optional1=some_other_data&optional2=more_data...
can up to 5 or more optional fields... the first optional field/data have to act like a primary key and have/need the same level as the account RS eg;
to get some data from the blockchain relative to an account created with this function you can use the first optional as marker...
http://localhost:7876/nxt?requestType=getAccount&optional=some_data
will return the same as
http://localhost:7876/nxt?requestType=getAccount&account=NXT-4VNQ-RWZC-4WWQ-GVM8S
if the optional some_data was linked to the NXT-4VNQ-RWZC-4WWQ-GVM8S account...

in my specific case i need a way to link an NXT account to an opensim account by storing some data in the blockchain see here what kind of data (Universal User Identifier (UUI)):
https://www.ics.uci.edu/~lopes/opensim/HypergridReferenceGuide.html#MainTypes

storing the avatar's Universal User Identifier (UUI) in the blockchain will allow the cross grids and an avatar will have/use a single hot wallet everywhere in the metaverse (where my module is working)

Thank you and @++

You can set an account property for this purpose. Look at the "Account Properties" UI under the dashboard and the corresponding account properties APIs.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Jean-Luc on July 31, 2016, 12:51:31 pm
Right, you could do something like that using account properties. Store the key to retrieve an account as property names, the account ids as property values, all for a single account to which you know the secret phrase and is used to hold those properties. The limitation is that property name length is limited to 32 chars (and those are strings, not binary data). You may need some additional mapping of longer UUI's to such strings.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: OutSL on July 31, 2016, 01:06:51 pm
Hello World  :D

Title : Add new API Function - CreateAccount
Category : Core.

Description:
this API function is for the account creation by some external applications allowing the injection of costom data (applications data) in the operation.
this function is similar to the getAccountId but in addition, there will be some additional values in the request, eg;
http://localhost:7876/nxt?requestType=CreateAccount&secretPhrase=IWontTellYou&optional=some_data&optional1=some_other_data&optional2=more_data...
can up to 5 or more optional fields... the first optional field/data have to act like a primary key and have/need the same level as the account RS eg;
to get some data from the blockchain relative to an account created with this function you can use the first optional as marker...
http://localhost:7876/nxt?requestType=getAccount&optional=some_data
will return the same as
http://localhost:7876/nxt?requestType=getAccount&account=NXT-4VNQ-RWZC-4WWQ-GVM8S
if the optional some_data was linked to the NXT-4VNQ-RWZC-4WWQ-GVM8S account...

in my specific case i need a way to link an NXT account to an opensim account by storing some data in the blockchain see here what kind of data (Universal User Identifier (UUI)):
https://www.ics.uci.edu/~lopes/opensim/HypergridReferenceGuide.html#MainTypes

storing the avatar's Universal User Identifier (UUI) in the blockchain will allow the cross grids and an avatar will have/use a single hot wallet everywhere in the metaverse (where my module is working)

Thank you and @++

You can set an account property for this purpose. Look at the "Account Properties" UI under the dashboard and the corresponding account properties APIs.

yes i explored this way but this requiere 2 operations, (1) create the account and (2) set the account infos (not free)...
the suggested function do that in 1 time at the moment of the account creation... and the optional data can be hidden or visible but the user can't modify or alter it... like the account RS... when created you can't change it in the same account/public key...

this function will allow the applications to create a hidden accounts for the users without giving the passphrase like the exchanges hot wallets... and store some data in the blockchain in same time, like the application user ID and others...

Thank you and @++
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on December 10, 2016, 11:27:46 am
A link to the plugin would be usefull I think. Seems to me like a nice work. Unfortunally, no bounty on this afaik.

Since the NXT 2.0 conversation started, I haven't worked much on the plugin, but it should be working and can be found here:
https://github.com/mrv777/NXT_asset_analysis

MrV777, could you pls update your plugin?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on December 10, 2016, 11:30:00 am
Is this thread completely abandoned and none of the features will be implemented in NXT?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on December 10, 2016, 11:32:16 am
The thread is not abandoned, but clearly not use much these days.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on December 10, 2016, 11:39:26 am
What about future days?
Any ways or any chance to get this enhancements done?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on December 10, 2016, 11:57:10 am
What about future days?
Any ways or any chance to get this enhancements done?

Only core devs can answer this or MrV777 in this particular case.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Riker on December 12, 2016, 06:38:55 am
A link to the plugin would be usefull I think. Seems to me like a nice work. Unfortunally, no bounty on this afaik.

Since the NXT 2.0 conversation started, I haven't worked much on the plugin, but it should be working and can be found here:
https://github.com/mrv777/NXT_asset_analysis

MrV777, could you pls update your plugin?

The problem with this plugin is that the charting module is based on a commercial product from http://www.highcharts.com/
There is a free license for "Non-commercial" applications, but can you really define NXT as "Non-commercial" ?
To integrate it into the core we'll need to replace the charting module with a real open source alternative.

Having said that, what is wrong with using the plugin as is?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on December 12, 2016, 11:00:11 am
I can't make it work now, and it needs to be maintained by thirdparty dev when changes occurs:/

So, you agree to integrate some nice AE charting into the core if it is open-source, right?
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Jean-Luc on January 24, 2017, 11:20:16 pm
A017. 2015-07-28. Allow AE issuer use Asset to make dividends payment in another Asset.
A006. 2015-06-16. Allow AE issuer use MS to dividends payment.

Those two are already implemented in Ardor.

Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on January 24, 2017, 11:25:45 pm
A017. 2015-07-28. Allow AE issuer use Asset to make dividends payment in another Asset.
A006. 2015-06-16. Allow AE issuer use MS to dividends payment.

Those two are already implemented in Ardor.

Hi JL, thanks for this input and reviving this topic  :)
I will update OP.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on January 24, 2017, 11:28:57 pm
Btw, these are great additions, it nice to see that the AE is support and being develloped!
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Jean-Luc on January 25, 2017, 08:33:06 am
Of course the AE is being developed, it is one of our most important components. One major improvement is that the limitation on number of decimal places is gone, but this required changing the way order prices are defined, they are now in NQT per share of the asset instead of NQT per QNT.

Next is allowing editable asset descriptions and increasing number of shares, this may be done after testnet launch though.
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: xcn on January 27, 2017, 09:22:23 am
Don't really want to bother you, you're doing great, but what about AE charts?
Title: Re: List of feature request for Ardor, Ignis, and Nxt (with the full list in OP)
Post by: Sebastien256 on May 09, 2017, 08:10:25 pm
Updated topic subjects to :
List of feature request for Ardor, Ignis, and Nxt (with the full list in OP)

Do not hesitate to post your feature request  :)
Title: Re: List of feature request for Ardor, Ignis, and Nxt (with the full list in OP)
Post by: silverblade07 on May 10, 2017, 06:26:23 am
Thanks for the update, Everything seems clean, How about making it look more categorised?
Title: Re: List of feature request for Ardor, Ignis, and Nxt (with the full list in OP)
Post by: TheWireMaster on May 25, 2017, 05:21:18 am
Suggestion: would it be possible to add to the bundler setup page something like a slider for the settings? Showing the Ardor fees and corresponding childchain fees dynamically when you move the slider? Not sure how to then set the ranges, but I think it would help:
http://www.html5tutorial.info/html5-range.php
I've post it also here:
https://nxtchat.slack.com/archives/C0XP71MBL/p1495655399561693
Title: Re: List of feature request for Ardor, Ignis, and Nxt (with the full list in OP)
Post by: marenkar on May 26, 2017, 09:47:39 pm
One of the developers from Adel mentioned that if he clicked the "Approve" button on the transaction approval multiple times, they would all go through and be charged 1 NXT per approval. Perhaps the "Approve" button can be removed after the user clicks it? Or maybe make it unable for them to click it again?

Their transaction IDs : 8417111258393153200, 4819137358901398901, and 6744435325057202220
Title: Re: List of feature request for Nxt and NRS (with the full list in OP)
Post by: Sebastien256 on July 29, 2017, 06:15:34 pm
Installer request:

Archive Nxt node check box in the Nxt installer setup.

When installing Nxt, make it possible to setup Nxt as a achival node. That should be simple as possible to install archive node, i.e. just check a box in the installation process. That will certainly promote archive node and this request is very easy to be done, i think. Overall, this feature request, once implement, will promote decentralization of Nxt archive data.

I just saw that light client option is available now in the installer. This is great. It would be nice if the archival option would also be available. Keep up the good work.
Title: Re: List of feature request for Ardor, Ignis, and Nxt (with the full list in OP)
Post by: Right.Here on September 19, 2017, 05:53:58 pm
Hi there  :D

Title : suggestion of relooking of the lockscreen interface.
Category : UI.
Platform : All.

a nice background using HTML5 / JS I found on the internet, I tested it and it gave a nice result...

if you want to try it, do the following:
1) create an empty javascript file .js here :
...\nxt\html\www\js\3rdparty\particles_matrix.js
2) Copy/paste/save the following code in the particles_matrix.js file :
Code: [Select]
//Particles Script from : http://cssdeck.com/labs/html5-canvas-particles-web-matrix
// RequestAnimFrame: a browser API for getting smooth animations

window.requestAnimFrame = (function(){
  return  window.requestAnimationFrame       ||
  window.webkitRequestAnimationFrame ||
  window.mozRequestAnimationFrame    ||
  window.oRequestAnimationFrame      ||
  window.msRequestAnimationFrame     || 
  function( callback ){
window.setTimeout(callback, 1000 / 60);
  };
})();

// Initializing the canvas
// I am using native JS here, but you can use jQuery,
// Mootools or anything you want
var canvas = document.getElementById("canvas");

// Initialize the context of the canvas
var ctx = canvas.getContext("2d");

// Set the canvas width and height to occupy full window
var W = window.innerWidth, H = window.innerHeight;
canvas.width = W;
canvas.height = H;

// Some variables for later use
var particleCount = 100,
particles = [],
minDist = 100,
dist;


// Now the idea is to create some particles that will attract
// each other when they come close. We will set a minimum
// distance for it and also draw a line when they come
// close to each other.

// The attraction can be done by increasing their velocity as
// they reach closer to each other

// Let's make a function that will act as a class for
// our particles.

function Particle() {
// Position them randomly on the canvas
// Math.random() generates a random value between 0
// and 1 so we will need to multiply that with the
// canvas width and height.
this.x = Math.random() * W;
this.y = Math.random() * H;


// We would also need some velocity for the particles
// so that they can move freely across the space
this.vx = -1 + Math.random() * 2;
this.vy = -1 + Math.random() * 2;

// Now the radius of the particles. I want all of
// them to be equal in size so no Math.random() here..
this.radius = 2;

// This is the method that will draw the Particle on the
// canvas. It is using the basic fillStyle, then we start
// the path and after we use the `arc` function to
// draw our circle. The `arc` function accepts four
// parameters in which first two depicts the position
// of the center point of our arc as x and y coordinates.
// The third value is for radius, then start angle,
// end angle and finally a boolean value which decides
// whether the arc is to be drawn in counter clockwise or
// in a clockwise direction. False for clockwise.
this.draw = function() {
ctx.fillStyle = "white";
ctx.beginPath();
ctx.arc(this.x, this.y, this.radius, 0, Math.PI * 2, false);

// Fill the color to the arc that we just created
ctx.fill();
}
}

// Time to push the particles into an array
for(var i = 0; i < particleCount; i++) {
particles.push(new Particle());
}

// Function to draw everything on the canvas that we'll use when
// animating the whole scene.
function draw() {

// Call the paintCanvas function here so that our canvas
// will get re-painted in each next frame


// Call the function that will draw the balls using a loop
for (var i = 0; i < particles.length; i++) {
p = particles[i];
p.draw();
}

//Finally call the update function
update();
}

// Give every particle some life
function update() {

// In this function, we are first going to update every
// particle's position according to their velocities
for (var i = 0; i < particles.length; i++) {
p = particles[i];

// Change the velocities
p.x += p.vx;
p.y += p.vy

// We don't want to make the particles leave the
// area, so just change their position when they
// touch the walls of the window
if(p.x + p.radius > W)
p.x = p.radius;

else if(p.x - p.radius < 0) {
p.x = W - p.radius;
}

if(p.y + p.radius > H)
p.y = p.radius;

else if(p.y - p.radius < 0) {
p.y = H - p.radius;
}

// Now we need to make them attract each other
// so first, we'll check the distance between
// them and compare it to the minDist we have
// already set

// We will need another loop so that each
// particle can be compared to every other particle
// except itself
for(var j = i + 1; j < particles.length; j++) {
p2 = particles[j];
distance(p, p2);
}

}
}

// Distance calculator between two particles
function distance(p1, p2) {
var dist,
dx = p1.x - p2.x,
dy = p1.y - p2.y;

dist = Math.sqrt(dx*dx + dy*dy);

// Draw the line when distance is smaller
// then the minimum distance
if(dist <= minDist) {

// Draw the line
ctx.beginPath();
ctx.strokeStyle = "rgba(255,255,255,"+ (1.2-dist/minDist) +")";
ctx.moveTo(p1.x, p1.y);
ctx.lineTo(p2.x, p2.y);
ctx.stroke();
ctx.closePath();

// Some acceleration for the partcles
// depending upon their distance
var ax = dx/2000,
ay = dy/2000;

// Apply the acceleration on the particles
p1.vx -= ax;
p1.vy -= ay;

p2.vx += ax;
p2.vy += ay;
}
}

// Start the main animation loop using requestAnimFrame
function animloop() {
draw();
requestAnimFrame(animloop);
}

animloop();

3) Now we have to add our HTML5 canvas to the lockscreen.html here:
...\nxt\html\www\html\lockscreen.html
right after the copyright section , copy/paste the following lines :

Code: [Select]
<script src="js/3rdparty/particles_matrix.js"></script>
<canvas id="canvas" style="width:100%;height:100%;position:absolute;display:block;z-index:0;opacity: .5;"></canvas>

AND! you have to add the style in the next line like this :
Code: [Select]
<div id="lockscreen" class="loading" style="position:relative;">

(before was)
Code: [Select]
<div id="lockscreen" class="loading">

that it  :D if you did it correctly, logout to see the lockscreen...  ;D
Thank you and BigZouuu!
Title: Re: List of feature request for Ardor, Ignis, and Nxt (with the full list in OP)
Post by: Sebastien256 on October 02, 2017, 08:37:41 pm
@Right.Here
Thank you for your input. I have update the OP.

This topic is not active as it once was. Please people, continue to give and share new ideas!  ;D
Title: Re: List of feature request for Ardor, Ignis, and Nxt (with the full list in OP)
Post by: Brangdon on January 08, 2018, 11:31:44 am
GUI request: way to resolve forks.

Currently I believe the way to resolve a fork is to use the test API to popoff blocks back to the common ancestor. It would be good if this could be integrated into the main GUI somehow. A better interface might be to let the user specify a block height and block ID of the side of fork they want to be on, and let the system work out how many blocks to pop off. Better still might be for the user to identify the node whose forks they want to follow, and let the system work out the block. Especially if nodes were named dependably.

This would essentially be progressing the Economic Clusters feature, which at the moment seems half-done. (Transactions specify the EC block, but the user can't say which economic cluster they want to belong to.)
Title: Re: List of feature request for Ardor, Ignis, and Nxt (with the full list in OP)
Post by: Right.Here on April 21, 2018, 06:23:24 pm
Hi  :D

after reading in our favorite magazine nxter.org (http://www.nxter.org) that there will be a big UI relooking, I decided to share my modest work in the hope that will be useful and may be will add some green in my account ;D ;D ;D ;D

well, this is the codes for NXT (only) marketplace, i will publish the codes for the NBCK in its relative topic here
https://nxtforum.org/nxt-blockchain-creation-kit/dgs-optimizations/

to try, download NXT-DGS.zip from here (link in green):
http://s000.tinyupload.com/index.php?file_id=28137852009882414436

extract it (to folder) you will find 3 files, you just have to:
- remove nrs.dgs.js file here
...\nxt\html\www\js\nrs.dgs.js
and replace it with the file from the zip file

- remove the dgs.html here :
...\nxt\html\www\html\pages\dgs.html
and replace it with the file from the zip file

- open the "add.to.app.css" file with a text editor or an IDE and copy paste the lines in it to
...\nxt\html\www\css\app.css
at the very end of the file after the last }

clean your browser cache... refresh the wallet and open the DGS  :D

enjoy and good continuation  :D
Title: Re: List of feature request for Ardor, Ignis, and Nxt (with the full list in OP)
Post by: jonnytracker on January 01, 2019, 04:09:45 am
It works on my Blockchain creation kit clone ?
elective-stereophonic
elective-stereophonic
assembly
assembly