robcxyz
commented
1 year ago I like the CSV export tool idea and think we should basically change all the APIs to respond to both application/json and application/csv heades for content type. Then on each table putting an icon to export to csv. Been thinking about this for a while.
Additionally, I really like the export functionality idea as a page. This could potentially be a query tool though that allows users to run different queries that aren't normally exposed. For instance a user wants to view / export a list of transactions from and to a specific addresses. This is not possible now without hitting the API directly. So perhaps building this page along with the export functionality would handle this feature request?
Generic queries would cover:
- Blocks
- block producer / number of transactions / logs / token transfers
- Transactions
- to / from address + amount + num logs
- Internal transactions
- to / from address + amount + num logs
- Logs
- to / from address
- Token Transfers
- ....
Basically make a UI to easily change a form that would be used to build a query. All the parameters are already built so it is mostly a UI challenge at this point.
There should be some set of tools that are useful for common operations. One such common operation is monitoring BTP transactions. This can simply be a link to the external site https://testnet.btp2.24x365.online/ .
For example, Etherscan has these tools https://etherscan.io/exportData . Note that the link directs to the "CSV Export" tool because there is no homepage for their tools and this is the first on the list in the left hand column.