I'm having some trouble with the secretPhrase parameter. How should parameters be encoded?
I'm using UTF-8 and URL encoding so, e.g. the secret öäü (german umlaut characters) would be öäü in UTF-8 and that would be urlencoded to %C3%83%C2%B6%C3%83%C2%A4%C3%83%C2%BC resulting in:
http://..../nxt?requestType=sendMoney&secretPhrase=%C3%83%C2%B6%C3%83%C2%A4%C3%83%C2%BC&recipient=...
Anything wrong with that?
Topic: [Nxt] API of Nxt - page 9. (Read 37336 times)
Given a transaction, what is the best way to know if that transaction is related to an ALIAS or AM?
"subtype"
Is the AM subtype = 2?
= 0
PS: type = 1
So is this right:
Regular Tx: type=type=0, subtype=0
Alias Tx: type= type=1, subtype=1
AM Tx: type=1, subtype=0
Yes, http://localhost:7874/nxt?requestType=getConstants gives description.
Given a transaction, what is the best way to know if that transaction is related to an ALIAS or AM?
"subtype"
Is the AM subtype = 2?
= 0
PS: type = 1
So is this right:
Regular Tx: type=type=0, subtype=0
Alias Tx: type= type=1, subtype=1
AM Tx: type=1, subtype=0
Given a transaction, what is the best way to know if that transaction is related to an ALIAS or AM?
"subtype"
Is the AM subtype = 2?
= 0
PS: type = 1
Given a transaction, what is the best way to know if that transaction is related to an ALIAS or AM?
"subtype"
Is the AM subtype = 2?
Given a transaction, what is the best way to know if that transaction is related to an ALIAS or AM?
"subtype"
Given a transaction, what is the best way to know if that transaction is related to an ALIAS or AM?
Is there a way to get a list of all the accounts?
Thanks!
Thanks!
Yes, this can be done via blockchain scanning.
Let me know if u need a special API call for that.
I'd definitely like an API call that would return all accounts. For blockchain scanning, what is the process to get all accounts? A quick look at blocks.nxt (12MB) shows only ~300 unique generatorPublicKey's, and transactions.nxt (also 12MB) has about ~3500 unique accounts. The blockchain explorer says "Accounts: 13919" and lists lots of new accounts being added though.
Get a unique list of the recipients of all transactions of all blocks.
Is there a way to get a list of all the accounts?
Thanks!
Thanks!
Yes, this can be done via blockchain scanning.
Let me know if u need a special API call for that.
I'd definitely like an API call that would return all accounts. For blockchain scanning, what is the process to get all accounts? A quick look at blocks.nxt (12MB) shows only ~300 unique generatorPublicKey's, and transactions.nxt (also 12MB) has about ~3500 unique accounts. The blockchain explorer says "Accounts: 13919" and lists lots of new accounts being added though.
Can the number of transaction confirmations only change when there is a new block? Or can it change "between blocks"?
Only new blocks or chain reorgs can change the number.
Can the number of transaction confirmations only change when there is a new block? Or can it change "between blocks"?
I'm posting this here again, since I would really like to have this implemented in the v1 API in one of the next NRS versions and not wait until v2 of the API.
What takes most of the time is when my client updates from NRS is getting the updated confirmation counts for transactions with less than 720 confirmations, because there are lots of back and forth calls since you have to call getTransaction again and again over a lot of transactions.
Would be nice to have some kind of batch mode, so e.g. send me all confirmations counts for all transactions that are in block x. Or block x to y. Or block x,y,z, etc. with just one request.
What takes most of the time is when my client updates from NRS is getting the updated confirmation counts for transactions with less than 720 confirmations, because there are lots of back and forth calls since you have to call getTransaction again and again over a lot of transactions.
Would be nice to have some kind of batch mode, so e.g. send me all confirmations counts for all transactions that are in block x. Or block x to y. Or block x,y,z, etc. with just one request.
What would be a good approach to cleanup orphan blocks and their transactions on the client side?
Right now, I would make a list of all blocks, then walk down the chain from the highest block and remove these blocks in the chain from my list.
The remaining blocks in the list would be the orphan blocks and would need to be deleted.
Is there a better approach? Like is there or could there been an API call that would return all block ids that NRS knows are orphans?
Right now, I would make a list of all blocks, then walk down the chain from the highest block and remove these blocks in the chain from my list.
The remaining blocks in the list would be the orphan blocks and would need to be deleted.
Is there a better approach? Like is there or could there been an API call that would return all block ids that NRS knows are orphans?
Post this idea in that new thread plz.
What would be a good approach to cleanup orphan blocks and their transactions on the client side?
Right now, I would make a list of all blocks, then walk down the chain from the highest block and remove these blocks in the chain from my list.
The remaining blocks in the list would be the orphan blocks and would need to be deleted.
Is there a better approach? Like is there or could there been an API call that would return all block ids that NRS knows are orphans?
Right now, I would make a list of all blocks, then walk down the chain from the highest block and remove these blocks in the chain from my list.
The remaining blocks in the list would be the orphan blocks and would need to be deleted.
Is there a better approach? Like is there or could there been an API call that would return all block ids that NRS knows are orphans?
What's the ETA for these new APIs?
Depends on how fast client devs decide what they need and how this should look.
We r planning to create other API. Old API will be called Legacy API and become obsolete. New API will be split to 2 parts - Low-level API and High-level API. If u r planning to write a client software u could start a thread to discuss what LL and HL API calls u need.
https://bitcointalksearch.org/topic/nxt-api-2-brainstorming-406839
-remove a peer
-handle block generation
-generate tokens
-handle block generation
-generate tokens
We r planning to create other API. Old API will be called Legacy API and become obsolete. New API will be split to 2 parts - Low-level API and High-level API. If u r planning to write a client software u could start a thread to discuss what LL and HL API calls u need.
What's the ETA for these new APIs?
-remove a peer
-handle block generation
-generate tokens
-handle block generation
-generate tokens
We r planning to create other API. Old API will be called Legacy API and become obsolete. New API will be split to 2 parts - Low-level API and High-level API. If u r planning to write a client software u could start a thread to discuss what LL and HL API calls u need.
NRS = Nxt Reference Software, it's the whitepaper written in Java.
It has 2 parts - server (as a Java servlet) and client (as HTML-files).
What do you call the parts of the Servlet that support the HTML like getInitialData, unLockAccount, etc?
I see 3 parts really: NRS, Client Servlet, and Client HTML.
Client HTTP requests.
Is there a plan for NRS APIs that handle these things?
-remove a peer
-handle block generation
-generate tokens
NRS = Nxt Reference Software, it's the whitepaper written in Java.
It has 2 parts - server (as a Java servlet) and client (as HTML-files).
What do you call the parts of the Servlet that support the HTML like getInitialData, unLockAccount, etc?
I see 3 parts really: NRS, Client Servlet, and Client HTML.
Client HTTP requests.
Jump to: