Analytical tool for operators and stakeholders.
Provides an opportunity to observe and analyze the life cycle of a node.
Bandwidth changes, delegate movements, rewards, updates, and more.
Budget: 260.000 NYM
Squad: @craftdome, @bumpmeup
Tech stack:
Frontend: HTML, CSS, Vue.JS
Backend: Go
Database: Clickhouse
Roadmap:
| Milestone | Duration | Description |
| 1 | 6 weeks | Move the clickhouse database to the cloud (fault tolerance). Configure CI/CD. Buy a domain name. Setting up the project to the prod-server. Choose a VPS provider. Pushing the Vue.JS project to Github repo. Deploy the website on github.io. |
| 2 | 6 weeks | - Selecting, testing and purchasing of a Vue.JS template. - Implementing infographics on specialized frameworks. - Developing of the GoLang library for obtaining information directly from the nyx chain. - Integrating of the library with Fetcher Service to stabilize the collection of information from mixnet, which will completely eliminate possible data loss. |
| 3 | 12 weeks | - Fetcher Service improvements: - Collecting information when an epoch changes; - Identification of errors from the nym-node api to avoid repeated requests (e.g., the 403 response status to expose_system_info=false ). - Refinement of the database architecture. - Development of mixnet analytics: - Node profit statistics, enriched statistics with knowledge about node events; - Index of node relevance; - Node update statistics; - Operator engagement index; - The history of selecting a node into the rewarded set. - Development of swagger docs for the analytics API. - Development of UI/UX website design and architecture: - Network map with search and sorting by fields; - Creating a node card (summary/brief info); - Development of infographic components; - The nym network summary page. - Development of unit and integration tests. |
Analytics:
1. ** Node profit statistics
How much the node earned during the selected period, broken down by day, enriched by node events on the same dates.
| Event | Description |
on_version_change |
Changing the node build version |
on_profit_margin_change |
Changing the node profit margin |
on_operating_cost_change |
Changing the node operating cost |
on_[mixnode/entry/exit]_role_change |
Changing the node declared roles |
on_delegations_change |
Changing the node delegations |
on_bond_change |
Changing the node original pledge |
on_delegations_count_change |
Changing the node unique delegations |
The statistics are supplemented with the current values of the node parameters.
| Param | Description |
config_score |
Coefficient of the node’s relevance and correct configuration |
performance |
Quality parameter of the packet routing |
tac |
Accepted operator terms and conditions |
2. Node Relevance Index
Determines the average duration to update the node to the latest build version.
3. * Operator Engagement Index
Determines the average duration to update nodes (50/120/70) of the mixnet to the latest build version.
4. Top Node Versions
Determines the frequency of build versions in the mixnet.
5. Rewarded Set History
Percentage of node selection to rewarded set per day, which calculated as
countIf(rewarded_set = true)/24.
6. Node Delegate Share
Includes the percentage of the delegate share in relation to the total delegations.
Draft version:
https://nymesis.vercel.app/
