-
Notifications
You must be signed in to change notification settings - Fork 648
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
api: obtain an account's history for a specific asset and operation #413
Comments
similar to what was requested initially here: #358 i had made the api call to get history by date several using different approaches, the last can be found at: #405 but it has been hard to get developer community approbation to include it. i will have no problem on make the exact call you need but the approach in bitshares is more generic and it will not include new calls that can be made by other ways. in your case you can use the last proposition i made to include if i get enough support for that i will be happy to make your calls, i have the conviction that more api calls is better but other devs think the opposite so is hard to get consensus. |
@derofim: technically this is not hard to implement. Just make a new plugin by copying the |
@derofim if you want to hold a bit i am working on a plugin that will move history into a database(elasticsearch). plugin purpose is to reduce ram while having all the history available and also be a general solution for this and other relational issues that are hard to do right now. stay tuned, i'll update on this on the next days. |
I guess it can be done with ES now. Won't implement it in core. |
Absolutely. The following is the transfers the committee-account made in the last 90 days where the asset was USD: |
Can we please have a call that returns asset activity history for account.
Example:
where:
start, stop, limit are for pagination
account_id identifies an account
asset_id identifies an asset
operation_id filters the account history for only operations of this paticular type (e.g. transfer, limit_order_create but also virtual operations like order_filled)
The text was updated successfully, but these errors were encountered: