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 ... 15 16 [17] 18 19 20  All

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

lopalcar

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

Tosch110

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

Tosch110

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

Jose

  • Global Moderator
  • Hero Member
  • *****
  • Karma: +78/-1
  • Offline Offline
  • Posts: 509
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #323 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.
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 #324 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.
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).

websioux

  • Sr. Member
  • ****
  • Karma: +69/-1
  • Offline Offline
  • Posts: 343
  • Great changes grow bottom up
    • View Profile
    • Scriba.io the Blockchain Scribe
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #325 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

Logged
Secret Miner <= communicate with style | NotBot <= timestamp digital docs

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 #326 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.
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).

websioux

  • Sr. Member
  • ****
  • Karma: +69/-1
  • Offline Offline
  • Posts: 343
  • Great changes grow bottom up
    • View Profile
    • Scriba.io the Blockchain Scribe
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #327 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

Logged
Secret Miner <= communicate with style | NotBot <= timestamp digital docs

testdruif

  • Full Member
  • ***
  • Karma: +71/-1
  • Offline Offline
  • Posts: 223
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #328 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 %
Logged
**Necessity is the mother of invention**
NXT-NNGD-V8TN-3MZR-DWWBE
https://arguseyes.net

websioux

  • Sr. Member
  • ****
  • Karma: +69/-1
  • Offline Offline
  • Posts: 343
  • Great changes grow bottom up
    • View Profile
    • Scriba.io the Blockchain Scribe
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #329 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 ?

Logged
Secret Miner <= communicate with style | NotBot <= timestamp digital docs

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 #330 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.
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).

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

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +439/-42
  • Offline Offline
  • Posts: 1796
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #332 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.
Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

LocoMB

  • Hero Member
  • *****
  • Karma: +101/-37
  • Offline Offline
  • Posts: 751
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #333 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?
Logged
TOX
90E54E5B5213290EE616D425CADC473038CFABFA53C913271AA8559D1937DC4AF3A354A9E4E5

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 #334 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:
  • 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.
« Last Edit: April 29, 2016, 07:29:24 am by Brangdon »
Logged

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +439/-42
  • Offline Offline
  • Posts: 1796
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #335 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.
Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

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 #336 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?
Logged

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +439/-42
  • Offline Offline
  • Posts: 1796
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #337 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.
Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

websioux

  • Sr. Member
  • ****
  • Karma: +69/-1
  • Offline Offline
  • Posts: 343
  • Great changes grow bottom up
    • View Profile
    • Scriba.io the Blockchain Scribe
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #338 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...
Logged
Secret Miner <= communicate with style | NotBot <= timestamp digital docs

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +439/-42
  • Offline Offline
  • Posts: 1796
    • View Profile
Re: List of feature request for Nxt and NRS (with the full list in OP)
« Reply #339 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.
« Last Edit: April 29, 2016, 01:23:56 pm by Riker »
Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651
Pages: 1 ... 15 16 [17] 18 19 20  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly