elective-stereophonic
elective-stereophonic
A relatively simple feature that would make Asset Exchange more useful
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Stable Nxt Client: Nxt 1.12.2

Author Topic: A relatively simple feature that would make Asset Exchange more useful  (Read 1883 times)

romanix

  • Jr. Member
  • **
  • Karma: +9/-0
  • Offline Offline
  • Posts: 35
    • View Profile

A relatively simple feature that would make Asset Exchange more useful:

If it was possible to add arbitrary key - value tuples that would be very useful -- even without any NXT logic related to these data.

e.g.
Asset Class = <enum value>
Termsheet = <URL>
ISIN = <ISIN>
and so on ...

Without that there is only the description field :(


Logged

NxtSwe

  • Hero Member
  • *****
  • Karma: +124/-9
  • Offline Offline
  • Posts: 657
    • View Profile

Neat idea.

One way is to add this as a core feature, with a new transaction type, where you can attach properties to an asset.
This would require a bit of core dev's work and a hard fork.

Another way would be to use the setAccountProperty api, where you could set a property to the issuer account and have the key set to the assetid_propertyname, where _ is a separator character.
The advantages would be that it would not require any hard fork and it could easily be done as a plugin as well, sparing the core devs all the trouble.
The disadvantages would be that the propertyname in setAccountProperty is limited to 32 chars, and the asset id would take up 19 of them + separator, leaving only 12 chars left for the actual propertyname on the asset.
Logged
Check out the NxtLib, the .NET Framework API for the Nxt platform.

romanix

  • Jr. Member
  • **
  • Karma: +9/-0
  • Offline Offline
  • Posts: 35
    • View Profile

Hi NxtSwe,

Thanks for this explanation.

Frankly, I didn't understand how the approach based on the NXT plugin and property account would work. Nevertheless, it's unlikely that I'll implement such a plugin. The hurdle to convince somebody to install NXT NRS is already high enough ... even without the trouble of locating, downloading and installing a plugin.
Logged

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +440/-42
  • Offline Offline
  • Posts: 1796
    • View Profile

The hurdle to convince somebody to install NXT NRS is already high enough ...

Just curious why is it so difficult to install NXT ?
After all we do have a digitally signed point and click installer now for every platform and if you are impatient you can download the blockchain from peer explorer.

I agree with NxtSwe that the account properties of the asset issuer account is a good place to store such data.
Adding free text properties directly to transactions is another use case we do not support at the moment. Not sure if it's important enough.
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

romanix

  • Jr. Member
  • **
  • Karma: +9/-0
  • Offline Offline
  • Posts: 35
    • View Profile

The hurdle to convince somebody to install NXT NRS is already high enough ...

Just curious why is it so difficult to install NXT ?
After all we do have a digitally signed point and click installer now for every platform and if you are impatient you can download the blockchain from peer explorer.

I agree with NxtSwe that the account properties of the asset issuer account is a good place to store such data.
Adding free text properties directly to transactions is another use case we do not support at the moment. Not sure if it's important enough.

Hi Riker,

1) I was not aware about the "point and click installier" - I always download, unzip, unpack the new version.
2) It's not so much about the technical difficulty -- it's about convincing somebody to go and try it out.

Logged
 

elective-stereophonic
elective-stereophonic
assembly
assembly