ambiretech / adex-explorer Goto Github PK

and implement the v0.1 design (#7)

take this directly from the core, using ethers.js and the default provider

it can be a background of the card itself; basically, visualize the 24 hour volume - we've got ~100 different data points, so all we have to do is establish min/max from those points, and convert each one to a ratio between 0 and 1000 (relative to min/max)

e.g. "N minutes ago", "N hours ago" and normal "13:03 03/03/2019"; when you hover, it should show the full date

which will allow us to also show

• last heartbeat
• status

the balance/volume/impressions cards can have a separate visual loading state

related to #3

the idea of this task is to make something mostly for internal usage; it won't be especially useful for publishers/advertisers we want to attract (but this is a long term goal of the explorer)

Feature subset:

• market - view all campaigns on the market, with their status, total budget, last updated, deposit in USD
• channel view - show ad units, latest Accounting, latest heartbeat time, chart of impressions in last {hour, day, week}; and on-chain status/withdrawn; possibly validators and claimed fees by the validators; and daily impressions
• validator view - show all channels from a certain validator; show all validators, basic info from the spec (minPerImpression, maxPerImpression), deposit in native currency; to enter this view, you could select from hardcoded validators in the sidebar (Tom & Jerry)

and additionally some summaries:

• total earned funds from all campaigns (including Expired)
• total impression estimation* from all campaigns (including Expired); the estimation only works when we're paying out minPerImpression and dynamic bidding is not enabled
• total funds on active campaigns
• count of ad units
• count of unique advertisers
• total DAI locked up on the SC

for a full list of ideas/discussion, see: https://github.com/AdExNetwork/organization/issues/22

Is your feature request related to a problem? Please describe.
On the advertisers page the very first button is sending users to the AdEx Explorer. This is nice, but since we are going to use the Advertisers page as a landing page, we would like the end destination for leads to be the platform. So we need to send them to the platform after they have seen the Explorer.

Describe the solution you'd like
Add a blue button saying "Go to Platform" in the AdEx Explorer

Additional context
The easies implementation:

When we launch the platform, we can use the images Ally created for the website:

requires that it's implemented in the market (/campaigns?depositAsset=...)

Make it work with this: AmbireTech/adex-validator#201

e.g. like https://github.com/SpankChain/uniprice

blocked by #6

total volume and CPM

Explorer enhancements that will make our lives much easier:

1. Introduce a new campaign status - "Closed"
Currently, campaigns closed by advertisers show as exhausted and 100% spent. It will be better to have a status showing the actual spent % and have the campaign status as Closed.

2. Add a field showing the account ID/email of the account running the ad
This will help us easily locate advertisers and cross-reference active campaigns for the purpose of monitoring/customer support.

implement a side navigation bar
create vector icons for Tom and Jerry so we have a quick shortcut to those two validators

gh-pages will be used to host the explorer

this requires the ability to get those from the market:

• connect publisher adderesses to ad slots to show who they are (if they've allowed that)
• or just show all ad slots separately

Challenge description:

NOTE: This challenge requires medium familiarity with Rust

We need to update to the latest published version of seed-rs: https://seed-rs.org/changelog

The biggest change we care about is being able to handle failures on deserializing JSON; right now, seed will just panic on failures

Case in point, when there's a parsing error, the app panics:

panicked at 'Error deserializing JSON: Error("missing field `aggrs`", line: 1, column: 6383)', src/libcore/result.rs:1051:5

Updating would require:

• router function taking an owned URL
• adapting to changes to the fetch API; the fetch API is totally different, so it would require changing the msgs

Submission requirements:

• the Explorer compiles and works with the latest seed v0.3.7 or later (it's a very simple UI, so "works" is easy to verify)

Judging criteria:

• First to submit a working submission that meets our quality standards/criteria

Submission deadline:

August 19

Bounty:

400 DAI

currently this UI is structured as a table, but it can still be prettified a bit