Anything else?
Yes.
http://localhost:7776/test --> click javadoc --> HTTP ERROR: 404 Problem accessing /doc/nhz/http/.... Reason: Not Found
You have to create javadocs with javadoc.sh.
Topic: . - page 99. (Read 491737 times)
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.
I wasn't able to send more than 100k HZ in one transaction. When I tried, the whole client hung and I had to restart the node.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.
NHZ V3.8
It'll usually warn you that you are sending over 100k, you just click submit again after that.
Does HZ keep all the historical order data, anyways?
Or is the
nhz.trimDerivedTables=false
also an option in HZ ?
... like the
nxt.trimDerivedTables=false
is supposed to make the historical order data reappear?
I am asking because to access that historical order data is my workaround to get the 'sender' of a trade.
And I cannot find a nhz.trimDerivedTables in conf/nhz-default.properties
Or is the
nhz.trimDerivedTables=false
also an option in HZ ?
... like the
nxt.trimDerivedTables=false
is supposed to make the historical order data reappear?
I am asking because to access that historical order data is my workaround to get the 'sender' of a trade.
And I cannot find a nhz.trimDerivedTables in conf/nhz-default.properties
Update on next client update: We are just finishing up the last GUI bug fixes and the update will be released.
Cool. Looking forward to that!Perhaps it is still time for a last-second improvement?
I suggest a small GUI change that might help some newbs - because it improves the intuitive approach.
When starting a new NHZ account, what to do?
For a while I was a bit confused. This is what I originally did ... to get a new NHZ account:
(1) I invent my own password (*), and put it into "Your Horizon Passphrase",
(2) then press "click here to create a new horizon account"
(3) I write down the generated passphrase (##)
(4) I paste (##) into "IN ORDER TO BE SURE THAT YOU HAVE SAVED IT,..."
When
(5) I log out, and log back in, using (##) - then all is cool, I come back to the same NHZ address.
But when
(6) I log out, and log back in, using my own password (*), I end up with a completely different NHZ-... address.
Hmmm ... Why? What is my password (*) good for then?
(7) After a while then, I realized, that my Step (1) above was completely ignored
when I pressed the "click here to create a new horizon account".
*slap*my*forehead*with*my*hand* :-)
--> IMHO: The button "click here to create a new horizon account"
does not belong near to that "Your Horizon Passphrase" / "remember passphrase during session"
- and especially not together into a bright layout box.
Because now the layout suggests a causal connection.
I would also recommend the same for NXT (place the button elsewhere) - but it's less likely to be misunderstood as they have not also put a suggestive bright box around those two unrelated functions.
Idea: Place the "new horizon account" button somewhere else.
?Perhaps above the logo, perhaps at the top right of the page?
Update from HZxchange: "Finished the BTC code, the first test run (get deposit address, deposit, send to multisig-address, withdraw) was completed successfully. Next step is adapting that code for NXT and BTS, so the beta tests with the future partners can commence soon. "
Update on next client update: We are just finishing up the last GUI bug fixes and the update will be released.
Update on next client update: We are just finishing up the last GUI bug fixes and the update will be released.
Anything else?
Yes.
http://localhost:7776/test --> click javadoc --> HTTP ERROR: 404 Problem accessing /doc/nhz/http/.... Reason: Not Found
A seller has an asset and asks for a price with an AskOrder.
A buyer wants to buy an asset and bid a price with a BidOrder.
If a sale occurs then the asset of the seller is transferred to the buyer.
Thanks a lot for clearing that up. Then I can try to implement my question now.A buyer wants to buy an asset and bid a price with a BidOrder.
If a sale occurs then the asset of the seller is transferred to the buyer.
All your guesses are correct, except:
*Hahaha* I love your style.Or is that called the Bid?
... 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.
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.
A seller has an asset and asks for a price with an AskOrder.
A buyer wants to buy an asset and bid a price with a BidOrder.
If a sale occurs then the asset of the seller is transferred to the buyer.
All your guesses are correct, except:
Or is that called the Bid?
... 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.
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.
What is the best way to list all transfers of an asset?
[...]
Currently there is no better way. Next major release will include new API call 'GetAssetTransfers'.[...]
Is there an ETA for the next major release?
It's been worked on.
Nice!And I am curious: Will HZ jump all the way to the current NXT version (from 1.2.9 to 1.4.16), or will the HZ fork go down a different path?
If you choose the first path, then this hope is answered implicitly:
Please include the new 'getTrades' function because the answer contains 'sender'.
In the old HZ that is not part of the answer ...
What is the best way to list all transfers of an asset?
[...]
Currently there is no better way. Next major release will include new API call 'GetAssetTransfers'.[...]
Is there an ETA for the next major release?
And I am curious: Will HZ jump all the way to the current NXT version (from 1.2.9 to 1.4.16), or will the HZ fork go down a different path?
We don't give exact dates. It's been worked on.
What is the best way to list all transfers of an asset?
[...]
Currently there is no better way. Next major release will include new API call 'GetAssetTransfers'.[...]
Is there an ETA for the next major release?
And I am curious: Will HZ jump all the way to the current NXT version (from 1.2.9 to 1.4.16), or will the HZ fork go down a different path?
Where can I find the complete manual of HZ requestTypes?
Thanks!
The list of request types can be found here: http://localhost:7776/testThanks!
getAccountAssets is not on the list.
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
:-)
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=4033048123059509069What is the best way to list all transfers of an asset in HZ?
Thanks a lot!
:-)
Currently there is no better way. Next major release will include new API call 'GetAssetTransfers'.
Where can I find the complete manual of HZ requestTypes?
Thanks!
Thanks!
The list of request types can be found here:
http://localhost:7776/test
getAccountAssets is not on the list.
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.
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.
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.
is there any reason all assets could be listed with links to what they are on the exchange platform? For instance, like the alt coins are listed on POLO?.. you have a choice to display ALL, 10, 20, 30 etc?
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.
I wasn't able to send more than 100k HZ in one transaction. When I tried, the whole client hung and I had to restart the node.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.
NHZ V3.8
It'll usually warn you that you are sending over 100k, you just click submit again after that.
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.
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.
A few days ago..
https://bitcointalksearch.org/topic/m.10751773
https://bitcointalksearch.org/topic/m.10754785
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=4033048123059509069What is the best way to list all transfers of an asset in HZ?
Thanks a lot!
:-)
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.
I wasn't able to send more than 100k HZ in one transaction. When I tried, the whole client hung and I had to restart the node.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.
NHZ V3.8
Jump to: