Show Posts
1
Android App Support / Re: GoldCoin Wallet v4.x
« on: June 30, 2016, 08:43:52 AM »
I received Gregs E-mail and I am looking into adding an unspent function to the API on CCE.
The only major issue I can see (which is also an issue for ABE based explorers) is that it is a resource heavy database query.
An unspent function would work very much like a ledger request and would be written as a modified ledger function.
Right now the ledger request is the most resource intensive query (both API and WEB) as there is no way to efficiently calculate and store a ledger for every address.
Ledger requests are generated in real time and thus are limited to the last 100 credits/debits.
However, I am thinking that an unspent function could be lighter then a ledger request.
Exactly what information do you need from an unspent request? The ABE unspent function seems to send back some extraneous information. Would each unspent TX_IN hash and amount be all that you need?
Since this would be a resource heavy query, I would ask that you only use it when necessary and use other API functions when able. For example: Use the address balance function to get the total amount in an address. This is updated and stored every block update so it is a fast light query as it does not have to search the entire database/table(s) or preform multiple comparisons/calculations.
The only major issue I can see (which is also an issue for ABE based explorers) is that it is a resource heavy database query.
An unspent function would work very much like a ledger request and would be written as a modified ledger function.
Right now the ledger request is the most resource intensive query (both API and WEB) as there is no way to efficiently calculate and store a ledger for every address.
Ledger requests are generated in real time and thus are limited to the last 100 credits/debits.
However, I am thinking that an unspent function could be lighter then a ledger request.
Exactly what information do you need from an unspent request? The ABE unspent function seems to send back some extraneous information. Would each unspent TX_IN hash and amount be all that you need?
Since this would be a resource heavy query, I would ask that you only use it when necessary and use other API functions when able. For example: Use the address balance function to get the total amount in an address. This is updated and stored every block update so it is a fast light query as it does not have to search the entire database/table(s) or preform multiple comparisons/calculations.
