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 2 [3] 4 5 ... 20  All

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

allwelder

  • Hero Member
  • *****
  • Karma: +196/-13
  • Offline Offline
  • Posts: 1867
  • NxtChina.org
    • View Profile
    • NxtChina.org
Re: List of feature request for NRS
« Reply #40 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.

« Last Edit: June 16, 2015, 05:11:42 am by allwelder »
Logged
NxtChina |Weibo |Twitter Donation welcomed:NXT-APL9-66GU-K8LY-B3JJJ

Roiman

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

capodieci

  • Hero Member
  • *****
  • Karma: +256/-19
  • Offline Offline
  • Posts: 1387
  • BlockchainZoo.com
    • View Profile
    • ZooBC - Advancing Blockchain Technology
Re: List of feature request for NRS
« Reply #42 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:



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.



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
« Last Edit: June 16, 2015, 02:04:06 pm by capodieci »
Logged
- Decentralised Business Network: DeBuNe -
Will be implemented on
ZooBC.com - Join the forum ZooBC.org - By Blockchain Zoo

Sebastien256

  • Hero Member
  • *****
  • Karma: +169/-24
  • Offline Offline
  • Posts: 2823
  • ^LOOK UP^ = Nxt community!
    • View Profile
Re: List of feature request for NRS
« Reply #43 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.
« Last Edit: June 16, 2015, 01:41:31 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).

capodieci

  • Hero Member
  • *****
  • Karma: +256/-19
  • Offline Offline
  • Posts: 1387
  • BlockchainZoo.com
    • View Profile
    • ZooBC - Advancing Blockchain Technology
Re: List of feature request for NRS
« Reply #44 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 :'(
Logged
- Decentralised Business Network: DeBuNe -
Will be implemented on
ZooBC.com - Join the forum ZooBC.org - By Blockchain Zoo

Sebastien256

  • Hero Member
  • *****
  • Karma: +169/-24
  • Offline Offline
  • Posts: 2823
  • ^LOOK UP^ = Nxt community!
    • View Profile
Re: List of feature request for NRS
« Reply #45 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  :)
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).

capodieci

  • Hero Member
  • *****
  • Karma: +256/-19
  • Offline Offline
  • Posts: 1387
  • BlockchainZoo.com
    • View Profile
    • ZooBC - Advancing Blockchain Technology
Re: List of feature request for NRS
« Reply #46 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 :)
Logged
- Decentralised Business Network: DeBuNe -
Will be implemented on
ZooBC.com - Join the forum ZooBC.org - By Blockchain Zoo

verymuchso

  • Hero Member
  • *****
  • Karma: +118/-2
  • Offline Offline
  • Posts: 549
    • View Profile
    • HEAT Ledger
Re: List of feature request for NRS
« Reply #47 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.
Logged
HEAT: DEX | SDK | HOME

blackyblack1

  • Hero Member
  • *****
  • Karma: +165/-82
  • Offline Offline
  • Posts: 1764
    • View Profile
Re: List of feature request for NRS
« Reply #48 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.
Logged

verymuchso

  • Hero Member
  • *****
  • Karma: +118/-2
  • Offline Offline
  • Posts: 549
    • View Profile
    • HEAT Ledger
Re: List of feature request for NRS
« Reply #49 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  ;)
Logged
HEAT: DEX | SDK | HOME

xivba

  • Full Member
  • ***
  • Karma: +14/-2
  • Offline Offline
  • Posts: 127
    • View Profile
Re: List of feature request for NRS
« Reply #50 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.
Logged
NXT-33DU-8Q49-R2LY-FQRTG

Tosch110

  • Ex-Staff Member
  • Hero Member
  • *****
  • Karma: +211/-18
  • Offline Offline
  • Posts: 2365
    • View Profile
Re: List of feature request for NRS
« Reply #51 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?

xivba

  • Full Member
  • ***
  • Karma: +14/-2
  • Offline Offline
  • Posts: 127
    • View Profile
Re: List of feature request for NRS
« Reply #52 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.
Logged
NXT-33DU-8Q49-R2LY-FQRTG

qq2536007339

  • Hero Member
  • *****
  • Karma: +42/-9
  • Offline Offline
  • Posts: 514
    • View Profile
Re: List of feature request for NRS
« Reply #53 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.
Logged
你送我阿朵,我是要的。ARDOR-DJ68-PG7W-4JEU-2LU5T

verymuchso

  • Hero Member
  • *****
  • Karma: +118/-2
  • Offline Offline
  • Posts: 549
    • View Profile
    • HEAT Ledger
Re: List of feature request for NRS
« Reply #54 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.
Logged
HEAT: DEX | SDK | HOME

verymuchso

  • Hero Member
  • *****
  • Karma: +118/-2
  • Offline Offline
  • Posts: 549
    • View Profile
    • HEAT Ledger
Re: List of feature request for NRS
« Reply #55 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.
Logged
HEAT: DEX | SDK | HOME

blackyblack1

  • Hero Member
  • *****
  • Karma: +165/-82
  • Offline Offline
  • Posts: 1764
    • View Profile
Re: List of feature request for NRS
« Reply #56 on: June 17, 2015, 09:56:49 am »

And? Did you spot it? I'll explain if you wish.
Ok explain it.
Logged

verymuchso

  • Hero Member
  • *****
  • Karma: +118/-2
  • Offline Offline
  • Posts: 549
    • View Profile
    • HEAT Ledger
Re: List of feature request for NRS
« Reply #57 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.
Logged
HEAT: DEX | SDK | HOME

blackyblack1

  • Hero Member
  • *****
  • Karma: +165/-82
  • Offline Offline
  • Posts: 1764
    • View Profile
Re: List of feature request for NRS
« Reply #58 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.
Logged

verymuchso

  • Hero Member
  • *****
  • Karma: +118/-2
  • Offline Offline
  • Posts: 549
    • View Profile
    • HEAT Ledger
Re: List of feature request for NRS
« Reply #59 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.
Logged
HEAT: DEX | SDK | HOME
Pages: 1 2 [3] 4 5 ... 20  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly