Watching a new address

[zomglings]

When a user watches a new address, we provide different functionality depending on whether:

1. The address can be an externally owned account (EOA)
2. The address is a smart contract on a chain that we support

This requires us to:

• [ ] Disclose the chains that we support via an API endpoint
• [x] Add an API endpoint which checks if an address is a smart contract (using eth_getCode) on any of our supported chains - if so, it should return a list of the chains on which eth_getCode has a non-trivial response.
• [x] If the address is a smart contract on a given chain, check supportsInterface on that contract using standard interfaces (IERC20, IERC721, IERC721Metadata, IERC721Enumerable, IERC1155, IERC165, etc.). There should be an API endpoint which returns the supported interfaces for a contract on a given chain. If an address is provided which is not a smart contract address on that chain, we should return an error from the API.
• [ ] API endpoints which expose the admin user queries publicly, along with whether they apply to smart contracts or EOAs. If they apply to smart contracts, we should also specify the interfaces they apply to (if any). This endpoint should allow search (can use Bugout - public journal).
• [x] An API endpoint which shows the status of historical crawl for a given subscription. It should be detailed enough to tell us if the crawl is in progress, is completed, or if it ended in an error. Progress bar stretch goal.
• [ ] Users should be able to add tags to subscriptions.
• [x] Users should be able to search for queries (among admin user queries/query templates) and add them explicitly to their subscriptions if they want. This will be useful if a smart contract either doesn't implement supportsInterface or implements it incorrectly.
• [x] Every subscription should have generic events and method_calls queries by default. (This can be implemented on the frontend.)

We need to add the following queries for EOAs (each query should be possible to run on every supported blockchain):

• [x] Transactions in/out (with start_timestamp, end_timestamp)
• [x] Favorite contracts (with start_timestamp, end_timestamp)
• [x] Deployed contracts (with start_timestamp, end_timestamp)

Default values: start_timestamp = 0, end_timestamp = int(time.time()). This can be implemented on frontend.

Decisions

1. We will not display query results in v2.0.0 frontend. We will only provide users with a download link for a JSON file.
2. We will not provide information about public contracts (e.g. Open Sea, Uniswap) in v2.0.0. This is a feature we will add in a future version of Moonstream Analytics. The purpose of this feature will be to improve the onboarding experience for users.

[zomglings]

@Anton-Mushnin : Default values for timestamps -- let us make it end_timestamp = int(time.time()) and start_timestamp = end_timestamp - (1 month).

[Andrei-Dolgolev]

Partially covered need add small fixes for missing parts.

PR for tags and descriptions: https://github.com/moonstream-to/api/pull/826 we in review process.

Tempalte endpoint for smart contracts or EOAs. Will comunicate with @Anton-Mushnin for deside correct tags structure for split SC and EOA.

Disclose the chains that we support via an API endpoint missing in current moment.