elective-stereophonic
elective-stereophonic
List of feature request for Ardor, Ignis, and Nxt (with the full list in OP)
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Nxt Client: Nxt 1.11.15

Pages: 1 ... 9 10 [11] 12 13 ... 20  All

Author Topic: List of feature request for Ardor, Ignis, and Nxt (with the full list in OP)  (Read 132749 times)

OutSL

  • Sr. Member
  • ****
  • Karma: +60/-0
  • Offline Offline
  • Posts: 332
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #200 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 @+
« Last Edit: November 12, 2015, 07:37:39 pm by OutSL »
Logged
Thank you for your financial help, your donations will be used in the R&D related to the implementation of NXT in the virtual worlds running under OpenSimulator.org | Donations Box : NXT-PC8Q-ZW86-7UYK-CC4XJ
Visit The NXT Community Virtal World! Your NXT 3D Chat Service

blackyblack1

  • Hero Member
  • *****
  • Karma: +165/-82
  • Offline Offline
  • Posts: 1764
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #201 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.
« Last Edit: November 15, 2015, 10:12:54 pm by blackyblack1 »
Logged

NxtSwe

  • Hero Member
  • *****
  • Karma: +124/-9
  • Offline Offline
  • Posts: 657
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #202 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*
Logged
Check out the NxtLib, the .NET Framework API for the Nxt platform.

Sebastien256

  • Hero Member
  • *****
  • Karma: +169/-24
  • Offline Offline
  • Posts: 2823
  • ^LOOK UP^ = Nxt community!
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #203 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.
« Last Edit: November 17, 2015, 08:22:10 pm by Sebastien256 »
Logged
Please drop your ideas concerning Nxt and/or NRS in this topic -> List of feature request for Nxt and/or NRS (with the full list in OP).

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #204 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.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

Sebastien256

  • Hero Member
  • *****
  • Karma: +169/-24
  • Offline Offline
  • Posts: 2823
  • ^LOOK UP^ = Nxt community!
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #205 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.
« Last Edit: November 17, 2015, 09:54:48 pm by Sebastien256 »
Logged
Please drop your ideas concerning Nxt and/or NRS in this topic -> List of feature request for Nxt and/or NRS (with the full list in OP).

Brangdon

  • Hero Member
  • *****
  • Karma: +229/-25
  • Offline Offline
  • Posts: 1389
  • Quality is addictive.
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #206 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.)
Logged

crimi

  • Hero Member
  • *****
  • Karma: +122/-11
  • Offline Offline
  • Posts: 863
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #207 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?
« Last Edit: November 21, 2015, 09:12:12 pm by crimi »
Logged

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #208 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.
« Last Edit: November 21, 2015, 06:14:25 pm by Jean-Luc »
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

crimi

  • Hero Member
  • *****
  • Karma: +122/-11
  • Offline Offline
  • Posts: 863
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #209 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?
« Last Edit: November 21, 2015, 06:59:03 pm by crimi »
Logged

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #210 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?
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

crimi

  • Hero Member
  • *****
  • Karma: +122/-11
  • Offline Offline
  • Posts: 863
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #211 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
Logged

qq2536007339

  • Hero Member
  • *****
  • Karma: +42/-9
  • Offline Offline
  • Posts: 514
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #212 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.
« Last Edit: November 24, 2015, 08:15:07 am by qq2536007339 »
Logged
你送我阿朵,我是要的。ARDOR-DJ68-PG7W-4JEU-2LU5T

ifinta

  • Jr. Member
  • **
  • Karma: +19/-0
  • Offline Offline
  • Posts: 88
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #213 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".
Logged

Sebastien256

  • Hero Member
  • *****
  • Karma: +169/-24
  • Offline Offline
  • Posts: 2823
  • ^LOOK UP^ = Nxt community!
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #214 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?
Logged
Please drop your ideas concerning Nxt and/or NRS in this topic -> List of feature request for Nxt and/or NRS (with the full list in OP).

Brangdon

  • Hero Member
  • *****
  • Karma: +229/-25
  • Offline Offline
  • Posts: 1389
  • Quality is addictive.
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #215 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.
Logged

crimi

  • Hero Member
  • *****
  • Karma: +122/-11
  • Offline Offline
  • Posts: 863
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #216 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.
« Last Edit: November 25, 2015, 09:56:23 pm by crimi »
Logged

Sebastien256

  • Hero Member
  • *****
  • Karma: +169/-24
  • Offline Offline
  • Posts: 2823
  • ^LOOK UP^ = Nxt community!
    • View Profile
Logged
Please drop your ideas concerning Nxt and/or NRS in this topic -> List of feature request for Nxt and/or NRS (with the full list in OP).

TwinWinNerD

  • Hero Member
  • *****
  • Karma: +222/-116
  • Offline Offline
  • Posts: 2012
  • CEO BitPanda.com
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #218 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

Sebastien256

  • Hero Member
  • *****
  • Karma: +169/-24
  • Offline Offline
  • Posts: 2823
  • ^LOOK UP^ = Nxt community!
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #219 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. Direct trade/exchange between MSCoin_1 and MSCoin_2, or between Asset_1 and Asset_2.

You need to convince him, I would say.
Logged
Please drop your ideas concerning Nxt and/or NRS in this topic -> List of feature request for Nxt and/or NRS (with the full list in OP).
Pages: 1 ... 9 10 [11] 12 13 ... 20  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly