Zeekoe Dashboard

[yaymukund]

Update: Notes from discussion w @jakinyele

There are three big goals of this project:

1. Analytics - List channels, see starting balance, closing balances if closed, see counts of total balances / number of channels.
2. Management - Closing channels, maybe used by merchant customer service teams.
3. Administration - Changing the description or URL of the merchant, maybe seeing uptime. We have to be careful not to expose footguns - e.g. we probably don't want people changing the IP, certs, or things like that.

For an MVP, we should expose what analytics we already have in the database.

---

(Original description of the ticket:)

Technically, zeekoe would produce some JSON (using the JSON interface from #116 ?) which would be fed into some static web application that exists in a separate repository.

[marsella]

Note that the database currently doesn't save final balances when a channel closes (although the places and amounts that will need to be saved are noted in comments in zeekoe). I think this is the main project we'll need them for, so noting it here.

EDIT 1/10/22: the database holds closing balances as of #179