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

Login with username, password and session length
Advanced search  

News:

Latest Stable Nxt Client: Nxt 1.12.1 Upgrade before block 2870000 is mandatory!

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

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

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 #180 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.
Logged
Check out the NxtLib, the .NET Framework API for the Nxt platform.

martismartis

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

SonsofCrypto

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

Seccour

  • Sr. Member
  • ****
  • Karma: +68/-15
  • Offline Offline
  • Posts: 380
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #184 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.
Logged
SecFund : 9125535795764729261 (Asset ID)

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 #185 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. Direct trade/exchange between MSCoin_1 and MSCoin_2, or between Asset_1 and Asset_2.
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).

Seccour

  • Sr. Member
  • ****
  • Karma: +68/-15
  • Offline Offline
  • Posts: 380
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #186 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. Direct trade/exchange between MSCoin_1 and MSCoin_2, or between Asset_1 and Asset_2.

Do you know why it will not be done in the core ? I don't see any explanation...
Logged
SecFund : 9125535795764729261 (Asset ID)

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 #187 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. Direct trade/exchange between MSCoin_1 and MSCoin_2, or between Asset_1 and Asset_2.

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

I don't.
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).

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 #188 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. Direct trade/exchange between MSCoin_1 and MSCoin_2, or between Asset_1 and Asset_2.
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.
Logged

barbierir

  • Sr. Member
  • ****
  • Karma: +36/-2
  • Offline Offline
  • Posts: 316
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #189 on: November 01, 2015, 08:12:41 am »

GUI feature: button to download the trade history as a .csv file
Logged

MrCluster87

  • Hero Member
  • *****
  • Karma: +81/-3
  • Offline Offline
  • Posts: 855
    • View Profile
    • youtube
« Last Edit: November 09, 2015, 11:03:44 am by MrCluster87 »
Logged

doppelganger

  • Jr. Member
  • **
  • Karma: +2/-0
  • Offline Offline
  • Posts: 15
    • View Profile
Re: List of feature request for Nxt and NRS
« Reply #191 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.
Logged

remix

  • Jr. Member
  • **
  • Karma: +18/-2
  • Offline Offline
  • Posts: 90
    • View Profile
Re: List of feature request for Nxt and NRS
« Reply #192 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.
Logged

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 #193 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.
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 #194 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?
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).

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 #195 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.
Logged

allwelder

  • Hero Member
  • *****
  • Karma: +196/-13
  • Offline Offline
  • Posts: 1867
  • NxtChina.org
    • View Profile
    • NxtChina.org
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #196 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.
Logged
NxtChina |Weibo |Twitter Donation welcomed:NXT-APL9-66GU-K8LY-B3JJJ

Ludom

  • Hero Member
  • *****
  • Karma: +197/-15
  • Offline Offline
  • Posts: 1733
    • View Profile
    • Plaisir & Valeur d'histoire
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #197 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.
Logged
Support us to publish "The first book about Nxt"

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 #198 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)
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

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 #199 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
Logged
Check out the NxtLib, the .NET Framework API for the Nxt platform.
Pages: 1 ... 8 9 [10] 11 12 ... 20  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly