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
Copy file name to clipboardExpand all lines: README.md
-3Lines changed: 0 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,18 +35,15 @@ Complete details can be found in the
35
35
|[subvt-metrics](./subvt-metrics)| Common crate that contains Prometheus helper functions. Used by all other crates that export Prometheus metrics data. |
36
36
|[subvt-network-status-server](./subvt-network-status-server)| Publishes the network status data prepared by the network status updater through WS RPC. |
37
37
|[subvt-network-status-updater](./subvt-network-status-updater)| Fetches the network status data from the Substrate node after each finalized block and stores it in the Redis instance. |
38
-
|[subvt-nft](./subvt-nft)| Contains the functions to fetch NFT records for a stash account using the [sub.id](https://sub.id) public API. |
39
38
|[subvt-nofification-generator](./subvt-notification-generator)| Processes the indexed block (PostgreSQL), validator list (Redis) and Telemetry time-series (TimescaleDB) data for possible notifications, and persists notifications according to the previously-defined notification rules. |
40
39
|[subvt-notification-processor](./subvt-notification-processor)| Processes and sends the notifications persisted by the notification generator. |
41
-
|[subvt-onekv-updater](./subvt-onekv-updater)| Fetches the complete candidate data from the 1KV backend (only Polkadot or Kusama) in regular intervals, and Stores the candidate and all related data (ranking events, score, etc.) in the PostgreSQL network database. |
42
40
|[subvt-persistence](./subvt-persistence)| Complete persistence logic for PostgreSQL and Redis (TBD). Contains the full migrations for the network and application PostgreSQL databases. |
43
41
|[subvt-plotter](./subvt-plotter)| Used for server-side generation of report charts. Currently used by the Telegram bot to deliver rewards and payouts reports. |
|[subvt-report-service](./subvt-report-service)| Era and validator report REST service. OpenAPI YAML specification document [here](./subvt-report-service/open-api-spec/subvt_report_service.yml), viewable [here](https://helikon-labs.stoplight.io/docs/subvt/YXBpOjM0Mjg0NzAw-sub-vt-application-service). ||
46
44
|[subvt-service-common](./subvt-service-common)| Contains the service trait implemented by all SubVT services. |
47
45
|[subvt-substrate-client](./subvt-substrate-client)| Facilitates all of the communication between SubVT and Substrate node RPC interfaces. |
48
46
|[subvt-telegram-bot](./subvt-telegram-bot)| SubVT Telegram bot, currently live for Kusama and Polkadot. View its readme for details. |
49
-
|[subvt-telemetry-processor](./subvt-telemetry-processor)| Subscribes to the chain's feed on a Telemetry server, and persists the node data into the TimescaleDB instance for later analysis. |
|[subvt-utility](./subvt-utility)| Basic utility functions. Not used a lot at the moment, but more a place for later work. |
52
49
|[subvt-validator-details-server](./subvt-validator-details-server)| Publishes a validator's details through a WS RPC channel. Subscriber send the account id of the validator at the initial connection, receives the full validator data as the first response, then only the changes with the new finalized blocks. |
0 commit comments