I will.

And I have had an idea:

The Nxt wiki keeps ALL of history, so it is possible to go back to the API wikidocumentation of the Nxt version from which NHZ was forked.
That should help a lot (minus possible errors that were only found out later, but that is probably less of a problem?).


Thanks.
That is helpful to know, in general.
1.2.9 good to know (Nxt is at 1.4.16 now BTW).


Unfortunately the Nxt API wikipage has started to mention the version number only recently.
But perhaps one of you who knows NHZ history better, an can pinpoint a good history snapshot?

My best guess (as NHZ thread was started October 14, 2014, 08:25:18 PM) is around here:
--> http://wiki.nxtcrypto.org/w/index.php?title=Nxt_API&oldid=29356 <--

HZXchange asset price is going up, time to hold i think and to take some more before price will be high or to take some if you dont have any and want something that can be big.

We are currently at arround 40 to 43 horizon for one hzxchange asset and  there are only 1 000 000 assets created.

Im keeping mine, really want to see what will happen with it next weeks months but i think its a good good investment

Alright, we got the strange characters in some of the other languages on the wallet, the asset exchange bug with the overlay issue, and cramped text on some versions of the wallet. Anything else?

And the advanced options menu only opening on the first log in, and if you close it, it doesn't open it again and you need to restart the client to gain access to it when making a transaction.

What is the best way to list all transfers of an asset?

I am parsing the NHZ asset markets, and whenever an inconsistency shows up, there is usually a bug in my code. Which I then fix, and all is cool. This time, however, I didn't understand it - at first. Then I realized, there is probably an important API function missing? Please follow my train of thought ...

What made me wonder: The asset 4033048123059509069 (HZSPHERE) got issued, then there were numberOfTrades=0, but now the issuerAccount (6108610928966611972) has no HZSPHERE assets left. It is the only asset with this results.

Thinking deeper I realized, the assets might have been not traded, but 'transferred'. And yes, after manual digging in "getAccountTransactions" http://localhost:7776/nhz?requestType=getAccountTransactions&account=6108610928966611972 I find 6 tx, one AssetIssuance of 15000000, and 5 tx of
13956751
364655
44445
2000
632149
... which miraculously :-) add up to ... 15000000

The 5 are of
 type: 2     ("Colored coins")
 subtype: 1  ("Asset transfer")
(in brackets what 'getConstants' told me - http://localhost:7776/nhz?requestType=getConstants )

So YEAH: My original riddle is solved.

BUT the way to the goal is too far, IMHO.

getTrades does not help, it results in [] http://localhost:7776/nhz?requestType=getTrades&asset=4033048123059509069
getTransfers (my own invention ) results in "Incorrect request" http://localhost:7776/nhz?requestType=getTransfers&asset=4033048123059509069

What is the best way to list all transfers of an asset in HZ?


Thanks a lot!
:-)

It'll usually warn you that you are sending over 100k, you just click submit again after that.

i cannot get anything through port 7776 and my ISP provider blocks no ports.  ideas?

edit:  i just discovered that my modem has some uncorrected errors.  signal's good, tho my upstream's a little hot.  i'll get another tomorrow.

localhost = 127.0.0.1 is a "loopback network interface" of the computer to itself. Not related to your modem. Not to any hardware really - you can unplug all internet cables, and 127.0.01 will still work.

Step 1: download the HZ software
Step 2: run.bat (Windows) or run.sh (Linux/ (mac?) )
Step 3: Waiting, long. The HZ-backend has to crawl through all the already downloaded HZ blocks of the blockchain on your harddisk first: "Scanning blockchain..." ... until "Nhz server NHZ V3.8 started successfully."
Step 4: http://localhost:7776/ in your browser ... will then open a HZ frontend.


Then the page http://localhost:7776/test gives this amazing list of commands to interact with the HZ backend,
and all the other http://localhost:7776/nhz?requestType=... links that we have posted ... will give you cool insights into the HZ blockchain.

HTH
:-)

We don't give exact dates. It's been worked on.

... Until your upgrade ... I need to build my own workaround, to find the "sender" of a trade.


I guess the only way to find out would be while reading all trades, then also reading all mentioned ASK orders, right?
(Do I understand correctly? the AskOrder is published by the 'sender' of the ASSET? So the original ASSET owner was the one who put the AskOrder, and when the trade happens he gets HZ and gives away some of his ASSET? Or is that called the Bid?)

{"trades": [{
...
          "askOrder":    "ASK",
          "bidOrder":     "BID"
...}]}

Here is an example with only 6 trades: http://localhost:7776/nhz?requestType=getTrades&asset=14524494726253439285
and -as far as I understand it- all assets in those 6 trades originate from the same askOrder:

askOrder: "13535374938540622495"

Now I can get http://localhost:7776/nhz?requestType=getAskOrder&order=13535374938540622495

{
quantityQNT: "99999974"
priceNQT: "10000000"
accountRS: "NHZ-Y3AL-KLCC-UWLQ-4VCCS"
asset: "14524494726253439285"
type: "ask"
account: "3182175271062013202"
order: "13535374938540622495"
height: 156318
}

and find the 'sender' as 'account' here?

The "sender" of this transaction was "3182175271062013202" - right?


Thanks a million!

And sorry that I have to ask so many questions. But I think what I am building will be useful not only for myself ... and I want to be sure to make few mistakes.