Goal: Validator Monitoring
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- go
- Domain
- distributed-systems, observability
Research direction
Start by reviewing the CometBFT data-structures documentation and the dependency on kwil-db issue #995, then inspect the linked instrumentation and validator-monitoring issues (#573, #575, #583, and #584). Done requires defining whether this goal covers an API only, a metrics pipeline, visualization, or a combination of them.
Written by the indexing model from the issue text.
Description
Objective
Assess the participation of validators (node operators) in the network during normal operations.
Description
For example, a visual representation of this could be a graph showing how many blocks a day a certain operator was also supporting the network.
The mechanism includes a node's signature that gets validated, and then the indexer exposes its public key on block information after the consensus.
Probably, the internal cometBFT endpoint already supports that: https://github.com/cometbft/cometbft/blob/v0.38.x/spec/core/data_structures.md
Then, what is the easiest path to expose this data from the kwil indexer? Should we expose a node cometBFT API endpoint?
To Do
Define what is the scope of this goal:
- just providing API to get the data
- create the metrics consumption pipeline
- visualizing data
Problems
Blocked By
Instrumentation
- #573
- #575
Validator monitoring
- #583
- #584
- Dominant language
- Go
- Stars
- 7
- Forks
- 3
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 13
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from trufnetwork/node
-
trufnetwork/node#1435 · 1 assignee ·
-
trufnetwork/node#1429 · 2 comments · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
trufnetwork/node#1313 · 2 comments · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
trufnetwork/node#1200 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
trufnetwork/node#1190 ·
All issues in trufnetwork/node
Similar issues
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/bursa#904 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yanet-platform/ipfw-go#129 ·
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100