-
Notifications
You must be signed in to change notification settings - Fork 643
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
get_account_history in API-0 without login. #105
Comments
requested in: bitshares#105 i tried first to move the original get_account_history function from the history api to the database api but i had errors in the wallet.cpp so i decided to make a new call. not sure if this is the way to go or either the name but function is there and it works just as get_account_history.
Commit adds a new function get_account_history_public to the database unprotected api. Not sure if the name will be accepted but the working is ok: alfredo@graphene: |
related: |
thanks @xeroc. i think #223 made by @elmato cover the subject of this issue the request here was to make a function get_account_history available from api-0. whatever is the case, the pint is @elmato pull will allow to call by curl to any authenticated function of the api, a lot better. if someone need yes or yes the function get_account_history in api-0 we can get back to this but as the original question was in 2015 i doubt it. |
From @jabbabts on October 22, 2015 18:39
It would be very useful if possible, to make get_account_history available over the stateless API-0 RPC.
That way, merchants could check for new transaction over public trusted websockets/api with curl php for example.
Copied from original issue: cryptonomex/graphene#391
The text was updated successfully, but these errors were encountered: