Complete work on eth-event-viewer

[dominic22]

See requirements of the bounty here:
https://grants.urbit.org/bounties/831044524-display-eth-data

[Fang-]

This certainly fulfills the bounty! But that's not what I'm here for. I'm here for the strict code review. (;

I tried and review the hoon here pretty thoroughly. Only really skimmed the js, but didn't see anything too crazy there. Let me know if there's anything specific there you want feedback on, and I can take a look.

Usability things:

I know we've already spent some time talking about eth-watchers idiosyncrasies. Arguably it needs a "release after x blocks" parameter. Until that's fixed, we'll just have to live with the slightly-slower release.

Would be nice if this also read from the data.event-log field and rendered those in the event lists too. It already loads in full event signatures, so should be able to do that, right?

The hardcoded "from" block should probably change. Suggestion: on the backend, just take in a block number alongside the contract address/config. On the frontend, render a slider, or numerical input or w/e, for selecting between "starting now", "from last week", etc, "from contract creation". I think it can get the contract creation date & current block number from the Etherscan API, right? Actually, all API calls here go through the backend, it seems? Probably wouldn't want to add frontend-side calls just for that...

General code things:

The order of the arms in your app core is kinda unconventional. Generally best to group the lifecycle ones (init, save, load) together at the top, then follow with request (poke, watch) and result (agent, arvo, fail) ones. That generally mimics execution orders/flows more tightly, making for a slightly comfier read-through. (But I'm probably making it sound like a bigger deal than it is.)

Also a bunch of comments below.

[dominic22]

@Fang- I've worked through your suggestions and also added the request of the block number, so the user does not have to insert it by himself. Furthermore the user is able to request the block number of the prev. week by clicking a button. I've also made the ui more robust, since the user can run into "Max rate limit reached, please use API Key for higher rate limit" when requesting the etherscan api too often in a short time period.

Please have another look at the app if it fits your expectations and please let me know if the bounty can be completed with my revised version. :)