You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the liquidity taskforce, but also in general to understand product usage, we need the ability to measure router events
We want to be able to visualize this in both Connextscan and the Looker dashboards (fed by bigquery)
Impact
Allows us to measure liquidity provision and share rewards back fairly and transparently with the LTF
It's also critical for us to work with routers better over time and understand churn events
Proposed Solution
Log how much liquidity is added and removed with timestamps, for example
event type (add/remove)
amount
asset
chain
router
timestamp
Acceptance Criteria
From an end user perspective, the below criteria must be met to consider this done:
We can query against timestamped router events in SQL
Coinhippo can fetch this data to display in our connextscan UI
We can pull this data into our bigquery db in order to create new visualizations in Looker
We can build these visualizations in USD values to segment across routers/assets at scale (for example it's fine if we can join against USD prices somehow, but should confirm this)
The text was updated successfully, but these errors were encountered:
update connext subgraph. contracts emit all events for adding/removing liquidity, so we can add event handlers simply to the subgraph.
Add the decimal of the adopted asset. currently, we have only decimals of local assets, and it causes the issue for calculating USD volume on bigquery. ????
Add migration to db
Update cartographer poller to fetch add/remove events from subgraph and store to db
Unit tests
Redeploy the runtime subgraph to testnet prod and test
Problem
For the liquidity taskforce, but also in general to understand product usage, we need the ability to measure router events
We want to be able to visualize this in both Connextscan and the Looker dashboards (fed by bigquery)
Impact
Allows us to measure liquidity provision and share rewards back fairly and transparently with the LTF
It's also critical for us to work with routers better over time and understand churn events
Proposed Solution
Log how much liquidity is added and removed with timestamps, for example
Acceptance Criteria
From an end user perspective, the below criteria must be met to consider this done:
The text was updated successfully, but these errors were encountered: